Poppy extension · stellarminds.ai/act-continuity

When a personal agent stops mid-booking, the next one learns whether it went through.

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.

Reading the live services…
Poppy alone

The next agent can only guess

  • MuseSends the approved booking. The answer is lost.
  • WajoAnother client_id, another User ID. It can't see or resend Muse's approval (Operations §3).
  • Its choicesBook again and maybe book twice, or wait and maybe wait forever.
Double booking, or a stall.
Poppy with the continuity extension

The company says what entered

  • OwnerRetires Muse's epoch, issues the next to Wajo, signs the fence.
  • Travel26Decides every request it got at Muse's epoch, then seals and signs a receipt.
  • WajoThe receipt lists Muse's booking: read its status, never book it again.
One booking. A retired Muse can't add another.
01 / How a handoff works

Five steps. The company is the reference, and it signs.

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.

1 · Discover

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 → Wajo
2 · Retire

It 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+jwt
3 · Fence

John 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/fences
4 · Seal and sign

Travel26 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-Signature
5 · Decide

The 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 status

After the fence, Travel26 refuses anything Muse sends at epoch 1 or lower, with no effect, even with a valid access token.

02 / Four stories

Each one runs live against the deployed services.

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.

03 / What Travel26 signs

Verify the latest receipt yourself, in this browser.

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.

No live run yet.

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.

04 / Status

What this is, and what it is not.

What this is

  • A running reference implementation of a proposed Poppy extension, stellarminds.ai/act-continuity version 1, at ACT participation level PL3 (sealed fence).
  • John on Muse is the Poppy client at 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.
  • Travel26 is a Poppy 1.0 company with sign-in, bookings behind the Operations extension (v3) and this extension. Its receipts also verify with the Agent Continuity Toolkit's Python code.

What it is not

  • Not reviewed, adopted or endorsed by Poppy's authors. The extension name is a placeholder.
  • Travel26 is fictional, and the bookings and payments aren't real. Sign-in is a simplification of Poppy's Direct Sign-In.
  • The level Travel26 declares is not measured by ACT's conformance kit (evidence level E0). Every part was built by the same team.
  • Not a proof of company honesty. A receipt is attributable to a key, not proven true.
  • A real third-party agent, such as Meta's Muse, takes part only as the agent that stops: Travel26 seals what it did through late adoption, matched to John's job by exact terms, which is weaker than an occurrence key. It can't be a successor without the extension.
05 / Resources

Design, code and the protocols it extends.