Designed, not started. And we say so.

The design that’s done

Cattle compliance runs on program status: a herd is enrolled in a program, holds a standing in it, has to keep evidencing that standing, and can lose it on an event. That’s the identical mechanics Earmark already runs for swine claims — hold a revocable status, watch its clock, revoke it the instant it stops being supportable, and chain the reason. The cattle design maps herd-program status onto that proven substrate rather than inventing a new one.

What carries over on day one

• The tamper-evident chain, the exports with standalone verification, and the database-level refusal to rewrite history.
• The auto-revoke primitive — an event defeating a claim in real time — already live for swine antibiotic-free and welfare claims.
• Producer-controlled sharing with scope tiers, revocation, and chained read-receipts.

Why the honesty matters here most

Species pages are where ag-software roadmaps usually go to lie. Ours ranks below chickens — which ranks below swine, where everything is live — and each page says exactly which one it is. If you run cattle and want the record layer shaped around your programs before the defaults harden, that conversation is welcome now.