OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

Contract Verification Table

How the impact report renders per-contract verification status.

field.key.label
Contract Verification Table
field.version.label
field.type.label
field.title.label
Contract Verification Table
field.description.label

How the impact report renders per-contract verification status.

field.tags.label
report,drift,verification,impact
field.owners.label
platform.core
field.stability.label
public

The impact report includes an optional per-contract verification table that summarises the health of each contract at a glance.

Columns

| Column | Description | |--------|-------------| | Contract / Endpoint / Event | Fully qualified contract name (e.g. `user.create`) | | Drift debt | Number of mismatches currently detected | | Time since verified | Human-friendly elapsed time (e.g. "23 days") or "Never" | | Surfaces covered | Comma-separated list (API, runtime validation, UI form, docs/examples, permissions) | | Last verified commit | Short SHA of the last drift-free commit |

Data flow

1.

The drift detector produces per-contract mismatch counts.

2.

`.contractspec/verified.json` records the last clean commit per contract.

3.

The report script reads both sources and renders the Markdown table.

Backward compatibility

When `contracts` is absent from the report JSON, the table is skipped and the existing report sections render unchanged.

Contracts

•

Query: `report.getContractVerificationStatus` (v1.0.0)

•

Data view: `report.contractVerificationTable` (v1.0.0)