Skip to content

ADR 0040 step 2 — Bind journals to session lifetimes #4966

Open

Description

@thymikee

Make journal access depend on the lifetime that produced the events.

ADR 0040

Required behavior

  • Use a generated lifetime ID for new journal storage. Delete address-derived reads for new records.
  • Read session events through the admitted lifetime. Write request events to that lifetime after proof.
  • For a refusal before admission, write detached diagnostics with an opaque record ID. Use the presented lease verifier or an explicit unleased marker.
  • Preserve bounded retrieval with producer proof. When legacy owner proof is unknown, refuse remote retrieval.

Verification

Run case-variant and close/reopen cases on the journal path. Verify that each lifetime gets its own journal. Verify that a refused request writes nothing to another lifetime's journal and can read only its own diagnostics.

Related work

Use the journal alias work in #4949.

Depends on the admitted capability in step 1.

Activity

  1. apex-sentinel-staging commented on Nov 22, 2026

    @apex-sentinel-staging

    Apex Sentinel · Issue review

    Suggested label: feature

    The issue describes a planned enhancement for ADR 0040 step 2, including required journal lifetime binding, refusal diagnostics, retrieval proof, and verification cases, rather than a defect in current behavior. It is actionable because it provides concrete implementation and testing requirements, with dependencies noted.

    Possible duplicates

  2. thymikee commented on Nov 22, 2026

    @thymikee
    MemberAuthor

    When this step lands, amend the ADR that ADR 0040 (#4964) lists for it in its Amendments table, in the same PR. ADR 0040 does not edit those ADRs up front, because an ADR states the current truth and the code has not changed yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions