Platform design

Start with platform architecture to understand the OpenClaw Control Plane's components, ownership, and trust boundaries. Its implementation status and remaining design work distinguish current behavior from approved requirements that are not yet supported.

Find the right source

• The RFC guide explains how to propose architectural decisions and develop them alongside implementation.
• Design philosophy explains how to put complete caller tasks behind small interfaces with clear ownership and failure behavior.
• Readable code develops those principles through functions, values, composition, and an illustrative TypeScript example. Use the design-review skill to assess a design or refactor through a supported caller.
• Driver development collects the base contracts for extending infrastructure behavior. For supported products and setup, use Integrations.
• Runtime flows trace how the current code processes requests, deploys Agents, and runs background work.
• Repository layout maps packages and source directories to their owners.
• Implementation specifications record individual proposals and delivery history. They are not proof that a capability exists in the current product.

Keep architecture pages about components, ownership, trust boundaries, and major interactions. Put a feature's detailed behavior in its current reference and link it from architecture when it changes a system boundary. See Documentation for file ownership and verification.