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

Task

Tap a task in the map to see what it's waiting on and what it unlocks. 3 open blockers in this wave.

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

Lanes

RAG / Semantic Search