61 lines
2.0 KiB
Markdown
61 lines
2.0 KiB
Markdown
# AtoCore Next Steps
|
|
|
|
## Current Position
|
|
|
|
AtoCore now has:
|
|
|
|
- canonical runtime and machine storage on Dalidou
|
|
- separated source and machine-data boundaries
|
|
- initial self-knowledge ingested into the live instance
|
|
- trusted project-state entries for AtoCore itself
|
|
- a first read-only OpenClaw integration path on the T420
|
|
|
|
## Immediate Next Steps
|
|
|
|
1. Use the T420 `atocore-context` skill in real OpenClaw workflows
|
|
- confirm the ergonomics are good
|
|
- confirm the fail-open behavior remains acceptable in practice
|
|
2. Ingest selected active projects only
|
|
- start with the current active project set
|
|
- prefer trusted operational/project sources first
|
|
- ingest broader PKM sources only after the trusted layer is loaded
|
|
3. Review retrieval quality after the first real project ingestion batch
|
|
- check whether the top hits are useful
|
|
- check whether trusted project state remains dominant
|
|
4. Define backup and export procedures for Dalidou
|
|
- SQLite snapshot/backup strategy
|
|
- Chroma backup or rebuild policy
|
|
5. Keep deeper automatic runtime integration deferred until the read-only model
|
|
has proven value
|
|
|
|
## Recommended Active Project Ingestion Order
|
|
|
|
1. `p04-gigabit`
|
|
2. `p05-interferometer`
|
|
3. `p06-polisher`
|
|
|
|
For each project:
|
|
|
|
1. identify the matching AtoDrive/project-operational sources
|
|
2. identify the matching PKM project folder(s)
|
|
3. ingest the trusted/operational material first
|
|
4. ingest broader notes second
|
|
5. review retrieval quality before moving on
|
|
|
|
## Deferred On Purpose
|
|
|
|
- automatic write-back from OpenClaw into AtoCore
|
|
- automatic memory promotion
|
|
- reflection loop integration
|
|
- replacing OpenClaw's own memory system
|
|
- syncing the live machine DB between machines
|
|
|
|
## Success Criteria For The Next Batch
|
|
|
|
The next batch is successful if:
|
|
|
|
- OpenClaw can use AtoCore naturally when context is needed
|
|
- AtoCore answers correctly for the active project set
|
|
- project ingestion remains controlled rather than noisy
|
|
- the canonical Dalidou instance stays stable
|