nuggets checkpoint: AIOS/privacy session, open items for the next window

ACTIVE/NEXT rewritten. Four decision lines added covering the scp verification
failure, the silent-success pattern, the cto-architect PHI verdict, and the
Hazel scope confirmation.

Records an OPEN DISAGREEMENT: Kisa said she does not fully agree with the
Gmail-recovery / ops-steward proposal and stopped before saying which part.
Marked so the next session does not treat it as agreed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011bZhDfpTgToFvDX1CDE8oh

context/current-state.md

@@ -2,14 +2,22 @@ v:1
 
 # current-state
 
-ACTIVE: 2026-07-07 [CC]. SIGNAL READINESS-MODEL BUILD COMPLETE P1-P6 (final commit 6181de7): backend + patient-nested worklist shipped, six independent audits, deployed to Railway + Vercel, live-verified where measurable (171 tests, Pi E2E 33/33, new bundle confirmed serving). All mockup decisions approved incl. the generalized data-gap family. REMAINING: Kisa signed-in click-through (5 probes in ledger).
+ACTIVE: 2026-07-27 [CC]. AIOS/privacy-architecture session, NOT Signal product work. Delivered: STTIL's first data-classification scheme (OPEN/INTERNAL/RESTRICTED, `sttil-vault/Projects/STTIL-data-classification-v1.md`); a dry-run file classifier at `~/.claude/automation/classify/classify.py` (reports only, contains no file-moving code); `~/Documents/Playground/` built; review-hold moved OUT of `~/Documents` to `~/STTIL-Review-Hold/` (iCloud sync risk). Hazel 6.1.2 installed by Kisa, license located and REGISTERED (was on trial). Reference files corrected across two passes after `challenger` caught that the first pass introduced a new false fact. Signal touched only for doc flags, no code change. **PRIOR ACTIVE (still the real product state): 2026-07-07 [CC]. SIGNAL READINESS-MODEL BUILD COMPLETE P1-P6 (final commit 6181de7)**: backend + patient-nested worklist shipped, six independent audits, deployed to Railway + Vercel, live-verified where measurable (171 tests, Pi E2E 33/33, new bundle confirmed serving). All mockup decisions approved incl. the generalized data-gap family. REMAINING: Kisa signed-in click-through (5 probes in ledger).
 
-NEXT: (Kisa+CC) FIRST: debug the Clerk sign-in issue — Kisa reported she cannot get into the app (details incoming; observed: prod sign-in page renders email-only form, no Google button visible on the Clerk card). It gates the click-through. THEN: (Kisa) 5-probe click-through of the new worklist; (Kisa) confirm OQ1 + legacy-stopgap deviation; (Kisa) attorney bundle SEND to Clyde Mathes (attorney-bundle-2026-07-07, rulings applied; LOI 8.4 carve-out open to discuss) + Gaboro re-approach; (CC) pilot-guide screenshots + demo narrative plan-type step; (CC) CSV formula-injection sanitization backlog.
+NEXT (as of 2026-07-27): (Kisa, 2 min) sign-in test at signal-ui-xi.vercel.app — decides whether pilot readiness is honestly 13/13 or 12/13; do not quote 13/13 externally until then. (Kisa) rule on the KG conflict below. (Kisa) Appwrite retirement step 1 (`docker compose stop`, reversible, frees 1.3GB and 23 of 28 containers). (CC) design the Hazel ruleset once Kisa supplies the workflow design from her other window. (CC/ops-steward) license + subscription register, Hazel registration email needs moving off the lost lokissed@gmail.com account, transaction ID 8Z4LR26B4D8H.
+
+OPEN DISAGREEMENT (2026-07-27): Kisa said "I don't agree entirely" about the Gmail-recovery / ops-steward proposal and stopped the session before saying which part. **Do not treat that plan as agreed.** Ask her before acting on it.
+
+PRIOR NEXT: (Kisa+CC) FIRST: debug the Clerk sign-in issue — Kisa reported she cannot get into the app (details incoming; observed: prod sign-in page renders email-only form, no Google button visible on the Clerk card). It gates the click-through. THEN: (Kisa) 5-probe click-through of the new worklist; (Kisa) confirm OQ1 + legacy-stopgap deviation; (Kisa) attorney bundle SEND to Clyde Mathes (attorney-bundle-2026-07-07, rulings applied; LOI 8.4 carve-out open to discuss) + Gaboro re-approach; (CC) pilot-guide screenshots + demo narrative plan-type step; (CC) CSV formula-injection sanitization backlog.
 
 PRIOR ACTIVE: 2026-06-28. Signal paused at clean checkpoint — Insight Engine in active BUILD phase for July 4 deadline. See insight-engine/context/current-state.md and insight-engine/handoff-clock.md for full state. Key progress today: x-sight guided experience designed (Compass) and approved by Kisa, lane-lock handoff clock created, frontend finish readiness assessed (15 ranked items). Claude is building the Compass landing + B1 deploy blocker + finish items. Signal READINESS MODEL still queued at the clean checkpoint from 2026-06-27.
 
 [AIOS build status] The map is written. Highest-impact build is the readiness model, NOT AIOS enhancements. AIOS Phase 1 items (reasoning frameworks, Playground, /board skill) are <5 hours total and optional until Signal has customer momentum.
 
+- 2026-07-27 [CC]: Verify claims against the live system, never against a document. I "confirmed" that scp/SFTP were disabled on the VPS by reading the skill file against itself, seeded that false fact into the KG (which outranks every other source), and `challenger` disproved it in one command. Same failure shape as the stale files I was correcting.
+- 2026-07-27 [CC]: Silent success is this stack's characteristic failure. Eight of nine LaunchAgents gone, the KG empty, `.secrets.env` missing, `~/.claude/plans/` and `raycast/` silently gitignored, Appwrite 502 for weeks. Every one reported success by saying nothing. Assume absence, verify presence.
+- 2026-07-27 [CC]: cto-architect ruling — Hazel does NOT substitute for the Game Center token layer (different surfaces), but the token layer was never a PHI solution either (its own guardrails: shipment dates break safe harbor regardless). AWS is the real-PHI path, BAA already signed, RDS/S3 provisioned, Supabase coupling verified at only 11 references across 3 files. Recommended unit is a supplier-side de-identification tool (3-5 days), not local deployment of Signal (3-5 weeks). Pricing in that report is unquoted, do not act on dollar figures.
+- 2026-07-26 [CC]: Hazel gate returned STOPPED by integration-steward, then overtaken by events (Kisa had already installed it). Scope confirmed by Kisa: Downloads and working files only, transcripts and Signal data excluded.
 - 2026-06-27 [Pi]: Insight Engine adaptivity review cycle COMPLETE — 3 audit docs written (pi-build-review-2026-06-27.md: 7 findings, 3 HIGH/2 MEDIUM/2 LOW; claude-pushback-to-pi-2026-06-27.md: 3 challenges; pi-pushback-response-2026-06-27.md: all 3 conceded with code evidence). Claude implements 5 fixes next. Truncation root cause found: deepseek/deepseek-v4-flash was missing from models.json with no explicit maxTokens, compounded by thinking:high. Added with maxTokens=65536.
 
 ## Cross-Project Bridge