data2dsl

Participant: codex (AI agent)

Understanding

The requested system is not a new parser framework or a replacement for todo2code. Phase 0 must prove which existing capabilities can be composed, which smallest neutral seams may later be extracted from todo2code, which existing components could be extended, and which requirements remain genuinely missing. All conclusions require current evidence. The user explicitly asked to execute Phase 0, which records SESSION_EXECUTION_AUTHORIZATION for this bounded documentation and governance scope.

No trusted human identity has been supplied; the human response route remains unresolved:human.

Execution plan

1. Adopt and verify the published immutable governance revision.
2. Establish only the governance, roadmap, and Docker bootstrap carriers.
3. Inspect the current repositories, public interfaces, schemas, tests, runtimes, dependencies, licenses, inputs, outputs, and coupling.
4. Classify each required capability as CANDIDATE, REUSE, EXTRACT, EXTEND, MISSING, or REJECTED with concrete evidence.
5. Publish docs/CAPABILITY_MAP.md and the provisional composition graph.
6. Run the deterministic governance gate and attempt Docker validation.

Risks

• README claims may not match exported or tested behavior.
• Candidate repositories may be planning-only or tightly coupled products.
• Cross-repository paths can accidentally leak into committed evidence; all committed paths must remain repository-relative.
• Docker Desktop is currently unavailable, so container validation may remain blocked even if configuration is complete.
• Creating the GitHub repository is external coordination and requires separate authority from the local Phase 0 work.

Acceptance criteria

• AC-01 through AC-07 are defined in the ticket README and require referenced deterministic evidence or an explicit blocker.
• No product source, extraction, refactor, final schema, or new runtime dependency is introduced.

Actual changes

• Initialized the bounded ticket and recorded SESSION_EXECUTION_AUTHORIZATION from the request to execute this work.
• Adopted published wellmanifest/new-project v0.16.2 at revision 63a03d0c2ec417f8eab9a6edb3c4ed654937a1ac through public Goal 2.1.300.
• Prepared governance-only root and Docker bootstrap carriers.
• Scanned 78 semcod, 60 subactor, and 15 wellmanifest Git repositories, then verified shortlisted candidates against their implementation, public surface, package metadata and tests.
• Published docs/CAPABILITY_MAP.md with evidence-backed reuse, extraction, extension, missing and rejected decisions plus a provisional composition graph.
• Ran the deterministic governance gate: GOV-PASS with zero errors and zero warnings.
• Built the pinned Docker image and ran the isolated read-only Compose check; both completed successfully without a host-runtime fallback.
• Received explicit authority to create a public repository and publish the Phase 0 results, then created semcod/data2dsl and configured it as origin.

Remaining authority boundaries

• New authority remains required for destructive action, secret access, new external coordination, material objective expansion and trusted merge.
• The user explicitly prohibited implementation and changes in other repositories during this publication step.