aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--inbox/lint-followups.org7
-rw-r--r--todo.org16
2 files changed, 7 insertions, 16 deletions
diff --git a/inbox/lint-followups.org b/inbox/lint-followups.org
deleted file mode 100644
index 13b65fa..0000000
--- a/inbox/lint-followups.org
+++ /dev/null
@@ -1,7 +0,0 @@
-
-* 2026-05-29 lint-org follow-ups — todo.org
-** TODO line 2429 — obsolete-properties-drawer — Incorrect contents for PROPERTIES drawer
-** TODO line 2371 — misplaced-heading — Possibly misplaced heading line
-** TODO line 1718 — misplaced-heading — Possibly misplaced heading line
-** TODO line 1213 — invalid-custom-id-link — Unknown custom ID "16 Generic agent runtime support"
-** TODO line 1176 — obsolete-properties-drawer — Incorrect contents for PROPERTIES drawer
diff --git a/todo.org b/todo.org
index 1a48463..621c9fe 100644
--- a/todo.org
+++ b/todo.org
@@ -1163,6 +1163,9 @@ Pearl recommends a one-page spec (problem + design + open questions + acceptance
Three more pearl handoffs landed and were filed during this audit. Filed: [[file:docs/design/2026-05-28-pattern-catalog-prompt-labels-and-defaults.org][prompt-labels-and-defaults]] (patterns 4-5: label-matches-behavior, default-most-common with friction-proportional-to-consequence) and [[file:docs/design/2026-05-28-pattern-catalog-prompt-collapse.org][prompt-collapse]] (pattern 6: collapse N orthogonal prompts into one enriched prompt). The catalog's evidence base is now four pearl notes in =docs/design/= covering six patterns plus the synthesizing principle Pearl articulated — "choices on screen, accurately labeled, ordered by what the user most often wants, friction sized to the cost of being wrong."
** TODO [#C] Generic agent runtime support — Codex spec v0 :spec:design:
+:PROPERTIES:
+:LAST_REVIEWED: 2026-05-28
+:END:
Codex drafted a v0 design doc for making rulesets runtime-neutral rather than Claude-Code-specific. Motivating cases: offline operation with a local LLM, and two LLMs running in the same project at the same time without trampling each other's session-context.
Spec at [[file:docs/design/2026-05-28-generic-agent-runtime-spec.org]] (moved here from inbox on intake).
@@ -1173,10 +1176,6 @@ Broader refactor proposes runtimes/ adapter manifests, generic install commands,
Before any implementation: needs a real review pass on the spec, and a decision on whether to do Phase 1 alone (low risk, fixes the race) vs commit to the larger arc.
-:PROPERTIES:
-:LAST_REVIEWED: 2026-05-28
-:END:
-
** TODO [#B] Startup Phase A rsync propagates dirty rulesets WIP into downstream projects :feature:
:PROPERTIES:
:CREATED: [2026-05-29 Fri]
@@ -1210,7 +1209,7 @@ Touches: =.ai/protocols.org= (rename rule + recovery anchor), =.ai/workflows/sta
Verification: simulate two agents sharing a project (separate AI_AGENT_ID values) and confirm session-context writes land in distinct files without interleaving.
-Parent: see [[#16 Generic agent runtime support][Generic agent runtime support — Codex spec v0]] above for the larger arc this is sliced from.
+Parent: see [[Generic agent runtime support — Codex spec v0]] above for the larger arc this is sliced from.
** TODO [#B] Add Signal MCP server (rymurr/signal-mcp) :feature:
SCHEDULED: <2026-05-29 Fri>
@@ -2414,6 +2413,9 @@ Scope: one Makefile target that prints a compact summary of:
Output should be roughly 10 lines, scannable in one glance. Composes the existing checks; no new logic except the summary formatting.
** DONE [#C] Iteration-history backfill for spec-review and spec-response :docs:followup:
CLOSED: [2026-05-28 Thu]
+:PROPERTIES:
+:LAST_REVIEWED: 2026-05-28
+:END:
Source: org-drill inbox 2026-05-28.
Once the in-flight WIP lands (the requirement that specs carry a bottom =Review and iteration history= section, with iteration / date / contributor / role / what / why / artifacts), backfill the two workflow files themselves using rulesets' session history as evidence.
@@ -2425,7 +2427,3 @@ Files to update:
Investigation: search =.ai/sessions/=, =.ai/notes.org=, inbox archive, and git log for mentions of these workflow docs. Identify review/response/design iterations, dates, and contributors (including agents where known: Claude Code, Codex, local models). Distinguish high-confidence history (commits, dated session entries) from inferred (chat-only context). Recommend whether enough evidence exists to populate the section, and draft the entries if so.
Dependency: spec-review.org and spec-response.org have uncommitted edits in flight. Wait for those to land before writing to the files. The read-only research portion (search sessions, identify iterations, draft entries to a scratch file) can run in parallel without conflict.
-
-:PROPERTIES:
-:LAST_REVIEWED: 2026-05-28
-:END: