RRVI™ Repository · Reference Document

Architecture

The architecture of the EU AI Act Compliance Management System™ — repository structure, the module model every one of the 70 documents follows, traceability, governance, inspection navigation, and versioning.

System: EU AI Act Compliance Management System™ Repository: RRVI™ Version: 1.0.2

On this page

  1. 01Purpose
  2. 02Architectural Principles
  3. 03Repository Architecture
  4. 04Module Architecture
  5. 05Compliance Architecture
  6. 06Traceability Architecture
  7. 07Governance Architecture
  8. 08Inspection Architecture
  9. 09Versioning Architecture
  10. 10Architecture Status
  11. FAQFrequently Asked Questions
01 — Purpose

What this document describes

This document describes the architecture of the EU AI Act Compliance Management System and the relationships between its components — how the repository is structured, how each module is built, and how everything traces back to evidence.

02 — Architectural Principles

Six principles the system is built on

01

Compliance by Design

02

Documentation by Design

03

Evidence by Design

04

Traceability by Design

05

Inspection Readiness by Design

06

Continuous Improvement

03 — Repository Architecture

How the repository is laid out

Every module sits at the same level, alongside the root governance documents that apply across all of them.

Repository │ ├── Root Governance Documents │ ├── Module 01 ├── Module 02 ├── Module 03 ├── Module 04 ├── Module 05 ├── Module 06 ├── Module 07 ├── Module 08 ├── Module 09 └── Module 10
04 — Module Architecture

The model every module follows

Every one of the 10 modules follows the same seven-stage engineering model, without exception:

Policy Procedure Work Instruction Checklist Register Evidence Declaration
05 — Compliance Architecture

What the system consists of

10Modules
70Controlled Documents

Alongside the 10 modules and 70 controlled documents, the system includes Repository Governance Documents, Version Control, Audit Documentation, and Inspection Documentation.

06 — Traceability Architecture

Every document links to the next

Policy Procedure Work Instruction Checklist Register Evidence Declaration
No declaration exists without supporting evidence. This is a structural rule of the traceability architecture — a Declaration with no linked Evidence is treated as incomplete, not as a stand-alone attestation.
07 — Governance Architecture

What governs the repository

08 — Inspection Architecture

How an inspector navigates the repository

01README
02DOCUMENT_INDEX
03Module
04Register
05Evidence
06Declaration
07Traceability Matrix
08Compliance Matrix
09 — Versioning Architecture

What each release includes

01

Git Tag

02

GitHub Release

03

Zenodo DOI

04

CHANGELOG Update

10 — Architecture Status

Current status

1.0.2Current Version
CompleteArchitecture Status
FAQ

Frequently asked questions

How many modules does the Compliance Management System have?

10 modules, together forming 70 controlled documents, plus repository governance, version control, audit, and inspection documentation.

What is the document model inside each module?

Every module follows the same seven-stage model: Policy, Procedure, Work Instruction, Checklist, Register, Evidence, and Declaration, each linked to the next.

Can a Declaration exist without supporting Evidence?

No. No declaration exists without supporting evidence — this is a structural rule of the traceability architecture, not a style preference.

In what order does an inspector navigate the repository?

README, then DOCUMENT_INDEX, then the relevant Module, then its Register, Evidence, and Declaration, then the Traceability Matrix, then the Compliance Matrix.

What governs the repository itself?

README, DOCUMENT_INDEX, DOCUMENT_TRACEABILITY_MATRIX, COMPLIANCE_MATRIX, CHANGELOG, AUDIT_PLAN, and INSPECTION_GUIDE.

What does each release include?

A Git Tag, a GitHub Release, a Zenodo DOI, and a CHANGELOG update.

What are the core architectural principles?

Compliance by Design, Documentation by Design, Evidence by Design, Traceability by Design, Inspection Readiness by Design, and Continuous Improvement.