Compliance console

Annex IV composer

Build Annex IV, section by section

Work through ten Annex IV blocks with guided prompts, evidence checks, and editable drafts.

Technical documentation composer with evidence checklist and traceability timeline

Why teams adopt the composer

Reduce copy-paste between Confluence, Git, and policy PDFs — one narrative with traceable references.

Guided interviews

Plain-language prompts surface missing lineage, bias mitigation, and oversight duties before legal review.

Source awareness

Attach architecture files, logs, and tickets so each paragraph maps to an artifact auditors can open.

Section integrity

Progressive completion meter shows which Annex chapters still need evidence — not just text.

Risk linkage

Cross-walk risk management measures to the technical capabilities you actually deploy in production.

Living document

Re-open any section after a model or data change; diffs highlight what must be re-attested.

Executive-ready

Export polished summaries for boards while engineers keep the deep annex in version control.

Annex workflow

ScopeDraftValidateFinalize

Annex IV technical documentation

Wizard view · align with internal style guides before external filing

Compliance map

Ten sections under Annex IV — complete evidence before sign-off.

COMPLETION70%
1. System Description
2. Model Components
3. Data Governance
4. Technical Specifications
5. Risk Management
6. Post-Market Monitoring
7. Record Keeping
8. Transparency
9. Human Oversight
10. Accuracy & Cyber
Step 3 of 10

Data governance & provenance

Document training, validation, and testing data — origin, selection criteria, and bias mitigation — with enough depth for competent authorities to verify claims.

Interrogating: architecture_v2.pdf

Analyzing technical sources…

Active scan

“I've identified pipelines referring to 'Synthetic-Set-Alpha'. Is this the primary training corpus for bias mitigation?”

Technical sources

architecture_v2.pdf
data_pipeline.py
testing_logs.csv

Compliance note · Article 11(1)

Documentation must allow authorities to assess compliance — include bias metrics, limitations, and mitigation strategies in one coherent narrative.