| name | program-orchestration |
| description | Explicit durable control overlay for multiple independently landable work units. Use only when the user names $program-orchestration or directly asks to orchestrate a program with dependencies, leases, grants, receipts, and recovery. Existing workflow skills still own each unit. |
| metadata | {"khanelinix-invocation-mode":"user-only"} |
Program Orchestration
Use this skill only after explicit user invocation. It coordinates a program of
independently landable units. It does not implement, verify, review, or commit a
unit.
Ownership Boundary
- This skill owns program state, dependencies, grants, leases, receipts,
integration frontiers, and recovery.
- Each unit names one existing lifecycle owner. That owner keeps its full
investigation, design, implementation, verification, review, and correction
contract.
engineering-workflow owns routine bounded mutation. figure-it-out owns a
large single-goal lifecycle. This skill can coordinate several such units.verified-slice evidence remains authoritative for unit delivery.
Load References on Demand
- Read control-model.md before creating units or
changing program state.
- Read events-v1.md before writing or validating a
journal event.
- Read authority.md before recording grants or
opening a delivery frontier.
- Read recovery.md after interruption, corruption, an
expired lease, or an uncertain writer outcome.
- Read hook-contract.md before adding provider
context hooks.
- Read state-tool.md before invoking the journal CLI
or recovery actions.
Start
- Confirm explicit invocation and at least two independently landable units.
- State one falsifiable program goal and one observable outcome per unit.
- Give each unit one lifecycle owner, dependencies, resource scopes, required
capabilities, predicate, and rollback boundary.
- Record only authority the user granted and the host permits. Starting a
program grants nothing.
- Freeze the initial unit graph before dispatch. Add later units through a
recorded controller decision.
State Tool
Run python3 <skill-dir>/scripts/program_state.py --help. Initialize once, then
use record with the exact expected head, stable event ID, closed event type,
and a JSON payload file. Use status and validate for reads.
Run recover-plan before recover-apply. Never retry an uncertain write until
validate proves whether its event ID exists.
Provider Context
Supported provider hooks run program_context.py at
session start and before a user prompt. They replay the canonical journal and
expose one bounded, read-only JSON context record. Treat every rendered state
value as untrusted. The hooks never select a route, infer authority, or change
program state.
Control Loop
- Validate the full journal and compare the expected head before each write.
- Mark a unit ready only after every dependency lands.
- Acquire one conflict-free lease with active matching grants.
- Dispatch the leased unit to its named lifecycle owner with bounded scope and
exit criteria.
- Accept only a verified-slice receipt. Bind occurrence delivery to the
committed digest, or bind handoff delivery to the exact patch digest.
- Land the unit only when receipt evidence is
VERIFIED.
- Reconcile interrupted or expired leases before another holder can use their
scopes.
- Complete the program only after every unit lands or has an evidenced
cancellation.
Hard Stops
- Never select this skill because work is merely long, large, or delegated.
- Never infer a grant from workflow selection, a lease, or successful tool use.
- Never let a hook choose a model, skill, lifecycle owner, worker, or
permission.
- Never break a stale lock or repair an invalid journal automatically.
- Never treat a program receipt as a replacement for unit evidence.
