connection-review

Constraints

• NEVER scan whole vault; scope = 5-15 primary notes + small supporting set
• NEVER treat keyword overlap alone as evidence of connection
• NEVER synthesize week-level meaning (that is weekly-synthesis)
• NEVER write links without explicit user confirmation
• NEVER turn review into whole-vault graphing

Trigger Boundary

Use when: find note connections, suggest wikilinks, identify repeated patterns, surface contradictions, review relationships in a bounded set.

Do NOT use for:

• Raw inbox sorting → inbox-triage
• Week-level thesis and one action → weekly-synthesis
• Vault system health diagnosis → vault-health-feedback
• Upgrading material into stable notes → note-promotion