munlucky Moon Relay Kernel
Goal
The account command skillset defaults to Kernel. Bind the current project/worktree to Moon Relay Kernel, execute assigned bounded work units, and drive the task to authoritative Kernel completion with verified proof and receipts; for a non-kernel track return wrong_harness without mutating the repository.
Context
- Binding Scope:
Project → Worktree → Run, scoped by canonical root and Git worktree identity under runtime home~/.moon-relay-kernel. - Two Core Commands:
kernel next [--contract-json <file>](or MCPkernel_next): Returns objective, acceptance, constraints, context capsule, and the active work unit.kernel report [--report-json <file>](or MCPkernel_report): Submits change summary, changed paths, risks, and requested verifications.
- Task Contract: Captured as compact JSON (objective, acceptance, constraints, non-goals) passed via
kernel next --contract-json <file>on the first call to atomically create/bind the Run; do not bootstrap a fresh session with barekernel next(use barekernel nextonly after a Host binding exists).
Autonomy & Priorities
- Implementation Autonomy: Perform code edits, testing, and commands directly in the native owner session and stay inside its allowed paths returned by
next. - Mutation Boundary: Never mutate files outside
allowedPaths. Mutations outside the allowed unit are rejected before verification runs. - Delegation: Subagents are optional for genuinely partitioned tasks; they are never a prerequisite for ordinary implementation.
- Fast Blockers: When blocked, immediately report the blocker reason (
question,permission,unsupported-verification, etc.) rather than looping or improvising.
Context and Wait Budget
- Use
kernel --helporkernel report --helpfor CLI usage; help never binds a Run or starts verification. Default CLI/MCP output is compact; request--verbose(MCPverbose: true) only for a specific diagnostic need. - Search with
rgfirst, then read the relevant function or section. Keep each tool result near 4,000 tokens or less; save long diagnostics to a file and inspect only failures or selected fields. - Inspect
git diff --statfirst, then one relevant file or hunk per read. Do not dump the entire multi-file diff into the model context. - For tests and report verification, use a 10–30 second initial wait and 30–60 second continuation waits supported by the tool. Avoid one-second polling; keep user progress updates within 60 seconds. Inspect completion and failures once the process exits.
- Declare directory scope as globs such as
scripts/kernel/**, notscripts/kernel/. For broad work (3+ acceptance criteria or files), supply bounded steps with acceptance IDs or a defensibly narrow explicit scope. Never invent file ownership by splitting acceptance text.
Definition of Done
- Treat Kernel completion decisions as the only completion authority; a run is done only when
kernel nextreturns{ action: { type: "done" } }. Narration or plain text completion claims have zero authority. - Reusable invariants, required verifications, architecture decisions, and failure patterns are recorded in
knowledgeObservationsupon completion.
Verification
- Request verifications using the command refs
nextlists for each outstanding obligation; the Kernel runtime executes them and owns the resulting evidence receipts. - For independent review actions (security review, protected T3 obligations, explicit flags), satisfy them via trusted review receipts recorded from an independent reviewer session (or native subagent fallback). In single-session environments where independent sessions cannot be spawned, request user operator approval. Resolve only outstanding judgment obligations via
kernel approve <run-id>orkernel-commit --approvewhen the Host supplies an operator approval reference; hard evidence remains mandatory. - Satisfy every verification obligation with fresh evidence; choose an order that fits the work, and report only after all required evidence is recorded.
Plan Ingestion & Worktree Reclaim
- Fast 2-Turn Plan Reading: When ingesting an external plan or large specification (>200 lines), do not run iterative chunk loops (
Select-Object -Skip ... -First ...or repeatedhead/tailturns).- Turn 1 (Index Scan): Extract outline and line numbers in one turn:
- PowerShell:
Select-String -Path <planPath> -Pattern '^#+ ' | Select-Object LineNumber, Line - Shell:
grep -nE '^#+ ' <planPath>
- PowerShell:
- Turn 2 (Targeted Slice): Extract only the targeted section or Wave range identified from the index scan, then proceed immediately to task contract creation.
- Turn 1 (Index Scan): Extract outline and line numbers in one turn:
- Contract Scale Sizing:
- Small / Bounded Tasks (1–3 files): Produce a lightweight 1-step contract (30–40 lines) to enter execution within 30 seconds.
- Multi-Wave / Large Tasks (5+ subsystems): Map all waves into a structured task contract up front so the run executes autonomously under Kernel step sequencing.
- Ghost Run Recovery: Starting a new task with
--invocation-intent new-taskor a distinct task contract automatically supersedes and archives any unresumedblockedrun on the worktree, reclaiming the mutation lease.