Clarify operating model and project corpus state

docs/atocore-ecosystem-and-hosting.md

@@ -86,6 +86,24 @@ file replication of the live machine store.
 - OpenClaw must continue to work if AtoCore is unavailable
 - write-back from OpenClaw into AtoCore is deferred until later phases
 
+## Intended Daily Operating Model
+
+The target workflow is:
+
+- the human continues to work primarily in PKM project notes, Git/Gitea repos,
+  Discord, and normal OpenClaw sessions
+- OpenClaw keeps its own runtime behavior and memory system
+- AtoCore acts as the durable external context layer that compiles trusted
+  project state, retrieval, and long-lived machine-readable context
+- AtoCore improves prompt quality and robustness without replacing direct repo
+  work, direct file reads, or OpenClaw's own memory
+
+In other words:
+
+- PKM and repos remain the human-authoritative project sources
+- OpenClaw remains the active operating environment
+- AtoCore remains the compiled context engine and machine-memory host
+
 ## Current Status
 
 As of the current implementation pass:
@@ -95,6 +113,8 @@ As of the current implementation pass:
 - the service is running from Dalidou
 - the T420/OpenClaw machine can reach AtoCore over network
 - a first read-only OpenClaw-side helper exists
+- the live corpus now includes initial AtoCore self-knowledge and a first
+  curated batch for active projects
 - the long-term content corpus still needs broader project and vault ingestion
 
 This means the platform is hosted on Dalidou now, the first cross-machine