Governance and evidence pack

Forge ties governance to evidence in the repository: versioned policies (Blueprints), decision records, and release readiness linked to work-unit IDs. This supports architecture review, change control, and audit without parallel “documentation theater.” Enterprise patterns: scaling ForgeSDLC.

Audit and compliance

Controls in Blueprints — discipline files encode what must be checked (security, compliance, testing)
Versona sessions — time-bounded application of that knowledge to a specific decision, with outcomes suitable for evidence packs
Immutable history — git history on Blueprints, ADRs, and merged PRs provides who changed what, when

Map organizational control IDs to blueprint sections and template outputs in your enterprise change playbook.

Architecture review

ADRs for cross-cutting technical choices; link from Sparks and Ingots that implement them
Architecture Versona when the blueprint calls for gates (interfaces, NFRs, deployment topology)
Knowledge base depth for methodology context: knowledge hub

Change control (operations / ITIL-style)

Release readiness — Assay Gate ties ship / no-ship to criteria, tests, and traceability (ceremonies)
Standard changes — encoded as repeatable Spark patterns + automation; normal / emergency paths still use your tooling (tickets, pipelines)—Forge supplies what to prove

Coexistence summary

Framework	How Forge typically maps
TOGAF	ADRs + architecture blueprints ↔ architecture repository expectations
ITIL	Change records ↔ pipeline + Assay evidence; DevOps blueprint alignment
ISO 27001	Security blueprint controls ↔ control testing notes and session records
CMMI	Process areas ↔ blueprint policies + journals showing planned / performed / measured

Artifact crosswalk

See artifacts before and after for day-to-day naming.

Templates and ceremony I/O live in the Blueprints handbook—use it as the source of copy-paste structure; keep Forge.com pages as sponsor and pilot narratives.

Next: Executive overview · Sponsors hub