[P1] Session protocols: close architecture/assurance projection and source-binding scope

[wsdt]

[P1] Session protocols: close architecture/assurance projection and source-binding scope

Review baseline and scope

Reviewed source: c9d32008e98d0e1711f47cb739f61c42376b884e on main, 22 September 2026.
Classification: REMAINING PROJECTION / SCOPE DECISION.
Predecessors: #206.
This replaces their remaining work; closing a predecessor during backlog migration is not a claim that its original scope was completed.

Already delivered — do not rebuild

e51226d migrates the real project transport and database transaction lifecycle onto the session-protocol kernel, removing their duplicate hand-rolled state machines. Context/graph protocol catalog outputs also exist. The unresolved criterion is faithful protocol facts in architecture and assurance outputs; calling those outputs not applicable was only a proposed scope narrowing, not completion.

Remaining implementation / execution

• Obtain an explicit maintainer decision on the unchanged four-output criterion versus a documented narrowing; do not treat the proposed narrowing as already approved.
• If the original criterion stands, implement the necessary checked declaration/HIR bindings and versioned architecture/assurance projection, with coordinated verifier/graph/backend behavior where source syntax carries meaning.
• Keep legal-order checking distinct from grants/resource authority and run the existing two real lifecycle integrations plus projection non-vacuity/drift tests.

Acceptance evidence

• Either all four original outputs are implemented with accurate checked-program bindings, or a clearly recorded maintainer scope decision identifies exactly what is no longer claimed.
• The two real runtime integrations remain live; a transcription/catalog alone cannot satisfy enforcement.
• Protocol ordering cannot mint permission for an effect, and all relevant grant/ownership/failure/cancel rules remain enforced.

Boundaries

Do not migrate the same two subsystems a second time or reclassify an already implemented runtime as a reference-only model. A task description is not an authorization for provider spend, signing, publication, remote deployment or a change to support policy. Preserve existing stable identities, explicit profile limits, source authority and non-vacuous acceptance gates.

Evidence and implementation entry points

• Issue #206 update
• Issue #206 update
• Repository entry point: src/session_protocol (review at the pinned revision).
• Repository entry point: src/project_transport/session/lifecycle.rs (review at the pinned revision).
• Repository entry point: docs/SESSION-PROTOCOL-TYPES-V1.md (review at the pinned revision).

Test results described above are retained repository evidence, not a fresh full test run performed by this backlog review. Re-run the owning gates for the implementation being accepted.

[wsdt]

Coordinator update (2026-09-23)

Status: blocked on scope/contract choice; no semantic edit was made.

Catalog/context support exists, but per-source graph, architecture, and assurance outputs lack declaration/HIR/source binding. Two runtime lifecycles remain live, and ordering metadata grants no authority. Satisfying the full four-output criterion is a coordinated semantic version rather than a narrow projection patch.

Next step: retain and approve the full four-output source-binding criterion, or explicitly narrow it without claiming the original acceptance. The issue remains open.