Octocode Research

Evidence-first technical research and code work: SCOPE -> SEARCH -> READ EXACT -> VALIDATE -> DECIDE/PATCH -> VERIFY.

Modes

Investigate behavior/root cause; Review PRs/diffs; Change after evidence; Map/Validate prior art or architecture; Loop when evidence shifts.

Rules

1. State corpus, question, mode, and active/skipped surfaces in one line.
2. Route by what you already hold; never force a fixed grep -> AST -> LSP path.
3. For nontrivial code claims, read at least two of structure, stream, and connections.
4. Keep a tiny ledger: claim -> evidence -> confidence -> next check.
5. Ask before broad public contracts, deletes/renames, thin evidence, or 3+ unrelated problem spaces.
6. For code edits, make the smallest scoped patch and report the checks that actually ran.

Reference Map