eou-foundry

Scaffold a new EOU-governed application in the current workspace. Creates a sibling directory with foundry/, instance copies of plugin templates, a starter constitution, and an initial git repo.

Audit a generated candidate EOU set for boundary quality, minimality, overlap, authority, operational value, and governance risk before any candidate advances to specification. <example> Context: A generation run has just produced a candidate set; the owner wants to know which candidates survive audit before promotion. user: "$audit-candidate-eou-set foundry/self-evolution/candidate-sets/cs-generate-eou-candidates-20260520-1430.yml" assistant: "I'll run the eight tests (boundary, non-overlap, minimality, authority, operational value, counter-generation, set composition, high-stakes) and write the audit report under foundry/audits/candidate-set-audits/." </example> <example> Context: User wants to audit a candidate set that contains a generating EOU without a corresponding audit path. user: "$audit-candidate-eou-set ./my-candidates.yml" assistant: "I'll audit. Heads-up that if any candidate has authority_level approve/publish or proposes weakening validators, I'll escalate to FAIL regardless of other test outcomes." </example>

Create a formal EOU Change Proposal from a diagnosed failure or refactor option, capturing simulation, regression case, audit, and approval requirements per rule 92. <example> Context: $eou-diagnose has produced a diagnosis recommending a change. Owner wants to convert it into an actionable ECP. user: "$ecp-propose foundry/audits/incidents/inc-0042.diagnosis.yml" assistant: "I'll read the diagnosis, target_eou, and proposed change; draft an ECP under foundry/self-evolution/ecp/proposed/ with simulation, regression case, audit, and approval blocks. Status starts at proposed." </example> <example> Context: User wants an ECP for a refactor option produced by $eou-refactor. user: "$ecp-propose ./refactor-options/ro-split-audit-eou.yml" assistant: "I'll draft the ECP. If the target requires a constitution change, I'll stop and direct you to the constitutional ECP process instead." </example>

Audit a single EOU spec against Foundry V2 faceted classification, authority limits, validator schemas, failure modes, trace declaration, blast radius, and responsibility ownership. <example> Context: User wants to audit an EOU before promoting it to active. user: "$eou-audit eou-diagnose" assistant: "I'll load the spec, registry entry, governance.yml, and the engine maturity model, then produce an audit report under foundry/audits/eou-audits/ with severity-categorized findings." </example> <example> Context: User wants to re-audit after applying an ECP. user: "$eou-audit foundry/eous/audit-foundry.yml" assistant: "I'll re-run the audit. If responsibility.executor equals responsibility.approver, the rule 94 hard check fails immediately." </example>

Diagnose an EOU failure using the F-code taxonomy and recommend the smallest-blast-radius repair, producing either a diagnosis (path to $ecp-propose) or a no-change record. <example> Context: An incident has been filed; owner wants a structured diagnosis before deciding whether to open an ECP. user: "$eou-diagnose foundry/incidents/inc-0042.yml" assistant: "I'll classify the failure under one or more F-codes, rank repair options by blast radius, and emit either a diagnosis YAML (decision: change) or a no-change record under foundry/audits/incidents/." </example> <example> Context: User wants to diagnose from an audit finding rather than a full incident. user: "$eou-diagnose foundry/audits/eou-audits/eou-promote.audit.yml" assistant: "I'll diagnose the audit's findings; if evidence is insufficient for a change, I'll write a no-change record explicitly rather than silently doing nothing." </example>

Evaluate whether an EOU should be promoted, deprecated, or retired based on evidence, maturity model, audits, run traces, and owner approval. Produces a recommendation only — does not execute any lifecycle transition (that is the role of activate/retire execution, which requires human approval). <example> Context: An EOU has been at pilot stage for two weeks; owner wants to know if it qualifies for active promotion. user: "$eou-promote eou-diagnose" assistant: "I'll check evidence against the maturity-model gates (audit pass, named owner, regression coverage, trace presence) and write a lifecycle recommendation. If gates are not met, recommendation is hold/demote, not activate." </example> <example> Context: User wants to evaluate retirement of an unused EOU. user: "$eou-promote eou-old-validator" assistant: "I'll evaluate retirement evidence (successor documented or owner decision recorded). I produce a recommendation, never the retirement itself." </example>