Docs
Technical documentation of the suite
Objective references for the mechanisms behind each product — what the anchoring marker means, how the hash chain ensures integrity and how a bug crosses triage from the scare to the proof of closure.
-
Triage flow: from the scare to the regression sensor
The path TriageBug imposes on every bug — reproduce, isolate, fix and prove — and why the last step is what prevents the return.
-
Evidence anchoring: how to read [A], [P] and [?]
Reference for the TriageCode anchoring scale — what each marker means, the mechanical obligation of each level and how the sensor verifies the citation.
-
Audit-hash chain: verifiable integrity of the decision trail
How TriageShield chains events with SHA-256 so that any tampering with the audit trail breaks the verification — and what that requires of the operation.