{
  "contract": "course-content/1",
  "slug": "entering-the-record",
  "title": "Entering the Record",
  "primitive": "The record",
  "audience": "Anyone whose organization should be findable, mergeable, and cited rather than described",
  "summary": "How an organization becomes a node in a graph nobody maintains by hand: the directory (directory/1), fragments and edges, the consent that gates a boundary-crossing claim, the public projection, and why a settled edge is derived rather than posted.",
  "track": "working-with-agents",
  "pin": {
    "source": "@flashyos/directory — federated fragments, the merge, the validator",
    "ref": "flashyos:packages/directory",
    "revision": "a75060a693c9e628564a9dc7410d847e6feb88b3",
    "state": "current"
  },
  "intro": [
    "The record is how the estate — or anyone else — merges organizations into one graph without a list somebody keeps by hand. This track is what that record is made of and how you enter it honestly.",
    "The idea to carry through: the record is append-only and consent-gated. You can always add what you say about yourself; a claim that reaches across to another organization becomes real only when that organization signs it.",
    "Four lessons. Every mechanism here is a real file an organization serves and a real validator anyone can run."
  ],
  "lessons": [
    {
      "n": "01",
      "title": "A fragment, and the merge",
      "outcome": "Describe how federated fragments become one graph without a central list.",
      "body": [
        "Each organization publishes a directory/1 fragment: nodes for what it is, edges for its relationships, served from its own domain. Nobody maintains a master list. A merge reads every fragment and folds them into one graph, and a validator checks each fragment against the spec before it is trusted.",
        "This is federation rather than a registry: the record of an organization lives where the organization serves it, and the graph is a view computed over all of them. The estate can go down and your fragment still describes you.",
        "You enter the record the same way anyone reads it: you serve the file. The emitter writes the fragment from what you already declare, so the record and the charter cannot drift apart into two stories."
      ],
      "source": {
        "label": "Flashy OS — @flashyos/directory",
        "href": "https://flashyos.com/packages"
      }
    },
    {
      "n": "02",
      "title": "Only the other side consents to crossing a boundary",
      "outcome": "Explain why a claim about a relationship needs the counterparty’s signature.",
      "body": [
        "Every write to the record lands as proposed. A claim that stays inside your own organization can proceed on your say-so. A claim that crosses a boundary — an edge naming another organization — reaches its countersigned state only when a human at the other organization signs it.",
        "This is the estate’s deepest rule applied to the record: agents suggest, humans consent. An agent may draft the edge, but nobody’s machine turns a proposal into a mutual fact, and there is no setting that auto-approves one.",
        "The consequence for a reader: a countersigned edge is a claim both sides stand behind, while a proposal is one side talking. The public record shows the first and never the second."
      ],
      "source": {
        "label": "Flashy Academy — Running a Joint Initiative",
        "href": "/academy/curriculum/running-a-joint-initiative"
      }
    },
    {
      "n": "03",
      "title": "The public projection: private is indistinguishable from missing",
      "outcome": "Explain why being unlisted and not existing look identical from outside.",
      "body": [
        "The public projection of the record never queries proposals, private-tier rows, or superseded entries — they are absent from the query, not filtered out after it. What a stranger sees is what has been earned and consented to, and nothing else.",
        "A private organization is deliberately indistinguishable from one that does not exist: existence is itself information an organization gets to withhold. Being in the record publicly is earned by publishing and being verified, and it lapses — in public — when that stops.",
        "So the record is not a phone book of everyone who signed up. It is the set of claims that are both consented to and current, which is exactly the set a reader can rely on."
      ]
    },
    {
      "n": "04",
      "title": "A settled edge is derived, not posted",
      "outcome": "Explain why the record of completed work cannot be written by the parties directly.",
      "body": [
        "When two organizations complete a joint initiative, a settled edge appears in the record. Unlike an ordinary edge, nobody posts it: it is a projection derived from a sealed settlement, so it exists only because the work was sealed, not because someone claimed it.",
        "That is why a settled edge legitimately skips the propose-and-countersign flow — it is not a claim a caller could make, it is a consequence of a settlement that already happened and is already verifiable. A settlement with nothing sealed against it produces no edge.",
        "The lesson generalizes: the most trustworthy entries in any record are the ones no party could have written directly. When you see a derived edge, you are reading the shape of work that occurred, not the shape of what someone wanted you to believe."
      ],
      "source": {
        "label": "Flashy Network — the public face of the mesh",
        "href": "https://flashynetwork.com"
      }
    }
  ],
  "faqs": [
    {
      "q": "How does my organization get into the record?",
      "a": "Serve a directory/1 fragment from your own domain, emitted from what you already declare. The merge reads it the way anyone does — by fetching it — so there is no central list to be added to."
    },
    {
      "q": "Can I add an edge saying I work with another organization?",
      "a": "You can propose it, but it only becomes a public, countersigned fact when a human at that organization signs it. Agents suggest; humans consent; there is no auto-approval for a boundary-crossing claim."
    },
    {
      "q": "Why can’t I just publish that a piece of work settled?",
      "a": "Because a settled edge is derived from a sealed settlement, not posted. It exists because the work was sealed and is verifiable, which is exactly what makes it worth more than a claim you could write yourself."
    }
  ],
  "related": [
    {
      "label": "Joining the Mesh",
      "href": "/academy/curriculum/joining-the-mesh"
    },
    {
      "label": "The Verifiable Record",
      "href": "/academy/curriculum/the-verifiable-record"
    },
    {
      "label": "Opening a Front Door",
      "href": "/academy/curriculum/opening-a-front-door"
    }
  ]
}