Use case 04 Deployment evidence The attester's narrowing table on this estate

Wherever it runs, proof sets the ceiling.

The attester runs the same checks for every copy. The evidence a runtime can present decides which capabilities that copy keeps.

What each runtime can prove, and what it keeps

The same fourteen checks

The attester runs them for every copy, in one order. Only the evidence it asks for changes with the runtime.

  • One order
  • A key per copy
  • Evidence sets the ceiling
  1. A cloud workload

    The Batch Reviewer

    Proves itself with
    An SVID from the workload domain, bound to its own key.
    In the token
    assurance attested

    What it keeps 5 of 5

    • records.read, kept
    • records.annotate, kept
    • transfer.status, kept
    • transfer.initiate, kept
    • review.submit, kept
  2. A managed workstation

    The Analyst Companion

    Proves itself with
    An enrolled person, and its own key.
    In the token
    assurance asserted

    What it keeps 1 of 5

    • records.read, kept
    • records.annotate, withheld
    • transfer.status, withheld
    • transfer.initiate, withheld
    • review.submit, withheld
  3. A workstation with a hardware key

    Declared in the attester's table

    Proves itself with
    An enrolled person and a hardware bound key.
    In the token
    assurance attested

    The attester on this estate holds no hardware root, so no copy reaches this column today.

    What it keeps 3 of 5

    • records.read, kept
    • records.annotate, kept
    • transfer.status, kept
    • transfer.initiate, withheld
    • review.submit, withheld
  4. Keys held by the operator

    The Balance Monitor at Quillon

    Proves itself with
    A key its operator holds. The attester takes no part.
    In the token
    assurance absent

    This token carries no assurance claim.

    What it keeps

    No attester ceiling. The envelope set through its chain is the limit.

The API platformIt grants only inside the ceiling, and writes the assurance into the token.
  • The same checks everywhere

    Fourteen, in one order, for every copy the attester vouches for.

  • A key per copy

    Each attested copy proves the key it generated with its own client instance attestation.

  • Evidence sets the ceiling

    What a copy can prove decides which types it keeps.

  • Assurance in the token

    The platform writes attested or asserted into the token it issues.

Watch

Wherever it runs

2 min 35 s Open the film file

Which runtimes do you have, and which assurance would you accept for which envelope?

Ninety minutes, on the shape of your estate: which systems resolve first, which anchor each pins, and which key each party holds.

Next use case Across the boundary