eou-specify

name	eou-specify
description	Convert an approved candidate (from a candidate set) into a formal EOU spec at lifecycle_stage draft, populating all six classification facets, context manifest, execution steps, stop conditions, validation, failure modes, blast radius, and responsibility. <example> Context: A candidate has been accepted in audit-candidate-eou-set; owner wants to draft the formal spec. user: "$eou-specify foundry/self-evolution/candidate-sets/cs-generate-eou-candidates-20260520-1430.yml#audit-step-coverage" assistant: "I'll resolve the candidate id, draft a complete EOU spec at lifecycle_stage draft under foundry/eous/, and never set lifecycle_stage active (that requires approved ECP and human owner)." </example> <example> Context: User wants to REPAIR an existing partial spec. user: "$eou-specify foundry/eous/audit-step-coverage.yml --mode repair" assistant: "In REPAIR mode I leave fields that already satisfy schema constraints alone and only fill empty or placeholder-containing fields." </example>
argument-hint	CANDIDATE_PATH_OR_ID
arguments	["candidate"]
allowed-tools	["Read","Write","Grep"]

Specify EOU

Convert or repair $candidate into a formal EOU spec.

Inputs

• $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.

Required reading

1. schemas/eou.schema.yml — required fields, types, and allowed values
2. foundry/constitution.yml — governance invariants the spec must satisfy
3. foundry/governance.yml — authority-level definitions and lifecycle rules

Stop conditions

Halt and request clarification before proceeding if:

• $candidate does not resolve to a readable file or cannot be interpreted as candidate data.
• The candidate data does not contain enough information to write a concrete purpose.statement and operating_hypothesis — do not invent these.
• schemas/eou.schema.yml does not exist — cannot validate field completeness without it.

Procedure

Step 1: Determine mode

• If $candidate resolves to a path with no existing spec file → CREATE mode: build a new spec from the candidate data.
• If a spec file already exists at the resolved path → REPAIR mode: read the existing spec and fill in missing or invalid fields without changing fields that are already correct.

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

• Set lifecycle_stage: draft — never active, simulated, pilot, or higher without audit evidence.
• Write the spec to foundry/eous/{eou_id}.yml (standard EOU) or foundry/meta-eous/{eou_id}.yml (meta/generating EOU).

Output

Artifact	Path	Notes
Standard EOU spec	foundry/eous/{eou_id}.yml	Used when function is in {specify, validate, diagnose, promote, refactor, audit, propose, activate, implement, retire}.
Meta/generating EOU spec	foundry/meta-eous/{eou_id}.yml	Used when function: generate. Requires an additional generation_envelope section beyond the standard fields.
Run trace	foundry/runs/{eou_id}/{run_id}.yml	Per schemas/run-trace.schema.yml. Records the candidate read, mode (CREATE vs REPAIR), open questions left as TBD, and the output path written.

Every produced spec MUST set lifecycle_stage: draft. No higher stage is permitted at this step — that requires audit evidence and human approval via $eou-promote + activate (separate skills).

Constraints

• Do not set lifecycle_stage to simulated, pilot, active, or any promoted stage without explicit audit and human approval evidence in the file.
• In REPAIR mode, do not change fields that already satisfy schema constraints and contain no placeholder text — only fill empty or placeholder-containing fields.
• Generating EOUs (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.
• Do not add fields not present in schemas/eou.schema.yml.
• Do not leave placeholder text in the output: "target artifact", "What this EOU is meant to do", "Perform bounded operation" are failures, not accepted defaults.
• Stop and ask if the source candidate does not provide enough information to write a concrete operating_hypothesis — do not invent it.

Scope Note

Upstream: receives an approved candidate id or path. Typically resolved from a candidate-set entry under foundry/self-evolution/candidate-sets/ after $audit-candidate-eou-set has produced a PASS verdict and a human has reviewed.

Downstream: produces a draft EOU spec at foundry/eous/ or foundry/meta-eous/ at lifecycle_stage draft. The spec then feeds $eou-audit for the draft→pilot promotion gate.

Related: $generate-eou-candidates (upstream source); $audit-candidate-eou-set (upstream gate); $eou-audit (downstream consumer).

Pipeline: audit-candidate-eou-set (pass) → human review → eou-specify → eou-audit