note-promotion

Constraints

• NEVER promote everything; require stability + reuse + independence
• NEVER polish before deciding; score first, format only if promoting
• NEVER create notes without integration targets (minimum 2 links)
• NEVER write without user confirmation
• NEVER overwrite source voice; preserve strong original phrasing

Trigger Boundary

Use when: upgrade material into formal note, decide if finding is worth preserving, turn synthesis output into stable note, create linkable knowledge unit, user says "promote" or "stabilize."

Do NOT use for:

• First-pass inbox routing -> inbox-triage
• Note relationship discovery -> connection-review
• Week-level meaning extraction -> weekly-synthesis
• Vault system health diagnosis -> vault-health-feedback