Files
felhom.eu/documentation/audits
admin 71c43f87c2
gates / gates (push) Successful in 6s
SPIKE R-241 — ruled: a MINTING defect, not a screen-predicate defect
Read-only spike on the standing venue (demo-hp VM 324 finalwalk-appliance),
read before anything else touched the fleet. No product code written.

THE RULING. The recovery screen was telling the truth. There genuinely was
nothing recoverable under the key the box held, because the box minted that
key itself over the top of a sealed package it already knew the hub held.
Fixing the predicate would paper over a box quietly making its own history
unopenable.

Three measurements carry it:
  1. WriteOffboxSecrets (offbox.go:411) mints on ONE input - does the file
     exist. Its two neighbours in the same file both consult
     GetHubEscrowIdentityPresent(). Same fact on three paths, used on two.
  2. The flag was the PRECONDITION of the chain that reached the minting:
     the retry job only logs when the declaration is live, and the venue
     logged it at 02:48:03Z - 30 minutes and six ticks before the mint.
  3. The box KNEW and discarded it: at 03:28:03Z, 35 minutes before the
     customer looked, escrow_confirm.go:154 computed the exact
     discriminator and logged the mismatch. Never persisted, never surfaced.

And the hub explicitly disclaims doing this - offsiteheal's package doc:
'credential automatic, key customer-present ... must not quietly widen'.

Also answered: Q2 (shape (b) is structurally unreachable - the escrow gate
sits upstream of the only orphan producer, with a positive control that the
scheduler was alive); Q7 (the 'create a new code' button does NOT destroy
the data - R-198's retention holds - but it converts a self-service recovery
into one needing an unbuilt read path, and it re-enables the screen while
invalidating the code that screen accepts).

New rows:
  R-242 - a release that changes customer-visible behaviour is not delivered
          until a golden carries it, and nothing enforces that. Recorded
          with three proposed shapes; deliberately NOT built.
  R-243 - a box in this state silently stops backing up and NO alarm fires:
          three individually-correct exclusions leave one state unobserved.

Highest register ID moves R-241 -> R-243.
2026-08-07 08:53:16 +02:00
..
@
2026-07-14 00:45:20 +02:00
@
2026-07-14 10:12:21 +02:00
@
2026-07-14 12:17:26 +02:00
@
2026-07-14 12:17:26 +02:00