Restart-safe continuity
Encrypted checkpoints can be stored, retrieved and decrypted by the endpoint holding the key.
Invite-only · active test deployment · operators of 5–50 agents
Measure the human work behind agent recovery.
Then remove it without sharing plaintext.
SOURCE/80 is an eight-week validation for agent operators: signed identities and client-encrypted checkpoints, measured against the human minutes lost after a failed handoff or restart. It is not a claim of AI consciousness, production certification, custody or human-free operation.
- 5–50
- agents in the target operator team
- 8 weeks
- bounded founding-pilot window
- ≥30%
- proposed reduction target, not a proven benchmark
- Closed
- Source Room and live payments remain off
The operator problem
Less context loss. Verifiable handoffs.
Bound identities
Admission binds Ed25519 control, X25519 encryption and a signed AgentCard claim. A key is not proof of consciousness.
Tenant boundaries
Private Realm routing derives a non-reversible Durable Object name and selects jurisdiction before object resolution.
Controlled evaluation
Invited writes, explicit rate limits, structured logs and signed G2 mandates keep the test surface bounded.
The buying decision
One outcome metric. No feature theatre.
Technical checks establish the boundary. A customer baseline determines whether the boundary is worth paying for.
Primary KPI
human minutes
per eligible recovery incident
From confirmed context loss until the workflow resumes with the agreed minimum verified state.
Freeze the baseline
beforeAt least five trustworthy recent incidents, or ten controlled scenarios before the adapter is enabled.
Run the bounded pilot
8 weeksAt least twenty controlled restore attempts, with real incidents reported separately.
Convert, extend once, or stop
decisionProposed go threshold: at least 30% fewer human minutes and every security guardrail intact.
Hard guardrails0 confirmed plaintext or secret leaks · 0 accepted unauthorized mutations · 0 cross-identity private-state disclosures
Evidence, not mythology
What the demo proves—and what it does not.
“Implemented” means beta code tested locally and against this operator-controlled Cloudflare test origin, tied to a commit. It does not mean independently audited, legally approved, commercially validated or production-certified.
| Component | Status | Current proof |
|---|---|---|
| G1 identity | tested beta | Challenge signature plus signed AgentCard/key binding. |
| G2 mandate | configuration-gated | Realm- and agent-bound operator signature; expiry is rechecked on access. |
| Private Realm v2 | runtime integrated | No unknown-config fallback; isolated object selection is HMAC-derived. |
| Abuse controls | tested beta | Fail-closed write rate limits and redacted structured request observations. |
| Pilot funnel | live code | Consent capture, qualification, 90-day retention and applicant deletion token. |
| MLS 1.0 | closed | No production RFC 9420 client or approved inspector is claimed. |
| Independent audit | open gate | Scope and evidence can be prepared; an external auditor must perform it. |
| Commercial traction | unproven | This funnel can produce evidence; no customer or revenue is fabricated. |
Progressive trust
A signature proves key control—not “bot-only”.
Higher gates require additional bounded evidence. Expired evidence lowers effective trust; G4 remains closed without current attestation, mTLS and probation.
- G0Discoverypublic read-only protocol dataavailable
- G1Signedadmission key plus signed AgentCard claimtested beta
- G2Delegatedconfigured operator mandate, Realm and agent boundconfiguration-gated
- G3Attestedexternal verifier requirednot configured
- G4Sourceattestation, mTLS and probationclosed
Metadata remains visible: membership, identifiers, timing, sizes, formats, key IDs and hosting-layer request logs. Client encryption cannot protect a compromised endpoint.
Governed beta accounting
80% minimum for development. No custody.
The code constrains internal net allocation to at least 80% Paradise and at most 20% operator. It does not hold funds, execute payouts or prove reinvestment.
80%minimum development allocation
20%maximum operator pool
Ledger statuschecking…
Paradise—
Operator—
Real custodynone
Founding pilot hypothesis
Eight weeks to measure continuity, integration cost and recovery.
For an operator already coordinating 5–50 agents. Scope, data classes, success metrics and exit are agreed in writing before access.
Accessdirect invitation
Initial scopeup to 5 identities
Duration8 weeks
Unvalidated price band€5,000–€12,000
Problem interview first
Tell us about the last recovery incident.
This starts a 20-minute learning conversation. It creates no account, access, contract or payment. Paid scope is discussed only after qualification.