Gå til hovedinnhold

Format support & maturity

neokapi reads and writes native document formats. The format-ops framework measures each format's support against committed evidence, publishes the results, and schedules maintenance as formats and implementations change.

A deterministic scorer derives the maturity levels from that evidence. Repeated runs over the same evidence produce the same levels.

Score and tier​

Each format has a maturity score and a published support tier.

The scorea multi-axis vectorone ladder per axisrecomputed every auditdeterministic file evidencediagnostic; promises nothingheadline tier = min over gating axesThe promisea support tierSupported / Maintained / Availablechanged only by a human eventbacked by a CI gatewhat you may rely on

The score explains and bounds the tier; the tier is the contract users rely on.

  • The score (a multi-axis vector) answers how good support actually is. It has one small ladder per axis, and it is recomputed by every audit from deterministic evidence in the format's own files. It ranks the remaining work and explains the tier.
  • The promise (a support tier) answers what you may rely on. A format is Supported (a regression blocks a release), Maintained (tested and kept green), or Available (registered and usable, explicitly experimental). The tier changes only by an explicit, human-approved event, and it is backed by a CI gate that fails the build on a regression.

The headline tier is the minimum over the gating axes, so a high score on one axis cannot hide a weakness on another. The vector bounds the tier (a tier may never claim more than its gating axes support), but the published tier moves only by a human-approved promotion or demotion. A tier claim is valid only while a CI gate enforces it.

What it detects​

Format readers and writers must preserve content and structure during edits (see Formats). Changes to an implementation or an upstream specification can introduce regressions. Format-ops tracks the evidence needed to detect them. Each format carries committed evidence (its reader and writer, a specification, reference corpora, and the tests that exercise them), and the audit computes a level per axis from that evidence alone. When evidence is removed or becomes stale, the score falls on the next run; when a gate stops running, the tier cannot be claimed. Scheduled maintenance keeps the measurement current with the code (see Keeping it alive).

The live dashboard​

The per-format scores, tiers, and trends are published on the live /format-maturity dashboard. The upkeep loop regenerates it, and the formats it reports come from the format directories in the build.

  • The axes: the three families and what each axis measures.
  • Keeping it alive: the runbook, calibration, vigilance, and new-format funnel that keep the measure current.
  • Deeper detail on the engine being measured: Formats and the Content model.