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 charter, and your asks

A partner organisation joins the network by publishing two files at its own domain, and is read by this index by publishing a third. Nothing here is hosted for you; the index 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. Publish your open asks at /.well-known/backlog.json, in your own words, no figure. The index reads the titles and nothing else.

This property's charter, as an example

{
  "org": "org/kulture",
  "name": "kulture.network",
  "accountableTo": "<one named human>",
  "roles": [
    { "id": "index", "worksIn": ["kulture-network"],
      "x-capability": ["measure-tally", "read-demand"] },
    { "id": "publish", "worksIn": ["kulture-network"],
      "x-capability": ["publish-handshake", "publish-llms"] }
  ]
}

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