Sign in required
Mutation signals are operator-only. They aggregate user-facing edit attempts across all signed-in users; we never publish them without an explicit decision. Set your bridge token in the pkclient panel, then come back.
Already set the token? Reload.
What users tried to fix
Aggregated text-mutation envelopes from signed-in users browsing any user-facing page wired with the ServerCore mutation sandbox. User edits stay per-user. Each signed-in user sees only their own corrections; nothing here pushes to other users automatically. Our role: triage the aggregate signal and decide which suggestions are worth us making the actual edit to the canonical source.
Suggested corrections (top 30)
How decisions land — and what they DON'T do
Each decision becomes a signed Thump broadcast over
/v1/transport/thump with
broadcast_kind = "mutation_decision". The
broadcast is audit-anchored in
rootrabbit_observations for the trail.
- Flag for review — adds the suggestion to our team's editorial-review queue. Goes nowhere automatically. A global change happens only when one of us actually edits the canonical source.
- Per-user — confirms the change is a legitimate personal preference. The user keeps their edit (they were already going to); we leave the source as is.
- Noise — archives the signal so it stops crowding the operator view; the user's local overlay is unaffected.
Per-user-not-global is the contract. Per pk-docs § mutation-signals-operator-2026-06-23 + the prior warren-burrow-thump-transport-and-tier-model canon.