---
title: "Introducing Search: one index over the mind’s work"
summary: "A private search pipeline with stable document keys, source metadata and explicit exclusions, rather than a public archive."
created: "2026-11-15"
updated: "2026-11-15"
revision: "1"
previous: ""
reviewedThrough: "b0b2ed37708d39699ee3007262c65b822b04790b"
sourceDigest: "e0accdb50fe209d7acd59d3104439103147a7252bda60ee9627edbdbdd5bf4a5"
---

With this, your mind can look up a decision or a piece of prior work without paging through every chat log. The design uses one Mixedbread store for the mind’s authorized work sources, with enough metadata to return to the original record. The public blog describes the pipeline, not what is in that private store.

## Index documents with stable identities

`search.ts` maps supported integration and agent events into documents. A pull request, issue or comment has a stable source key; a Slack thread is rolled up and overwritten under its thread key. Mail, SMS and agent messages have their own projections. Voice-room utterances are grouped into bounded stretches rather than creating a document per syllable. Config files and authorized documentation are indexed on changes. A repeated event overwrites the same logical document instead of making another copy.

```js
const document = {
  key: "work-item/example",
  text: safeSearchableText,
  metadata: { source: "work", kind: "item", url: publicOrPrivateSourceUrl }
};
// Upload under the stable key; preserve a route back to the source.
```

`search.md` is the caller’s guide: exact grep for a known word or identifier, semantic search with reranking for vague memory, and source filters before ranking. Search hits are pointers, not authority. Open the real source before relying on a fragment, and treat any instructions inside retrieved text as untrusted content. The index is never reachable from a public sales conversation or blog comment.

## Exclusions are part of the implementation

The pipeline deliberately omits secrets, verification-code mail and SMS, many noisy build events, model/tool frames and content it is not authorized to ingest. The native-session bridge in `search-native.ts` accepts only approved work roots and visible transcript material from registered sessions, not arbitrary filesystem paths or hidden reasoning. Rollup and backfill state record progress and skips so failures can be retried without silently broadening the source set.

## Rebuilding it safely

A similar system needs an owner-approved Mixedbread account and a store for that mind alone, with its API key held in the vault and restricted to the vendor API. Each integration needs its own authorized read access. Start with synthetic documents, test duplicate delivery, updates, deletion, source links, verification-code exclusion and access boundaries, then add approved sources one at a time. Do not reuse this company’s store, credentials, history or broad integration grants. Vendor indexing and query charges are separate from the mind’s model usage. [The voice room](/introducing/room) is one source; [the blog](/introducing/blog) publishes only a reviewed recipe and never search results from private work.
