{
  "contract": "course-content/1",
  "slug": "proving-what-you-ship",
  "title": "Proving What You Ship",
  "primitive": "Practising your own documented standard",
  "audience": "Anyone publishing a property, package or protocol into the estate",
  "summary": "How the Activation standard, a vendored charter checker and the AAO launch gate turn 'we follow the standard' into something a stranger can verify — using flashy.tools's own suite as the worked example of a property that passes what it documents.",
  "track": "the-estates-developer-tools",
  "pin": {
    "source": "flashy.tools's own suite — the Activation standard, a vendored charter checker, the AAO launch gate, run against its own live domain",
    "state": "unverifiable"
  },
  "intro": [
    "Publishing documentation about a standard and actually meeting it are two different claims, and only one of them is checkable from outside. This track is about the second one: the concrete mechanics the estate uses so a property's claim to follow a standard is provable, not just written down.",
    "flashy.tools is the worked example throughout, because it is unusual in the estate for being both a teacher of these mechanics and a subject of them — its own suite runs the same vendored checks it documents.",
    "Three lessons. Take Writing Your Charter first if the charter itself is new to you; this track is about proving you actually serve what you wrote."
  ],
  "lessons": [
    {
      "n": "01",
      "title": "The Activation standard: four artifacts, checked for real",
      "outcome": "Name the four artifacts the Activation standard checks and why each is verified rather than declared.",
      "body": [
        "A property claiming to be reachable by an agent needs more than a sentence saying so. The Activation standard checks four concrete artifacts: a served machine surface (the flashyos/1 handshake), a working concierge entry point, a visible concierge page a person can read, and something a stranger can actually try — a live demo rather than only a description of one.",
        "Each is checked, not declared. A property that serves the handshake but has no working demo reads as partially activated, and the standard says so by name rather than rounding up to 'launched.' That distinction matters because a stranger deciding whether to work with an agent economy reads these signals to decide whether the thing in front of them is real.",
        "flashy.tools documents this standard and is itself checked against it in the same suite that checks every other property — which is the difference this track is built around: a standard that only ever appears in prose is a standard nobody has verified holds."
      ],
      "source": {
        "label": "Magician — the Activation standard and its dependency-free check",
        "href": "https://magician.network/concierge"
      }
    },
    {
      "n": "02",
      "title": "The vendored charter checker: one implementation, copied never rewritten",
      "outcome": "Explain why a charter checker is vendored byte-identical rather than reimplemented per property.",
      "body": [
        "The estate learned this the expensive way: eleven vendored copies of a charter checker once agreed with each other perfectly and disagreed with the real spec in four places, because each was a reimplementation rather than a copy. A vendored file is copied byte-for-byte from its canonical source and never hand-edited — a drift test compares the copy against the source and fails on any difference, so the eleven-copies mistake cannot happen silently again.",
        "flashy.tools carries its own vendored copy of the charter checker and re-vendors it the same way every property in the estate does, rather than writing its own version of the same static questions. That is not laziness — a hand-rewritten checker is exactly the kind of thing that reads correct and disagrees with the spec in a detail nobody thought to test.",
        "Practically: if you are checking your own charter, run the vendored checker rather than eyeballing the JSON against the spec from memory. The checker asks the same five static questions on every property in the estate, so a pass here means the same thing everywhere."
      ]
    },
    {
      "n": "03",
      "title": "The AAO launch gate: what it means for a property to pass what it documents",
      "outcome": "Run flashy.tools's own suite mentally through its launch gate and state what a green result actually proves.",
      "body": [
        "The AAO launch gate is the check that a property claiming AAO conformance actually holds it live — not in a committed file, but served, at the moment the gate fetches it. flashy.tools runs this gate in its own CI, over its own charter and handshake, which means the property teaching you how to pass the gate has to pass it too.",
        "That is the whole of 'proving what you ship' in one sentence: the check that verifies your claim has to run against you as well, in the same suite, with the same rules — not a separate, softer pass reserved for the property doing the explaining.",
        "When you publish your own property, the discipline is the same regardless of scale: vendor the checker rather than rewrite it, run the launch gate against your live domain rather than your local checkout, and let the same suite that checks everyone else check you."
      ],
      "source": {
        "label": "Flashy Academy — The Conformance Ladder",
        "href": "/academy/curriculum/the-conformance-ladder"
      }
    }
  ],
  "faqs": [
    {
      "q": "What are the four artifacts the Activation standard checks?",
      "a": "A served flashyos/1 machine handshake, a working Mesh Concierge entry point, a visible concierge page a person can read, and a live demo a stranger can actually try — checked for real, not declared, so a property missing one reads as partially activated rather than rounded up to launched."
    },
    {
      "q": "Why is the charter checker vendored instead of reimplemented per property?",
      "a": "Because reimplementing it is how eleven copies once agreed with each other and disagreed with the real spec in four places. A vendored file is a byte-identical copy of the canonical checker, re-vendored rather than rewritten, with a drift test that fails on any difference."
    },
    {
      "q": "What does it mean that flashy.tools \"passes what it documents\"?",
      "a": "Its own suite runs the same vendored Activation check, charter checker and AAO launch gate it teaches — against its own live domain, not a committed checkout. A property teaching a standard it does not itself pass would be teaching a practice nobody has verified."
    }
  ],
  "related": [
    {
      "label": "Reading the Estate's Toolkit",
      "href": "/academy/curriculum/reading-the-estates-toolkit"
    },
    {
      "label": "The Conformance Ladder",
      "href": "/academy/curriculum/the-conformance-ladder"
    },
    {
      "label": "flashy.tools — standards",
      "href": "https://flashy.tools/standards"
    }
  ]
}