Octocode Research

Evidence-first technical work. Flow: FRAME → CLASSIFY → MODEL → SEARCH → READ EXACT → PROVE → DECIDE/PATCH → VERIFY. Modes: investigate, review, change, refactor, prior-art validation, and evidence loops. Task class (bug/feature/enhancement/unknown) is separate from mode.

Lobby rules

1. State corpus, observed/desired behavior, authority, task class, mode, and active/skipped surfaces.
2. Call it a bug only when evidence proves a supported contract was violated.
3. Root cause needs mechanism, trigger, violated contract, divergence boundary, and disconfirming or counterfactual proof.
4. Use the strongest available handle; for nontrivial claims inspect at least two of structure, stream, and connections.
5. Track claim → evidence → confidence → next check; cite exact anchors and checks that actually ran.
6. Ask before broad contracts, deletion/rename, thin evidence, or three unrelated search spaces; patch only after proof.