# AtoCore Master Plan Status

## Current Position

AtoCore is currently between **Phase 7** and **Phase 8**.

The platform is no longer just a proof of concept. The local engine exists, the
core correctness pass is complete, Dalidou hosts the canonical runtime and
machine database, and OpenClaw on the T420 can consume AtoCore safely in
read-only additive mode.

## Phase Status

### Completed

- Phase 0 — Foundation
- Phase 0.5 — Proof of Concept
- Phase 1 — Ingestion

### Baseline Complete

- Phase 2 — Memory Core
- Phase 3 — Retrieval
- Phase 5 — Project State
- Phase 7 — Context Builder

### Partial

- Phase 4 — Identity / Preferences

### Not Yet Complete In The Intended Sense

- Phase 6 — AtoDrive
- Phase 8 — OpenClaw Integration
- Phase 9 — Reflection
- Phase 10 — Write-back
- Phase 11 — Multi-model
- Phase 12 — Evaluation
- Phase 13 — Hardening

## What Is Real Today

- canonical AtoCore runtime on Dalidou
- canonical machine DB and vector store on Dalidou
- project registry with:
  - template
  - proposal preview
  - register
  - update
  - refresh
- read-only additive OpenClaw helper on the T420
- seeded project corpus for:
  - `p04-gigabit`
  - `p05-interferometer`
  - `p06-polisher`
- conservative Trusted Project State for those active projects
- first operational backup foundation for SQLite + project registry
- implementation-facing architecture notes for future engineering knowledge work

## Now

These are the current practical priorities.

1. Finish practical OpenClaw integration
   - make the helper lifecycle feel natural in daily use
   - use the new organic routing layer for project-knowledge questions
   - confirm fail-open behavior remains acceptable
   - keep AtoCore clearly additive
2. Tighten retrieval quality
   - reduce cross-project competition
   - improve ranking on short or ambiguous prompts
   - add only a few anchor docs where retrieval is still weak
3. Continue controlled ingestion
   - deepen active projects selectively
   - avoid noisy bulk corpus growth
4. Strengthen operational boringness
   - backup and restore procedure
   - Chroma rebuild / backup policy
   - retention and restore validation

## Next

These are the next major layers after the current practical pass.

1. Clarify AtoDrive as a real operational truth layer
2. Mature identity / preferences handling
3. Improve observability for:
   - retrieval quality
   - context-pack inspection
   - comparison of behavior with and without AtoCore

## Later

These are the deliberate future expansions already supported by the architecture
direction, but not yet ready for immediate implementation.

1. Minimal engineering knowledge layer
   - driven by `docs/architecture/engineering-knowledge-hybrid-architecture.md`
   - guided by `docs/architecture/engineering-ontology-v1.md`
2. Minimal typed objects and relationships
3. Evidence-linking and provenance-rich structured records
4. Human mirror generation from structured state

## Not Yet

These remain intentionally deferred.

- automatic write-back from OpenClaw into AtoCore
- automatic memory promotion
- reflection loop integration
- replacing OpenClaw's own memory system
- live machine-DB sync between machines
- full ontology / graph expansion before the current baseline is stable

## Working Rule

The next sensible implementation threshold for the engineering ontology work is:

- after the current ingestion, retrieval, registry, OpenClaw helper, and backup
  baseline feels boring and dependable

Until then, the architecture docs should shape decisions, not force premature
schema work.