coulomb/informed-decision
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Prepare pinned fresh authentication rollout and rollback with container proof

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1029c-c003-7283-acc9-930b434e6cae
This commit is contained in:
tegwick 2026-10-03 20:36:00 +02:00
parent 50adfa0326
commit 2db3dc41e8
5 changed files with 104 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/INFD-WP-0006-fresh-review-authentication.md
View file

@ -42,7 +42,7 @@ id: INFD-WP-0006-T02
status: wait
priority: high
needs_human: true
blocking_reason: "Publish and prepare a pinned review image, obtain founder approval for the live rollout, then complete human password/OTP login and verify a new signed authentication time and p01 read allowance."
blocking_reason: "Narrow pinned review image and rollback are published/prepared; obtain founder approval for the live rollout, then complete human password/OTP login and verify a new signed authentication time and p01 read allowance."
```
Source tests are insufficient for native admission. Publish the exact tested
@ -54,3 +54,10 @@ signed timestamp is new and exact p01 read is allowed. If genuine fresh MFA
still reports the prior time, KeyCape must correct assurance issuance under
INFD-IN-0005; if its upstream freshness check fails, KeyCape/Authelia own that
dependency. Do not increase the 900-second action limit to mask either issue.
Candidate published at
`sha256:ccca0b377bb8ba6af52a37edc453b5b51c96e380840ec8243ffaab3ac2170885`.
Installed fresh-login parameter check, base-layer equality check and all 11
container lifecycle checks pass. Concrete rollout/rollback and acceptance
requirements are in `deploy/FRESH-AUTH.md`; image-only strategic patches are
prepared alongside it. Live deployment has not changed.