capability map: the recovery row stays FAIL — what Phases 2+4 add, and what they do not

Browse Source

Says explicitly that these faults are NOT a re-walk, so the row cannot go green
on them. What they add: the BACKUP promise strengthened (the offsite tier ran
itself at 04:15 on a twice-rebuilt box, snapshot_count 1->2; all five daily jobs
fired once; nothing on the must-not list fired), R-217 and R-215 proven live
under exactly their faults, and the set-aside proved not to delete (12 535 KB
byte-exact at the far end).

What they do NOT add: any progress on the JOURNEY. R-224 is Phase 1's headline
defect relocated from the version channel to the transport — a hub outage and a
stopped agent are both reported as a bad recovery code, in 0.056s and 0.030s,
with no unseal attempted. Plus R-225, R-226, R-228.

Also records that §4.1 is now MEASURED rather than deduced, and §4.2's positive
half still is not.

...

This commit is contained in:

authentik Default Admin

2026-08-06 04:33:27 +02:00

parent 9c1d05d360

commit 453e4503a9

1 changed files with 1 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

documentation/architecture/00-capability-map.md

+1 -1

File diff suppressed because one or more lines are too long