reference / maturity labels

Maturity Labels

How this documentation distinguishes Available, Developer Preview, In Development, and Roadmap features.

Availablellms.txtSource evidence
Progressive Discovery Pi receives compact context first and asks for bounded slices of state only when the task requires them. Progressive Discovery Pi receives compact context first and asks for bounded slices of state only when the task requires them. starts stableasks just enoughacts with evidencerepairs narrowly Bounded context loop small prefixtyped readsvalidator feedback 1 Stable prompt Policy summaryCurrent taskKnown tools 2 Discover ListSearchDescribeRead evidence 3 Act Use toolValidate outputPersist artifact 4 Repair Clear errorNarrow retryKeep trace
Pi receives compact context first and asks for bounded slices of state only when the task requires them.

Label Definitions

  • Available: documented user path, validation evidence, troubleshooting, and stable UX.
  • Developer Preview: substantial implementation and tests exist, but the team is still proving edge cases.
  • In Development: important building blocks exist, but UX, contracts, or validation are still moving.
  • Roadmap: strategic direction that should be visible but not promised as available.

Reliability Contract

Every page prefers exact maturity over vague optimism. If a feature is strategic but not available yet, it says so and points to the implemented building blocks.