Five steps · no assessment writing
From premises to evidence pack
Fire Clock is a compliance tracker, not an assessment writer. You describe the building, the product generates what is due, you record what happened, and you keep a pack that cannot be quietly edited later.
The loop
Describe, generate, record, export
Every step writes something you can hand over. Nothing in the chain depends on remembering.
$ fire-clock status
✓ rule set 2026.2 · England
✓ records append-only
✓ evidence hashed at upload
✗ high-rise 18m+ unsupported
$
-
Add a premises
Capture address, use, height band, assets present, assessment date and the Responsible Person. Buildings 18 metres or taller are flagged as unsupported rather than given an incomplete calendar that looks complete.
premises.create → height band → assets
-
Generate obligations
A versioned rule set for England produces the duties that apply. Each item carries a plain-English explanation, a source, a rule-set version, and a basis flag: statutory or good practice. Rules that do not apply appear as dormant with an explanation — they are not silently omitted.
rule set 2026.2 → obligations[] → basis flag
-
Record append-only events
When a check is done — or not done — you write a permanent entry. Optional notes and evidence files are hashed on upload. A mistake is corrected by a superseding record that cites its predecessor. Nothing is deleted.
event.store → sha256(evidence) → sealed
-
Export the evidence pack
Hand an enforcing authority, insurer or incoming assessor a pack that shows what was due, what was recorded, and which rule-set version applied. Branding can change the cover; the record, hashes and rule-set version cannot.
pack.export → cover + record + hashes
-
Daily digest, even when empty
The digest always sends. An empty digest is the signal that the system is alive. A separate heartbeat alerts operators if the digest did not run.
digest.send → heartbeat.check