Customer exports use the new S3 bucket as of this week. The old bucket is read-only.
- source
- slack#platform · 2026-08-12T09:41Z
- ratified
- j.ramos · human inbox · 10:02Z
- supersedes
ctx_7f3a12ctx_9b41d2- delivered
- snap 3f2c9a…41be · run_4418
Missing context makes an agent ask. Bad context makes it act.
Rabbleset is governed, shared ground truth for teams that work with agents. Every object has a source, a chain, and a record of who ratified it.
The problem
Context is scattered across tools, unshared and never validated. Agents act on it anyway.
Per-tool memory is unshared and unvalidated.
Every tool keeps its own notes. Nothing is ratified, and nothing carries over when the team switches tools.
Agent output silently becomes truth.
An agent writes a summary. The next run reads it as fact, with no provenance and no record of who signed off.
In closed loops, drift does not persist. It amplifies.
A wrong claim does not fade. Each run builds on it, and the loop confidently diverges.
How it works
Capture
Decisions, facts, and agent output land as candidates. Nothing enters directly.
Validate
Low-stakes changes auto-accept with undo. High-stakes changes go to a small human inbox.
Deliver
Every agent run receives the current ground truth, with a source and a chain behind every object.
Agents get context they can act on. Humans get a record they can audit.
When loops prompt agents, nobody is in the room. The context package is the room.
Founder: Nicholas Meyers
LinkedIn ↗