What problem does it solve? Recurrence-proposal drafts accumulate in a vault inbox and need a consistent human review gate; without one, proposals pile up, get auto-accepted without judgment, or are re-litigated repeatedly. ## Core Features & Use Cases - Inbox triage: Lists pending drafts in 80_agents/hermes-nan/proposals/*.md and presents each candidate's root cause, occurrences, evidence, and suggested placement for review. - SOP-driven disposition: Applies the curation runbook's promote / merge / keep / wontfix decisions, updating each draft's frontmatter with its disposition status. - Issue filing and promotion: On accept, creates a proposal-labelled GitHub issue via gh, adds it to the project board, and on approval authors the Tier-4 artifact and redistributes it via the compile-harness scripts. - Use Case: During a weekly curator session, run the dispose step to batch-review five pending recurrence proposals, promote two into tracked issues, and record one wontfix with its reason so the same false cluster is not re-litigated. ## Quick Start Ask the assistant to dispose the proposal inbox by triaging all pending recurrence proposals in the vault.
