Context
Sub-3 of #10103, graduated from Discussion #11961. This sub owns cloud deployment docs and readiness tests after the Tier-1 config and runtime provider routing shape is in place.
The Problem
Current cloud deployment examples and tests cover important container and embedding paths, but they do not prove the complete Agent OS model-provider path required for a non-macOS client deployment: embeddings, chat completions, and Dream/REM graph mutation.
The Architectural Reality
Primary surfaces:
learn/agentos/cloud-deployment/Day0Tutorial.mdai/deploy/docker-compose*.yml- Integration tests under
test/playwright/integration*
- Provider mocks for OpenAI-compatible / Ollama-like APIs
- Dream/REM graph-mutator readiness path
This sub should run after or alongside the implementation subs but must not paper over unsupported runtime routes.
The Fix
Align deployment docs and integration coverage with the final provider contract. Prove cloud readiness using mocked provider endpoints for embeddings and chat completions, plus one Dream/REM graph-mutator readiness path.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback / Edge Case |
Docs |
Evidence |
| Cloud provider docs |
#11961 OQ2/OQ6 |
Document native Ollama and OpenAI-compatible fallback profiles accurately |
If native route is incomplete, docs must say so until Sub-2 lands |
Day0 tutorial |
Docs diff + test references |
| Embedding readiness |
#11961 OQ6 |
Test /v1/embeddings or native equivalent under deployment profile |
Mock server must expose enough metadata to verify route |
Test comments |
Integration test |
| Chat readiness |
#11961 OQ6 |
Test /v1/chat/completions or native equivalent under deployment profile |
Provider-specific request differences stay explicit |
Test comments |
Integration test |
| Dream/REM readiness |
#11961 OQ6 |
Prove selected provider can drive the load-bearing graph-mutator path |
Session summarization alone is insufficient |
Test/docs |
Integration or focused service test |
Decision Record impact
Aligned with #11961's readiness bar. No ADR superseded.
Acceptance Criteria
Out of Scope
- Moving config keys.
- Provider dispatch implementation.
- Per-tenant provider variation.
Avoided Traps
- Do not let docs advertise native Ollama before runtime tests prove it.
- Do not count container health or embeddings-only tests as full Agent OS model readiness.
Related
- Parent: #10103
- Discussion: #11961
- Sub-1: config ownership ledger + Tier-1 lift
- Sub-2: runtime provider routing + native Ollama wire-up
Handoff Retrieval Hint: "Sub-3 #10103 cloud deployment docs integration tests embeddings chat dream readiness"
Context
Sub-3 of #10103, graduated from Discussion #11961. This sub owns cloud deployment docs and readiness tests after the Tier-1 config and runtime provider routing shape is in place.
The Problem
Current cloud deployment examples and tests cover important container and embedding paths, but they do not prove the complete Agent OS model-provider path required for a non-macOS client deployment: embeddings, chat completions, and Dream/REM graph mutation.
The Architectural Reality
Primary surfaces:
learn/agentos/cloud-deployment/Day0Tutorial.mdai/deploy/docker-compose*.ymltest/playwright/integration*This sub should run after or alongside the implementation subs but must not paper over unsupported runtime routes.
The Fix
Align deployment docs and integration coverage with the final provider contract. Prove cloud readiness using mocked provider endpoints for embeddings and chat completions, plus one Dream/REM graph-mutator readiness path.
Contract Ledger Matrix
/v1/embeddingsor native equivalent under deployment profile/v1/chat/completionsor native equivalent under deployment profileDecision Record impact
Aligned with #11961's readiness bar. No ADR superseded.
Acceptance Criteria
Out of Scope
Avoided Traps
Related
Handoff Retrieval Hint: "Sub-3 #10103 cloud deployment docs integration tests embeddings chat dream readiness"