# current-state

ACTIVE: Readiness-model redesign locked + design brief written for Pi. Client supplies plan type (Signal never determines payer/eligibility/coverage); cite-the-basis; patient/CoverageLine/Shipment data model; required-vs-supplied verdict (no false green). cto-architect review folded in.
NEXT: Pi produces the build design from `docs/readiness-model-brief-2026-06-23.md`; then Claude builds (sequence: rename coverage->readiness, rules-to-config, patient/line/shipment grouping + verdict, device-keyed override+recompute, require-plan-type + client mapping + remove guesser, frontend nesting). Pi has RESOLVED the tension of a rotating anonymous patient ID vs. persistent worklist by proposing the RAP-ID/CSP-ID architecture.

Pi has also refined strategic plans for a "Signal AIOS" for clients and an "Automated Blog" for the STTIL Solutions website, incorporating Granola call insights for API-first strategy, SEO tools, and agent orchestration.

## Decisions (last 7)

- 2026-06-23: Readiness model redesign. Signal never determines/guesses payer plan type, eligibility, or coverage; client supplies plan type as a required mapped field; every determination cites the rule + client input. Worklist = one record per patient UUID with per-device CoverageLines; verdict from required-vs-supplied (Clear to Ship earned by positive evidence, never by absent data). MA "bug" = delete the name-guesser. "coverage" code renamed to "readiness". Brief: docs/readiness-model-brief-2026-06-23.md. KG: plan_type_policy, scope_exclusion, determination_explainability.
- 2026-06-23: RAP-ID/CSP-ID architectural solution proposed by Pi to reconcile rotating anonymous patient ID with persistent worklist tracking. Web App (SaaS Hosted by STTIL) is the recommended deployment model, with client-side management of Real Patient ID to CSP-ID mapping; HIPAA-compliant host like Validated Cloud is still required.
- 2026-06-23: Shield architecture designed by Pi (standalone compliance product, tiered deployment, security, scalability, AI Consent Addendum focus). Ready for Claude Code build or further refinement.
- 2026-06-23: DNSSEC verified live (DS propagated to public resolvers, ad flag set = chain validating). Website agent-files: staged compliance/factual fixes in local repo, NOT deployed: removed outreach wording, banned >25% stat, exposed pricing; fixed SWO term to Standard Written Order; refreshed learn-signal SKILL.md digest in agent-skills index. Prose rewrites + v0.2.0 field polish route to lead-content / deferred (agentskills.io schema URL unreachable).
- 2026-06-23: Pi drafted strategic plans for "Signal AIOS" (productizing Shield's compliance architecture for Signal clients) and an "Automated Blog" for STTIL Solutions website (AI/SEO optimized, leveraging research agents and TriLane). These plans have been refined based on Granola call insights, emphasizing API-first strategy, specific SEO tools (AnswerThePublic, Schema.org), and agent orchestration concepts.  Awaiting Claude Code's recommendations for implementation.
- 2026-06-22: Phase 4 (support bot foundation) spec written by Pi — gen-api-ref.py + manual cross-reference. Ready for Claude Code build.
- 2026-06-22: Build Spec Phase 2 built (Claude Code). navaigate-session-brain now auto-writes current-state.md (Step 3B) + extracts research insights to TriLane (Step 3C). Clerk prod migration COMPLETE (pk_live on Vercel + JWKS on Railway).

## Open Threads (max 5)

- READINESS MODEL REDESIGN (2026-06-23): design brief for Pi at `docs/readiness-model-brief-2026-06-23.md` (folds in cto-architect review). Pi produces the build design; then Claude builds. Supersedes the piecemeal 3-blockers framing. KG added: plan_type_policy, scope_exclusion, determination_explainability.
- SIGNAL AIOS & AUTOMATED BLOG STRATEGIC PLANS (2026-06-23): Pi has refined these plans based on Granola call insights. Claude Code to review and make recommendations for moving forward.
- LabABLE Meeting Fri 2026-06-26 1:30 PM — /pilot-prep (deferred).
- Website copy: brief lead-content for human-page rewrites (extract "eligibility"/"coverage" language, stat consistency), run copy-review, then commit + deploy the staged agent-file fixes. Retention 6-year doc fix (2 stale "7 year" lines). BAA privacy wording attorney-gated.
- Build Spec Phase 4 (support bot foundation) spec by Pi - ready for Claude Code build.

## Stack

- Signal: PHI contained in `patient_id` field (name, MRN, account #s) — requires tokenization via proposed RAP-ID/CSP-ID architecture (2026-06-23 call: rotating anonymous ID, not static UUID; PROBLEM RESOLVED BY PI).
- 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). Non-MCP agents (Pi) reach it over HTTP at `127.0.0.1:8000` — full contract (search via branch-scoped retrieval, memory read/write, live branch ids) in `trilane/TRILANE_HTTP_API.md`. Verified live 2026-06-23.
- Clerk: production key deployed to Vercel + Railway. Frontend auth via `clerk.sttilsolutions.com` (verified). Google OAuth configured.

## Tip

TriLane Memory has the `research_insight` category live in the Signal workspace. Session summaries live in the Sessions workspace (auto-flow), not Signal. Meeting/Granola notes also land in the Sessions workspace; Pi can query them over HTTP.

## Updated: 2026-06-23 (Claude Code + Kisa: locked the readiness-model redesign via brainstorming + cto-architect review; wrote the design brief for Pi at docs/readiness-model-brief-2026-06-23.md; added KG facts plan_type_policy/scope_exclusion/determination_explainability; shared today's AI-OS call notes for Pi; flagged the rotating-ID vs persistence tension. Next: Pi designs the Readiness Model build; Pi integrates Granola insights into AIOS/Automated Blog plans. Next: Claude builds
