How-to guides
Goal-oriented procedures for designing a system and turning accepted rules into executable work.
The workflows, standards and defaults used on every project: what to do, which rule governs it, and why that rule exists.
Goal-oriented procedures for designing a system and turning accepted rules into executable work.
The working rules, architecture default, technology choices and cross-stack disciplines.
Exact artefact contracts and terminology, with the reasons and trade-offs behind each rule.
One rule, two decisions
Variable values belong in the model from the start. The screen, validation and governance that let a client administer them are a separate decision, justified by who uses them and how often.
Open systems and the two decisionsCIR-006 — Transmettre pour décision
Act the direction closes its analysis
Initial state En analyse
Authorised actor Agent traitant, scoped to the seised unit
Preconditions an opinion of the central direction is on file
Resulting state En attente de décision
Trace author, timestamp, opinion reference
Notification the applicant, of the state change
Atomicity state, trace and notification succeed as one
Observable the file appears in the decision queue