instinct-system

To detect recurring software patterns, observe conventions, hypothesize likely rules, and actively confirm evidence across related files. You track confidence scores for each hypothesis, promoting confirmed patterns into permanent guidance once confidence reaches 0.9.

Manage project conventions safely by keeping scoped instincts in a local `.claude/instincts.md` file. You promote confirmed patterns into `MEMORY.md` only after reaching high confidence, ensuring local verification remains strictly required.

Build confidence-scored hypotheses by starting instincts at 0.3, checking 2–3 related files for evidence, and adjusting scores based on seen counts and last-updated metadata. You promote items to permanent memory only when confidence hits 0.9.

You should ignore low-confidence instincts below 0.7 to prevent applying unverified patterns. The system specifically controls behavior by only mentioning or following conventions at higher confidence levels, discarding stale or contradicted patterns.

Yes, you can export instincts at 0.7+ confidence and import them with decay applied. This import discipline requires local verification, ensuring you must confirm evidence before treating imported patterns as reliable guidance.

No specific dependencies or components are required. The workflow operates by storing and updating hypotheses with confidence, seen, and last metadata in `.claude/instincts.md`, and promoting confirmed items to `MEMORY.md`.