一键导入
eou-specify
Convert an approved candidate into a formal EOU spec using Foundry V2 faceted classification and governance constraints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Convert an approved candidate into a formal EOU spec using Foundry V2 faceted classification and governance constraints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit a generated candidate EOU set for boundary quality, minimality, overlap, authority, operational value, and governance risk.
Audit value_invocations in run traces for EOUs with classification.judgment_authorized:true. Verifies invocations against the captured_workflow's declared priority (no F15), checks for drift over multiple runs (no F16), detects hallucinated value ids (no F17), catches silent decisions on contested cases (F14), and runs counterfactual-swap audit as the V1 anti-theater defense.
Audit EOU specs for Foundry V2 faceted classification, authority limits, schemas, validation, failure modes, trace, blast radius, and responsibility ownership.
Synthesize a Stage 0 captured_workflow (D2.4 step 1–5 outputs + per-app constitutional domain_values layer) from a user goal, structured 5-role reference set, and constraints. For users entering an unfamiliar craft domain who cannot articulate a workflow unaided, and for any user who needs the constitutional layer made explicit before downstream EOU generation begins.
Generate a minimal, ranked candidate EOU set from a messy workflow using Foundry V2 constraints. Candidates are proposal-only and cannot be activated.
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 outc
| name | eou-specify |
| description | Convert an approved candidate into a formal EOU spec using Foundry V2 faceted classification and governance constraints. |
Convert or repair $candidate into a formal EOU spec.
$candidate (required) — path to a candidate YAML file or YAML content describing the EOU to specify. Resolved in this order: direct file path → foundry/self-evolution/candidate-sets/*.yml (search the candidates list for an entry whose id matches) → foundry/eous/{id}.yml.schemas/eou.schema.yml — required fields, types, and allowed valuesfoundry/constitution.yml — governance invariants the spec must satisfyfoundry/governance.yml — authority-level definitions and lifecycle rulesHalt and request clarification before proceeding if:
$candidate does not resolve to a readable file or cannot be interpreted as candidate data.purpose.statement and operating_hypothesis — do not invent these.schemas/eou.schema.yml file does not exist — cannot validate field completeness without it.Step 1: Determine mode
$candidate resolves to a path with no existing spec file → CREATE mode: build a new spec from the candidate data.Step 2: Load source material
Read $candidate to extract: purpose, operational context, known failure modes, authority level, and blast radius.
Step 3: Map all required fields
Populate each group in order:
classification:
function: # generate | specify | validate | diagnose | promote | refactor | audit | propose | activate | implement | retire
target_object: # the artifact or decision this EOU acts on
automation_mode: # deterministic | LLM_assisted | hybrid | human_executed
authority_level: # suggest_only | draft_only | write_candidate | write_inactive | mutate_active | approve | publish
risk_level: # low | medium | high | critical
lifecycle_stage: # candidate | draft | simulated | pilot | active | monitored | stable | deprecated | retired
purpose:
statement: # one sentence — what this EOU does
non_goals: # explicit list of what it must not do
operating_hypothesis: # "Given [inputs], this EOU can [action] without [boundary violation]."
inputs:
required: # files or data this EOU cannot run without
optional: # files that improve output quality if present
forbidden_assumptions: # things the EOU must not silently assume
context_manifest:
source_of_truth: # canonical files (registry, constitution, schemas)
supporting: # reference files (taxonomy, patterns, maturity model)
forbidden: # files this EOU must not read or mutate
execution:
steps: # ordered, concrete, bounded steps — no "perform bounded operation"
decision_points: # named branch conditions with explicit resolution criteria
stop_conditions: # observable states that stop execution before completion
allowed_tools: # explicit tool list
prohibited_actions: # explicit prohibitions
outputs:
primary: # concrete file path(s) — no placeholder labels
secondary: # supplementary artifacts
trace: # always: foundry/runs/{eou_id}/{run_id}.yml
success_criteria:
must_pass: # binary, verifiable conditions
should_pass: # quality checks that are not hard blockers
validation:
deterministic: # machine-checkable: field presence, schema conformance, count limits
judgment: # audit-level checks that require human or LLM review
red_team: # adversarial scenarios to test boundary robustness
failure_modes:
known: # named failure patterns
warning_signs: # observable signals that a known failure is occurring
repair_actions: # concrete responses to each warning sign
escalation:
require_human_when: # observable conditions that mandate human review
require_approval_for: # actions that cannot proceed without human approval
responsibility:
executor: # Claude | script | human (pick one primary; hybrid: name the split)
reviewer: # who reviews outputs
approver: # who approves lifecycle transitions
cannot_delegate: # non-delegable authorities
blast_radius:
allowed_scope: # directories or files this EOU may write to
forbidden_scope: # directories or files this EOU must never touch
versioning:
supersedes: # prior EOU IDs replaced by this spec
changelog: # list of version entries
Step 4: Validate completeness
Check every field group is populated. Reject placeholder strings ("target artifact", "What this EOU is meant to do", "Perform bounded operation"). If the source candidate does not contain enough information to fill a field, write TBD: [specific question] and list it under open_questions.
Step 5: Set lifecycle and write
lifecycle_stage: draft — never active, simulated, pilot, or higher without audit evidence.foundry/eous/{eou_id}.yml (standard EOU) or foundry/meta-eous/{eou_id}.yml (meta/generating EOU).lifecycle_stage to simulated, pilot, active, or any promoted stage without explicit audit and human approval evidence in the file.function: generate) require an additional generation_envelope section scoped to the specific outputs this EOU produces; do not copy a generic envelope from another EOU.schemas/eou.schema.yml.operating_hypothesis — do not invent it.