Working Memory

The live coordination layer for difficult work in this checkout. It exists because chat context is volatile.

Use wiki/content/onboarding/ for stable orientation. Use this folder for the current operation: active invariants, unresolved decisions, open work breakdowns.

How To Use

At the start of a new session:

  1. Read wiki/content/onboarding/README.md.
  2. Read the active control doc, currently jobs-architecture-control.md.
  3. Read wiki/content/architecture/PRIVATE-EDGE-SHARED-HQ-MODEL.md for the decided D1/Cockroach storage split.
  4. Read d1-cockroach-todo.md for the parallel work breakdown.
  5. Read open-decisions.md for unresolved questions.
  6. Read missing-journeys.md for the user-journey test backlog.
  7. Read graph-quality-overnight-refactor.md before unattended graph cleanup.
  8. Read qa-object-pov-dashboard-design.md before rewiring QA API/MCP/UI.

Cutover inventory (v1/v2/v3 hosts) is archived at wiki/content/archive/2026-05/versioned-deploy-archives.md.

Before substantial edits:

  • Update the active control doc if the intended change affects architecture.
  • Record any blocker in open-decisions.md.
  • Keep changes atomic: one invariant-preserving slice at a time.

Rules

  • This folder is not polished product documentation.
  • Prefer short, factual notes over long analysis.
  • Use terms and names as simple as possible, but not simpler. Avoid authority/status labels or version-stage labels unless a live source/target boundary needs them.
  • Do not let implementation outrun the control doc.
  • If code and this folder conflict, inspect code and update this folder.
  • When a working-memory note's work has fully landed, delete the note. This folder is for work in progress, not history. Move durable architecture findings into wiki/content/architecture/ or wiki/content/runbooks/ before deleting.
Source: wiki/content/working-memory/README.md