Private architecture evidence review
Find where the submitted architecture and machine evidence disagree.
Load the architecture your team or client submitted, add current Terraform or AWS Config exports, map legitimate aliases, and work a source-linked exception queue. Your files stay in this browser.
Private, browser-local review
Files are parsed in this browser. Diogrum does not upload them. Saving is explicit and uses this browser's local storage.
Private workspace exports contain the full source artifact text.
1 · Assertion
Submitted architecture
Mermaid or uncompressed draw.io XML.
current-architecture.mmd
2 · Evidence
Machine evidence
Add every export relevant to this boundary. Raw HCL is not inferred.
Source 1: evidence-1.json
3 · Identity
Map names that refer to the same thing
Diagrams use business names while evidence uses resource IDs. Add explicit mappings; Diogrum will not silently guess.
Run once to discover exact entity names, then map any legitimate aliases and rerun.
4 · Reconcile
Build the assessor review queue
Exact support can pass. Every contradiction, omission, conflict, stale source, and unknown remains reviewable.