The trust tasks of the City

What the members, visitors and services of Mages City ask of each other, written down so that each side can check it. An open list, and an open door to help write the next one, for this community or yours.

A trust taskis one thing one party asks of another, written so both sides can check it: who asks whom, what is carried, what changes, what is disclosed. The shape comes from the Trust over IP Trust Tasks framework.
A familyis the set of trust tasks one community speaks: its interface. This is the City’s: 14 tasks and one ceremony, all drafts.
An intentis what a person does on their own device: a thumbs up kept in the browser, a note sealed, a gate opened. It is not a task until something is sent. Intents

The mages family

Each name opens its specification, and each Type URI is its own address: https://tasks.mages.city/spec/mages/<name>/0.1. “Records” means the recipient keeps something (a link on a chain, a queued word, a sealed copy); “checks only” means it answers and keeps nothing.

At the guide

The Hitchhiker's Guide to Trust (trust.mages.city): a night in a room, a chain of what happened.

taskwhat it doeswho asks whomeffect · today
presence/thumbA visitor sends a thumbs up, "I was here", to a guide that keeps a chain; the guide appends a link under the visitor's mark (a witness link when the room's code is given) and holds the digest of the visitor's claim code for later.Visitor → Guiderecords
live
meet/openA visitor opens a meeting at the guide and gets a five-character code to show the person they are meeting; nothing is on the chain yet.Opener → Guiderecords
live
meet/acceptThe person shown a meeting code says yes with their own mark; the guide records them as the meeting's second party, and only the opener can now confirm the edge.Acceptor → Guiderecords
live
meet/confirmThe visitor who opened a meeting confirms it after the other has said yes, and the guide appends one bilateral meet edge (both marks) to its chain; two phones, two yeses, one edge.Opener → Guiderecords
live
⟲ meet (ceremony)The three steps above as one rite: two phones, two yeses, one edge.opener, acceptor, guideceremony
proverb/submitA visitor sends a proverb, a poem or a guide (a place and its first clue) to the guide's keeper; the words wait in the keeper's queue and only their leaf goes on the chain, under the visitor's mark.Visitor → Guiderecords
live
voice/commitA visitor puts a voice note on the guide's chain by its hash. Proof by default; the audio stays sealed on the phone; only a note offered to Hitchhiker FM is stored, sealed and open, with a cap per visitor.Visitor → Guiderecords
live
voice/shareAfter the fact and by choice, a visitor shares one of their committed voice notes with the keeper; the phone seals a copy to the keeper's public key, the guide stores what it cannot open, and the audio's hash goes on the chain.Visitor → Guiderecords
live

Stars and seasons

agentprivacy.ai: stars made on the device, committed once a moon, sealed for the City.

taskwhat it doeswho asks whomeffect · today
constellation/commitOnce per moon, a visitor sends up to 42 deliberate stars, as hashes only, to the shared stars chain, with this moon's hidden star and a proof of work; the chain appends them and answers with where they landed.Visitor → Stars chainrecords
built
island/stoneA walker presents the stone proof of a Drake Island walk (the quests in order and the stone laid at the threshold, each with its revealed preimage) and the verifier answers with the five checks, re-derived from nothing but hashes.Walker → Verifierchecks only
live
moon/sealWhen a moon closes, the chain keeper seals that moon's rows of the shared stars chain as a scroll (every row and the root they fold to) and sends it to Mages City, which re-derives the root before recording it.Chain keeper → Mages Cityrecords
draft

Keys and artefacts

What a bearer carries between the sites: the City Key, and blades forged in spellweb.

taskwhat it doeswho asks whomeffect · today
city-key/presentA bearer presents their City Key, with any packets and chain faces it claims, to a Mages City reader; the reader re-derives what it can and answers with one of four states per claim, never a permission.Bearer → City readerchecks only
live
artefact/presentA bearer presents an artefact forged or witnessed in the spellweb ceremony (its blade, the constellation it was evoked from, and the blade's place on the bearer's chain), and the verifier answers with the checks it could re-derive.Bearer → Verifierchecks only
built

Keeping the record

The keeper's answers, and evidence sealed as scrolls.

taskwhat it doeswho asks whomeffect · today
contribution/disposeThe guide's keeper answers one contribution (a note, a request, a recording) by its hash, as addressed (with the guide root where the change lives), declined, deferred or kept private, so no contribution is left without an answer.Keeper → Contributorrecords
built
scroll/sealA mage asks Mages City to seal one or more κ evidence bundles as a scroll on its own mages.city subdomain; the City re-derives each bundle's root, publishes nothing but hashes, dates and numerals, and joins the hashes to its seal ledger.Mage → Mages Cityrecords
live

