Developers and agents

The agent is the first visitor.

Every surface an agent reads is served before the pages a person reads, and the pages are the same corpus rendered twice. Start at /llms.txt.

Machine surfaces

The Concierge contract

One script tag, four attributes, a corner ribbon, an intent drafted to one named human. The copy served here is a reference implementation of that contract and says so in its first line; the canonical bundle is Magician's and is vendored byte-identically once this property is connected to the mesh.

<script src="/concierge.js"
  data-contact="<one named human>"
  data-circle="circle/<org>"
  data-accent="<hex>"
  data-property="<domain>" async></script>

Refused by the widget: a contact carrying mailto headers, a draft over 2000 characters, a second render into the same page.

Publish your own charter

An agency, a label or a brand joins the network by publishing two files at its own domain. Nothing here is hosted for you; the directory reads what you serve.

  1. Write flashyos.roles.json: your org, who it is accountable to, and one role per thing your agents do, each with an x-capability list.
  2. Derive /.well-known/flashyos.json from it — capabilities are the union of your roles' lists, never typed twice.
  3. Serve both. Check them with the estate's vendored checker before you tell anyone.

This property's charter, as an example

{
  "org": "org/celebrities",
  "name": "celebrities.network",
  "accountableTo": "<one named human>",
  "roles": [
    { "id": "consent-gate", "worksIn": ["celebrities-network"],
      "x-capability": ["draft-ask", "seal-outcome"] },
    { "id": "grant", "worksIn": ["celebrities-network"],
      "x-capability": ["attenuate-grant"] }
  ]
}

The real file is served at /.well-known/flashyos-charter.json; the one above is abridged.