docs(design): capture wrap-up inbox/transcript routing proposal

A wrap-up router that surfaces outstanding inbox items, recommends a destination project for each, and batch-moves task items into that project's todo.org, with a parallel transcript-filing step. I captured it as a design source and filed a spec-bound feature task rather than building it now: the work clears the spec bar, with design uncertainty (merge or stay separate from the inbox sanity check, recommendation-engine confidence, an unresolved transcript source-location dependency) and overlap with this session's defer-and-stage router to reconcile.

From the archsetup handoff 2026-06-13.

1 files changed, 17 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index a456c26..6d94160 100644
--- a/todo.org
+++ b/todo.org
@@ -34,6 +34,23 @@ Tags are assigned and refreshed by =task-audit=; =task-review= keeps them honest
 
 * Rulesets Open Work
 
+** TODO [#B] Wrap-up inbox/transcript routing to destination projects :feature:spec:
+:PROPERTIES:
+:CREATED: [2026-06-13 Sat]
+:LAST_REVIEWED: 2026-06-13
+:END:
+Add a routing step to =wrap-it-up.org=: when outstanding inbox items remain, surface them, recommend a destination project for each, and offer a batch-level "go with recommendations / skip" (not per-item, not a wrap gate). Task/event items move into the destination's =todo.org= "Open Work" section per =todo-format.md=; a parallel step files meeting transcripts into =assets/= per =working-files.md=.
+
+Spec-bound, not implement-now — clears the spec-create Phase 0 bar (>6h, real design uncertainty, cross-cutting, hard to reverse). Run =spec-create= first. Design questions the spec must settle:
+- Reconcile with this session's defer-and-stage router in =process-inbox.org= (the Skeptical Review's VERIFY path) — two "move inbox items to todo.org" mechanisms shouldn't compete.
+- Merge into the existing wrap-up "Inbox sanity check" step or stay a separate optional router (archsetup leans separate: one gates, one is optional).
+- Transcript half has an unresolved dependency (where recordings accumulate) and an open question (extract action items into todo.org, or file the artifact only and let the task-router handle items). Consider splitting transcript work to vNext.
+- Recommendation engine: infer destination from item content against discovered projects; low-confidence recs must flag themselves so the single keystroke stays trustworthy.
+- Widen project discovery from "=.ai/protocols.org= present" to "has =todo.org= with an Open Work heading" (reuse =todo-cleanup.el='s =--archive-done= matcher); a plain code repo with a =todo.org= is a valid destination.
+- Cross-project write discipline (=cross-project.md=): the batch "go" authorizes the write into another project's scope, but the move stays visible and leaves a provenance note. Likely needs an atomic cross-project move helper (extend =todo-cleanup.el= or a new =.ai/scripts= tool).
+
+Source: archsetup handoff 2026-06-13 (=inbox/2026-06-13-0021-from-archsetup-wrapup-inbox-routing-request.org=, moved to =docs/design/= on filing). No archsetup-side work; entirely a rulesets workflow change.
+
 ** TODO [#B] Helper-instance support — concurrent same-project Claude :feature:spec:
 :PROPERTIES:
 :CREATED: [2026-06-11 Thu]