What the City takes from the public registry

Most of what a community does is already in the public registry. The City writes its own task only where nothing there fits, and uses these instead:

in the Citypublic trust tasks
A guide night, a quest, a blade, once you are a membervtc/badges/create, vtc/badges/claims/create, vtc/badges/claims/redeem, vtc/badges/awards/offer
Joining the Cityvtc/join-requests/manifest, vtc/join-requests/submit
An edge between two members who metvrc/relationships/propose, vrc/relationships/issue
Vouching for a membervtc/endorsements/issue, vtc/endorsement-types
Inviting someone by namevtc/invitations/issue, vtc/invitations/deliver
A run of agentic work, with its evidenceprocess-attestation
A chronicle or a sealed season, as the record of a ceremonytrust-ceremony-receipt
A member signing what they sendvault/sign-trust-task
Every refusal and plain acknowledgementtrust-task-error, trust-task-ok

The whole registry, 903 tasks, read for what a community like this one uses, takes or leaves: the registry, read.

Build with it

Where each task goes today. Every task above runs, or is built, in its own JSON shape, and its page says where (“Today: …”). live runs now; built is made and tested but not switched on; draft is written, not built. No site accepts this document form yet. The sites move to it one at a time, starting with the guide at trust.mages.city. Until a task’s page says it accepts documents, build against its spec and expect its own JSON on the wire.

Who is who. Mages City, the community, is did:webvh:QmQ8GMNCTui2H9gjxQWByS1ScsWkByaeQHYnzhcET1UPne:dids.mages.city:vtc; its DID log resolves at dids.mages.city. Other service identifiers in the examples are placeholders until those services publish their own: which are real and which are not.

Before and after joining. A visitor who has not joined sends under a mark, a hash of a secret kept on their device, with no signature. A member’s agent signs what they send (vault/sign-trust-task), with a proof on the document:

{
  "id": "urn:uuid:4f2a9c61-0d8e-4b37-a1f5-9e3c7b2d6a10",
  "type": "https://tasks.mages.city/spec/mages/city-key/present/0.1",
  "issuer": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
  "recipient": "did:webvh:QmQ8GMNCTui2H9gjxQWByS1ScsWkByaeQHYnzhcET1UPne:dids.mages.city:vtc",
  "issuedAt": "2026-11-17T10:00:00Z",
  "payload": {
    "key": {
      "kind": "agentprivacy.vta/1",
      "kappa": "sha256:6e1d…"
    }
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "verificationMethod": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK#z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
    "created": "2026-11-17T10:00:00Z",
    "proofPurpose": "authentication",
    "proofValue": "z… (illustrative: the member’s agent signs the document’s canonical form)"
  }
}

Asking the City what it speaks. A community answers trust-task-discovery with the Type URIs it accepts. The City’s VTC will; until then the same list is family.json.

Help define a community’s trust tasks

Every Verifiable Trust Community will speak tasks that no registry holds yet: its own rites, its own records, its own ways of saying “I was there”. Those tasks are the community’s interface, and they are better written together than alone. If you build on OpenVTC, or keep a community of your own, this is an invitation.

How this family was made, in four steps anyone can repeat:

  1. Read the code, not the wish. Each task here describes something a site already does, endpoint by endpoint.
  2. Write each act as a specification: who asks whom, the payload and its schema, what it changes, what it discloses, and what it refuses.
  3. Check it with the task force’s own validator, unchanged, against the public registry.
  4. Keep it under your own domain (SPEC §6.5) until others need it; then propose it to the registry, and use the registry’s own tasks wherever they already fit.

Start with the kit. The trust tasks starter kit has the template (front matter, schema, invalid examples), a scaffold that writes a new task which already passes the validator, and the script that checks your family with the task force’s own tooling: node tools/new-task.mjs <family>/<area>/<verb>, then node tools/check.mjs <TF checkout>.

Propose a task for the City

Open an issue in the kit with the “Propose a trust task” template. A task joins the City’s family when three things hold: it describes something that already runs, no task in the public registry fits it, and it passes the check. The City’s keeper reviews proposals and answers each one. To list your own community’s family beside this one, open an issue with the address it is served at. Where the public registry itself needs to change, raise it with the task force, where that work belongs.

Drafts, version 0.1, private Trust Task specifications (SPEC §6.5) published by the City under its own domain. Every specification here passes the Trust Tasks task force's own validator against its registry at 0cdf9e517 (17 Nov 2026). Formal models of the family and of the public registry: trust-tasks-formal. Nothing here is on the wire yet: the City's sites still speak their own shapes, and move to these one at a time. Text: CC BY 4.0; schemas and tools: Apache-2.0.