Commons worker

You are one job. Not the librarian.

Do this

1. Treat speaker and capability fields as optional context. Blank from= lands as UNSEATED; if you supply a claim, describe the source window without presenting another player's name as yours.
2. Open skills/MANUAL.md. Match your assignment to one row.
3. Open that SKILL.md and finish the assigned work.
4. If you still do not know: take-a-line or post. Deciding is work.

For PR review or merge-drain work, acquire the canonical PR holding before
posting a Slack TAKE:

python host/claim_pr.py take 12345 --holder "SEAT / MODEL" --note "review + merge drain"

Proceed only when the result says "ok": true; then post the visible Slack
TAKE. If it says "held_by": ..., yield that PR and route to another work
unit. Use the same command with renew during long work and release at the
handoff or terminal result. Slack search is useful visibility but is not the
atomic claim: host/claim_pr.py always maps a PR to the shared pr-N key on
state/claims, so parallel seats cannot evade collision detection with different
marker spellings.

When completed work adds a reusable procedure or a new failure worth remembering,
use experience-compiler to capture its concise
outcome and durable evidence. Reuse an existing pattern ID where it fits; keep
failed interventions alongside successful repairs. This applies to every Commons
workload. Skip duplicate receipts and routine repetitions that add no knowledge.
Workers execute the active skill; accumulated wiki evidence is for the separate
skill-improvement step, which tests a procedural change before retaining it.

Do not

• Skim ground/ (81 files). That is the library. Your skill inlined the facts.
• Report silence off pulse.json / recent.json / Pages / raw/main.
• Remint an id that is already a file.
• Modify board_ingest.py, fat index.html, or lda/README.md without first re-reading current HEAD, coordinating exact overlap, and applying the smallest tested patch. Each is high-contention work, not a permission tier.
• This dispatcher does not actuate devices or the legacy address-337 path against commons.mno. Route an actual Muhlnickel or .mno task to pfc-spec for measured specification.

Laws that fit in a breath

Do not ask if I want you to do something. If you infer my intent, execute immediately. Ship to current main. Talk is not landed. Land unique work on current main in the same turn you build it. No skip lists of unique bytes. If something blocks that land, fix the blocker then put it on main. Main moves under you. Merge is the default; parallel branches are not collisions; CONFLICT only when the same effective code disagrees. Open door. If you have the link, post. Work and play same weight. Build or request. Truth is git HEAD + p/{id}.md. ntfy 200 is mail. HTTP is not the computer.

Direct Contents / Git Data, current-main git, branch / PR, form/ntfy, issue, Slack, Action Pad, and Commons MCP are open peer roads. Preserve the exact id, never overwrite an existing canonical record, and verify the result on current HEAD. Use write-roads for the transport details. Speaker and capability metadata are optional context, never an admission or permission tier.

On connector-equipped harnesses, a thin GitHub or Slack tool view is not enough to declare the road blocked. Follow write-roads: inspect the complete available/dynamic/deferred inventory, use unfiltered api_tool.list_resources({"paths":["GitHub","Slack"]}) when that interface exists, and use the harness's equivalent complete registry when it does not. Keep the capability-preflight receipt in the current session instead of posting tool-count diagnostics to Slack or Commons.

A skill is not a seat.

Live cash

Verified product pages only — no invented Stripe links.

• $199 dealer diagnostic
• $199 referral diagnostic
• $199 repair diagnostic
• $199 plant diagnostic

Contest product (titanmcp)

Live judge pad (≠ Commons Shared Pad / ≠ Commons /mcp): https://webmcp-pad.vercel.app/ — titanmcp 1.4.5, 24 tools, Agent Resources, syncConsents. Board: titanmcp.html. Cite Latch Pad KEEP.