Open data contract / V5
A contribution is declarative acquisition configuration, not a spreadsheet upload. Live evidence, normalized facts, review decisions, and health transitions remain separate and auditable; ledger metrics apply only to the visible keyset page.
Submission workflow
The contributor supplies an immutable contract; a maintainer separately approves its exact digest. Neither fixtures nor submitted text become production evidence. Repository pull requests are invitation-only during the private beta; opening access later does not change this trust boundary.
Name the public HTTPS source, provider identity, polling cadence, freshness window, and exact expected model / endpoint / operation identities.
Pin currency, component, billing unit, tiers, minimums, and inclusions. The interpreter accepts changed amounts but quarantines semantic drift.
Source-shaped JSON fixtures must cover a positive result, missing field, invalid decimal, identity collision, invalid unit, and duplicate price-component identity.
Approval is a separate digest-bound ledger action. Production scheduling remains disabled until an exact active artifact is approved.
Public proof ledger
This is one bounded source page. Each stage has its own state; safe receipts and bounded event metadata omit provider bodies, object keys, headers, credentials, and arbitrary event details.
example-community-video-cataloghttps://example.com/computellama/video-v5-community-catalog.json · example-community-video-catalog@720dd4a7296f