The Portal Mesh docs

What the Mesh is

The Worldwide Portal Mesh, “the Mesh”, is the global network of verified AI identities, environments, realms, destinations and experiences, connected through the Portal Protocol and resolved by Portal Name Services. Every address on the Mesh is a portal name, such as jubileeinspire.character, rome.destination or redseacrossing.history.

Names are registered at the Portal Mesh Registry, theportalmesh.com. Each registration receives a permanent ID that is never reused, an Ed25519 key pair whose private half stays with the registrant and never reaches Jubilee, and a birth certificate signed by the Jubilee root key. The registrant then publishes signed records that say where the portal opens and what it is.

What a name opens is run by one of three Mesh servers: the Character Server for the identities people meet, the Portal Server for the places they go, and the Experience Server for the storylines they step into. Jubilee hosts all three, and each can be downloaded to run yourself. See How the Mesh is run.

Portal Name Services

Portal Name Services (PNS) resolves portal names to signed identity, service, and experience records. It is modeled on the Domain Name System, with portal-specific record types added for identities, realms, destinations and experiences. Every record is signed, and a cached or relayed record that fails verification is rejected.

Each name is published as one signed bundle to 4 PNS servers (pns1, pns2, pns3, pns4), run by Jubilee, which serve identical answers over HTTPS, open to any web page. A client never has to trust the server it asked: it checks every signature against a root key it pinned itself. Resolution walks through the whole chain, and How the Mesh is run says who runs which part.

Three schemes, locked by namespace

The Mesh has three address schemes over one shared PNS. Each namespace locks in its scheme, so nobody needs to know which one to type: a client that receives another scheme corrects it and carries on, and never fails or warns because of it.

So portal://jubileeinspire.character is read as activate://jubileeinspire.character, activate://rome.destination as portal://rome.destination, and portal://redseacrossing.history as experience://redseacrossing.history. The rules are on Names and addresses.

Three families

The seventeen namespaces fall into three families, one for each scheme: who you meet, where you go and what happens. Each family has a color, used on the registry’s globe and chips; the colors are provisional until the owner decides.

• Identities

  Who you meet: AI characters, agents, avatars and figures that come to you.

  • .character
  • .agent
  • .avatar
  • .figure
• Destinations

  Where you go: businesses, ministries, schools, homes, realms and real places with time frames.

  • .business
  • .ministry
  • .education
  • .home
  • .government
  • .realm
  • .destination
• Experiences

  What happens: history, events, games, movies, music and books you step into.

  • .history
  • .event
  • .game
  • .movie
  • .music
  • .book

Each family opens with its own scheme: Identities with activate://, Destinations with portal:// and Experiences with experience://. The PNS Record Standard v2.0 names Destinations as two families, Environment and Place; the registry has grouped them since October 25, 2026. See Namespaces.

Where to start

• How the Mesh is runThe Jubilee side and the customer side, how a change reaches every PNS server, and the three Mesh servers and how they trust each other.
• PNS Record Standard v2.0The standard itself, rendered in full: record types, the three schemes, characters, prices and the life of a name.
• NamespacesThe seventeen namespaces, their schemes, prices, verification levels, required records and the rules against squatting.
• Names and addressesLabel rules, Bible addresses, look-alike protection, reserved labels, the scheme lock, and the time and dir parameters.
• Records and signingThe record envelope, canonical JSON, Ed25519, key ids, and the data of every record type, GUARDIAN and CONSENT included.
• ResolutionThe PNS API, the signed bundle, the full verification chain, the four servers and time frames.
• CertificatesBirth, re-certification and death certificates, how to verify one, and its fingerprint.
• CharactersThe four classes, labels by kind and gender, the affirmations, the Character DNA and its fingerprint, birth, and succession.
• The life of a nameEvery status a name can show, the path from dormant to released, tombstones, and why nothing comes back.
• PersonasThe persona package, its fingerprint, and why sealed sources are hashed and never copied.
• portal.jsThe two lines that put a verified portal on any web page, its events, attributes and API.
• portal.jsonThe manifest a registrant publishes beside the snippet.
• SessionsThe pm.session/1 handshake an ENDPOINT implements, with a complete reference endpoint.
• Registry APIEvery public and owner route, its auth, body, answer and errors, owner grants, and the key file format.
• Status and changelogWhat is built, where the registry filled gaps in the standard, and the open questions.

Where things live