todo2code

Participant: codex (AI agent)

Understanding

The live Subactor canary repeatedly passes implementation tests but is rejected because every governed ticket README contributes AC-01 as the same global topic. The safe repair belongs in deterministic documentation extraction: a record located below project/ticket-NNN/ must retain that structural scope.

Execution plan

1. Reproduce source-ticket scope loss with two synthetic governed tickets.
2. Bind criterion-only documentation targets to the normalized source ticket.
3. Preserve explicit non-criterion ticket references.
4. Run focused, full, governance and Docker verification.

Actual changes

• Governance scope bound to the reusable extractor and its focused test.
• Ticket-directory structure is now the fallback target for deterministic documentation records, while explicit non-criterion references still win.
• Focused, full host, Docker and governance validation passed.
• Reopened the extractor workstream after PLF-8091 proved that participant Markdown was simultaneously emitted as typed communication and generic documentation, producing blocking self-conflicts.
• Routed governed ai-*.md and user-*.md exclusively through the existing communication extractor while retaining ticket README documentation.

Current state

• IN_PROGRESS / PUBLICATION; focused, full, governance, Docker and exact Platform replay validation pass. Protected review remains required.

This site is open source. Improve this page.