πŸ”AI System Audit Trail Infrastructure

Observability, traceability, lineage, integrity, monitoring, documentation
with AI Act compliance as the first killer use case.

Orbit is AI System Audit Trail Infrastructure. We provide the logging standard, integrity service, and compliance workflows that enable observability, traceability, and regulatory documentation. AI Act compliance is the first killer use case, not the only value.

AI Act: phased application through 2028
Data Act: applies since 12 September 2025
🎯

Not just compliance documentation

β†’ AI System Audit Trail Infrastructure

Orbit provides observability, traceability, lineage, integrity, monitoring, and documentation for AI systems. AI Act compliance is the first killer use case, enabling vendors to sell to banks faster. But the value extends beyond compliance to operational excellence and risk management.

The Problem

Modern data systems face four converging pressures that existing infrastructure cannot address

πŸ”

No Verifiable Audit Trail

Organisations can claim anything about how they use your data. Users can only trust, but never verify. Regulators can only investigate after the fact.

βš–οΈ

AI Act + Global Regulation

EU AI Act obligations apply in stages. Transparency rules already apply; high-risk requirements follow in 2027 and 2028. Organisations need traceable records to support the obligations relevant to their systems.

πŸ”—

High-Risk AI Systems Need Provable Data Lineage

KYC, healthcare, hiring, credit decisions, and insurance systems must prove what data was used, under what consent, who accessed it, and when.

🚫

Missing Declarations, Not Missing Storage

Everyone already has the data. The problem: nobody is required to declare what they actually did. If they lie, omit, or fail to record, users can't detect it.

Orbit's Solution

What Orbit stores (and what it doesn't)

  • βœ“Pointers to where data already lives (off-ledger)
  • βœ“Hashes of data as it was at specific timestamps
  • βœ“Declarations from organisations about their actions, signed by Orbit on receipt
  • βœ“User consent state (granted/revoked scopes)
  • βœ“Access/share/update events with full attribution
  • βœ—Never stores PII β€” all sensitive data stays off-ledger
πŸ”

Signed Event Ledger

An audit trail that sits around existing systems. Never stores PIIβ€”only pointers, hashes, signatures, and declarations. Hash-chain verification is in development; when live, it is verified by Orbit, not independently.

πŸ“Š

Off-Ledger Snapshots

Data stays where it is. Orbit stores pointers and a hash of each snapshot as it was recorded.

✍️

Signed Declarations

Organisations declare their actions, and Orbit signs each declaration on receipt: profile updates, data usage, sharing events, consent changes.

βœ…

Consent State Tracking

User consent state (granted/revoked scopes) tracked per organisation, with policy checks for usage outside the recorded consent scopes.

πŸ”„

Verification Routing

Routes verification requests between organisations without touching raw PII. Records verification outcomes in the ledger.

🚨

Undeclared-Event Detection

Policy engine detects usage without consent, unknown recipients, hash mismatches, and anomalous access patterns.

How Orbit Fits

The audit infrastructure layer around existing systems

Upstream: Organisations Declare Possession

"We hold data about this user. Here's the snapshot pointer + hash."

🌐
Orbit
Audit Layer

Downstream: Organisations Declare Usage

"We used fields X/Y/Z under scope A for purpose B, at timestamp T, signed by our system."

Orbit becomes the record layer between organisations and users

Event Types (Ledger Schema)

PROFILE_REGISTERED

Org registers initial user profile snapshot

PROFILE_UPDATED

Org updates user profile snapshot

CONSENT_GRANTED

User/system grants consent for a scope

CONSENT_REVOKED

User/system revokes consent for a scope

DATA_USED

Org declares usage of user data for a purpose

DATA_SHARED

Org declares sharing data with another org

VERIFICATION_REQUESTED

Requestor asks Orbit to route a verification claim

VERIFICATION_RESPONDED

Verifier responds to a routed verification

Why This Matters Now

βš–οΈ

AI Act Compliance

Phased requirements, not a single deadline

Transparency rules apply since 2 August 2026. High-risk rules apply from 2 December 2027 for Annex III systems and 2 August 2028 for AI embedded in regulated products. These include logging, documentation, risk management, and human oversight.

Check the rules and transition arrangements for your system.

European Commission implementation timeline

πŸ“Š

Data Act

Applies since 12 September 2025

Organisations must enable users to access and share data generated by connected devices and services. Orbit tracks consent and sharing events.

Regulatory information checked: 26 October 2026.

Revenue Streams

B2B: Compliance Infrastructure

Infrastructure for organisations to write signed declarations

B2B: KYC Integration Layer

Primary GTM. Integrates with KYC providers to create reusable identity attestations. 40–60% cost reduction for financial institutions.

B2B: RegTech Audit Dashboards

Real-time compliance reporting, data lineage visualisation, risk scoring for banks, fintechs, healthcare providers

Technical Infrastructure

πŸš€

Phase 1 (2025–2026)

Centralised Audit-Log-as-a-Service

  • β€’ Single-environment deployment
  • β€’ Ledger schema + snapshot model
  • β€’ Consent model + policy engine
  • β€’ Verification routing service
  • β€’ Web UI for timeline & integrity checks

Orbit transforms regulatory compliance into shared infrastructure

Orbit is the missing infrastructure layer of the digital identity stack. A signed record of who did what with a user's data.

Go-To-Market Strategy

Validate audit workflows with KYC vendors

Support preparation for phased AI Act requirements

Explore enterprise and cross-border use cases

Try Orbit PoC

Proof-of-concept for AI providers: Compliance Workflows and Technical Documentation Generation

πŸ“‹

AI Act Technical Documentation

Compliance documentation as a service for AI providers. Generate Annex IV, VIII, and XI technical documentation using the Orbit Integrity Service and Compliance Workflows.

βœ“Orbit Integrity Service: Event signing (HMAC-SHA256)
β—‹Hash-chain verification: in development (verified by Orbit, not independently)
βœ“Compliance Workflows: Governance alerts from the policy engine (proof of concept)
βœ“Documentation Generation: Annex IV, VIII and XI bundle drafts from logs (proof of concept)
Open AI Act POC β†’