Refresh current state and next steps docs

docs/current-state.md

@@ -79,17 +79,29 @@ The Dalidou instance already contains:
 - curated repo-context docs for:
   - `p05`: `Fullum-Interferometer`
   - `p06`: `polisher-sim`
+- trusted project-state entries for:
+  - `p04-gigabit`
+  - `p05-interferometer`
+  - `p06-polisher`
 
 Current live stats after the first active-project ingest pass:
 
-- `source_documents`: 32
-- `source_chunks`: 523
-- `vectors`: 523
+- `source_documents`: 33
+- `source_chunks`: 535
+- `vectors`: 535
 
 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
 completed, but the corpus is now meaningfully seeded beyond AtoCore's own docs.
 
+For human-readable quality review, the current staged project markdown corpus is
+primarily visible under:
+
+- `/srv/storage/atocore/sources/vault/incoming/projects`
+
+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.
+
 ## What Is True On The T420
 
 - SSH access is working
@@ -121,6 +133,15 @@ 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
 
+In `Trusted Project State`:
+
+- each active seeded project now has a conservative trusted-state set
+- promoted facts cover:
+  - summary
+  - core architecture or boundary decision
+  - key constraints
+  - next focus
+
 This separation is healthy:
 
 - memory stores distilled project facts
@@ -130,10 +151,9 @@ This separation is healthy:
 
 1. Use the new T420-side AtoCore skill in real OpenClaw workflows
 2. Tighten retrieval quality for the newly seeded active projects
-3. Promote only the most stable active-project facts into trusted project state
-4. Define the first broader AtoVault/AtoDrive ingestion batches
-5. Add backup/export strategy for Dalidou machine state
-6. Only later consider deeper automatic OpenClaw integration or write-back
+3. Define the first broader AtoVault/AtoDrive ingestion batches
+4. Add backup/export strategy for Dalidou machine state
+5. Only later consider deeper automatic OpenClaw integration or write-back
 
 ## Guiding Constraints
 

docs/next-steps.md

@@ -23,21 +23,32 @@ AtoCore now has:
    - check whether the top hits are useful
    - check whether trusted project state remains dominant
    - reduce cross-project competition and prompt ambiguity where needed
-3. Promote a small number of stable active-project facts into trusted project
-   state
-   - active architecture
-   - current selected path
-   - key constraints
-   - current next step
-4. Continue controlled project ingestion only where the current corpus is still
+3. Continue controlled project ingestion only where the current corpus is still
    thin
    - a few additional anchor docs per active project
-5. Define backup and export procedures for Dalidou
+4. Define backup and export procedures for Dalidou
    - SQLite snapshot/backup strategy
    - Chroma backup or rebuild policy
-6. Keep deeper automatic runtime integration deferred until the read-only model
+5. Keep deeper automatic runtime integration deferred until the read-only model
    has proven value
 
+## Trusted State Status
+
+The first conservative trusted-state promotion pass is now complete for:
+
+- `p04-gigabit`
+- `p05-interferometer`
+- `p06-polisher`
+
+Each project now has a small set of stable entries covering:
+
+- summary
+- architecture or boundary decision
+- key constraints
+- current next focus
+
+This materially improves `context/build` quality for project-hinted prompts.
+
 ## Recommended Near-Term Project Work
 
 The first curated batch is already in.
@@ -45,8 +56,8 @@ The first curated batch is already in.
 The near-term work is now:
 
 1. strengthen retrieval quality
-2. promote the most stable facts into trusted project state
-3. only then add a few more anchor docs where still needed
+2. add a few more anchor docs only where retrieval is still weak
+3. keep trusted project state concise and high-confidence
 
 ## Recommended Additional Anchor Docs
 
@@ -86,6 +97,7 @@ The next batch is successful if:
 - OpenClaw can use AtoCore naturally when context is needed
 - AtoCore answers correctly for the active project set
 - retrieval surfaces the seeded project docs instead of mostly AtoCore meta-docs
+- trusted project state remains concise and high confidence
 - project ingestion remains controlled rather than noisy
 - the canonical Dalidou instance stays stable