inbox-triage

Constraints

• NEVER scan whole vault; scope = Inbox/ or user-specified path only
• NEVER write back without explicit user confirmation
• NEVER produce synthesis or thesis; output is routing decisions only
• NEVER deep-read all items; deep-read only when routing is genuinely uncertain
• MAX 20 items per batch; split and report remainder if more

Trigger Boundary

Use when: triage inbox, sort captures, route raw notes, process fleeting notes, decide what to promote/archive.

Do NOT use for:

• Cross-note relationship analysis → connection-review
• Week-level meaning extraction → weekly-synthesis
• Stable note creation → note-promotion
• Vault health diagnosis → vault-health-feedback