Clarify source staging and refresh model

This commit is contained in:
2026-04-06 07:53:18 -04:00
parent 82c7535d15
commit 0f95415530
5 changed files with 192 additions and 6 deletions

View File

@@ -84,11 +84,12 @@ The Dalidou instance already contains:
- `p05-interferometer`
- `p06-polisher`
Current live stats after the first active-project ingest pass:
Current live stats after the latest documentation sync and active-project ingest
passes:
- `source_documents`: 33
- `source_chunks`: 535
- `vectors`: 535
- `source_documents`: 34
- `source_chunks`: 550
- `vectors`: 550
The broader long-term corpus is still not fully populated yet. Wider project and
vault ingestion remains a deliberate next step rather than something already
@@ -102,6 +103,14 @@ primarily visible under:
This staged area is now useful for review because it contains the curated
project docs that were actually ingested for the first active-project batch.
It is important to read this staged area correctly:
- it is a readable ingestion input layer
- it is not the final machine-memory representation itself
- seeing familiar PKM-style notes there is expected
- the machine-processed intelligence lives in the DB, chunks, vectors, memory,
trusted project state, and context-builder outputs
## What Is True On The T420
- SSH access is working
@@ -132,6 +141,8 @@ In `source_documents` / retrieval corpus:
- real project documents are now present for the same active project set
- retrieval is no longer limited to AtoCore self-knowledge only
- the current corpus is still selective rather than exhaustive
- that selectivity is intentional at this stage
In `Trusted Project State`: