Parent epic: #12225
Context
The learn/agentos/cloud-deployment/ guides are mechanics-heavy and intent-light. The Overview opens with "what cloud-native KB ingestion means" → contract splits, parsed-chunk-v1, topology anchors. A reader learns how to wire ingestion but never why to deploy the Agent OS, what they get, or the recommended end-to-end path. They also over-index on Knowledge Base ingestion, which is only a fraction of the Brain.
This sub is part of the #12225 organism-apex rollout: it adds the benefit/intent layer for deploying the Brain without changing runtime behavior or naming clients.
The Fix
Add the missing why/benefit/path layer (capability framing, fully generic — no client names):
- A "why deploy the Agent OS" overview: what a deployed Brain gives you (a memory-backed, cross-family engineering team operating over your own content), framed as capability/benefit.
- The recommended end-to-end deployment path, top-down, before the contract-level mechanics.
- Rebalance: present the full Brain (Memory Core, orchestrator, dream/golden-path, A2A) — not KB ingestion alone — as what is being deployed.
- Keep the existing mechanics guides; this adds the layer above them.
Acceptance Criteria
Out of Scope
- Monetization, pricing, commercial terms
- Any specific client deployment
- Engine/runtime changes
Related
- Parent: #12225 · Surfaces:
learn/agentos/cloud-deployment/**
Origin Session ID: 94a91ebc-d325-4d32-a746-4ff8c26c0342
Retrieval Hint: "cloud-deployment guides why benefit intent layer KB-centric rebalance"
Parent epic: #12225
Context
The
learn/agentos/cloud-deployment/guides are mechanics-heavy and intent-light. The Overview opens with "what cloud-native KB ingestion means" → contract splits,parsed-chunk-v1, topology anchors. A reader learns how to wire ingestion but never why to deploy the Agent OS, what they get, or the recommended end-to-end path. They also over-index on Knowledge Base ingestion, which is only a fraction of the Brain.This sub is part of the #12225 organism-apex rollout: it adds the benefit/intent layer for deploying the Brain without changing runtime behavior or naming clients.
The Fix
Add the missing why/benefit/path layer (capability framing, fully generic — no client names):
Acceptance Criteria
Out of Scope
Related
learn/agentos/cloud-deployment/**Origin Session ID: 94a91ebc-d325-4d32-a746-4ff8c26c0342 Retrieval Hint: "cloud-deployment guides why benefit intent layer KB-centric rebalance"