> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform architecture

> Technical boundaries between the Console, consumer portal, APIs and supporting services.

Revision: 2026-10-13.

## Applications and responsibilities

The business Console manages workspace records, keys, policies, workflows and billing. Platform Administration handles staff review and platform operations. The consumer Verify application provides individual account workflows and record checking. The public documentation site is maintained through Mintlify; it does not run the old Next.js documentation application.

```mermaid theme={null}
flowchart LR
  C[Business Console] --> A[Authenticated service APIs]
  V[Consumer Verify] --> A
  P[Platform Administration] --> A
  A --> R[Identity and issuer registry]
  A --> S[Signing and verification]
  A --> T[Transparency and audit]
  A --> W[Workflows and automation]
  A --> B[Billing]
  R --> D[Managed PostgreSQL]
  S --> K[Managed signing keys]
```

## Identity and isolation

Services validate credentials and derive account context from authenticated identity. A caller-supplied tenant header is not authority to access another account. Database row-level policies provide another boundary, while individual operations enforce permissions and record ownership.

Sandbox and production are separate operating environments. Record identifiers, API credentials and environment selection must agree. Do not treat a sandbox test as evidence of production acceptance. New accounts must complete the applicable onboarding and production-access review before production use.

## Evidence and verification

The signing service produces signatures with a selected available key. The transparency service records log entries and proof references. Verification checks the evidence supplied and the available registry state. A record's signature establishes integrity and attribution to a key; it does not establish that every claim is true.

Keep original payload bytes and proof bundles needed for independent checks. The printable certificate is a readable summary, not a replacement for cryptographic verification.

## Infrastructure and operating limits

The current deployment uses Google Cloud for compute, managed PostgreSQL, secret storage and managed key operations. Email delivery uses Zoho SMTP. Available billing providers depend on the verified billing country and configured payment capabilities.

Recovery objectives and availability commitments require a demonstrated restore and operational evidence. Do not infer a contractual SLA, multi-region recovery capability or completed certification from this architecture. Historical evidence depending on unavailable former signing keys cannot be made verifiable by relabelling it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.