Skip to content

Documentation Map

Use this page as the reader path map for the public docs. It keeps roadmap history discoverable while routing active work to the pages that own executable contracts.

Reader Paths

Reader Start here Then use Success signal
First-time local user Quick Start CLI Reference, Examples And CLI Commands a mock world, provider diagnostic, or checkout-safe demo runs locally
Provider author Provider Authoring Guide Providers, Capability Fixture Corpus, Public API Stability provider capability, profile, fixtures, docs, and tests agree
Operator Operations User And Operator Playbooks, Security, Artifact Integrity diagnostics, run manifests, safe bundles, and recovery commands are available
Evaluator or research user Evaluation Benchmarking, Claim-To-Evidence Map, Live Smoke Evidence Registry claims point to preserved reports and clear claim boundaries
Demo or showcase user Examples And CLI Commands Demo Showcase Workflows, Use Case Cookbook, Robotics Replay Showcase, TheWorldHarness, Rerun Integration checkout-safe demos or prepared-host showcase commands produce artifacts
Release maintainer Engineering Quality Artifact Integrity, Operations, Changelog local gates, package checks, audit, evidence JSON, and release notes line up

Roadmap History

Roadmap pages remain public because they preserve why the project chose a direction. They are not a substitute for active issue state or executable docs.

Page Role
Roadmap current top-level public direction and links to historical tracks
Roadmap Expansion 30-issue expansion record created for the current production, demo, and feature streams
Roadmap Continuation earlier continuation plan and completed coordination notes
Provider And Platform Roadmap prior provider-platform tracker and evidence history

Active work should be tracked in GitHub issues. When a roadmap item changes public behavior, update the owning docs page, changelog, tests, and this map if the reader path changes.