Authoritative standards for defining binary logic, deterministic branching gates, swimlane boundaries, and state resolution across operational workflows.
A decision diamond serves as a single evaluation junction. It must accept strictly one incoming path and release two or more mutually exclusive outgoing vectors. Text inscribed inside the diamond shape must frame an explicit binary or discrete query rather than an operational activity.
Compliant Phrasing
[Is Verification Complete? (Y/N)]
Framed as a state evaluation query with strict boolean outcomes.
Non-Compliant Phrasing
[Review Request and Notify User]
Combines process execution with evaluation, creating ambiguity.
SYNTAX-02Section 2.0
Deterministic Gate
Mutually Exclusive Exit Paths
Outgoing branches must be exhaustive and mutually distinct. No data condition should simultaneously satisfy multiple diverging edges from the same vertex. When multi-tier evaluations exist, convert them into sequential decision diamonds or explicit discrete tables.
Every exit line must display an explicit label (e.g., "Approved", "Rejected", "Threshold Exceeded").
Implicit default fallthrough paths are prohibited; an explicit fallback gate must be documented.
Conditions must reference measurable variables available at that exact timeline milestone.
GOV-01Section 3.0
Custody Standard
Decision Custody & Swimlane Boundaries
Every decision diamond must reside strictly inside a single organizational swimlane or system component lane. Crossing a lane boundary inside a diamond vertex is disallowed. If secondary sign-off is required, a distinct sequential diamond must be instantiated in the secondary participant lane.
RACI Mapping Protocol:
Evaluator (Responsible)Operator analyzing parameters inside lane boundaries.
Sign-off (Accountable)Designated authority committing final outcome.
Premature branch convergence leads to corrupted audit logs and missing contextual states. When divergent flows execute independent validation tasks, they may only merge when downstream requirements are fully equivalent regardless of preceding route histories.
Convergence Rule A
All required data keys produced in divergent paths must align to a shared target schema prior to merge point insertion.
Convergence Rule B
Exception and escalation paths must conclude in terminal states or dedicated escalation loops without silently merging into normal pipelines.
INT-01Section 5.0
Diagram Markup
draw.io Architecture & XML Tagging
For machine-readable diagram export and automated compliance checking, draw.io custom shapes must include custom properties specifying decision codes, gate identifiers, and evaluation types.
Custom Object Metadata FormatXML / draw.io
No Matching Specifications
Adjust your search query or reset the module filter above.
