Refresh current state and next steps docs

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