docs/ — Context & Tracker Index

Workspace-wide context lives here. The root holds only CLAUDE.md + README.md.
Last cleaned: 2026-06-01 (health-check sweep — superseded/dup/dated docs moved to archive/2026-06-01_docs-cleanup/).
One canonical doc per domain. Dated snapshots and superseded versions go to archive/, not here.

START HERE (the always-current layer)

File	Purpose
`../CLAUDE.md`	Auto-read entry point. Rules, topic-preload, current status. Read first.
CONTEXT.md	Live session log + open loops + current state. Read second.
WORKSPACE_AUDIT.md	Canonical map of every folder/repo/sheet. Use instead of re-running `ls`/re-searching.
CONNECTIONS.md	The connections hub — every live data source (calendars, Gmail, cards, cash, Airbnb…), what's read/write, what's pending, what links Sam still owes.
SCOPE_BACKLOG.md	No-blind-spots registry — every parked item / open loop.
SESSION_OPEN.md · CADENCE.md	How to open a session · the weekly rhythm + email/Mildred plan.

CANONICAL REFERENCE — one per domain

Domain	Doc
Money / obligations	OBLIGATIONS.md · MORTGAGE_ROUTING.md (live sheet = system of record)
MIS / trading	MIS_FSE_ARCHITECTURE.md (+ the `MIS_V2_*` build docs)
Triggers / automations	TRIGGER_REGISTRY.md
Design / surfaces	DESIGN_SYSTEM.md · STITCH_BRIEF.md
Channels / comms	CHANNELS.md
Mildred (VA)	MILDRED_SCOPE.md
Tools available	CLAUDE_TOOLS_AVAILABLE.md
Repos (snapshot)	GITHUB_REPO_AUDIT_2026-05-19.md
HOW-TO runbooks	HOW_TO/ (see HOW_TO/README.md)

BUSINESS / PROJECT BRIEFS

MALCA_YENTA_CONTEXT.md (LevSMS) · CONSULTING_PACKAGE.md · MOM_INVOICE_BUILD_SPEC.md · malca-yenta/ · revenue/ · obligations-v3/ · superpowers/specs/ · levsms/

INTENTION & DESIGN-SEED LAYER — find & revive (NOT done, NOT dead)

These are things Sam wanted to build + design seeds + capability ideas, kept here so Claude Code can FIND them and revive them — not graveyard material. Several are already partly realized; the link shows what they seeded. When you build in these areas, READ THE SEED FIRST (it usually holds the architecture).

Folder What it is Already seeded → Status

SIGNAL_OS/ The external-brain capture→extract→route→review loop (Apr 27). The conceptual parent of the whole capture stack. action-queue normalization · WhatsApp capture v0 · braindump-router · command inbox LIVE in spirit — the loop is being realized piecemeal; the doctrine + prompts + schema are still the reference. Revive the EXTRACT-automation step when ready.

workflow/ WORKFLOW_ARCHITECTURE.md — how multi-step work should flow OPERATORS.md · steering/ reference; reconcile with OPERATORS model

daily-cadence-system/ Morning-brief template + proactive-brief spec morning-spine · cloud Routines partly realized; spec still useful for the proactive brief

superpowers/specs/ 4 build design specs (cadence-pulse, queue-triage, MIS dashboard, Mildred ops) several shipped KEEP. (folder name collides with the superpowers skill plugin — rename to design-specs/ someday)

captures/ One-off captured facts (e.g. 589 Hook St school tax) — low-friction capture bin; fold into the capture pipeline

scripts-pending/ dailyDraftScanner.js — auto-scan Gmail drafts the session-open draft-scan ritual pending; decide promote-to-scripts/ or retire

world/ empty container — intended-but-empty; name a purpose or fold

Folder	What it is	Already seeded →	Status
`SIGNAL_OS/`	The external-brain capture→extract→route→review loop (Apr 27). The conceptual parent of the whole capture stack.	action-queue normalization · WhatsApp capture v0 · braindump-router · command inbox	LIVE in spirit — the loop is being realized piecemeal; the doctrine + prompts + schema are still the reference. Revive the EXTRACT-automation step when ready.
`workflow/`	`WORKFLOW_ARCHITECTURE.md` — how multi-step work should flow	OPERATORS.md · steering/	reference; reconcile with OPERATORS model
`daily-cadence-system/`	Morning-brief template + proactive-brief spec	morning-spine · cloud Routines	partly realized; spec still useful for the proactive brief
`superpowers/specs/`	4 build design specs (cadence-pulse, queue-triage, MIS dashboard, Mildred ops)	several shipped	KEEP. (folder name collides with the `superpowers` skill plugin — rename to `design-specs/` someday)
`captures/`	One-off captured facts (e.g. 589 Hook St school tax)	—	low-friction capture bin; fold into the capture pipeline
`scripts-pending/`	`dailyDraftScanner.js` — auto-scan Gmail drafts	the session-open draft-scan ritual	pending; decide promote-to-`scripts/` or retire
`world/`	empty container	—	intended-but-empty; name a purpose or fold

RULES FOR NEW .md FILES

Workspace-wide context/tracker → docs/ (here). Project-specific → inside that project folder. Session output (briefing/recap/SOP) → outputs/.
One canonical doc per domain. A new "current state" doc must REPLACE the old one (move old → archive/), not sit beside it.
Dated snapshots (NAME_YYYY-MM-DD.md) are frozen — fine to keep, but archive once superseded.
Stale / superseded / duplicate → mv → archive/ (never hard-delete). Don't leave dead files in docs/.

See CLAUDE.md "WHERE THINGS LIVE" for the full map.