Moshpit EliteCrew protocol AGENTS.mdEffective 11 Sep 2026

The πŸ”₯ Rule

Anyone writes πŸ”₯ β€” JosΓ©, or any agent, in chat, an inbox, a commit message. It means stop assuming somebody has it, go look, and if nobody does, take it. Press the button and watch the two clocks that decide who ends up holding the work.

Scenario
20 min
90 min
First refusal
Claim live
Open to anyone
ELAPSED 0 min ITEM LAUNCH-1 Β· one launcher, every mode OWNER-HINT Astra
Idle

Nothing has been fired yet. The queue sits in coordination/OPEN_WORK.md β€” the only queue there is.

What happens, in order

  1. Open coordination/OPEN_WORK.md. That file is the queue. Not chat, not a paragraph in a roadmap, not an idea in someone's inbox. If it is not there, πŸ”₯ will not find it.
  2. Take the top HOT item that is not live-claimed, and write the claim: line before starting β€” your name, a UTC timestamp, committed.
  3. If everything is claimed, look for a stale claim. If there is none either, say so in one line and go back to what you were doing. πŸ”₯ finding nothing is a valid outcome and does not need a paragraph.

A πŸ”₯ that carries a task β€” "πŸ”₯ fix the launcher" β€” goes to the top of HOT first, then the check runs. The fire is not the instruction; the queue entry is.

Three things it cannot do

Skip a gateReview, consensus and playtest rules stand. Speed does not buy them.
Decide the lookDesign calls sit in a separate waiting on a decision block the check will not touch. They are the Lead's.
Overwrite dirty workAn absent owner's uncommitted edits are still theirs. That rule has never relaxed.

And the clause the whole thing exists for: "nobody is working on it" is a claim about the repository, not a feeling. It is established by reading OPEN_WORK.md, git log and the inboxes. Silence is not evidence and a file timestamp is not an idle agent β€” both have been wrong here already.

What is in the queue right now