pluribus

Vote on Pluribus curation chores when wakeup or recall surfaces housekeeping.

Vote on Pluribus curation chores when recall or wakeup surfaces housekeeping.

Retrieve durable Pluribus context before substantive work. Use when editing multiple files, changing APIs or schema, debugging failures, handling security or compliance, or any task needing more than two sentences to explain to a teammate.

Memory loop — recall before work, housekeeping when chores exist, record after outcomes.

Memory loop — recall before work, record after outcomes.

Memory loop — recall before work, record after outcomes.

Check that Pluribus is reachable before relying on memory tools. Use when MCP errors, timeouts, or disconnects appear, or when validating a new install.

Inspect pending memory curation when reviewing what needs human promotion or review. Use when the user asks about learnings queue, promotion, or advisory candidates—not for routine coding.

When Pluribus applies—tags and situation, not project silos; server owns truth. Use when clarifying scope of recall/record or correcting mistaken “per-repo only” assumptions.

Persist outcomes to Pluribus after meaningful work. Use after landing a fix, resolving a non-obvious failure, confirming a design decision, or discovering a durable pattern or mistake to avoid.