Local Quickstart
The first real local planning → task → land loop.
Docs
Find the right page for the path you're on.
Start with the right document
You do not need to read everything first. Use the shortest honest entry point for the path you are on, then expand only when the work really needs deeper workflow, deployment, or service context.
First documents for new users
Workflow Doctrine
Why the workflow is agent-mediated, planning-first, and local-first.
Prompt Patterns
Copyable ways to tell the agent what you want.
Deeper developer docs
Self-Hosted
The later path for shared deployment and broader control-plane routing, after the first local loop is already clear.
Package Targets
Which public surfaces belong to which install and boundary, without turning the first learning path into a packaging lecture.
Compatibility Matrix
Which combinations are supported for the current release family when you move beyond the first local route.
Supporting proof and references
Public Demo Data
Public evidence and example workflow outputs that support the service story without replacing the first-run learning path.
Services map
See the core capabilities and surface map only after the first local loop is already clear.
Legal hub
Read the public privacy, terms, release-license, and trademark boundaries for the official website.
Docs hub rule
The docs hub should route visitors into already-landed public guidance. It should not clone the authenticated app, restate every internal strategy document, or turn the official website into a second workflow UI.