Pyxproof

Operator console Back to introduction

Five stories, ten minutes

Each story runs against the live prototype. Nothing on this page is a recording.

I

Admit or refuse

Two applicants. One is clean. One is on a screening list.

II

Allow or block

One tenant, three requests. Every refusal names its rule.

III

Prove it

Verify the record, alter one entry, and watch it get caught.

IV

Never trust, always verify

An AI agent with its own short-lived credential. Scope, region, data class, suspension, and a list that changes.

V

Do not trust us either

Issue a proof, check it in this browser, try to cheat, then challenge a decision.

What happened

  1. Run a story to begin.

Tenants

TenantCountryOwnersStatusScreened against

Access

Every user and AI agent holds its own credential under a tenant: a narrower scope and a short life. Trust is checked on every request and can be withdrawn at any time.

PrincipalKindTenantModel scopeExpiresStatus

Requests

#TenantModelOutcomeRuleDetail

Ledger

#WhenTypeSubjectOutcomeRuleHash

The standard this engine is built to evidence.

ControlRequirementInstrumentStatusEvidence in this record

The published rules

Every decision cites one of these. An operator can read them before it is judged by them.

RuleStageText