docs: consolidate historical records and verify public manual publication

docs/architecture/overview.md

@@ -81,20 +81,20 @@ The model proposes; a human reviewer decides at gates through widgets:
 
 The frontend renders these widget descriptors (registry in `src/widgets/`). It rebuilds the live transcript in memory from the SSE stream (`src/store/sessionStore.ts`); it is **not persisted**.
 
-## Curated and immutable Evidence
+## Evidence sources, local authority and search projections
 
-The workspace repository is the publication boundary. The curator prepares `evidence/source/`,
-reviews units in `evidence/curated/`, validates them, and merges them. With `evidence.schema_version: 2`,
-the runtime materializes the full `evidence/` tree from the exact Git commit, but the renderer passes
-only `curated/**/*.md` from the immutable revision root to preprocessing. Sources, manifests, and
-evaluation data remain available for traceability. The runtime never modifies, stages, commits, or
-publishes the authoring repository.
+The workspace repository publishes revision-pinned workspace identities and Evidence sources.
+An initialized editable Evidence archive is maintained locally through external editors and
+explicit consolidation; normal preprocessing or source refresh must not overwrite its manual
+corrections. File save, active search generation and a later human Git commit/push are separate
+outcomes. See [the current Evidence contract](../contracts/curated-evidence-v4.md) and
+[source/publication boundaries](../contracts/workspace-evidence-v3.md).
 
-Before indexing, the curated corpus from the pinned revision is validated. Each workspace has two
-physical Qdrant collections with different lifecycles. `reference` contains Schema, relationships,
-and Evidence and may be replaced or cleared by preprocessing; `memory` contains `memory` and
-`solved_question` records and is never preprocessing output. Only the `reference` collection has the
-sparse `bm25` vector with `idf`, and only the Evidence stage writes sparse values.
+Each workspace has separate Qdrant collections. `reference` contains Schema, relationships and
+Evidence and may be replaced or cleared by preprocessing. Memory uses its own dense/BM25
+projection, rebuilt from authoritative PostgreSQL cards rather than old vector payloads or
+session artifacts. Both collections can contain sparse vectors; their ownership and cleanup
+lifecycles remain separate. See [Memory](../gestione-memory.md).
 
 The Administration control can clear the replaceable reference collection, LSH, corpus, and derived
 checkpoints. The operation preserves the memory collection and makes preprocessing required before
@@ -115,6 +115,13 @@ the core can admit a new session.
 
 ## Runtime composition
 
+PostgreSQL is the current database-metadata authority for all core consumers, not a deferred
+catalog-to-core integration. The historical research on a separate catalog service and
+`annotations.yaml` publication is superseded by ADRs 0004 and 0016. Preserve read-only DWH access,
+installation-local bindings/secrets, revision-pinned workspace identity, and fail-closed readiness
+when changing those boundaries. The exact snapshot interface is the
+[Catalog Schema Snapshot contract](../contracts/catalog-schema-snapshot.md).
+
 The local stack is started by `./scripts/run-stack.sh` after the installation descriptor and
 `deploy/env/local.env` exist. `core` includes Pi. `catalog-db`, Qdrant, and the Ollama embedding
 service are internal Compose services; only the DWH and model-provider endpoint remain external.