proposal-create

# Create Proposal Create a proposal only when you discover something with real leverage: - A missing helper or utility that would save significant time across sessions - A missing validation or guardrail that could prevent real errors - A workflow improvement that would benefit multiple sessions - A reusable pattern worth operationalizing ## Three-Condition Rule Only create a proposal if all three are true: 1. **Repeated pattern** — observed more than once, across sessions. **Skip for `scheduled-check/*`, `operator-request`, `current-session`, and `capability-brainstorm` evidence sources** — recurrence is either established by the check's own analysis, validated upstream by `reflection-judge`, or established by the brainstorm pass. For candidates whose `Artifact:` line cites `state/observations.jsonl`, the ledger graduation is the recurrence evidence — the judge verified the ledger; do not re-check here. For efficiency/cost-class candidates, evidence citing a machine-written state file with the measured values also counts — the judge verifies the file. Procedure-capture candidates meeting the ephemerality exception (ephemeral artifacts + quantified cost, single current session) also count — see reflect § Procedure capture. 2. **Meaningful consequence** — something goes wrong without fixing it 3. **Operator-actionable change** — something the operator can concretely approve If any applicable condition cannot be stated concretely, do not create the proposal. Respond: "Not e...