Clearception
Illustrative Demo — Simulated Policy Decisions. Decisions are computed in your browser from a fixed example policy. Tenant, repository and agent names are synthetic. Nothing is sent to TrustFabric.
Clearception TrustFabric

A development agent asks for a restricted client repository

Tenant acme-regulated keeps client code in client-ledger-service, under a regulated jurisdiction. Change the scenario and follow the request through the gateway to the decision and its evidence record.

Simulated walkthrough

Scenario inputs

Simulated decision: Require approval

  1. Request submitted

    dev-agent-07 (Claude Code) asks to write code / open pr on client-ledger-service.

  2. Context identified

    Agent
    Claude Code · voluntary enforcement
    Tenant
    acme-regulated
    Repository
    client-ledger-service · Restricted
    Operation
    Write code / open PR
    Policy context
    European Union profile · Same-region approved endpoint · approval none
  3. Gateway evaluates

    The authorization gateway evaluates the request against approved bundle sdlc-sovereignty v12. Rules are checked in order and the first match decides; with no matching allow rule the answer is Deny.

  4. Controls checked

    • Security — approved model providerPass
    • Data sovereignty — cross-border transferPass
    • SDLC — change control for deploy and exportPass
    • Legal — client data handling obligationsApproval required
    • Security — agent execution pathPass
  5. Decision

    Require approval
    • The repository holds restricted client data.
    • Changing it (write code / open pr) requires a human approval under the client data handling obligations.
    • Claude Code calls the gateway through a hook it could disable, so this decision is voluntary enforcement.
  6. Recorded as evidence

    Record
    ev_0495665fb3305534
    Chained to
    ev_da0060582223daab
    Note
    Simulated identifiers. In the product each record is HMAC-chained per organization.
  7. Developer gets an explanation

    Next action: An approval request has been opened for the repository owner. Read-only work and test runs can continue meanwhile.

In the product, rules come from your own approved policy bundle, and the gateway fails closed: missing required context returns Insufficient context and no matching allow rule returns Deny. Enforcement levels are shown honestly per agent — see agent permissions.

Request a demo

Tell us about your environment and we will contact you about a demo or an Enterprise quote. Requesting a demo commits you to nothing.

Current development platforms
* Required