Mechanical catalog

The Living Index

Every room, exhibit and source span in one place. Cross references come from PHAROS's recorded graph, or are written comparisons and say so.

Pass 3 of 3 · Deep dive of the hallPass 1 · OverviewPass 2 · How it works

Text catalog

Every entry, as plain links
PHAROS components, from the source audit
FromRelationTo
Ingestion jobsrunsIndexer
Indexerparses withParsers
Indexerembeds withEmbeddings
IndexerrebuildsCall graph
ParserschunksPostgreSQL store
EmbeddingsvectorsPostgreSQL store
Call graphedgesPostgreSQL store
PostgreSQL storesearched byRetriever
Retrieverranked hitsContext assembly
Source verificationverified codeContext assembly
Repository memorymemory blockContext assembly
Context assemblyretrieve_contextMCP server
Context assembly/context/retrieveREST API
Retrieversearch_codeMCP server
Retriever/search/codeREST API
Between projects. These are editorial comparisons, not relations extracted from code.
ProjectsComparisonReason
PHAROS, CognitiveOS / ValerieTwo control boundariesPHAROS compares source with the Git blob recorded at indexing. A mismatch withholds the code, but with no recorded blob the code is returned marked unverified. Valerie checks typed moves against issued state before native engines run them. Both checks are deterministic code, not a model’s judgement.
PHAROS, CognitiveOS / ValerieTwo kinds of memoryPHAROS keeps repository evidence and conventions. Valerie keeps sourced temporal facts and a ledger.
BABEL, CognitiveOS / ValerieTyped outputBABEL validates chapters against a typed schema on its batch path, but its single-chapter path accepts looser blocks, so validation is inconsistent. Valerie validates typed moves against issued state before native engines run them.

Symbol-level calls and imports are on each symbol page, with direction and resolution.