القائمة
Use when an existing v1 run must compile its reviewed control chain into runtime.control.json.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when a formed task needs durable human-approved meaning, completion obligations, evidence claims, non-goals, or live/destructive authority boundaries.
Use when maintaining or resuming an existing v1 requirements.control.json run; new runs use forming-cybernetic-commitments.
Use when optional local workflow guidance or legacy v1 workflow compatibility needs diagnosis.
Use when an existing v1 control chain requires design.control.json; v2 strategies remain agent-owned.
Use when cybernetic routing is requested but user input is pre-task intent or role-ambiguous context: confusion, dissatisfaction, risk sense, observed symptoms, failed attempts, method preference, process distrust, source material, declared current state, or unclear requested transformation.
Use when resuming an existing v1 run that already requires pre-goal control-chain compilation.
استنادا إلى تصنيف SOC المهني
| name | compiling-cybernetic-runtime-goals |
| description | Use when an existing v1 run must compile its reviewed control chain into runtime.control.json. |
Legacy v1 compatibility only. New runs do not compile strategy artifacts.
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.
requirements.control.json and
run.control.json.run.control.json.current_generation names exactly one active
generation.runtime.execution or amendment generations, confirm an approved generation
review exists before compiling.execution_policy projection, and
evidence_subject_mode: required_single_manifest with one required component
per mainline work package.after-runtime-compile to validate the compiled
projection./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.
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。
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.
run.control.json is present.current_generation is declared and active.execution and amendment./goal is pointer-only.