Status

Technical-health reference contract

A static, synthetic privacy-safe technical-health contract defines a thresholded weekly aggregate and deterministic local dashboard document. This build does not collect those metrics. Metric absence or suppression is not shown as success, health, uptime, or availability.

A separate static synthetic assurance-pack v1 contract demonstrates bounded release/dataset pinning, evidence-review summaries, uncertainty, and replacement disclosure. It is not a live assurance service, customer/provider export, paid offer, or claim about availability or quality; provider claims remain untrusted pending or rejected input.

The static synthetic provider-claim v1 contract demonstrates staging and conflict-free independent review only. It is not a provider portal or live intake/review service; acceptance means candidate eligibility for a separate approved workflow, never canonical publication, verification, or ranking.

The single-item static synthetic reviewer-work-queue v1 contract adds an administrative-only queue order and a three-event hash-chained disposition audit. Its release-pinned snapshot can detect history tampering; this is not a claim that mutable logs are inherently append-only. It is not a live workbench, admin, assignment, persistence, auth, or write service, and cannot bypass provider-claim promotion gates.

The managed API plans v1 contract is a static synthetic proposal for a free monthly managed allowance and explicitly opted-in future paid tiers. The managed API, signup, billing, keys, counters, telemetry, SLA, and support service are not live; current static crisis-information surfaces remain free and keyless.

The deprecation proposal and audit-export v1 contract is static and synthetic. It records no canonical change or publication authority, exposes no contact values or source locators, and cannot bypass existing candidate, approval, dry-run, or explicit apply gates.

The evidence-backed coverage assessment v1 contract is static and synthetic. It reports separate recorded-evidence dimensions and explicit unknown states only; source checks do not establish real-time availability, answering, eligibility, capacity, safety, outcomes, quality, or universal geographic coverage.

Inspect the evidence

All public integration surfaces remain static beta with no uptime, support, or SLA commitment. If an artifact cannot be fetched or verified, integrators should use their reviewed degraded behavior and revalidate before promotion.