Architecture

How the core service works. For environment setup, start with Getting Started; for making changes, see Schema & Codegen; for where the code lives, browse the core repository directly.

How the System Works

• Request Lifecycle: middleware stack, transaction boundaries, REST and GraphQL coexistence
• Workflows Engine: approval and automation flows

For orientation to the compliance object model, the platform overview covers the domains and their relationships, and the GraphQL object reference is the authoritative schema.

Authorization lives with the rest of the access-control material; see Privacy and Authorization in the Security section. The tenancy model itself (organization isolation, hierarchy, and permission inheritance) is covered in Organizations.

Supporting Repositories

The core service leans on shared libraries maintained in their own repos; see Helper Repositories for what lives where.

Several in-repo packages also carry their own documentation, maintained beside the code:

• Object storage: the provider-agnostic storage layer (S3, R2, disk, database)
• Gala: durable event dispatch built on River
• Integrations framework: the provider builder system
• Config generation: how Helm values and external-secrets resources are generated from Go structs