Expand active project wave and serialize refreshes

docs/next-steps.md

@@ -29,9 +29,11 @@ This working list should be read alongside:
    - check whether the top hits are useful
    - check whether trusted project state remains dominant
    - reduce cross-project competition and prompt ambiguity where needed
-3. Continue controlled project ingestion only where the current corpus is still
-   thin
-   - a few additional anchor docs per active project
+   - use `debug-context` to inspect the exact last AtoCore supplement
+3. Treat the active-project full markdown/text wave as complete
+   - `p04-gigabit`
+   - `p05-interferometer`
+   - `p06-polisher`
 4. Define a cleaner source refresh model
    - make the difference between source truth, staged inputs, and machine store
      explicit
@@ -39,15 +41,20 @@ This working list should be read alongside:
    - foundation now exists via project registry + per-project refresh API
    - registration policy + template + proposal + approved registration are now
      the normal path for new projects
-5. Integrate the new engineering architecture docs into active planning, not immediate schema code
+5. Move to Wave 2 trusted-operational ingestion
+   - curated dashboards
+   - decision logs
+   - milestone/current-status views
+   - operational truth, not just raw project notes
+6. Integrate the new engineering architecture docs into active planning, not immediate schema code
    - keep `docs/architecture/engineering-knowledge-hybrid-architecture.md` as the target layer model
    - keep `docs/architecture/engineering-ontology-v1.md` as the V1 structured-domain target
    - do not start entity/relationship persistence until the ingestion, retrieval, registry, and backup baseline feels boring and stable
-6. Define backup and export procedures for Dalidou
+7. Define backup and export procedures for Dalidou
    - exercise the new SQLite + registry snapshot path on Dalidou
    - Chroma backup or rebuild policy
    - retention and restore validation
-7. Keep deeper automatic runtime integration modest until the organic read-only
+8. Keep deeper automatic runtime integration modest until the organic read-only
    model has proven value
 
 ## Trusted State Status
@@ -69,36 +76,39 @@ This materially improves `context/build` quality for project-hinted prompts.
 
 ## Recommended Near-Term Project Work
 
-The first curated batch is already in.
+The active-project full markdown/text wave is now in.
 
 The near-term work is now:
 
 1. strengthen retrieval quality
-2. add a few more anchor docs only where retrieval is still weak
+2. promote or refine trusted operational truth where the broad corpus is now too noisy
 3. keep trusted project state concise and high-confidence
+4. widen only through named ingestion waves
 
-## Recommended Additional Anchor Docs
+## Recommended Next Wave Inputs
 
-1. `p04-gigabit`
-2. `p05-interferometer`
-3. `p06-polisher`
+Wave 2 should emphasize trusted operational truth, not bulk historical notes.
 
 P04:
 
-- 1 to 2 more strong study summaries
-- 1 to 2 more meeting notes with actual decisions
+- current status dashboard
+- current selected design path
+- current frame interface truth
+- current next-step milestone view
 
 P05:
 
-- a couple more architecture docs
-- selected vendor-response notes
-- possibly one or two NX/WAVE consumer docs
+- selected vendor path
+- current error-budget baseline
+- current architecture freeze or open decisions
+- current procurement / next-action view
 
 P06:
 
-- more explicit interface/schema docs if needed
-- selected operations or UI docs
-- a distilled non-empty operational context doc to replace an empty `_context.md`
+- current system map
+- current shared contracts baseline
+- current calibration procedure truth
+- current July / proving roadmap view
 
 ## Deferred On Purpose
 
@@ -115,6 +125,8 @@ The next batch is successful if:
 - OpenClaw can use AtoCore naturally when context is needed
 - OpenClaw can infer registered projects and call AtoCore organically for
   project-knowledge questions
+- the active-project full corpus wave can be inspected and used concretely
+  through `auto-context`, `context-build`, and `debug-context`
 - OpenClaw can also register a new project cleanly before refreshing it
 - existing project registrations can be refined safely before refresh when the
   staged source set evolves