tegwick 56b8d61583 Work the register due list, and add the one-check-per-sitting rule ... Nine records checked. Five clean and climbed to 1h: RISK-F-0003, 0004, 0005, 0006, 0009 and RISK-REG-0001. Three moved and stay at instant — RISK-F-0002 (RISK-V-0001 found the flex-auth-ops-warden policy admits no ingress, so the live question there is now availability rather than attestation), RISK-F-0007 (the on-request path walked for the first time as RISK-V-0002), RISK-F-0008 (the determination now exists). The rule: a finding recorded as moved is not clean-checked in the same sitting. Re-reading your own keystrokes and climbing produces a rung that says the world held still when what held still was the last five minutes. The rung carries stability information or it carries nothing. record_check.py now handles regulatory records as well as findings. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-08-20 12:03:12 +02:00
..
__pycache__	RISK-WP-0004: five of six tasks done; the executor is the operator's call	2026-08-20 08:49:23 +02:00
inbox_check.py	RISK-WP-0004: five of six tasks done; the executor is the operator's call	2026-08-20 08:49:23 +02:00
record_check.py	Work the register due list, and add the one-check-per-sitting rule	2026-08-20 12:03:12 +02:00
register_check.py	RISK-WP-0004: five of six tasks done; the executor is the operator's call	2026-08-20 08:49:23 +02:00
register_index.py	Adaptive check cadence: the interval is earned, not assigned	2026-08-20 07:43:51 +02:00
register_lib.py	RISK-WP-0004: five of six tasks done; the executor is the operator's call	2026-08-20 08:49:23 +02:00