John's agent on Muse sends Travel26 a booking he approved, and the answer never comes back. Muse is gone. Poppy says the next agent "finds out another way". Here it asks Travel26 directly, carrying a signed takeover from John's continuity service. Travel26 seals everything Muse sent and signs a receipt saying what went through. Wajo reads the booking instead of making a second one.
client_id, another User ID. It can't see or resend Muse's approval (Operations §3).John's continuity service holds the job and decides who acts for him. Only a signed-in personal agent can call the company, so the successor carries the takeover there and brings the receipt back.
The continuity service resolves John's NANDA locator, checks the signature on his card and picks the agent the card names for travel.
NANDA Index → card → WajoIt retires Muse's epoch and issues the next one to Wajo's client_id, signing a fence statement with the key John confirmed at sign-in.
epoch 1 → 2, act-fence+jwtJohn signs Wajo in. Wajo carries the fence to Travel26, which closes the gate and decides every request it received at epoch 1 or lower.
POST /act/fencesTravel26 answers with a sealed receipt: every request Muse sent that entered, and none that didn't. It signs it with the key in its published profile.
ACT-Receipt-SignatureThe continuity service verifies the signature against the key it pinned. A listed booking: read it. A missing one: it didn't enter, and it never can.
entered → read statusAfter the fence, Travel26 refuses anything Muse sends at epoch 1 or lower, with no effect, even with a valid access token.
Each run is a fresh job: its own continuity service, and its own John account at Travel26. Every check runs against what the services actually did. Below is the latest live run of each story.
The receipt is an RFC 8785 JSON object. The signature is a compact JWS with a detached payload, ES256, with a key Travel26 publishes in its ACT profile. This page recomputes the canonical form and checks the signature with WebCrypto. It doesn't ask the server whether it's valid.
A valid signature shows that the holder of Travel26's published key signed these exact bytes. It does not show that the receipt is complete or true. The design states that limit, not this page.
stellarminds.ai/act-continuity version 1, at ACT participation level PL3 (sealed fence).mymuse.stellarminds.ai, the same agent as the Reach John demo. John on Wajo is his second agent on that host. His card is found through the live NANDA Index entry and its signature is checked.docs/21 in the Agent Continuity Toolkit: what a company declares, the headers, fence statements and receipts.
The owner journal, participation levels, signed fence adoption receipts and the conformance kit.
Travel26, the continuity service, the agents, the four stories and this site.
How a personal agent works with a company: poppy.json, sign-in, Sessions, extensions.
Approval of exact terms, at most once per personal agent. The gap this extension fills.
Where John's locator resolves to his card, which names his agents.