STATUS: back to one screen

STATUS.md

@@ -44,15 +44,9 @@ Proven end to end on real hardware.
   never been tested on either machine. Both also proved their off-site copy on the same night, one
   after the other rather than at once, which is the machine deciding for itself what to do first.
   *(closes the last open half of R-86/R-185)*
-- **A backup copy the machine was never allowed to read — and could not tell you about.** One demo
+- **A backup copy the machine was never allowed to read — and could not tell you about**, on both
-  machine kept its whole-machine backups on a dedicated storage area the agent had never been granted
+  demo machines. The permission was one command; the silence was the real fault, and the machine now
-  permission to read. Asked what was there it was told "nothing", while an administrator saw three
+  checks whether it may read each copy it depends on and says so when it may not. *(R-185)*
-  backups. **The permission was one command; the silence was the real fault** — a storage that answers
-  "nothing" looks exactly like a brand-new one, which is a normal, healthy state, so that copy had
-  never been test-restored and nothing had ever mentioned it. The machine now checks whether it is
-  allowed to read each copy it depends on and says so when it is not — the alert reached you by email
-  before the permission was granted, which is the whole point. **Both demo machines carried it and
-  both are fixed**, and new machines no longer inherit it. *(R-185)*
 - **Three ways the alarm system was misreporting its own work — all fixed.** None of them ever risked
   data. **(1)** When the machine proved a backup restores, that result could vanish if the agent was
   restarted in the following quarter-hour — and yesterday's change made the gap a week rather than a