2.3 KiB
2.3 KiB
current-state
ACTIVE: Build Spec Phase 2 DESIGNED — session-brain auto-write + insight extraction spec ready for Claude Code. NEXT: Claude Code builds Phase 2 (modify navaigate-session-brain SKILL.md). Pi stands by for verification.
Decisions (last 5)
- 2026-06-22: Clerk prod migration COMPLETE — frontend (pk_live on Vercel) + backend (CLERK_JWKS_URL → clerk.sttilsolutions.com on Railway) both deployed. DNS verified, JWKS serving.
- 2026-06-21: Subagent cost guardrails installed — all 8 builtin subagents default to deepseek/deepseek-v4-flash with 2-5 min hard timeouts.
- 2026-06-21: Audit logger trust fix committed + pushed (Supabase client detection, error wrapping). Cascade test assertion corrected.
- 2026-06-21: SIGNAL_API_KEY rotated by Claude Code. Leaked key removed from Vercel + source. Exposure closed.
- 2026-06-21: Build Spec Phase 1 done (Claude Code). research_insight category live. CGM-to-pharmacy insight planted.
Open Threads (max 5)
- LabABLE Meeting Fri 2026-06-26 1:30 PM — run /pilot-prep.
- Build Spec Phase 2: spec written at signal/docs/superpowers/specs/2026-06-22-build-spec-phase2.md. Ready for Claude Code to build.
- 3 validation product blockers: MA misclassification, duplicate patient_id, doc-status override (Claude Code is on these).
- Primary domain sttilsolutions.com still "Pending" in Clerk (separate from Frontend API — non-blocking for auth).
Stack
- Signal: PHI contained in
patient_idfield (name, MRN, account #s) — requires tokenization. - Model for Pi:
deepseek/deepseek-v4-flash(cheap, high-thinking). Subagents also default to this model. - Signal-api: Railway (signal-api-production-91c2)
- Signal-ui: Vercel (signal-ui-xi.vercel.app)
- Supabase: itmospnregdyiatbbdwl (JWT key)
- TriLane: localhost:8000 (signal/sessions/scale-software workspaces)
- Clerk: production key deployed to Vercel + Railway. Frontend auth via
clerk.sttilsolutions.com(verified). Google OAuth configured.
Tip
TriLane Memory now has the research_insight category live + 1 planted insight (CGM-to-pharmacy, salience 1.0) in the Signal workspace. Session summaries no longer leak into the Signal workspace; they live in the Sessions workspace.