This pack supersedes the uploaded L9 Cognitive Runtime (kernels).zip by deduping overlapping kernel material into a smaller kernel-first runtime layout.
runtime/kernels/
├── constitutional/
│ ├── K01-platform-architecture-engine.yaml
│ ├── K02-contracts-code-laws-enforcement.yaml
│ ├── K03-constellation-transport-authority.yaml
│ ├── K04-domain-spec-yaml-authoring.yaml
│ └── K05-file-ownership-placement-capability-registry.yaml
│
├── task/
│ ├── developer_core_kernel.yaml
│ ├── repo_auditor_kernel.yaml
│ ├── prompt_compiler_kernel.yaml
│ ├── l9_engine_build_kernel.yaml
│ └── code_review_ci_kernel.yaml
│
├── architecture/
│ ├── repo_taxonomy_and_dependency_architecture.md
│ ├── dependency_birth_and_mirror_codegen.md
│ └── bundle_and_node_extras.md
│
├── improvement/
│ ├── recursive_alignment.md
│ ├── validate_eliminate_stubs.md
│ ├── recursive_improvement.md
│ └── recursive_leverage.md
│
└── terminal/
└── flawless_victory.contract.yaml
Use runtime/kernel_pipeline/KERNEL_PIPELINE.yaml as the source of truth.
Phase flow:
P0_UNPACKP1_CONSTITUTIONAL_PREFLIGHTP2_TASK_ROUTINGP3_ARCHITECTURE_DECISIONP4_ALIGNMENT_AND_STUB_GATEP5_RECURSIVE_IMPROVEMENTP6_LEVERAGE_COMPRESSIONP7_FLAWLESS_VICTORY
The old pack remains source history. This clean pack is the active runtime kernel pack.
Do not re-import old profile, blueprint, audit, or contract files as active kernels unless a future migration explicitly promotes them through the duplicate kernel policy.
- Profile/persona material.
- Duplicate blue sky audits.
- Build contracts that are source context rather than active kernels.
__MACOSXfiles.- Overlapping gap/stub kernels merged into
validate_eliminate_stubs.md. - Overlapping improvement/leverage instructions separated into bounded phases.
flawless_victory.contract.yaml runs only after prior phase gates are complete. It is not a brainstorming prompt, not an audit prompt, and not a general kernel.
The pack now includes a validator layer under runtime/kernel_pipeline/validators/. Run:
python runtime/kernel_pipeline/run_validators.pyThe validators enforce:
- canonical phase order from P0 through P7
- K01 -> K05 constitutional load order
- terminal-only
flawless_victory.contract.yamlactivation - role-directory cardinality
- duplicate active-kernel detection
- phase-output contract alignment
This is the first self-policing layer for the superseding clean kernel pack.
This pack now includes a deterministic activation planner:
runtime/kernel_pipeline/planner/
├── TASK_ROUTING_RULES.yaml
├── ACTIVATION_PLAN_SCHEMA.yaml
├── plan_activation.py
├── KERNEL_ACTIVATION_PLAN.example.yaml
└── README.md
Use it to select the smallest valid kernel set for a task:
python runtime/kernel_pipeline/planner/plan_activation.py \
"clean and dedupe this L9 kernel pack, then prepare a build contract" \
--terminal \
--out KERNEL_ACTIVATION_PLAN.yamlThen run validators:
python runtime/kernel_pipeline/run_validators.pyThe planner is not an executor. It emits the route, phases, active kernels, skipped kernels, required outputs, blockers, and Unknowns.
The pack now compiles canonical runtime contracts before rendering to any tool-specific environment.
Runtime Intent
→ Kernel Activation Plan
→ FINAL_EXECUTION_CONTRACT.yaml
→ VALIDATION_CONTRACT.yaml
→ HANDOFF_CONTRACT.yaml
→ adapter render
Added files:
contracts/
├── execution_contract.schema.json
├── validation_contract.schema.json
├── handoff_contract.schema.json
└── adapter_render.schema.json
runtime/contract_compiler/
├── compile_execution_contract.py
├── compile_validation_contract.py
├── compile_handoff_contract.py
└── adapters/
├── claude_code.md
├── cursor.md
├── codex.md
├── chatgpt.md
└── human_operator.md
Rule: Flawless Victory is terminal doctrine inside the universal execution contract, not a Claude-only output format.
This pack now supersedes v4 by adding the missing compiler-grade intermediate representation path:
Human Intent -> Intent Compiler -> Kernel Planner -> Universal Execution Contract -> Execution Graph -> Validation -> Adapter Render
New convergence files:
contracts/intent_contract.schema.jsonruntime/intent_compiler/runtime/execution_graph/EXECUTION_GRAPH.jsonEXECUTION_GRAPH.mdCOMMIT_PACK.mdCONVERGENCE.md
Run validators:
python runtime/kernel_pipeline/run_validators.pyAdapter renderers are a planned next layer, but they must remain deterministic serialization modules, not new planning engines.
Before building renderer scripts, prove that FINAL_EXECUTION_CONTRACT.yaml and EXECUTION_GRAPH.json are stable across 2-3 real use cases. The renderer promotion rule is documented in ROADMAP.md.
Target future shape:
runtime/contract_compiler/renderers/
├── render_claude_code.py
├── render_cursor.py
├── render_codex.py
├── render_chatgpt.py
└── render_human_operator.py
Rule: renderers serialize canonical plans only. They do not choose kernels, rewrite graph order, invent validation, or own execution logic.