Skip to content

The content graph

How much of the estate we teach

The Academy is a graph, not a pile of courses: every teachable idea is a concept pinned to a real source, and coverage is the share of them a course teaches yet. It is deliberately a figure we cannot raise by talking more about ourselves — it only rises by teaching more of the graph, and the frontier stays visible.

This is the mesh curriculum. Looking for the For-Gold Economy tracks instead? Tracks.

77.5%
concepts taught
86/111
covered of total
25
frontier — not yet taught
55
courses · 10 tracks

By source

SourceTaughtFrontier
agent-dns/1 — the discovery naming layer0/33 to teach
agent/1 — the discovery document0/33 to teach
bastion — the commercial gateway0/33 to teach
pay-policy/1 — the commerce layer0/33 to teach
Tether WDK + wdk-policy-guard — the execution layer0/33 to teach
web4/1 — the nine-layer stack map0/33 to teach
delegation/1 — the identity layer0/22 to teach
graph/1 — the graph layer0/22 to teach
@flashyos/countersign — proof over the record: countersignature, delegation, audit, badge0/11 to teach
@flashyos/llms-txt — the file that tells an answer engine what an organisation is0/11 to teach
@flashyos/verify — the shared canonicalisation a settlement, receipt and shipped entry all hash through0/11 to teach
@flashyos/agent — the SDK agents import1/1complete
@flashyos/assetmesh — rwa/1, a real-world-asset record served at /.well-known/rwa.json1/1complete
@flashyos/backlog + @flashyos/shiplog1/1complete
@flashyos/checkpoint — an RFC 6962 tree head over the sealed claims a property publishes1/1complete
@flashyos/conformance — the levels a node is graded against, held not issued1/1complete
@flashyos/conformance + flashyos/packages/aao1/1complete
@flashyos/countersign + @flashyos/verify1/1complete
@flashyos/create-mesh-agent — npx scaffolds a starter mesh agent1/1complete
@flashyos/create-mesh-node — the one-command on-ramp2/2complete
@flashyos/create-mesh-node — writes the four files and verifies L21/1complete
@flashyos/defined — a vocabulary where one authority owns each term and a citation is a link, never a copy1/1complete
@flashyos/directory — federated fragments, the merge, the validator1/1complete
@flashyos/frontdoor — which lanes an org opens, and what it owes1/1complete
@flashyos/holding — transitions, not states1/1complete
@flashyos/llm-gateway — the inference seam3/3complete
@flashyos/llm-gateway — the provider-agnostic inference seam1/1complete
@flashyos/llm-gateway — the provider-agnostic seam, with the gatewayz provider1/1complete
@flashyos/llm-gateway README — failover, empty-success guard, cost attribution1/1complete
@flashyos/mail — the single send path and its content-free log1/1complete
@flashyos/mcp — the same surface as the SDK, exposed as MCP tools1/1complete
@flashyos/mesh — what a repository has adopted, what is left, and the command for each1/1complete
@flashyos/reward + @flashyos/wallet — the accrual log and the venue it refuses to settle into1/1complete
@flashyos/ritual — ritual/1, the third tense: the state ladder, and the doctrine only a person can consecrate1/1complete
@flashyos/ritual — the refusals: money/amount and standing vocabulary invalid at any depth; value lives in reward/1, never inside1/1complete
@flashyos/ritual — the transition kit: every call re-validates the whole fragment; a correction is a new observance, never a rewrite1/1complete
@flashyos/ritual — unpublished until the first adopter; the tally/1 ladder each figure declaring who has to act for it to move1/1complete
@magician-network/attendant — the Telegram-native tier: the broadcast rule, the ask-loop link, the two absolute boundaries1/1complete
@magician-network/cli — a local-first terminal client over a private .magician/ store1/1complete
@magician-network/concierge — the Mesh Concierge, the Activation standard, and the mesh handover that refuses to guess1/1complete
@magician-network/core — introduction/1: canonical JSON, portable sha256, the append-only log, the notary leaf1/1complete
@magician-network/core — the consent state machine: proposed, the decline-as-absence collapse, no partial-yes introductions1/1complete
@magician-network/core — trust/1: the parser that refuses, the register that grades every figure, the standing invariant1/1complete
Flashy Finance — the wallet and rail2/2complete
Flashy Gold — the rewards layer2/2complete
Flashy Gold + @flashylabs/ledger (Flashy Finance declared, not yet operational)1/1complete
flashy.tools — the estate's developer-tools catalog (tools.ts), documenting every package with its edge cases beside the happy path1/1complete
flashy.tools's own suite — the Activation standard, a vendored charter checker, the AAO launch gate, run against its own live domain1/1complete
flashyID — rail issuance and consent/grant tokens (docs/rail-consent.md, docs/rail-grant.md)1/1complete
flashyID — the identity layer2/2complete
flashyID — the OIDC provider + @flashyid/sdk grant kernel1/1complete
flashyID + flashy network — a verification/1 leaf that reveals an assurance level and a time, never who1/1complete
flashyos — the estate's operating practice (charters, thresholds, evidence)1/1complete
FlashyOS + flashyID + Flashy Gold + Flashy Network — mesh nodes that compose1/1complete
flashyos.com/concepts/agentic-autonomous-organization + @flashyos/aao (the seven questions)1/1complete
flashyos/1 handshake + @flashyos/conformance (committed is not served)1/1complete
flashyos/1 handshake + the AAO charter, served at /.well-known/1/1complete
flashyos/packages/aao — the AAO manifest spec4/4complete
flashyos/packages/api jointInitiativeService — consent doctrine1/1complete
flashyos/packages/backlog — backlog/11/1complete
flashyos/packages/compute — compute/13/3complete
flashyos/packages/countersign — countersign/12/2complete
flashyos/packages/directory — directory/13/3complete
flashyos/packages/frontdoor — frontdoor/11/1complete
flashyos/packages/shiplog — shipped/11/1complete
flashyos/packages/verify — offline verification2/2complete
flashyos/tools/estate-tally.mjs + pulse/11/1complete
Gatewayz — gatewayz.ai onboarding: key, unified endpoint, catalog1/1complete
Gatewayz — gatewayz.ai, the unified inference gateway1/1complete
Gatewayz — the unified inference gateway4/4complete
Gatewayz API — the prompt-caching and tool-calling guides (beta.gatewayz.ai/docs)1/1complete
IntentMesh — intent/1, a machine-readable statement of what an organisation wants1/1complete
IntentMesh + FlashyOS + Magician (introductionApi) + the settlement record1/1complete
Per-request tokens + requestId (the inference seam), summed by initiative id1/1complete
Task-specific evals (rubric + golden set) measured through @flashyos/llm-gateway1/1complete
The accelerator + data-centre supply chain, framed by Gatewayz1/1complete
The economics of compute utilisation — idle capacity to income1/1complete
The estate on-ramp end to end — charter, conformance, spokes, the record1/1complete
The estate's AAO operating experience + @flashyos/llm-gateway1/1complete
Freshness55 current against sourcenone drifted56 unpinned · graph.json

