Captures the why behind key choices made during planning. Useful when revisiting a decision later — if a choice no longer fits, the original reasoning makes it easier to see what changed and whether to revisit.
This file is generated — do not edit it by hand. Each decision is its own file in DECISIONS/;
this is the index over them. Regenerate it with npm run decisions:index.
To add a decision, ask for an id first. POST /api/decisions/allocate returns the next
D-NNN, and that counter is the only thing that ever hands one out. Write
DECISIONS/D-NNN-<slug>.md with # D-NNN: Title as its first line, and cite D-NNN in code
straight away.
Never pick a number yourself — not even in a session you are sure is the only one running.
A number chosen by reading this file is the max + 1 that produced the D-056 and D-065
collisions (D-070, D-087).
Newest first.
- D-098 — Robot PRs are gated by a
review-gatestatus the Evaluator sets with a statuses-only token the Robot never holds - D-097 — A body edit to a refined ticket must say whether it stays refined, in the UI as a prompt and in the API as a required field
- D-096 — Refine is an asynchronous question queue, auto-started on every new ticket and paced by how fast Steve answers
- D-095 — Habit schedules are effective-dated rows, and due/streak are pure shared functions computed in a server Today view
- D-094 — The turn ceiling is a checkpoint, not a failure: report, save the work, and let Steve choose Continue or Restart
- D-093 — The shared offline outbox is a plain module with an
onChangecallback, not a reactive.svelte.tsstore - D-092 — Habits are a second shared domain store in
apps/server/src/lib/, beside the daily log — not widget tables, and not daily-log columns - D-091 — Robot work enters the Queue only refined — one predicate, enforced at every door the server owns, with the loop as backstop
- D-090 — The daily log is one shared store in
apps/server/src/lib/— the first shared domain table, and still not a firewall - D-089 — On an Epic,
refinedmeans the decomposition holds — and a membership change clears it automatically - D-088 — Decision ids are allocated at authoring time by a counter in the DB; the decision itself stays in git (PD-556; supersedes D-078)
- D-087 — A Robot asks the server for a decision id; it still cannot touch the board DB (PD-558; clarifies D-055, D-039)
- D-086 — The queue-model rules are enforced at the API boundary, and Reopen is a route (PD-542; amends D-083, implements D-080)
- D-085 — The maintenance window budgets job STARTS; a running job is never cancelled (PD-546)
- D-084 — Approving a Refine proposal writes content, never placement (PD-510; strengthens D-057, implements D-080)
- D-083 — Terminal is final — a completed or closed Ticket is read-only, and leaving it is one deliberate act (PD-539; amends D-036, D-040)
- D-082 — The maintenance hold is the scheduled thing, and maintenance jobs subscribe to it (PD-498; amends D-078)
- D-081 — The maintenance hold gets its own slot, and the numbering cycle reports dangling citations rather than repairing them (PD-498; implements D-078)
- D-080 — The Epic is the unit of priority and dispatch; the
prioritizedlane is removed (PD-383; amends D-054, D-057, D-058) - D-079 — A worker reports the commit it was BUILT from, not the one it reads (PD-528)
- D-078 — Decisions are authored with a provisional id and numbered in a daily cycle behind a maintenance hold (PD-498)
- D-077 — A human session writes to the memory inbox too, and
MEMORY.mdbecomes a wrap-up-only write (PD-513) - D-076 — The Evaluator is not Core's Oracle — it runs post-PR, on its own ledger, and reaches the Robot through the DB (PD-487)
- D-075 — The worker fetches documentation, not the agent — and the URL is the channel that needed closing (PD-310)
- D-074 — A job run's outcome belongs in the schema, not in its message
- D-073 — Page membership is user state in the DB, not a registry field; the widget registry declares no placement at all (PD-334)
- D-072 — A GitHub rate limit holds dispatch; only a broken credential pauses it (PD-248)
- D-071 — The Robot's orientation is injected, not fetched — and its memory is one file per run (PD-306)
- D-070 — One decision per file, with a generated index and a duplicate-id test as the real guard (PD-490)
- D-069 — Arrange mode drag-to-reorder uses native HTML5 DnD (commit-on-drop) rather than
svelte-dnd-action(PD-331) - D-068 — The Robot's tools are an explicit allowlist, and it may not spawn sub-agents (PD-486)
- D-067 — The path-guard gates unsupervised agents, not Steve — author-scoped, with a Robot-branch backstop (PD-474; amends D-047)
- D-066 — A ticket may raise its own turn ceiling, bounded — and decomposing stays preferred
- D-065 — The BST list is gear, duplicates are legal, and the matcher is tuned for precision
- D-064 — The loop-wide budget ceiling counts turns per rolling 24h, and pauses deliberately
- D-063 — A session limit holds the loop and expires itself; it never parks a ticket
- D-062 — A widget card links to a dedicated page; it does not flip
- D-061 — The agent control plane is named Osiris
- D-060 — The shared Spotify client uses a custom confidential-client refresh-token auth strategy and no-ops (never throws) when unconfigured (PD-377, slice 1/3)
- D-059 — Epic area drag-to-resize uses a CSS custom property driven by a pointer-capture handle; height persisted to
localStorage(#249) - D-058 — One
queuelane (assignee decides dispatch);ready(computed formatting) is the single dispatch gate with an explicit bypass; Epics are barred from the queue and get aPopulaterefine mode (PD-390, PD-377, PD-382) - D-057 — Refine approval never dispatches — split "Approve" from "Approve & queue";
isSortieReadyis a soft hint (PD-377) - D-056 — Pomodoro interval settings as a shared draggable bar-graph component (
IntervalBars) rather than duplicated<input type="number">rows (#235) - D-055 — Retire the third-party Sortie runtime — absorb dispatch into
agent-workeras the Sentinel loop; board DB becomes the agent-state machine (PD-323/PD-231/#220) - D-054 — Epics are a first-class umbrella primitive (
is_epic+epic_id), distinct fromsplit; status is derived and rendered in a non-draggable board band (PD-318) - D-053 — Widget "Arrange" mode edits the existing auto-flow grid (reorder + resize) with per-page
localStorageoverrides — not free 2D placement, not DB persistence (PD-331) - D-052 — Auto-merge bridge keys off
mergeStateStatus == CLEAN, not specific check names (PD-211) - D-051 — A
blocksticket relation is a hardrobot_queue-entry gate (a second queue-entry precondition besideisSortieReady); relations carry anorigin(agent|human); PD-156 sliced backend→frontend (PD-156) - D-050 — Embedded live widgets use a registry-provided component + span; generic card is shared chrome (PD-207)
- D-049 — Acute Strategies Generator uses client-side filtering and randomisation (PD-202)
- D-048 — Acute Strategies Generator stores tags as a JSON array in a SQLite TEXT column (PD-202)
- D-047 — Sortie sensitive-path guardrails are two-tier — an authoritative, runtime-independent CI path-guard (Tier 1) plus a runtime-coupled in-loop Claude Code layer (Tier 2), both fed by one shared denylist (PD-308, PD-312; supersedes C-2, PD-13, C-15)
- D-046 — Sortie's
after_runsafety-net publishes a hand-off ONLY when the agent earned it (a green-verify marker), never a mid-work tree (PD-299) - D-045 — The Ticket Audit is an autonomous, recurring agent-worker job that produces sticky, human-approved recommendations over the backlog — read-only run, human-gated apply, verify-and-confidence-gated for trust (PD-281)
- D-044 — Grill/Refine is a dashboard-owned, interactive, async triage agent launched from a "Refine" button — reinstating an interactive Refine step (reverses [[D-038]]'s drop) but async-over-notifications, not [[D-033]]'s synchronous SSE modal (PD-172, PD-245, PD-250, PD-255)
- D-043 — Board reflects GitHub changes via an on-demand sync trigger (page-load + "Sync now"), not just the once-a-minute cron (PD-252)
- D-042 — Sortie review re-work moves from the native
reactions.review_commentsto an in-repo Actions bridge (PD-256) - D-041 — Cmd+K shortcut uses metaKey-only (no Ctrl+K fallback) and toggles search focus (PD-126)
- D-040 — Agent + widget notifications go through a dashboard-native Notification Center with a pluggable delivery transport; web push is primary, Discord is demoted to an optional adapter (PD-6, PD-142, PD-242, PD-243)
- D-039 — Board↔issue authority — ticket is the durable spec, issue is an execution lease; ticket stays amendable post-queue; agent-created tickets are backlog-only, queuing gated by a server-computed depth cap (PD-207, PD-232)
- D-038 — Issue pipeline is hybrid — mechanical
isSortieReadygate + async in-run grill viaask_human; the heavyweight Refine sidecar (D-033) is dropped (PD-232) - D-037 — Deploy status uses server-start time as deploy proxy; GitHub API fetched once at startup (PD-111)
- D-036 —
closedis a separate terminal status fromcompleted(PD-81) - D-035 — Mac Mini migration mechanics — Colima, manual cutover,
.localaddressing, auto-login boot, NFS library (resolves [[D-031]]'s open items) - D-034 — Lane show/hide uses localStorage; board grid uses grid-auto-flow:column (PD-49)
- D-033 — "Refine" (PD-172) is a Claude-Agent-SDK sidecar with clone-grounded grilling and propose→approve write-back
- D-032 — The TODO→Sortie "Phase 3" splits — Claude formatting moves to Refine (PD-172); the Queued poller (PD-164) is mechanical and Claude-free
- D-031 — Mac Mini M4 becomes the primary always-on host; NAS demotes to storage/backup appliance
- D-030 — Off-LAN access via Tailscale, with tailnet membership as the authentication (PD-34)
- D-029 — Consistent SQLite snapshots run in-process via node-cron, not a host script (PD-33)
- D-028 — Priority is a nullable P0–P5 scale, stored under NOT NULL via a
'none'sentinel; status locks only when agent-owned - D-027 — Base PRs on
main, not on another open PR's branch — stacking silently opts out of CI + branch protection - D-026 — Kanban is drag-and-drop with fractional
sort_order;queuedlane added; status list is the single source of position - D-025 — Prod self-seeds an empty board on boot (opt-in via
SEED_ON_BOOT); dev is visually marked - D-024 —
@dashboard/sharedis consumed from source (no build, nodist); the server is esbuild-bundled - D-023 —
packages/sharedemits Node-resolvable ESM (NodeNext + explicit.jsextensions +exportsmap) - D-022 — Widget-only logic lives with its widget, not in
packages/shared;apps/webhas its own test runner - D-021 — Non-destructive migration framework — schema only ever grows
- D-020 — Cross-project ticket backlog (
agent_tickets+agent_projects), distinct from D-014 agent-run tables - D-019 —
packages/sharedemits ESM;devdoes not auto-build it (rebuild-after-edit is manual) - D-018 — Pomodoro timer logic lives in
packages/shared; tile renders full widget on home page - D-017 — Sortie follow-up detection is state-based (existing PR), not
.run.is_continuation - D-016 — Sortie hand-off is done by the agent in-turn, not by
after_run - D-015 — Widget tile as a flippable card component (
lib/Widget.svelte) - D-014 — Mission Control UI lives in Personal Dashboard; data owned by Symphony
- D-013 — Symphony as standalone project; Claude Code as the agent runner
- D-012 — Multi-agent coding workflow (DIY Symphony) — full architecture deferred
- D-011 — n8n deferred as workflow orchestrator
- D-010 — PostgreSQL deferred; SQLite flagged for upgrade on agent dashboard
- D-009 — All widgets share one SQLite database, namespaced by table prefix
- D-008 — Build dashboard shell now, not later
- D-007 — Show raw vs matched metadata side-by-side in the review UI
- D-006 — Fuzzy metadata matcher with duration as a gate, not a score component
- D-005 — Track status as a small enum, not separate booleans
- D-004 — Defer Chromaprint/AcoustID fingerprinting to TODO
- D-003 — Scan the NAS mirror of the DJ library, not the PC directly
- D-002 — Local DB queue instead of pushing everything to Lidarr automatically
- D-001 — Node + TypeScript, not Go