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

chore(consistency): sync task status from DB [auto]

Browse source 
Updated by fix-consistency on 2026-10-04:
  - update .custodian-brief.md for whitehat-security

Assistant: grok
Assistant-Session: 01a10450-dda4-7253-91a9-b8dccb2f0173
This commit is contained in:
custodian-sync 2026-10-04 12:10:54 +02:00
parent b7306ddc7e
commit 4dc4151e3d
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.custodian-brief.md
View file

@ -2,7 +2,7 @@
# Custodian Brief — whitehat-security
**Domain:** infotech
**Last synced:** 2026-10-04 09:37 UTC
**Last synced:** 2026-10-04 10:10 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
@ -19,7 +19,7 @@ Progress: 0/3 done | workplan_id: `fe26f070-70ca-55ba-92b3-3378929ba90f`
**Open tasks:**
- ! T01 — Live E3 against a runtime-safe surface `ed82ecb5`
*(wait: Guessed 2026-10-04 from rapp-postgres 11c1d489: database isolation_probe on platform-pg, view isolation_probe.rls_conformance, runtime role isolation_probe_app is NOBYPASSRLS and NOLOGIN, and SELECT is still granted only to isolation_probe_migrate. A human must approve that one grant and a short-lived login member, then a complete engagement must name the window, rate ceiling, abort contact, and finding destination. The guess is not approval. See engagements/2026-10-04-guessed-live-inputs.md.)*
*(wait: rapp-postgres 8d4106f, still present at 0374403, grants SELECT on isolation_probe.rls_conformance to isolation_probe_app and keeps that role NOLOGIN, NOBYPASSRLS, and NOSUPERUSER. The change is file-only. platform-pg stays not_applicable until an authorized promotion, a railiance-platform broker receipt for an ordinary runtime LOGIN member, and a complete engagement naming the database, window, rate ceiling, abort contact, and finding destination. No connection was opened.)*
- ! T02 — Live P1/P2 against a bounded substrate window `f226b8e1`
*(wait: No approved substrate window exists. The 2026-10-04 guess leaves the aggressor, probe allowance, headroom threshold, and abort numbers unknown rather than inventing them. rapp-postgres ADR-0004's 14-connection quota and four-consumer cell are admission estimates, not a probe allowance. An operator must still approve the window. See engagements/2026-10-04-guessed-live-inputs.md.)*
- ! T03 — Remaining E2 under new engagement IDs `414a7f68`