Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

docs(relay): the relay README names the 64 MB snapshot limit

Corey Olson0de9fd89dcc1
diff --git a/relay/README.md b/relay/README.md
index 3a545a17..2151bc25 100644
--- a/relay/README.md
+++ b/relay/README.md
@@ -156,8 +156,8 @@ The client owns the encryption format and engine-version checks.
It removes the link and its board-scoped credentials too; other boards and person sessions remain valid.
All responses and refusals retain envelope `version: 1`. Moves use the shared
-100,000 byte JSON-body limit. Legacy API1 snapshots allow a bounded 14,000,000
-byte JSON body and 10,000,000 decoded bytes; API2 uses the bounded objects below. One private SQLite journal per board stores only its
+100,000 byte JSON-body limit. Legacy API1 snapshots allow a bounded 90,000,000
+byte JSON body and 64,000,000 decoded bytes; API2 uses the bounded objects below. One private SQLite journal per board stores only its
identity, format, head cursor, receive times, public sender identities and sealed payloads. Compaction
keeps the head cursor, so the next move never reuses an earlier sequence.