Developer Guide

This section contains development guidance for Assurance Forge contributors.

Start here:

• Documentation map — which page is canonical for which policy, what each authority level means, and what the CI documentation gate enforces. Read this before adding a page.
• Layers and ownership — what each subsystem owns and which direction dependencies may run.
• Generating class diagrams
• Releasing — how a release is cut, and what its notes must say.

Repository quality

• Repository quality baseline — a measured snapshot of size, tests, coverage, architecture gates, documentation reach, and tooling, with the gaps named. Regenerate it with python tools/quality/collect_baseline.py.
• Code coverage — why the project publishes several coverage views rather than one headline number.