benefactor

Use when agreed memor.re/platform work should move end-to-end through refresh, validation, commit, push, PR, migration, deploy, or production verification…

Use when the user says Stabilizer, invokes $stabilizer, asks for Stabilizer-led judgment, or needs routine, recovery, energy, travel prep, health-signal…

Use when measurement, regression analysis, reporting, or calibration of memor.re product, agent, gate, or Council decisions is needed.

Use when a memor.re/platform worktree or branch is dirty and needs a release sweep: classify local changes, identify safe cross-merge candidates, preserve…

Use when the user says Closer, invokes $closer, asks to Closer this, or needs sequencing, triage, follow-through, handoff, release readiness, admin cleanup…

Use when Tier 1 weighted canonical agent judgment, ownership arbitration, full-bench review, approvals, goals, evals, or a product or operating decision needs…

Use when building, editing, or validating presentation decks: Figma plugin API, slide-type templates, index schema, brand constants, and quality gates before…

Use when the user wants sustained autonomous waterfall work on a topic across environment, agents, tools, connectors, plugins, skills, API, CLI, MCP…

Use when the user names memor.re as the system, wants the whole canon, names a callable canon target through the front door, wants a learning broadcast, or…

Use when the user says Negotiator, invokes $negotiator, says Negotiate, or needs leverage framing, tactic diagnosis, threshold setting, tradeoff structuring…

Use when cleaning stale, hallucinated, source-contaminated, deprecated-name, or split-authority residue from active memor.re docs, handoffs, specs, skills…

Use when completed or blocked work needs validation against repo close state and a consistent closeout across tasks, issues, plans, deployments, migrations…