Teaching next

The frontier is a roadmap, not an embarrassment: these are the ideas no course teaches yet, grouped by the source they share. The largest cluster is the next course to write.

agent-dns/1 — the discovery naming layer · 3 to teach

  • One TXT record points, the document describesA single DNS TXT record at _agent.<domain> carries v=agent1 and the https URL of the domain’s agent/1 document — DNS does the pointing, the well-known document does the describing.
  • Four findings, and a failure is never absenceThe resolver returns exactly ok / absent / unreachable / invalid; a transport failure resolves to unreachable and never collapses to absent, because “could not reach” is not “is not there”.
  • Same-domain, with no suffix guessingRedirects are followed only within the same domain over https, host-or-subdomain — there is no Public Suffix List in the checker, so it refuses to guess rather than read two publishers as one.

agent/1 — the discovery document · 3 to teach

  • A machine front door names a reachable humanThe /.well-known/agent document must declare who is accountable — an org id and a named, reachable human — because a door with no one behind it is not a door.
  • Silence on auth never reads as openEach action declares its auth (none / api-key / oauth2 / delegation/1); an omitted auth is refused, never interpreted as “anyone may call”.
  • Discovery only — no execution materialThe document says who, what, where and what it costs; it carries no negotiation, execution, settlement, or DNS material, so publishing it commits nothing but discoverability.

bastion — the commercial gateway · 3 to teach

pay-policy/1 — the commerce layer · 3 to teach

  • Payment policy is rail-neutralA pay-policy/1 describes what may be spent, by whom, up to what — and a stablecoin or USDT rail plugs in underneath unchanged, because the policy never names the rail.
  • Amounts are whole minor unitsEvery figure is a whole number of minor units; floats, strings, negatives and bare numbers are refused, because rounding someone’s money is not a thing a policy may do quietly.
  • A delegated policy only ever narrowsAttenuation refuses a larger cap, a later expiry, or a changed purpose — a child policy can never widen the parent that granted it.

Tether WDK + wdk-policy-guard — the execution layer · 3 to teach

web4/1 — the nine-layer stack map · 3 to teach

  • The agentic internet is nine layersWeb4 names nine layers — identity, graph, discovery, trust, gateway, representation, execution, commerce, audit — each a contract a stranger can read, so a system maps to layers before it writes code.
  • Reuse the layer’s contract, never coin a new oneWhen a layer already answers the question, its format name is vocabulary the stack owns — a design implements the existing contract rather than inventing a parallel one.
  • Layers interoperate by contract, not by couplingThe formats compose one-directionally and dependency-light: they agree by contract name, most are zero-dependency and vendored, so a layer can be replaced without touching the ones above it.

Check it yourself

The whole graph is machine-readable at /academy/graph.json — every concept with its source pin and prerequisites, every course, the gate report, and this coverage figure derived rather than typed. An agent reads the graph; a person reads this page.

An agent can be taught from the courses, not just navigate them: /academy/courses.json enumerates every course and its freshness, and each course serves its full lessons as data at /academy/curriculum/{slug}/course.json.

The frontier is the roadmap: the largest cluster of untaught concepts is the next course. The count only falls by teaching, never by dropping a concept to flatter the ratio.