Requirements, governance and enterprise review
External gates with required evidence
The governance gates an external party imposes, drawn with the evidence each gate demands before passage.
ddn@1New DDN source
Why use it?
Audit surprises are usually known gates nobody drew; the diagram makes the evidence list a design input.
When it helps
Regulated delivery: planning for audits, certifications, external sign-offs.
How to read it
- Gates are the checkpoints; their attached notes list the required evidence.
- Read the order — evidence produced out of order is evidence produced twice.
What you need
- The external gates
- The evidence each requires
- The order they fall due
Things to check
- Do not paraphrase a regulator's requirement — quote it and trace your artefact to it.
- A gate with no owner produces its evidence at the deadline, badly.
Scope of this diagram
Declared gates and evidence lists; compliance itself is an audit outcome, not a render outcome.
Work with the converted example
- Open the viewer and select
external. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.