Skip to content

Status

  • Draft, version 0.1. It defines file format version 1 (version: 1 in oryxkb/project.yaml).
  • Fields may still change. Fields may be added. Breaking changes are announced in the changelog before v1.0.
  • One implementation: oryxkb, an open-source Python tool that reads and checks the file and renders cards for agents.
  • Open licence: Apache-2.0.
  • Not ratified. It is not a certification and not governed by a standards body. It is published so others can use it, comment on it and implement it.

Not in the spec yet

  • Warning that a newer release should exist (the as-of date is shown, not judged).
  • Structured licence terms for agent use.
  • Per-request price quotes.
  • Cost per run.
  • Usage tracking (tooling, not the file).
  • MCP and API response shapes.
  • The exact shape of the card.
  • The full citation form, including cells and project-level facts.
  • A probe script contract (what a script accepts and prints).
  • A test that the declared grain is unique.
  • Many-to-many joins and mapping tables as a declared construct.
  • Scale and kind fields for a column (level, change, rate); the value type is a field now.
  • A field for what a blank means.
  • A revision-policy block, and a mark for preliminary or final values.
  • A per-release file (release id, as-of date, what it replaces) and a machine-readable changelog.
  • A map from old to new key values when ids are recoded.
  • A mark on a column that its unit or definition changed (today: a new name, or a dated blocker fact).
  • Compatibility rules per kind of change in machine-readable form (today: the Schema changes page).
  • Persistent column ids: decided against. A column is its name, plus aliases.
  • A generator that writes whole ODCS or Ossie files.

Every area and its status: The full picture.