Cabier Global Assurance · Architecture

    AssureMark

    Consequential intelligence needs provenance. AssureMark is the machine-readable assurance context that travels with an AI system, an agent, an application or a specific action: what it is, who owns it, what it may do, which rules apply, what controls hold, what evidence exists, and when that position stops being current.

    It exists so the next system in the chain, the institution's own reviewer and a supervisor can all read the same position rather than each inferring one.

    Published as reference architecture. The record schema is stable in shape; the assurance thresholds behind it are set per engagement.

    The record

    Versioned, dated and expiring. An approval without an expiry quietly becomes a permanent assumption.

    Assurance subject

    The model, version, system, agent, application or action the context describes.

    Owner and accountable person

    Assurance without a named human owner is a document, not a control.

    Purpose and permitted activity

    What the system is for, and what it is not for.

    Authority and permission envelope

    What it may do, up to what value, over what data, on whose grant.

    Jurisdictions engaged

    Every place whose law is engaged by entity, user, data, inference or consequence.

    Applicable obligations

    The obligations resolved for that combination, cumulatively.

    Control set and state

    Which controls apply, their current state and the date each was established.

    Evaluation record

    What was evaluated, by whom, against what, and when it expires.

    Evidence position

    Completeness, residency, retention and the earliest expiry in the set.

    Consequence class

    Everyday, regulated, critical, strategic or systemic, which sets assurance intensity.

    Assurance state and expiry

    The current state and the date it stops being current, so approvals do not become assumptions.

    Provenance

    Corpus version, control version, model version and decision lineage for reproducibility.

    What it is

    • A machine-readable assurance context that travels with the system, so any consuming service can read the current position rather than infer it.
    • A record with an expiry, a named owner, an evidence position and a version history.
    • An interoperability format, so a lab, an enterprise and a supervisor can express assurance information the same way.

    What it is not

    • A certification of safety, quality or compliance.
    • A rating, ranking or comparison of any provider against another.
    • A badge. Cabier Assured describes a live assurance mechanism operating beneath or alongside the system, not a logo applied to a page.

    Assurance context becomes useful commercially when the builder keeps the product and the assurance sits underneath it.

    See the ecosystem model