Requirements, governance and enterprise review
Balanced process contract
Interfaces drawn with their declared state and the verification that keeps both sides balanced — the contract as a diagram.
ddn@1New DDN source
Why use it?
Integration defects are contract assumptions colliding; drawing the declared state on each side exposes the mismatch.
When it helps
Interface design between systems or teams, especially asynchronous ones.
How to read it
- Each side declares what it provides and expects; the verification marks say how balance is checked.
- A state declared on one side with no counterpart is the integration bug you just found early.
What you need
- The interfacing parties
- The declared state per side
- The verification method
Things to check
- Do not leave the verification method as "testing" — name the check.
- A balanced contract says nothing about latency; declare that separately.
Scope of this diagram
Declared contracts and verification intent; runtime conformance monitoring is out of scope.
Work with the converted example
- Open the viewer and select
balanced. 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.