Platform

Shared Record

In development · pilot pairs by application

Shared Record is a record of what two companies' AI agents exchanged, signed by both sides and checkable by anyone offline. It is the next chapter of the AI Runtime Control Plane: the same boundary that decides each call also signs a receipt for it.

A pilot version is built and in testing. It is not in production or available to customers.

How it works in the pilot version

How Shared Record worksDiagram: company A's agent sends a call with a receipt company A signs to company B's agent (1); company B returns a signed acknowledgement (2); both register fingerprints on a shared log that both companies witness (3); an outside party verifies the exported records offline (4).Company AAI agentCompany BAI agentCall + signed receipt1Signed acknowledgement2Shared logFingerprints only · witnessed by both3Outside verifierChecks the export offline4
  1. Your agent sends a call with a signed receipt. Your company signs a receipt for the call, carrying your boundary's decision: allowed, redacted or blocked. A blocked call is not delivered; your partner gets a signed notice instead.
  2. Your partner signs an acknowledgement. Your partner's side checks the receipt against the content it received, applies its own boundary and signs an acknowledgement.
  3. Both register fingerprints on a shared log. Each side registers fingerprints (salted hashes) of what it signed on a shared log that both companies witness.
  4. Anyone can check it offline. In a dispute, either side exports the signed records, and anyone can verify them offline with Norcaster's verifier, which will be published.

If no acknowledgement arrives by the deadline, the sender records that too.

The pieces

Receipt (Shared Record)

What the sending company signs for each call to a partner's agent: who sent it, a fingerprint of the content, and the sender's boundary decision (allowed, redacted or blocked). In development.

Acknowledgement (Shared Record)

What the receiving company signs to say it received a call, whether the content matched the receipt, and what its own boundary decided. In development.

Hub (Shared Record)

In a Shared Record pilot, the Norcaster customer whose agents exchange calls with one to three partners. In development.

Counterparty (Shared Record)

A company that exchanges agent calls with a hub. It runs a free, self-hosted component, keeps its own keys and needs no Norcaster account. In development.

Witness (Shared Record)

A company that checks each update to the shared log against the history it saw before, and cosigns it, so a rewritten or split history is detected. In a pilot, both companies witness. In development.

Dispute export (Shared Record)

The signed records for chosen exchanges, with their log proofs and both companies' key documents, which anyone can verify offline. Either side can reveal the content of an exchange it chooses. In development.

What the shared log sees

Fingerprints (salted hashes), organisation and key ids, and times, plus each company's published key document, which names the company and the agents it exposes to partners. Never message content.

Keys and trust

Our goal: nobody in the middle has to be trusted, including us.

  • Norcaster runs the pilot log. The log never receives message content, and Norcaster cannot rewrite or split its history without the witnesses detecting it.
  • Pilot hubs hold their own root key, in their own KMS or Sync Agent.
  • In hosted mode, Norcaster holds a company's short-lived signing keys, so that company relies on Norcaster for its own signatures. Self-hosted or customer-held keys remove that.

Partners

They join free, run a small component on their own servers and keep their own keys. No Norcaster account needed.

Standards

  • Designed on the IETF SCITT architecture (RFC 9943).
  • Works with MCP tool calls in the pilot version. A2A and agent-SDK bindings are in design; one SDK binding is in testing.
  • Payment credentials such as AP2 mandates and Mastercard Verifiable Intent are designed to travel inside an exchange as content (in design). Shared Record records them; it does not replace or check them.

Status

A pilot version is built and in testing. It is not in production or available to customers.

Built and in testing

  • A draft protocol, designed on the IETF SCITT architecture
  • Receipts signed by the sender and acknowledgements signed by the receiver
  • Notices for blocked calls and records of missing acknowledgements
  • A shared log witnessed by both companies
  • Dispute exports
  • A portal page in Norcaster (Govern → Shared record)
  • A free, self-hosted component for partners
  • An offline verifier in Python and Node
  • A two-company demo

Not yet

  • The verifier and the partner component are not published
  • No outside review of the protocol
  • No customer pilot
  • Not in production

What Norcaster does today: Norcaster's evidence records are hash-chained and anchored to a public transparency log, and audit bundles can be verified offline without a Norcaster login. A record that two companies both sign is what Shared Record adds.

Taking part

Pilot pairs are by application: one hub and one to three partners, thirty days of real exchanges, and a dispute drill at the end in which an outside party verifies the evidence offline.

Shared Record →Apply for a pilot pair →