Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›RAG / Semantic Search·16 in this wave

Approve: RAG / Semantic SearchTo do · blocker Decide: RAG stays internal-only or becomes the agent's retrieval layerTo do · blocker Decide: will RAG ever index per-account/customer content?To do · blocker Verify RAG_QUERY_STUB is removedDone Build rag.search MCP tool and wire it into the customer agent turnTo do Fix score-floor fallback that silently answers from irrelevant chunksTo do Build a retrieval-quality eval harnessTo do Fix dead repos.yml config and scope the indexer's whole-repo catch-allTo do Add unit test coverage for chunkers, rerank, and collector logicTo do Run e2e retrieval smoke testTo do Confirm vector DB has dataTo do Add rate limiting to /api/rag/queryDone Verify RAG honest-degrade behavior after the score-floor fixTo do Run the eval harness and record a retrieval-quality baselineTo do Fix full-repo re-embed on every git push (unbounded per-push cost)To do Bound and monitor total OpenAI spend for RAGTo do

Wave

RAG / Semantic Search

Retrieval for the flagship agent — protected alongside it, not cut. Earlier framing as cut-list item #1 was wrong and is reversed. Critical finding: RAG is NOT actually wired to the customer agent today — searchAndAnswer() is only reachable via an internal endpoint behind a static token, and the corpus is TacTile's own monorepo and business docs rather than customer data. So it is currently an internal dev tool. Tenant isolation is safe only by accident: there is no account_id column and no scoping primitive, so the day customer content is added, cross-account leakage needs zero code changes to happen.

TacTile › Launch TacTile › RAG / Semantic Search

2/16 done14 open3 open blockers

Selected taskclear

Build rag.search MCP tool and wire it into the customer agent turn

To doOwner · Vivt_27391766

Waiting on 2 · 2 still openDecide: RAG stays internal-only or becomes the agent's retrieval layer Decide: will RAG ever index per-account/customer content?

Unlocks 1Approve: RAG / Semantic Search

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Build rag.search MCP tool and wire it into the customer agent turn** · to do

Where it sits: TacTile › Launch TacTile › RAG / Semantic Search

## Waiting on 2

- Decide: RAG stays internal-only or becomes the agent's retrieval layer — to do
- Decide: will RAG ever index per-account/customer content? — to do

2 of those are still open. If one genuinely blocks this, say so and stop rather than working around it.

## Unlocks 1

- Approve: RAG / Semantic Search

## The brief on file

Viv — contingent on the "RAG stays internal vs. becomes agent retrieval" decision landing on "wire it in": add a rag.search tool to packages/mcp-server/src/tools/ calling searchAndAnswer() (packages/rag-core/retrieval/answer.ts), register it in agent-core's ALL_TOOLS, and gate it (minTier: "plus" per prior audit recommendation) given real per-query OpenAI cost. Requires OPENAI_API_KEY + PG_* available in the Worker runtime (currently only the Next.js edge runtime has them) — may need a Supabase edge function as the retrieval backend instead of a direct Worker call. Done when: a live agent turn can call rag.search and cite grounded [SOURCE N] passages in its answer. File: packages/mcp-server/src/tools/rag.ts (new), packages/agent-core/src/runner.ts.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

RAG / Semantic Search

Build rag.search MCP tool and wire it into the customer agent turn