ATOCore/docs/current-state.md

AtoCore Current State

Status Summary

AtoCore is no longer just a proof of concept. The local engine exists, the correctness pass is complete, and Dalidou now hosts the canonical runtime and machine-storage location.

Phase Assessment

• completed
  • Phase 0
  • Phase 0.5
  • Phase 1
• baseline complete
  • Phase 2
  • Phase 3
  • Phase 5
  • Phase 7
• partial
  • Phase 4
• not started
  • Phase 6
  • Phase 8
  • Phase 9
  • Phase 10
  • Phase 11
  • Phase 12
  • Phase 13

What Exists Today

• ingestion pipeline
• parser and chunker
• SQLite-backed memory and project state
• vector retrieval
• context builder
• API routes for query, context, health, and source status
• env-driven storage and deployment paths
• Dalidou Docker deployment foundation

What Is True On Dalidou

• deployed repo location:
  • /srv/storage/atocore/app
• canonical machine DB location:
  • /srv/storage/atocore/data/db/atocore.db
• canonical vector store location:
  • /srv/storage/atocore/data/chroma
• source input locations:
  • /srv/storage/atocore/sources/vault
  • /srv/storage/atocore/sources/drive

The service and storage foundation are live on Dalidou.

The machine-data host is real and canonical.

The content corpus is not fully populated yet. A fresh or near-fresh live DB is running there until the ingestion pipeline loads the ecosystem docs and project content.

Immediate Next Focus

1. Ingest AtoCore ecosystem and planning docs into the Dalidou instance
2. Define the OpenClaw integration contract clearly
3. Wire OpenClaw to consume AtoCore read-only over network
4. Ingest selected project content in a controlled way

Guiding Constraints

• bad memory is worse than no memory
• trusted project state must remain highest priority
• human-readable sources and machine storage stay separate
• OpenClaw integration must not degrade OpenClaw baseline behavior