aboutsummaryrefslogtreecommitdiff
path: root/docs/specs/wrapup-routing-spec.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-20 08:49:52 -0500
committerCraig Jennings <c@cjennings.net>2026-07-20 08:49:52 -0500
commit70fbe011394523595974be311667db63425072ed (patch)
tree5deb5193cdf14b709531b32616622aee60d219ab /docs/specs/wrapup-routing-spec.org
parentb02eadec9392a9978cd526e2798460a53b5b79c4 (diff)
downloadrulesets-70fbe011394523595974be311667db63425072ed.tar.gz
rulesets-70fbe011394523595974be311667db63425072ed.zip
docs: fix four dangling file: links in specs and design notes
Three pointed at artifacts that were folded in or processed away (a spec-review file merged into wrapup-routing-spec, a removed pearl inbox note, a home-side subprojects log with no rulesets file) — delinked to plain text so the reference survives without a dead link. The fourth repoints the autonomous-batch spec at inbox.org, since inbox-zero.org was renamed in the consolidation. Surfaced by the sentry link-integrity pass.
Diffstat (limited to 'docs/specs/wrapup-routing-spec.org')
-rw-r--r--docs/specs/wrapup-routing-spec.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/specs/wrapup-routing-spec.org b/docs/specs/wrapup-routing-spec.org
index 1bdc0f3..07d9ec6 100644
--- a/docs/specs/wrapup-routing-spec.org
+++ b/docs/specs/wrapup-routing-spec.org
@@ -218,7 +218,7 @@ Everything else accepted as written: H1 (inbox-route supersedes direct-move; D2/
** 2026-06-21 Sun @ 01:58:41 -0400 — Claude Code (rulesets) — reviewer
- What: spec-review pass. Rubric *Not ready*, two blocking findings. H1: the inbox-route alternative (inbox-send each routable keeper to the destination's inbox/, let its own process-inbox file it) supersedes the direct-move design — reshape D2, drop Phase 2 and D3's provenance burden. H2: pin the candidate-set marking to Option A (tag =:ROUTE_CANDIDATE:= at process-inbox file time). Four medium findings (M1 confidence tiers, M2 empty-set silence, M3 paired process-inbox edit phase, M4 cross-project.md note). Full review + drop-in implementation tasks in the review file.
- Why: Craig challenged D2 directly (why edit a foreign todo.org rather than use the sanctioned inbox-send path). The review confirmed it: inbox-send already emits the exact provenance D3 reinvents, process-inbox already files per-item with the destination's own gate, cross-project.md sanctions the inbox path, and a verified precondition reverses the spec's assumption — chime and yt-sync have inbox/ but no todo.org, so direct-move silently drops keepers headed there while inbox-route degrades gracefully.
-- Artifacts: [[file:wrapup-routing-spec-review.org][review file]]. Next: spec-response to disposition H1/H2 (recommend accept both), which moves the rubric to Ready.
+- Artifacts: the review file (since folded into this spec). Next: spec-response to disposition H1/H2 (recommend accept both), which moves the rubric to Ready.
** 2026-06-21 Sun @ 02:06:37 -0400 — Craig Jennings + Claude Code (rulesets) — responder
- What: folded the spec-review in. Accepted H1 (inbox-route) and H2 (tag at file time); superseded D2 and D3; added D7 (deliver via =inbox-send=), D8 (=:ROUTE_CANDIDATE:= marker at file time), D9 (local source removal + reject-flow recovery). Rewrote Summary, Goals, Design mechanics, Implementation phases (dropped the atomic-move helper — Phase 2 is now the =process-inbox= marker edit), and Acceptance criteria for the inbox-route. One modify (D9) refines H1's vague source-handling. Cookie [9/9]; Status → Ready.