Document ecosystem state and integration contract

docs/dalidou-deployment.md

@@ -9,6 +9,8 @@ Deploy AtoCore on Dalidou as the canonical runtime and machine-memory host.
 - OpenClaw on the T420 consumes AtoCore over network/Tailscale API.
 - `sources/vault` and `sources/drive` are read-only inputs by convention.
 - SQLite/Chroma machine state stays on Dalidou and is not treated as a sync peer.
+- The app and machine-storage host can be live before the long-term content
+  corpus is fully populated.
 
 ## Directory layout
 
@@ -75,3 +77,15 @@ curl http://127.0.0.1:8100/sources
 - reverse proxy / TLS exposure
 - automated source ingestion job
 - OpenClaw client wiring
+
+## Current Reality Check
+
+When this deployment is first brought up, the service may be healthy before the
+real corpus has been ingested.
+
+That means:
+
+- AtoCore the system can already be hosted on Dalidou
+- the canonical machine-data location can already be on Dalidou
+- but the live knowledge/content corpus may still be empty or only partially
+  loaded until source ingestion is run