Dated source reference. Current release status: handoff state. Full original relative paths are in the developer archive.

Canonical HTTP v1 schema

Current private contract51 has84 named schemas, including typed durable rotation-plan events/history, native timeout commands and input discovery/selection. See match controls. Actual HTTP/closed-state/history validation preserves original database/result hashes; this is separate from physical gamepad certification.

openapi.json is the maintained OpenAPI3.1 contract for private OpenHoops0.2.0.dev50, with76 component schemas. It covers snapshotABI25/eventABI4, collegeprofiles1–4/courtdefinitions2–3 and supported older responses. New schemas describe native queue configuration, durable request observations and startup defense.493 Windows API tests and current positive-negative/historical result checks pass; external-flow evidence separates live entry from queue acceptance. Public preview2 retains36/ABI14. See API guide and verification.

Historical launch schemas for rules/presets, single-use requests, optional named roster authoring, startup cameras/participation and authenticated binary ROS export extend the13-control preparation contract. Older ABI snapshots and historical results remain valid. Prior59-schema acceptance covers eight live scenarios/127 commands and immutable historical results; current61-schema acceptance covers12 live scenarios/188 actual commands, immutable results and original database hashes. Empty optional roster_edits is a valid no-op, matching runtime validation. Schema count alone does not prove native feature availability or live validation.

build_schema.py validates schemas/references and formats this canonical file; it does not regenerate a reduced contract. Run it with the existing development jsonschema dependency on the Dell. jsonschema is not a broker runtime dependency. A valid schema does not prove that a game feature is available: clients must inspect /v1/session, health and declarations.

Profile4 final_exports_verified is a boolean reference-scenario statement: newly decoded current state is true after36ct OT/export validation. Historical stored profile4 state/results with false remain valid. Profiles1–3 remain false. Full-rulebook certification remains false for all college profiles. incomplete contains descriptive verification limits; it is not an enum of missing endpoints. Result completeness and ledger reconciliation are separate from those profile declarations.

Fields added by newer adapters can be absent or null on older/unavailable sources. Unknown record kinds/actor meanings remain numeric/null. Raw period is not the display period; use rules.period and available ledger logical periods. Court alignment does not identify currently loaded artwork, and physical attachment does not establish legal possession.

Documentation/metadata updates do not rewrite immutable captured fixtures, result revisions, source manifests or archived ZIPs. Recorded schemas and flags remain evidence of the version used at capture. Schema compatibility checks for current and historical results are retained in analysis/api-docs/current-verification.json.