Skip to main content

Active Execution Plans

This directory contains multi-step work that is currently active and must survive across sessions.

Active plans​

Detailed plan pages remain repository-only drafts linked from this index because they contain temporary contributor execution state rather than user guidance. They do not enter the public site, search index, or sitemap.

  • AI-verifiable development tooling — Phases 0--1 are complete; Phase 2 adds validation, isolated compile/Preview evidence, and bounded project analysis before protocol or converter work.
  • Pull-request gate scaling and build-logic modularization — split the 2,582-line root gate implementation into compiled, testable build logic, then add conservative pull-request impact selection, verified immutable-API caching, and affected-module verification without weakening required checks or full main validation.
  • Demo post-release verification closeout — hardware-deferred because no currently available physical device can prove the required stable CPU, GPU, and display-pipeline control. All other phases are complete; resume only to recapture the unchanged collection-stress revision-3 scroll baseline when a qualifying device is available. Completed framework-contract-hardening, documentation-governance, architecture, ViewModel-ownership, navigation-lifecycle-and-scene, animation-capability, design-system, theme-propagation, native-widget, component-appearance, tutorial, language-consistency, migration-sample, hosted-documentation, version-retention, and Paging-integration plans are retained in the archive.

Before adding a plan, read Documentation governance. A plan must have a clear completion condition, be updated during implementation, and move to docs/archive/ when complete.

Every active plan must also contain exactly one ## Maven release changesets section. Declare - None. before publication-relevant implementation begins; afterward, replace it with one inline-code bullet for every immutable release/changes/*.json file owned by the plan. Maven Central upload rejects selected direct or dependency-propagated artifacts while their linked plan remains in this directory.