services/service-search

service-search answers full-text queries across millions of platform documents in microseconds, using a static binary inverted index built in Rust on the Tantivy library — and because the index is a file rather than a live database process, it can be copied to portable media and queried on any machine without additional dependencies. The service is a Ring 2 knowledge-and-processing component and conforms to the Data Archive and Retrieval Protocol (DARP) standard. It locates documents; it does not generate or classify them.

[edit]Architectural Baseline

An inverted index works by building a compressed map from every word in the corpus to the list of documents that contain it — analogous to the index at the back of a reference book. At query time, the service looks up the query terms in this map and returns matching documents in microseconds, regardless of corpus size. Tantivy, the underlying Rust library, is designed for high-throughput indexing and low-latency retrieval on commodity hardware. [^1]

[edit]Ring and Role

service-search occupies Ring 2 — Knowledge and Processing in the three-ring-architecture. Ring 2 is multi-tenant via moduleId namespacing and operates deterministically without AI inference. service-search's role within Ring 2 is retrieval: it answers queries against the indexed corpus and returns ranked document references that Ring 2 or Ring 3 services use for downstream processing. The service does not generate content or classify documents — it locates them.

[edit]Structural Organization of Components

The index is built as a static binary file. Key architectural properties:

• No active process required for queries. The index is memory-mapped at query time; there is no database daemon to manage or restart.
• Portable. The index file can be copied to USB storage or a different machine and queried immediately.
• Compressed. Tantivy's index format uses block-maximal encoding for term frequency data, keeping the index compact relative to corpus size.
• Updatable. New documents are added to the index via a background indexing process that merges new segments. Queries can run against existing segments while new segments are being built.

The service is integrated with service-extraction for post-parse indexing and with the system contracts layer for programmatic retrieval.

[edit]Configuration

Parameter	Purpose
Index path	Filesystem path for the Tantivy index directory
Schema	Field definitions for indexed documents (title, body, date, category, moduleId)
Merge policy	Segment merge configuration controlling index compaction frequency
Writer threads	Number of indexing threads for parallel document ingestion

[edit]See also

• service-extraction — Ring 2 service whose parsed output is fed into the search index
• service-slm — Ring 3 intelligence layer that consumes ranked retrieval results
• service-people — identity ledger whose records form part of the searchable corpus
• trajectory-substrate — the substrate model for compounding retrieval intelligence over time