Document organic OpenClaw routing layer

This commit is contained in:
2026-04-06 14:04:49 -04:00
parent 26bfa94c65
commit 9943338846
4 changed files with 42 additions and 16 deletions

View File

@@ -20,8 +20,10 @@ This working list should be read alongside:
## Immediate Next Steps
1. Use the T420 `atocore-context` skill in real OpenClaw workflows
- confirm the ergonomics are good
1. Use the T420 `atocore-context` skill and the new organic routing layer in
real OpenClaw workflows
- confirm `auto-context` feels natural
- confirm project inference is good enough in practice
- confirm the fail-open behavior remains acceptable in practice
2. Review retrieval quality after the first real project ingestion batch
- check whether the top hits are useful
@@ -45,8 +47,8 @@ This working list should be read alongside:
- exercise the new SQLite + registry snapshot path on Dalidou
- Chroma backup or rebuild policy
- retention and restore validation
7. Keep deeper automatic runtime integration deferred until the read-only model
has proven value
7. Keep deeper automatic runtime integration modest until the organic read-only
model has proven value
## Trusted State Status
@@ -111,6 +113,8 @@ P06:
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
- 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