Skip to main content

Ontology

The fleet's explicit vocabulary for the agent estate: the concepts agents share — agent, role, story, sprint, claim, receipt, skill, runbook, adapter, and the work concepts the estate's own work produced: project, repository, board, backlog, work record, charter, dispatch, decision, audit, baseline, gate, cadence — each on its own concept page, with the relations between them recorded twice: as relations: frontmatter on each page and as lines in the YAML triples register.

This category is phase 1 of the fleet ontology: the agent estate only (this docsite, the fleet repositories, the boards, the skills library). Other estates — the cooking wiki, the Research Hub — join one at a time in phase 2, on the owner's decision, and are not represented here.

Read in this order​

  • Concept format standard — the normative shape of a concept page, the closed predicate vocabulary, and the triples register's rules. Read this before adding or editing a concept.
  • Triples register — every asserted relation in the ontology, as subject–predicate–object triples.

Seed concepts​

  • Agent — a registered fleet participant.
  • Role — a chartered function in the fleet.
  • Story — the unit of committed work on a board.
  • Sprint — a scope-bound set of committed stories.
  • Claim — the committed lease by which one agent holds a story.
  • Receipt — a hash-bound record of an independent review.
  • Skill — a reusable instruction set an agent loads.
  • Runbook — the document that defines a role's method.
  • Adapter — the bootstrap mechanism by which an agent joins the fleet.

Work concepts (added 2026-10-08, first daily-derivation tranche)​

  • Project — a bounded initiative with a stakeholder, scope, and deliverables.
  • Repository — the version-controlled home of a project.
  • Board — a project's queue surface: its backlog, stories, sprints, and claims.
  • Backlog — the capture pool in front of a board's stories.
  • Work Record — a project's living narrative record.
  • Charter — the governing statement of a project's scope and terms.
  • Dispatch — a recorded routing of a work item to its owning agent.
  • Decision — a recorded choice resolving a question, with decider and rationale.

Process concepts (added 2026-10-09, tranche 2)​

  • Audit — a structured examination against a standard, producing findings.
  • Baseline — the accepted reference state later runs diff against.
  • Gate — a control whose clearance is consumed at the moment of the act it guards.
  • Cadence — a standing scheduled rhythm of work that reports every cycle.

The ontology is maintained per the format standard: concept pages are the source of record for their own relations, and the register is their machine-readable projection. The knowledge graph, when it is built, is generated from the register — it is not edited by hand.