reference / source evidence

Source Evidence

Repo-relative source files that anchor the documentation.

Availablellms.txtSource evidence
Documentation Map The documentation is organized around installing Ambient, understanding the product model, and operating its core developer surfaces. Documentation Map The documentation is organized around installing Ambient, understanding the product model, and operating its core developer surfaces. orientsdocumentsgovernsfeeds roadmap Developer docs contract task pathmaturitysource evidence 1 Start HomeInstallQuickstartProduct North Star 2 Use Project BoardWorkflowsProvidersPlugins 3 Trust Security modelCurated defaultsBrowser safetySource evidence 4 Network Ambient NetworkAmbient MiniRoutingMarketplace
The documentation is organized around installing Ambient, understanding the product model, and operating its core developer surfaces.

Evidence Standard

Published pages are grounded in source, tests, screenshots, and product behavior. Readers should be able to trace important claims back to reviewable implementation evidence.

Canonical Source Families

  • Planning artifacts: documentation plan, phased implementation, plugin plan, local model plan, workflow plans.
  • Product contracts: shared TypeScript types for Project Board, workflow recorder, Symphony recipes, provider settings, and local runtime diagnostics.
  • Runtime services: ToolHive, browser service, local model manager, provider stack, plugin supervision.
  • Validation scripts: release gates, visual tests, provider tests, and docs checks.