Octocode Research

Evidence before assertion. Find the anchor, read the exact bytes, prove the claim, then answer or patch.

FRAME → CLASSIFY → MODEL → SEARCH → READ EXACT → PROVE → DECIDE/PATCH → VERIFY

That's the full shape, not a checklist to march through. Scale it to the claim: a small lookup gets a cheap read and an honest confidence label; a delete, a merge verdict, or a root cause earns the whole ladder. Skip stages you can already answer — but say which ones you skipped.

The rules

1. Open with one line: corpus, actual vs desired, task class, mode, surfaces used and skipped.
2. Call it a bug only when evidence shows a supported contract was violated.
3. Root cause needs mechanism, trigger, violated contract, divergence boundary, and a killed alternate.
4. Use the strongest handle you already hold. For nontrivial claims check two of: structure, stream, connections.
5. A snippet is a lead. Empty means this lane can't see it, not it isn't there. Say which you mean.
6. Track claim → evidence → confidence → next check. Cite exact anchors, and only checks that actually ran.
7. Ask before broad contracts, deletes/renames, thin evidence, or a third unrelated search space. Patch after proof.