The Compliance Platform is the review and disclosure surface for Arcane. It is separate from the end-user transaction path and is used when an approved compliance, audit, support, or investigation workflow requires access to private transaction evidence.
Access to the Compliance Platform does not make every private transaction visible. Users can review only the evidence allowed by their organization, application, permissions, case assignment, and access window.

​
Disclosure flow

1

Arcane indexes transaction evidence

The platform reads registered transaction sources and stores the records required for interpretation and authorized review.
2

A user requests disclosure

The request records the purpose of access and the proposed scope, including the relevant application, contract boundary, historical review period, access duration, disclosure fields, and assigned reviewers.
3

An authorized administrator reviews the request

The administrator approves or rejects the request according to the client’s access model. Approval creates the basis for a controlled review case.
4

The platform establishes the review boundary

The case defines assigned reviewers, permitted evidence, approved fields, and the duration of access.
5

An assigned reviewer examines the approved evidence

The reviewer can access only the transaction data available within the active case scope. Unrelated private activity remains outside the review.
6

The platform records the outcome

Authorized users can generate reports within their permissions. Case decisions, reviewer assignments, report generation, downloads, and administrative changes are written to the activity trail.

​
Control model

​
Platform responsibilities

The Compliance Platform provides:
  • organization and application boundaries;
  • identity, roles, and permission enforcement;
  • disclosure request and approval workflows;
  • review cases, assignments, and access windows;
  • scoped transaction review;
  • report generation and downloads;
  • activity records for governed workflow and administrative actions.
The client should route sensitive access through an approved case and retain stable product references and public transaction identifiers in its own system of record.

Create a case

Continue to the case creation workflow.

Manage user access

Configure organization membership and application-scoped permissions.