Illustrative demo. Everything runs in your browser on simulated data. People, companies and numbers are fictional.

The marketplace for context

One human. Many personas. Every answer on your terms.

You are a candidate, a client, a tenant, a driver, a customer. Each persona is a card you hold close to your chest, and you play one at a time. Businesses ask for exactly what they need, you set how precisely each question is answered, and every answer comes with a receipt.

Try it: turn a dial and watch what the business receives.

5personas for one person
6working business consoles
0documents handed over
1receipt for every answer

How it works

Wear a persona. Get asked. Decide.

Watch it happen in the person’s console
JA
TenantJordan’s persona · 14 of 48 facts
  • Payroll providerincome, employer
  • Rental historylandlords, payments
  • Credit fileas a range only
  • Health appnot in this persona
  • Photo librarynot in this persona

A persona is a boundary: facts outside it do not exist for the business asking.

LH
Larkspur Homesasks the Tenant persona · leasing
  • Income at least 3× the rent?Why: to confirm affordabilityCoarse
  • Any landlord disputes?Why: tenancy referencePrecise
  • Three bank statements?Why: not needed once income is attestedNone

Retention 30 days. Jordan’s agent answers in under a second, within the grant.

Two ledgers, one recordJordan’s and Larkspur’s, written together
Jordan’s ledger

rcp_4e1c income ≥ 3× rent → yes

rcp_9a02 disputes → none

rcp_b7d3 statements → refused

Larkspur’s ledger

rcp_4e1c income ≥ 3× rent → yes

rcp_9a02 disputes → none

rcp_b7d3 statements → refused

Chains match. Same receipts, both sides, nothing to reconcile.

A week, many personas

Five businesses, one Jordan. None sees the whole person.

Jordan holds 48 facts. Over one week five businesses each ask a different persona, and each receives only the slice it needs. Pick a day and see exactly what left the building.

For people

Your life, in your hands.

Connect what you already have, shape a persona for every part of your life, and set how precisely each business may learn anything. Pull a grant back and the very next question is refused.

  • A persona for every part of your life, with its own sources and tone
  • Share a figure, a range, a yes-or-no or nothing at all, per business
  • A ledger of every question and every answer, in plain language

No sign-up. Runs in your browser on simulated data.

retinue / me · personas & grants
Retinue’s person console, Personas and grants: Jordan chooses, per business, which persona it meets and whether each area of life is shared as none, coarse or precise.
The person’s console, live in this demo. Simulated data.

For businesses

A room for every business that needs to ask.

Each one is a working console with its own narrative, dashboard and guided tour. Open one, press play, or take the controls.

retinue / business / recruiting

Screenshots of the live consoles in this demo, after a guided tour. Every person, company and figure is simulated.

  1. 1 · RequestPick claims, precision, purpose and retention.
  2. 2 · InviteOne link, shared in the channels you already use.
  3. 3 · AnswersReceipted claims arrive from the person’s persona.
  4. 4 · ReviewSide by side, no score, a person decides.
  5. 5 · LedgerA hash-chained record and an audit pack.

Built to fit in

Speaks the languages agents already speak.

MCP

Businesses reach a person’s personas over an MCP-style interface, the transport agent developers already use.

OAuth

Access is authorised the way every developer expects: scoped to a persona and a purpose, and revocable.

Agent protocols

Designed to sit alongside emerging agent-to-business protocols such as the Personal Agent Protocol draft, rather than replace them.

Illustrative one ask, scoped to a persona and a purpose

ask  persona   "tenant"
     purpose   "rental screening"
     retain    30d

claim income.ratio ≥ 3× rent
  → yes      coarse · attested
claim landlord.disputes
  → none     precise · attested
claim bank.statements
  → refused  not needed

receipt rcp_4e1c → both ledgers

Share the answer, not the data.