proofloop-herdr-sol-luna

name

proofloop-herdr-sol-luna

description

Coordinate project-configured Herdr workflows in which Sol owns intake, architecture, design-sensitive implementation, integration, and the final decision while Luna Max serves only as an explicitly selected read-only silent sentinel, fresh bounded verifier, or interactive operator. Use for bounded Sol-Luna implementation runs that need explicit ownership, evidence, budgets, or pane lifecycle safety; do not use for trivial edits, hidden background processes, or overlapping writers.

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