Odylith Greenfield Governance

# Odylith Greenfield Governance

Use this skill when the operator asks Odylith to build, govern, plan, or
architect a new project before source code exists.

1. Do not refuse merely because the repo has no app source. Greenfield intent
   is valid proposal evidence, not source evidence.
2. Run the host-reasoning contract path:
   `./.odylith/bin/odylith greenfield propose --repo-root . --prompt "<operator request>"`.
3. Use the active host model's full reasoning to draft the proposal in normal
   chat. The CLI output is the evidence/schema/guardrail contract, not a
   canned in-code domain list. Render concrete backlog candidates, program waves,
   release plan, planned Registry components, draft Atlas diagrams,
   assumptions, risks, validation strategy, and open questions that are
   specific to the operator prompt. Each draft Atlas diagram must include
   host-authored `mermaid_source`; Odylith validates and scaffolds the source
   after confirmation, but it must not invent the topology. Default the first
   greenfield release target to `0.0.1` unless the operator provides a
   different release target, and identify the first-wave workstreams that should
   target that release.
4. Do not write records until the operator confirms the proposal or gives
   explicit edits. On confirmation, run:
   `./.odylith/bin/odylith greenfield apply --repo-root . --proposal-file <proposal.json> --confirm --release 0.0.1`.
5. Preserve the evidence boundary: observed source, user intent, and Odylith
   assumptions must stay distinct. For science and math, reason from the
   domain named by the user and propose correctness obligations such as proof
   checking, reproducibility, units, tolerances, derivation review, datasets,
   peer review, or validation fixtures only when they actually fit.
6. For vague or broad prompts, preserve the program-formation contract without
   forcing a fixed bucket: show the parent workstream, child-boundary
   strategy, wave-to-workstream policy, provisional release selector, and the
   decisive assumptions before asking the operator to confirm or revise.