CABIER Global Assurance · Reference architecture

    Data Centre Assurance

    Sovereignty is not where the server is. It is the legal relationship over the operator, the data and the institution that holds the consequence. A site can move under different control without a single byte moving, and the assurance position changes that day.

    This surface treats the site as an assurance subject: what runs here, for whom, under which law, with which dependencies, and what evidence survives the loss of the place it describes.

    Reference architecture. Extends the existing inventory and dependency structures rather than creating a second infrastructure register.

    Where the site sits in the hierarchy

    Beneath the model and the runtime, above nothing that removes the operator from the position.

    1. 01AI factory

      Where intelligence is manufactured: accelerators, clusters, training and the model estate itself.

    2. 02Data centre, cloud or sovereign infrastructure

      Where intelligence is operated, by a named operator, under a legal relationship.

    3. 03Model

      The capability, at a stated version, with evaluation evidence that belongs to that version.

    4. 04Runtime

      Where inference and agent execution actually occur, rather than where they are described.

    5. 05Agent

      The acting party, with an objective, a delegation path and an authority envelope.

    6. 06Tools, tool servers and credentials

      The reach an agent acquires the moment a tool or a credential is attached.

    7. 07Data

      Classification, residency, permitted purpose and onward flow of everything reachable.

    8. 08Application

      Where intelligence is distributed to people and to other systems.

    9. 09Enterprise and device

      Where intelligence is consumed, inside an institution or at the edge.

    10. 10Action

      The consequential thing that happens, which is the only place assurance finally matters.

    CABIER spans every layer

    • TrustGraph

      The relationships between every object in the hierarchy, so an effect can be traced rather than guessed.

    • AssureAdapt

      Detects change anywhere in the hierarchy and decides when the position must be re-derived.

    • AssureCore

      The single decision boundary: eight Trust Gates, five dispositions, no consequential autonomous execution.

    • AssureMark

      The machine-readable assurance and provenance record for whatever was decided.

    • Evidence

      One evidence architecture, dated, attributable and re-examinable by someone who was not there.

    • Human and institutional authority

      The named authority that adjudicates consequential findings, at every layer.

    Cabier does not replace the underlying infrastructure. Cabier assures what operates across it.

    The site as an assurance subject

    This extends the existing inventory and dependency structures. It is not a second infrastructure register, and it does not claim visibility Cabier has not been granted.

    Compute and model hosting

    What runs here, for whom, and under which contractual and regulatory terms.

    Inference locality

    Whether inference stays in the place the institution told its regulator it would.

    Data residency

    Where data rests, moves, is cached and is backed up, which is rarely one place.

    Identity and credentials

    Operator, tenant and machine identity, and the lifetime of each credential.

    Network and storage

    The paths that either uphold or quietly contradict a residency commitment.

    Physical and infrastructure dependency

    Power, cooling, carrier and site dependencies that no software control compensates for.

    Cloud and API dependency

    External services the site itself depends on to remain available.

    Tenant boundaries

    What isolation is asserted, what is tested, and what a breach would cross.

    Model and provider concentration

    How much of the institution's capability rests on one model or one provider here.

    Evidence locality

    Whether the evidence survives the loss of the environment it describes.

    Jurisdiction and sovereignty

    Sovereignty as a legal relationship over the operator and the data, not a map pin.

    Incident and change state

    What changed, when, attributable to which actor, with what effect on the assurance position.

    Resilience

    The stated fallback position, tested rather than assumed.

    When the legal position changes and nothing technical does

    Deterministic and synthetic. Every figure is illustrative.

    Synthetic demonstrator · illustrative

    Data centre assurance

    Sovereign-hosted site carrying inference for a regulated institution

    Consequence class: Strategic
    1. 1. Baseline
    2. 2. Dependency
    3. 3. Concentration
    4. 4. Change
    5. Assurance state

    Assurance that lives in a separate system describes the past. Embedded assurance sits where the action happens.

    See how assurance is placed