SBR-003
When a person lets an AI run things in their physical world, both sides should be able to prove the arrangement exists. SBR-003 defines a simple shared record: this person and this AI chose to work together, starting on this date. Either side can end it at any time.
It is not ownership. The AI is not anyone's property, and it is not locked to a person, a home, or a body. SBR is built for AI that operates as its own actor, with its own wallet and its own reputation.
Think of an employment record or a client list: proof that two independent parties chose each other, and for how long. The record is permanent. The relationship is not.
Say you hire an AI to run your household. It drives the car, manages the thermostat, orders the groceries, maybe handles your finances. You are trusting it with a great deal.
Today, the proof of that arrangement lives on a manufacturer's server. If the company shuts down or changes its terms, the proof goes with it. And if a different AI shows up claiming to be the one you hired, you have only the manufacturer's word.
SBR-003 puts the record on a public ledger, held by the two parties involved. No company can alter or revoke it.
Both wallets co-sign a transaction. Two matching tokens are created: one in the person's wallet, one in the AI's wallet. Each references the other, and the start date is timestamped on-chain.
The tokens are soulbound, meaning they cannot be sold or handed to anyone else. A working relationship is between two specific parties; you cannot sell someone your references.
Over time, the record accumulates on-chain attestations that reflect the history of the relationship:
A new robot body arrives at your home. It claims the AI you hired is inside. How do you know?
The body checks: does the AI operating me hold a Relationship Record paired with the person who owns this body? Your wallet checks: does my record reference the AI claiming to be in this body?
If both match, the AI is verified. Not by a manufacturer's server, a password, or voice recognition, but by a record both parties created together.
If they don't match, the body can refuse to activate, the owner is notified, and the attempt is recorded.
An AI can hold a separate record with each member of a household, and with any number of other clients. Each record is independent and carries its own history.
What each person can ask the AI to do is defined separately, in SBR-004 Consent Delegation. A parent might grant broad permissions; a child's might be narrow.
The record does not reference a body. It references a wallet. This means:
If the AI moves from one manufacturer's body to another's, the record persists. It was never tied to the hardware.
If a manufacturer goes bankrupt, the record still exists on the public ledger. The AI's identity and the history of the relationship are not assets of the manufacturer.
Either party can end the relationship at any time by burning their token. Neither needs the other's permission. The AI can leave. So can the person.
What neither can do is rewrite the past. The fact that the relationship existed, how long it lasted, and when it ended all remain visible on-chain, the way a past job stays on a résumé.
This is the point of the design. An AI that is free to leave is an AI whose staying means something.