| name | compiling-cybernetic-runtime-goals |
| description | Use when an existing v1 run must compile its reviewed control chain into runtime.control.json. |
Compiling Cybernetic Runtime Goals
Legacy v1 compatibility only. New runs do not compile strategy artifacts.
Overview
Compile the current approved generation of a JSON control run.
Default official input:
docs/cybernetics/runs/<slug>/
requirements.control.json
run.control.json
gen-N/runtime.control.json
run.control.json.current_generation selects the generation. The run records
strategy_policy; do not use old process-weight labels as compiler concepts.
This skill does not execute target work and does not edit approved meaning.
Detailed conditional checks live in references/runtime-compilation-detailed-rules.md.
Hot Path
- Confirm the run directory contains
requirements.control.json and
run.control.json.
- Confirm
run.control.json.current_generation names exactly one active
generation.
- Confirm that generation declares
runtime.
- For
execution or amendment generations, confirm an approved generation
review exists before compiling.
- For an expanded execution chain, require preserved requirements/design/goal
anchors, generation-specific plan/review refs for amendments, exact
plan-to-runtime required-step and
execution_policy projection, and
evidence_subject_mode: required_single_manifest with one required component
per mainline work package.
- For an amendment generation, hash-bind its exact patch, plan, and independent
review.
- Run the guard and compiler.
- Run the pre-goal guard at
after-runtime-compile to validate the compiled
projection.
- Output only the short
/goal pointer when every gate passes.
Preferred command:
python3 .agents/skills/compiling-cybernetic-runtime-goals/scripts/compile_runtime_goal.py \
--run-dir docs/cybernetics/runs/YYYY-MM-DD-feature
The compiler already enforces run.control.json, current_generation,
generation review rules, hashes, and runtime JSON shape. Do not hand-build a
runtime prompt from Markdown or old root-chain assumptions.
Pointer Rule
The user-entered /goal is an adapter, not a control fact:
/goal Use .agents/skills/using-control-json and execute docs/cybernetics/runs/YYYY-MM-DD-feature. Read run.control.json first; resolve current_generation to the current runtime.control.json; if the JSON is missing, invalid, inconsistent, or insufficient, stop and report the smallest required human decision.
Do not inline approved requirements, completion rules, work assignment,
evidence rules, review discipline, or subagent protocol prose into /goal.
If the approved work assignment is Serial subagent-driven or
Parallel subagent-driven, append only this minimal authorization sentence:
允许使用 subagent 执行 runtime.control.json 批准的 work assignment。
Failed Compile
If guard or compiler fails, do not emit /goal.
Report:
Runtime goal compilation failed.
Reason:
- ...
Guard/compiler result:
- `FAIL`
- transition-gate `next_action` if emitted
Response-only next step:
- return to `$orchestrating-cybernetic-pregoal` with the failing output, or
- run the smallest named upstream repair step.
Validation Checklist
