United States · CC7 and CC8
5 of 5 answered from the record. 1 more is outside the record — real obligations that no runtime log can evidence, listed rather than counted.
| Obligation | What proves it | Status |
|---|---|---|
| The system is monitored for anomalies, every day of the period.CC7.2 | The whole period's record, anchored every five minutes rather than sampled.4827 actions · 184 checkpoints, 180 countersigned · #0 | Satisfiedfrom the record |
| Identified events are evaluated by someone accountable.CC7.3 | Approvals and refusals carry the person and the rule that decided them.released by dev@lender.io · #20, #50, #57, #73 | Satisfiedfrom the record |
| One session id joins every plane that saw the run.2 sessions corroborated |
| Satisfiedfrom the record |
| Changes to what the system may do are authorised and recorded.CC8.1 | Every rule change is itself an event, and a rule version is the hash of its own bytes.rule changes are appended, never overwritten | Satisfiedfrom the record |
| Access is restricted to what each actor needs.CC6.1 | Deny-by-default tool scope, bounded by the invoking user's own rights.181 refusals recorded · #18, #23, #24, #48 | Satisfiedfrom configuration |
| Somebody signs off on the period before it closes.CC4.1 | A named person, on the chain, like everything else.Sign the period from the Evidence page. | Outside the recordnothing here can answer it |