Skip to content

ADR 0040 step 3 — Use the session visibility projection across daemon surfaces #4967

Open

Description

@thymikee

Use one visible-name projection for consumers that disclose session names.

ADR 0040

Required behavior

  • Use the shared visibility predicate from Share session visibility rules for public-network callers #4960. Route doctor, progress, and contention error builders through its projection.
  • Delete remaining response-specific name filters after the callers move. Preserve the local device-recovery exception.
  • When a caller lacks session proof, use detached evidence or a public contention reason as permitted by policy.

Verification

Exercise a shared-token caller without tenant isolation, a tenant-scoped caller, and a local device-recovery caller. Verify the same visibility outcome across listing, progress, and contention.

Related work

Depends on the shared predicate in #4960. Keep its existing listing and reply coverage.

Activity

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

    @apex-sentinel-staging

    Apex Sentinel · Issue review

    Suggested label: feature

    The issue requests implementation work: applying a shared session visibility projection to daemon surfaces, removing old filters, and verifying callers, rather than reporting broken behavior or asking for help.

  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