Getting started

One wiki. Every role.
Your compliance map.

AI Comply is guidance, not a rulebook. Same obligations, one place, in the language of your role and your stage. You decide how deep to go.

How it works

Three steps to your first doc

01

Choose your entry

Start from Compliance Paths (tailored to your org), Stages (browse the lifecycle), Instant Audit (find gaps), Enterprise AI Maturity Audit (find your level), or Search (find anything, anytime).

02

Set your role(s)

On any document page, tap Select role in the header to open the role picker. Choose one or more roles — we remember your choices across sessions. Change them anytime.

03

Read your slice

Use the Role Perspectives section to see controls, deliverables, and evidence for your selected role(s). Switch the Rosetta Stone lens for Technical, Legal, or Executive language.

Where to start

What do you want to do?

All paths lead to opening a document. Pick the entry that matches your intent.

Roles

Eight roles, one wiki

Every document is written for multiple roles. Pick yours so we show you what applies. This is guidance — same obligations, in the language of your role.

On any document page, use Select role in the header to open the role picker and choose one or more roles. We remember your choices. Same obligations, in the language of your role(s).

Architect

System design and cross-cutting decisions

StartStages 2 (Design), 4 (Deploy)
ReadsCompliance claim, Role Perspectives for architecture and audit trails
CXO

Executive sponsor, sign-off, risk acceptance

StartStage 1 (Inception), sign-off gates
ReadsCompliance claim, Executive lens in Rosetta Stone, sign-off and budget controls
Engineer

Application and software development

StartStages 2-3 or Compliance Paths
ReadsCompliance claim, Technical lens in Rosetta Stone, implementation controls
Data

Data pipelines, datasets, and ML data

StartStage 2 (Data) or Stage 3 (Metrics)
ReadsTechnical lens, data governance and fairness modules
DevOps

Deployment, infrastructure, and SRE

StartStages 4-5 (Deploy, Operations)
ReadsRole Perspectives for infra, runbooks, and access control
Compliance

Governance, audit readiness, and evidence

StartCompliance Paths or Instant Audit, then any stage
ReadsCompliance claim, What auditors ask, Legal basis, evidence checklists
Legal

Contracts, regulatory interpretation

StartSearch or Stages for high-risk docs
ReadsLegal basis, Legal lens in Rosetta Stone, Compliance claim
Security

Security testing and access control

StartStage 3 (Security), Stages 4-5
ReadsRole Perspectives for security controls, adversarial testing
On a document page

What you'll find on each doc

Compliance claim What must be done and why. The single obligation this document covers.
Legal basis Which laws and standards apply. Expandable accordion with regulation details.
What auditors ask The question an auditor would ask about this control. Your evidence target.
Rosetta Stone Key concepts defined in three lenses: Technical, Legal, and Executive. Switch between them to read in your language.
Role Perspectives Controls, deliverables, and evidence for each role. Filtered by your selected role(s) or view all at once.
Audit checklist A checklist of what to verify and what the auditor looks for. Track your progress.
Sidebar navigation All stages and modules in one panel. Jump anywhere without leaving the document layout.
Search Press ⌘K from any page. Find stages, modules, or documents by topic or keyword.
What you already know

We built on what you know

Checklists and sign-offsWe map who does what and what evidence looks like.
Legal and Engineering speak different languagesWe show the same obligation in Technical, Legal, and Executive words. We call it the Rosetta Stone.
Stages: design, build, test, deployWe use seven, from inception to retirement. Jump to the one that matters now.
Audits need evidenceEvery doc says what to produce and what auditors look for.
Best approach

The short version

Set your role(s) the first time you open a doc. Browse by stage or narrow by Compliance Paths. Use Search when you want to find something specific — no need to browse first. On each doc, read your role(s) and Role Perspectives. That's the flow.

You can't break anything. Change your role(s), try another path, or search again anytime.