[adrianwebb]

Outcome

Blocking inbox questions now gate only their related proposal work items. Managed answers require exact immutable read-back; a reopen or changed source invalidates the proof, and agent replies remain evidence for managed evaluation. Native MCP exposes safe typed Problem responses so coordinators can diagnose the same backend failures seen over REST.

Work authority

• Work item / Issue: Complete accounting transition observations for strict Agent acceptance #553 and Current deployment backlog: retained requirements after issue consolidation deployment#834; includes fix(api): authorize inbox question writes and exact readback #622's shared authoring permission repair.
• Proposal / decision: Deployment f7cc50fb-8984-42e3-aefd-7f0f2eddd418 v14 / 68de92c6-c5b4-49d7-94e4-abc8e83d858d supplies the real workflow.
• Assignment / checkpoint: native sends6ba9e85a4dcd78f3f20e55cede2ee3bc and910ed67be791bfcdb9e8871f57157192 informed the question boundary; no agent implementation or review product is claimed.
• Actor: Codex coordinator.
• Human authority: adrianwebb's standing authorization for shared-backend repairs and checked pre-launch delivery.
• Agent / capacity provider: existing native TreeSeed MCP discussion and workday boundaries; retained work, failures and unknown usage preserved.
• Exact base ref: staging c7e9bab.
• Exact head ref: codex/work-item-question-gates553 85eff60.

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Completed the shared authoring/gateway repairs, question-to-graph connection, exact answer provenance and serialized lifecycle transitions. Reused the existing graph-readiness observation for typed graph_not_ready and the existing REST Problem formatter for MCP. No new runner, status store, schema, migration or agent-specific proposal targeting.

Changes and commits

Authoring permissions retain governed schema/source authority. Question proof writes lock the inbox row and condition the state transition on the exact source and lifecycle sequence. Advisory, foreign and unknown relationships attach no work-item gate. Existing ownership and review behavior remain unchanged.

The graph query observes exact dependency readiness only after the typed not-ready response and re-queries the same authority. MCP catches typed ControlPlaneOperationError only, returning safe code/status/detail/requestId/instance as structuredContent and JSON text with isError=true. Causes and credentials are excluded; resources and signed confirmation receipts retain their existing behavior.

Verification

Exact-head Actions40159462985 passed complete owner verification, native TreeDX prerequisites, PostgreSQL backup/identity/concurrent-allocation checks, artifact packing, coded component scenes and cleanup. Local combined focused verification passed99cases/15files, strict build and policies.

Real native MCP on the qualified85eff candidate returned409/discussion_agent_chat_profile_missing for the retained group request, confirming structured diagnosis. Source inspection identifies a separate group-alias admission bug now tracked through real API proposal8bc60c93. The Deployment question was observed gating only Releaser while Writer was admitted. Full portfolio simulated release remains unproven; failed review/Reporter observations are retained in docs/agent-log.md.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

No migration. Blocking questions require managed approval; a normal comment cannot release their authority. Roll back through the existing exact-ref delivery process to c7e9bab, preserving all Git/TreeDX products, history and accounting. Group-alias admission, interrupted finalization and full simulation parity are separate unresolved work.

Completion summary

Exact candidate verification passed and supported coached adoption succeeded; final protected staging integration follows the checked PR. This is shared-backend bootstrap delivery, not a claim of a complete native-MCP simulated release.

AGPL committer authorization

Existing base-owned authorization remains authoritative. No license or grant change.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.