black O2, inc.
ACTIVE
    FOR-001 / ConceptsCON-015

    Compute Governance

    Active concept

    title
    Compute Governance
    Type
    concept
    Identifier
    CON-015
    Status
    Active
    Tags
    • literature
    • governance
    • hardware
    • session-2
    Aliases
    • compute threshold
    • FLOP threshold
    • hardware-enabled governance
    connections
    • [[LIT-007]]
    • [[LIT-009]]
    • [[CNF-007]]
    • [[SYS-003]]
    source path
    70_Literature/LIT-007.md

    Compute Governance

    The use of compute as the chokepoint for governing AI — because training requires specialised hardware that is manufactured in few places, is detectable in use, and can be tracked, metered or restricted at the point of production and sale. The claim is not that compute is the only lever but that it is the most governable one, since it is physical where models are not.

    Why It Is the Corpus's Strongest Rival

    The Citadel Stack locates enforcement in law and custody: privileged legal personality, cryptographic control of the weights, a sealed inference node. Compute governance locates enforcement in the supply chain, upstream of all three, and it has two advantages the Stack does not:

    1. It does not require the operator's cooperation. A hardware chokepoint binds a party that has not consented; the Stack's legal layer presupposes a jurisdiction willing to grant the privilege and an operator willing to accept the custody terms.
    2. It is already being implemented. Export controls, reporting thresholds and datacentre transparency obligations exist as instruments; the Stack exists as a proposal.

    The corpus never considers it. That absence is the substance of CNF-007 — the Stack is not wrong about its own mechanism, it is silent about the mechanism that would make it redundant or unnecessary.

    The Limits, Stated Honestly

    Compute governance governs training runs, not deployed capability, and it is weakest exactly where the Stack is strongest: an already-trained model running on unremarkable hardware. It is a governance of creation, not of use.

    Connections

    • LIT-007 — the source record.
    • LIT-009 — the institutional counterpart, on who has access and under what audit.
    • SYS-003 — the system that does not engage it.
    • CNF-007 — the confrontation.

    Back to Shackled AIForests