Bridge paragraph before the enterprise properties: same product spans one
laptop to hardened team deployment, configuration is the only difference,
and the enterprise checklist protects a single operator for free. Adds a
read_when bullet for the reader asking whether enterprise depth makes
OpenClaw heavyweight for personal use.
Replace the feature-list opener with a human introduction: what an agent
inverts about software, why that demands scrutiny, and the OpenClaw
Foundation's mission, governance, and Switzerland-of-AI aim. Dedupe the
Governance section so the sponsor list and 501(c)(3) framing state once.
Three mermaid diagrams for the densest arguments on the page: the
gateway/movable-execution topology, the fail-closed exec policy chain,
and the secret sentinel flow at the egress boundary. All blocks
parse-checked against mermaid.
* docs(start): add Why OpenClaw enterprise architecture page
Source-audited architecture argument for enterprise evaluators: trusted
gateway vs movable untrusted execution, policy-as-code, tiered access,
SecretRef chain, versioned state, provenance, open standards, and a
commit-pinned comparison with Hermes Agent verified against both source
trees. Registers the page in the Get started nav and fixes the OpenShell
policy config description (YAML path, not ID).
* docs(start): link landed feature pages and split the Hermes verdict paragraph
* docs(start): state the comparison in present tense
* docs(start): tighten register after external language review
* docs(start): address review findings
Restore main's OpenShell guide unchanged (rebase resolution had
resurrected the pre-rewrite page), defer the plugin consent screen
claim until its implementation merges, scope the memory forget claim
to tracked artifacts of selected sessions, replace brittle RPC and
capability counts, state OpenAI-compatible API limits, and add
immutable permalinks for every external Hermes citation.
Peter Steinberger