Antoine/ATOCore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add project registry refresh foundation

Browse Source
This commit is contained in:
Anto01
2026-04-06 08:02:13 -04:00
parent 0f95415530
commit 8293099025
12 changed files with 526 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/current-state.md
View File

@@ -38,6 +38,7 @@ now includes a first curated ingestion batch for the active projects.
- vector retrieval
- context builder
- API routes for query, context, health, and source status
- project registry and per-project refresh foundation
- env-driven storage and deployment paths
- Dalidou Docker deployment foundation
- initial AtoCore self-knowledge corpus ingested on Dalidou
@@ -144,6 +145,12 @@ In `source_documents` / retrieval corpus:
- the current corpus is still selective rather than exhaustive
- that selectivity is intentional at this stage
The source refresh model now has a concrete foundation in code:
- a project registry file defines known project ids, aliases, and ingest roots
- the API can list registered projects
- the API can refresh one registered project at a time
In `Trusted Project State`:
- each active seeded project now has a conservative trusted-state set

1
docs/next-steps.md
View File

@@ -30,6 +30,7 @@ AtoCore now has:
- make the difference between source truth, staged inputs, and machine store
explicit
- move toward a project source registry and refresh workflow
- foundation now exists via project registry + per-project refresh API
5. Define backup and export procedures for Dalidou
- SQLite snapshot/backup strategy
- Chroma backup or rebuild policy

11
docs/source-refresh-model.md
View File

@@ -78,6 +78,17 @@ The long-run workflow should become much more natural:
- AtoCore refreshes the machine representation cleanly
- OpenClaw consumes the improved context over API
## Current Foundation
The first concrete foundation for this now exists in AtoCore:
- a project registry file records known project ids, aliases, and ingest roots
- the API can list those registered projects
- the API can refresh a single registered project from its configured roots
This is not full source automation yet, but it gives the refresh model a real
home in the system.
## Healthy Mental Model
Use this distinction: