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

Deploy fresh review login image and record live readiness evidence

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:40:11 +02:00
parent 6d322eb210
commit 333a6dcf95
5 changed files with 83 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
workplans/ADHOC-2026-10-03.md
View file

@ -40,7 +40,7 @@ id: INFD-WP-ADHOC-2026-10-03-T02
status: wait
needs_human: true
decision_id: 62aa95e4-3ccc-4867-8806-5e3db005b483
blocking_reason: "p01 is loaded, but repeated browser read attempts retain KeyCape MFA time 17:08:08 UTC and fail the 900-second policy limit. Obtain genuinely fresh password/OTP authentication; if fresh OTP still emits the old time, KeyCape owns the correction (INFD-IN-0005). Then founder reviews, acknowledges and chooses a disposition."
blocking_reason: "p01 is loaded and fresh-login fix deployed; founder must sign in at decisions.coulomb.social/auth/start with password/OTP, open p01, acknowledge the required highlight and choose a disposition. If actual fresh MFA still emits old assurance, KeyCape owns correction under INFD-IN-0005."
priority: high
state_hub_task_id: "ffbc2e30-7a6a-5fb4-86c9-3db1e4a0bacf"
```
@ -130,3 +130,9 @@ it with a completed browser journey. Retain all policy freshness limits.
Evidence: `docs/evidence/2026-10-03-provisioning-window-review-refusal.json`.
`INFD-WP-0006` implements an explicit fresh-authentication request from review
sign-in; its narrow image rollout and native browser proof remain blocked.
Fresh-login image rollout completed under founder instruction "please deploy"
at 18:39 UTC (INFD-WP-0006). Revision 17 is Ready; public login now requests
fresh authentication from KeyCape. p01 and policy pins remain intact. Native
read and the founder's disposition are still pending. See
`docs/evidence/2026-10-03-fresh-auth-live-rollout.json`.

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

@ -44,7 +44,7 @@ id: INFD-WP-0006-T02
status: wait
priority: high
needs_human: true
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."
blocking_reason: "Fresh-login image deployed on founder approval; founder must complete review password/OTP login so we can verify a new signed authentication time and p01 read allowance."
state_hub_task_id: "dfcc2723-42bd-5b8f-b1b8-e205dc506764"
```
@ -64,3 +64,14 @@ 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.
2026-10-03 18:39 UTC: founder instructed "please deploy".
ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED.
Image-only patch deployed successfully as Deployment revision 17, one Ready
replica, Recreate, unchanged 5m CPU/64Mi memory requests. Node preflight showed
3445m of 4000m CPU requested; no additional request introduced. Public health
and readiness return 200; public sign-in redirects to the exact KeyCape issuer
with `prompt=login` and `max_age=0`. Read-only store verification confirms
schema 2, retained p01 and v7 policy digest. All process-local sessions reset.
Evidence: `docs/evidence/2026-10-03-fresh-auth-live-rollout.json`.
T02 remains wait solely for native human browser proof; no agent bound a memo.