# Inspect Loop

Use this branch to report dirtyloop state without changing files, Beads, branches, PRs, or sessions.

## Steps

1. Read `IMPLEMENT.md`, `loop-state.md`, `runtime/binding.json`, Pi-only `runtime/adapter.json` when present, and Beads state. Require the persisted execution profile to agree across generated docs and Beads.
2. Validate the binding and compare its target with Beads plus the current certified runtime manifest.
3. Compare docs against Beads and run `execution-readiness.mjs --doc-root <root> --policy report` across authored phase docs.
4. Report configured execution profile, configured harness, current harness, selected adapter, compatibility, execution-readiness state and findings, current phase, ready phase candidates, active ownership, blockers, and next recommended action.

Completion criterion: the user can see whether the loop is harness-compatible and ready to run, blocked, or complete, with the exact `dirtyloops convert <target>` command when conversion is needed.