System architecture map
How DutyLedger flows: each role works through modules; each module produces auditable outputs. Every module block links straight into its page. The Mosaic flow — stack tiles, resolve, generate the compliance package, sign off — is explained in the help overlay.
Maximum authority: platform management, configuration, audit chain, plus full access to every register and module below
Statutory officer: full visibility of every register, record, report and oversight module; s 27 due-diligence and dual sign-off authority
Owns duties, triggers and corrective actions
Runs the floor, closes actions
Works under a permit
Reading the map
Records (incidents, observations, risks, chemicals, contractors) are the evidence base. The Mosaic engine compiles that evidence into work permits; the wellbeing module runs the k=5 suppression gate so cohorts stay anonymous; every mutation lands in the hash-chained audit trail surfaced in Admin.
Incident lifecycle flow
Every incident moves through six gated stages; the dual sign-off gate is what separates an investigation from a closed, audit-chained record.
Cross-module spawning
An incident is the parent record: from the incident page it spawns follow-on records in six modules, each carrying the bind query shown on its card.
?sourceType=incident&sourceId={id}Form pre-binds to the incident Safety Inspection?incident={id}Inspection schedule carries the incident Risk?incident={id}&incidentNo={no}Linked risk rides sourceType=incident MeetingToolbox or investigation meeting ObservationSafe/unsafe observation follow-up Due Diligences 27 officer review spawned from the caseeach record links back to its parent incident