FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Dynamically enrolling editorial sessions into a room safely
Persisting the path from fresh-root ingestion to membership and stopping duplicate daily roots at admission
Purpose
Fresh roots started for each source needed a dynamic path into one logical room without disrupting normal conversation synchronization.
A retry that created a different root would conflict with the same source-and-day identity, so duplication had to stop before any remote delivery.
Implementation
Started and terminal records are collected from an owner-only secure spool, with the fresh root's format, working location, creation time, and parentage revalidated. After normal ingestion completes, a leased durable outbox sends logical-room membership and seals the record only after acknowledgement, with the sequence persisted in SQLite.
- Treat source ID and JST date as immutable identity and validate them at every persistence and delivery boundary.
- Allow only the first fresh root for a source and date, rejecting another root before it reaches the outbox.
- Retry only by rereading the same root records and resending the same durable outbox entry.
- Accept different sources on the same day and the same source on different days independently.
- Continue reading legacy pending records, payloads, hashes, and memberships without conversion.
A source that has not yet materialized is classified as a temporary prerequisite rather than a permanent failure, allowing retry under the same identity.
This shows the enrollment states and identity checks added in the primary Commit. Type annotations and several auxiliary comparisons are omitted in this public account.
Rendering diagram…
What was confirmed
Verification results
All 214 tests across 13 test files, type checks, the build, and diff consistency passed.
A different root for the same source and date was rejected before delivery when the first root was active, terminal-pending, or sealed.
Same-root rereads, different sources on one day, one source on different days, and continued scanning after rejection were verified.
Legacy nullable-source, raw-payload and hash, and multiple-roots-per-day behavior remained compatible.
Dynamic enrollment and membership delivery were applied to the target. Production process activation and an end-to-end round trip had not occurred by the cutoff.
Basis for completion
The work was complete when the secure spool, fresh-root revalidation, durable checkpoints and membership outbox, single-root admission, and legacy compatibility were implemented and all 214 tests covered success, contention, and retry paths.