Who these docs are for

Every page carries chips under its title saying who it was written for. The concepts are the same for everyone; what changes is the depth and the vocabulary.

ExecutivesThree pages. What Stratl is, what it will not do, and what to ask before relying on it. No code, no cryptography.The one-page briefCompliance and legalThe record field by field, the frameworks the packs map to, notices and deadlines, retention and holds, subject requests, custody, and verifying without trusting us.The decision record, explainedPortal usersOne page per screen, in the order you meet them. If you are the first person in a workspace, Get started walks you to your first verified record.Sign in and create a workspaceEngineersFrom an empty laptop to a running Stratl, then the SDKs, connectors, the record format and its integrity, custody on your cloud, the API and deployment.The developer documentation

If you are new to all of it

Read these five, in order. Together they take about half an hour.

1. What is Stratl?
2. Concepts and vocabulary
3. A five-minute tour of the portal
4. The decision record, explained
5. Verify evidence without Stratl

How the docs are organised

• Start here is for everyone and assumes nothing.
• For executives, For compliance and legal, Using the portal and Building with Stratl are the four paths. They cross-link constantly, so a legal reader who wants the engineering detail is always one click away, and the reverse.
• Reference holds the glossary, every configuration setting, the FAQ, the changelog and the API reference generated from the running service.
• Maintaining these docs explains how to change any of this. The site is a folder of Markdown files; anyone on the team can edit it.