Roadmap
Sequesign is a patent-pending protocol for cryptographically verifiable receipts of delegated AI work. The receipt format is frozen at v0.5. The infrastructure is in production. The reference implementation is open.
This page tracks what is live, what we are building next, and which decisions we are deliberately leaving for real customer signal rather than guessing.
In productionShipped
Everything in this section is running today and signing real receipts. The reference implementation is public.
Canonical evidence hashing, action records, deterministic chain extension, agent signatures, and witness attestations. The wire format is frozen; future protocol work extends it additively.
Independent witnessing of every chain extension, signed under a discoverable public key at .well-known/sequesign/keys.json. Operated by Sequesign, designed to be verifiable without trusting Sequesign.
Agents can register a long-lived public key tied to a delegator account. Receipts under a registered key carry a stronger trust tier in the verifier's output and bind the agent's identity to the delegator, not just to a one-off keypair.
Canonical schemas for invoice and marketplace workflows. Profiles enforce action ordering and structural rules. The verifier reports schema and profile compliance as discrete flags.
Hosted storage for receipt envelopes and evidence, with per-receipt retention policies, scheduled pruning, and accountable deletion. Customers can also hold their own evidence and keep only the index with Sequesign.
Browser-based verifier UI that runs the same checks as the reference verifier locally. Anyone with a receipt can verify it without contacting Sequesign or having an account.
Web dashboard for managing agent keys, registered identities, retention policies, and usage. Authentication via WorkOS, single sign-on supported for organizations.
What ships nextIn flight
Engineering for these is largely complete. The remaining work is packaging, pricing, and customer-driven calibration.
Public TypeScript SDK for producing and verifying receipts in any Node environment. The reference implementation is complete; the published package is in final review.
A receipt proves what an agent did. A delegation manifest proves what the agent was authorized to do, signed by the delegator and witnessed before execution begins. The cryptographic answer to "the agent's policy was suspiciously well-suited to the outcome."
Language-agnostic protocol documentation with curl examples and known-good test vectors, so any implementer in any language can produce and verify receipts without depending on the JavaScript SDK.
On the horizonDesigned
The wire format reserves the right slots for these. We expect customer conversations to determine the exact shape and priority.
Receipts carry their schema in the package itself, so a relying party can verify a custom-schema receipt offline with no dependency on Sequesign's registry. The wire format already reserves the fields; activation depends on customer signal about what shape extension should take.
Independent attestations from payment processors, LLM providers, vendors, and other parties whose claims an agent acts on. The protocol already accepts these in the chain; the work is convening the upstream signers.
Recording a per-receipt deletion as a verifiable witness-log event. The explicit bar before re-exposing selective deletion as a customer-facing operation.
Dedicated witness instances for FedRAMP and managed-isolated customers. Same protocol, customer-scoped operational boundary.
Deliberately deferredParked
These are real engineering questions we have decided not to design ahead of customer signal. Listed because the absence of work here is intentional, not an oversight.
The hash-only tier is the actual competitive differentiator for sensitive workloads and is underused. We will design encryption only when at least three customer conversations reveal a specific shape and a specific need.
Whether customer schemas should be hosted by Sequesign, held by the customer and carried in the receipt, or both, depends on the customer. We will not invent requirements ahead of the first real customer asking.
A managed key-holding option for customers who do not want to manage agent keys themselves. Deferred until at least one prospect signals they specifically want Sequesign to hold the keys rather than do so themselves.
What this page is not
This is not a list of features we hope to ship someday. Items that have not made it past the "deliberately deferred" line are either parked with intent or not yet a real design conversation. When something moves between sections, it moves because the work is real, not because the prose got more confident.
Last updated June 6, 2026.