ledger 2026-09-28T02:24:46.289Z · evidence sha256 af99a399d3c271ca94aafa6f… · machine-readable
CIRE runtime and calibration jobs
DEGRADED- What exists
- CIRE 2.0 runs on every inference in the request path; daily jobs recompute calibration profiles and re-run reference self-conformance.
- Current state
- cire-calibration: the latest scheduled run failed (21 consecutive failures). cire-reference-certification: the last 21 scheduled runs succeeded.
- Evidence
- Production database records · EV-SYS-CIRE-20260927 (sha256 0f252f2d27c2da42…)
- Last verified
- 2026-09-27T03:20:19.103+00:00
- Limitations
- CIRE signals are structural and policy states; they are not clinical accuracy.
- Activation requirement
- Each scheduled CIRE job needs 3 consecutive successful scheduled runs. cire-calibration also needs a registered production champion model; without one it records SUCCESS_NO_ELIGIBLE_DATA.
Outcome calibration materialization
NO DATA- What exists
- A daily job materializes confirmed, non-synthetic outcomes into append-only calibration buckets per tenant, label, species, and model version.
- Current state
- outcome-calibration-materialization: no scheduled run has been recorded.
- Evidence
- Production database records · EV-SYS-OUTCOME-MATERIALIZATION-20260928 (sha256 56dd2db3fcea2afc…)
- Last verified
- Never
- Limitations
- Calibration is tenant-local. It does not retrain or update model weights.
- Activation requirement
- 3 consecutive scheduled runs must materialize confirmed outcomes.
Network learning (federation)
NO DATA- What exists
- Federation substrate: enrollment, masked contribution commitments, round scheduling, and benchmark/calibration gates.
- Current state
- NETWORK NOT ACTIVE: 0 production participants (minimum 2).
- Evidence
- Production database records · EV-SYS-NETWORK-LEARNING-20260928 (sha256 f921ebc9d338f4ee…)
- Last verified
- 2026-09-28T02:24:46.289Z
- Limitations
- A network with fewer than two authorized participating clinics learns nothing across tenants.
- Activation requirement
- At least 2 authorized participating clinics.
Developer platform
NO DATA- What exists
- A versioned partner API contract with 10 endpoints, hashed scoped API keys, quota metering, and usage analytics.
- Current state
- Partner API contract is implemented; no products are currently published.
- Evidence
- Production database records · EV-SYS-DEVELOPER-PLATFORM-20260928 (sha256 88d4f754dbce899b…)
- Last verified
- 2026-09-28T02:24:46.289Z
- Limitations
- Partner access is provisioned manually after onboarding review.
- Activation requirement
- Publish at least one API product.
Partner API (/api/v1)
NO DATA- What exists
- The /api/v1 partner contract at https://www.vetios.tech/api/v1, authenticated with Bearer vios_k1_ keys.
- Current state
- No partner API calls were recorded in the last 7 days.
- Evidence
- Production database records · EV-SYS-PARTNER-API-20260928 (sha256 2f391f47c72bab31…)
- Last verified
- Never
- Limitations
- Operational status is inferred from recorded partner calls; with no calls there is no evidence either way.
- Activation requirement
- An authorized partner must call the API.
ProofLoop public verification artifact
OPERATIONAL- What exists
- A public, signed ProofLoop artifact and an independent verifier that runs without VetIOS systems.
- Current state
- The public artifact verifies: receipt integrity, evidence digests, signature, eval binding, and gate result.
- Evidence
- Recorded artifact · EV-SYS-PROOFLOOP-20260928 (sha256 6481dfa4b7997b61…)
- Last verified
- 2026-09-28T02:24:46.289Z
- Limitations
- The published artifact is synthetic. It proves the verification mechanism, not clinical performance.
- Activation requirement
- None: requirements are met.
Edge nodes
NO DATA- What exists
- Edge node registration, device credentials, heartbeats, and sync jobs.
- Current state
- No edge nodes are registered as online.
- Evidence
- Production database records · EV-SYS-EDGE-20260928 (sha256 fcbeaff61d1f1867…)
- Last verified
- 2026-09-28T02:24:46.289Z
- Limitations
- No edge node runs clinical inference offline in production today unless counted below.
- Activation requirement
- A clinic edge node must register and send heartbeats.
Public model registry
NO DATA- What exists
- A model registry with governance gates and read-only public model cards.
- Current state
- No public model cards are published.
- Evidence
- Production database records · EV-SYS-MODEL-REGISTRY-20260928 (sha256 d50c5eef4efec463…)
- Last verified
- 2026-09-28T02:24:46.289Z
- Limitations
- The production clinical engine is a deterministic, versioned rule system; it has no trained weights to publish a card for unless listed.
- Activation requirement
- Promote a model version through governance and publish its card.