Skip to content

How it works

A governed path from reviewed model to checked evidence.

GCC separates orchestration, specialised solving and independent verification so that an optimisation cannot silently widen the claim.

  1. 01

    Authenticate the boundary

    Bind source identity, model bytes, assumptions, property, reset policy and bounded horizon.

  2. 02

    Preflight the request

    Check supported semantics and resource policy before beginning proof construction.

  3. 03

    Select an exact route

    Use CQ-SAT only when a deterministic structural gate admits it; otherwise use a supported exact fallback.

  4. 04

    Publish canonical evidence

    Bind the result, route, model and policy into a deterministic artifact.

  5. 05

    Verify independently

    Recompute proofs or replay complete witnesses outside the specialised producer path.

  6. 06

    Return one terminal class

    Report bounded SAFE, replayable UNSAFE, or REFUSED with no logical answer.

Scope: GCC proves the declared bounded obligation over the authenticated model. It does not certify a whole device or replace a regulated safety lifecycle.