Dashboard
Recent decisions
Integrity events
SDK & platform onboarding
Guided setup without the shell: create a tenant, register model + edge source, generate signing keys, issue role keys, apply a sector pack, and download SDK snippets. Edge devices still hold the private key — the platform only stores public keys.
Step 0 · Create a tenant
Tenant creation runs on the platform host, not here. It is the one action that needs the platform admin key, and that key is a shared secret with power over every tenant — pasting it into a browser is the last place it should go. The CLI reads the platform's own data directory, so no key is needed at all.
provenant-platform create-tenant \
--name "Northstar Ops" \
--admin-user ops@company.com
It prompts for the password, prints the tenant id and the edge ingest key once, and creates the first admin user. Sign in with that username and password, then run the bootstrap below.
On Azure Container Apps, run it inside the running container:
az containerapp exec -n provenant-platform -g <rg> \
--command "provenant-platform create-tenant --name X --admin-user Y"
One-click bootstrap
Registers model, source, AI system, role keys, optional sector pack, and a sample decision you can open in Why.
Bootstrap result — copy secrets now
Private key and API keys are shown once. Download or copy before leaving this page.
Step-by-step (same as shell, in the UI)
- Models — register model ID + manifest
- Sources — generate keypair here, register public key with source ID
- AI systems — create system and link model + source
- Access & audit — create ingest key for the edge, investigate for auditors
- Control policy / Sector packs — set fidelity rules
- SDK — use snippets below on the edge device
Edge SDK wiring
Install: pip install provenant-capture (or editable install from this repo). Point HttpEmitter at this platform.
Signed tree head
Recent integrity events
Governed execution
How much autonomy agents actually ran with, and whether any exceeded the cap in your control policy.
Flag histogram (recent)
Continuous logging evidence pack (Art. 12)
Build a multi-record period package with integrity status, posture snapshot, and Art. 12 control mapping — no CLI required.
Art. 12 controls
Package
New investigation case
Open cases
Case detail
Open incident
Decision-native incident: link decisions, export signed bundle, push ITSM ticket webhook.
Incidents
Incident
Register AI system
Regulated system object: purpose, risk class, linked models/sources. Bind inventory to live capture.
Import CSV rows (paste)
Header: name,purpose,risk_class,eu_risk_tier,owners,jurisdictions,model_ids,source_ids
Systems
System
Deploy / promote gate
CI-friendly check: system + model linked, lineage, optional eval attestation, no open integrity incidents. Promote issues a signed receipt.
Recent gate receipts
Model change justification
Draft → cite training episodes → submit (registers lineage + package) → accept (immutable).
Change cases
Change
Provision source
Register an edge source public key so ingest can verify signatures. Requires admin role.
Register model
Content-addressed model identity + manifest. Requires admin role.
Eval attestation (thin link)
Point at external eval artifacts — does not replace bias labs. Used by promote gates.
Change evidence
Active capture control policy
Enforced at ingest. Optional per-source override; leave source empty for tenant default.
Policy history
Retention & legal hold
Register GRC / CMDB connector
Import inventory only — do not rebuild ServiceNow. Export evidence references back to GRC.
Import JSON into connector
Connectors & import runs
Export evidence references (for GRC)
Sector packs
Vertical configuration: control defaults, profiles, gate defaults, investigator runbooks. Apply only when a design partner pulls.
Pack
Register webhook
Events: integrity, policy_violation, anchor, posture_degraded, incident, ticket, or *.
Configured webhooks
Recent deliveries
Your password
Changing it signs out every other session on your account — which is how you evict someone who has one. This tab stays signed in.
UI users (username / password)
Humans sign in with password. Edge/automation still uses API keys below.
Machine API keys
Roles: ingest (push only), read, investigate, admin. Primary tenant key is always admin.
Keys
Audit log (human actions)
Payload access log (B2.5)
Consistency proof
Create tenant
Creates the organisation, its edge ingest key, and the credentials for its first tenant administrator. That person is made to choose their own password on first sign-in, and from then on manages their own users.
Tenants
Select a tenant to manage its users and controls.
Tenant
Platform operators
AeroMind staff who administer the platform. They can manage tenants but hold no tenant's decision data.
Operator audit log
Every action taken by a platform operator, across all tenants. The same rows appear in each affected tenant's own log — an operator cannot act on a customer invisibly.