TM Meridian Health System composite · on-prem · us-east SYNTHETIC DATA — briefing demo Chain head

Every action on the books, witnessed.

Four clinical AI systems governed at the boundary. Every inference and tool call is resolved against the signed charter and leaves a receipt — hash-chained, exportable, verifiable without Glacis.

0
Actions on the books · today
4
Systems governed
12
Controls enforced
3
Held for review
0.10 ms
Gate p99 · deterministic
Decisions · last 24 h
approved rejected modified escalated
Decision feed · live

    Governed systems

    charter-bound · receipts current
    SystemRisk tierCharterActive controls Receipts todayStatus

    Receipts

    Each row is a signed decision record — not a log line. Select one and verify it yourself: the checks run in this browser, against the bytes on screen.

    TimeSystemControlActionReceipt
    Receipt inspector
    Select a receipt to inspect and verify it.

    Why this standard is here to stay

    The shift from self-attested logs to independently verifiable evidence is not a vendor thesis — it is written into instruments that bind deployers now. OVERT receipts are the operational answer.

    AuthorityInstrumentWhat it requiresEffectiveOVERT answerStatus

    Volatile specifics (dates, citations) summarized for briefing — VERIFY against source before client use.

    One receipt schema, every framework

    capture once · evidence everywhere
    Evidence property of the receiptISO 42001NIST AI RMFEU AI ActHIPAATJC / CHAIInsurer DDQ

    ● satisfied by receipt fields   ◐ partial / paired with charter artifacts — excerpt of the full mapping engine.

    Stewardship

    OVERT v1.1
    Open runtime-evidence spec · royalty-free
    Co-stewardship
    Health-AI coalition (CHAI) — in progress
    Independent verification
    Standalone verifier · no Glacis in the loop

    The standard does not belong to Glacis — that is the point. A record only counts as evidence when the party checking it doesn't have to trust the party that produced it.

    Operationalize in two weeks

    No model changes, no prompt changes, no cloud dependency. Glacis installs at the boundary the client already owns and starts writing the books on day one.

    DAY 0

    Install at the boundary

    Unmodified LiteLLM proxy + callback for model traffic; MCP wedge for agent tool calls. On-prem.

    litellm_settings:
      callbacks:
        - glacis.GovernanceLogger  # receipts on every call
    DAY 1

    Charter signed as code

    The governing document becomes a signed policy: rules → named runtime controls → calibration, activated under the client's own key.

    WEEK 1

    Receipts flowing

    Baseline posture visible: every decision on the books, held-for-review queue live, drift measured against the attested baseline.

    WEEK 2

    First evidence pack

    Framework-mapped export with the standalone verifier — the client's auditor checks it offline, without trusting Glacis or the client.

    Evidence packs

    exports ship with the verifier

    ISO/IEC 42001 readiness

    12,384 receipts · 8 controls mapped
    PDF + JSONL + verifier

    EU AI Act Art. 12 extract

    record-keeping evidence
    per-system · per-period

    Insurer underwriting extract

    control-execution rates
    incident reconstruction paths

    Incident reconstruction

    causal chain for one correlation id
    who · what · under which policy

    Run your advisory engagement on the instrument.

    Your healthcare clients must move fast on AI without betting the institution. Glacis gives your engagement a measurable spine: a 30-minute assessment, a charter workshop, and a two-week evidence baseline — producing the artifacts their board, regulator, and insurer actually accept.

    30 minassessment
    Day 1charter workshop
    2 weeksevidence baseline
    Quarterlyattestation cycle