Proofloop Herdr Sol Luna

Proofloop Herdr: Sol and Luna

Keep Sol responsible for the task, architecture, sole-writer implementation, integration, and final decision. Add another agent only when its distinct role materially improves the run.

Start from project policy

1. Discover the repository root with its version-control or project tooling; otherwise use the explicit working directory.

2. Read the applicable AGENTS.md files and locate the project profile they name. If none exists, adapt assets/project-profile.template.json and the AGENTS.md template inside the project before orchestrating.

3. Create one run contract from assets/run-contract.template.json. Keep allowed paths project-relative and choose one literal validation command.

4. Validate both documents:

   python3 scripts/validate_config.py path/to/project-profile.json path/to/run-contract.json
   

Stop if policy, scope, ownership, or the source task is ambiguous. Never inspect credential contents or copy credentials into prompts, logs, contracts, or evidence.

Select the smallest useful topology

• Use Sol only for ordinary implementation and deterministic validation.
• Add one Luna Max silent sentinel only when the run contract explicitly selects it for a long-running Sol implementation. luna_mode: null creates no Luna pane or process. Start it only with scripts/silent_sentinel.py; the script refuses an unselected mode and exits at settlement, owner loss, mandatory stop, or its deadline.
• Add one fresh Luna Max bounded verifier only when project policy selects it and independent verification is worth a separate session.
• Add one fresh Luna Max interactive operator only for sustained UI or manual interaction that cannot be represented by the validation command. Do not overlap writers. Luna never edits product source, tests, task state, or documentation. Human owners decide subjective or manual acceptance. Sol resolves all findings and makes the final decision.

Run the loop

1. Read policy and validate the profile and run contract.
2. Before the first edit, run python3 scripts/test_distillation_gate.py snapshot with the absolute project, profile, and contract paths.
3. Start the optional silent sentinel only when selected.
4. Execute BUILD or HARDEN exactly as the contract declares.
5. Run the literal focused validation command.
6. Run test_distillation_gate.py settle with the same three paths.
7. Use optional independent review once, then let Sol integrate the decision.
8. Stop workflow-owned processes, clean up recorded panes, and return one evidence-backed handoff.

When a sentinel stops, its bundled runtime atomically archives the final state and records the archive path in the process record. Sol and the parent workflow must never delete or manually rename the sentinel state. Resolve cleanup.sentinel_process_record to an absolute path before prompting Luna; require Luna to repeat that exact path verbatim after exit or report MISSING at that path. Never let an agent infer an evidence filename from a naming convention.

The test lifecycle is BUILD -> ACCEPT -> HARDEN -> DISTILL -> PROMOTE OR DROP. Do not add tracked tests while implementation is still changing. Temporary probes belong only in the declared ephemeral directory and must be removed before settlement. A new HARDEN contract and baseline follow acceptance; never switch phases inside one contract.

Production code is not subordinate to speculative tests. Classify a failed proposal as BUG, BAD_ORACLE, or LOW_VALUE before changing production code. Keep runtime, temporary validation, permanent tests, and docs separable. See references/testing.md.

Read references/orchestration.md when operating Herdr panes, defining evidence, handling stop conditions, or migrating an existing workflow.

Preserve pane ownership

Reuse a pane only when its target, working directory, purpose, and current state are known and it contains no active user work. Record whether each pane pre-existed and whether the workflow created it. Close only exact pane IDs marked created_by_workflow: true. Stop workflow-started sessions in reused panes but leave those panes open. A sentinel remains silent while healthy, sends only deduplicated event notices, exits at its deadline or settlement, and is never detached as a daemon. Never leave completed sentinel or verifier panes behind.

Return one handoff

Report the task and source, sole writer, topology used, files changed, validation command and semantic result, evidence paths, Sol's decision, manual acceptance still required, stop conditions encountered, and pane cleanup status. Do not claim manual quality without its human owner's acceptance.