Approved direction — 2026-09-07
Two core products: Element and Router; UI is dogfood/reference with Route Mode and Framework Mode. Router has a universal record-based core; explicit records and file-generated records converge on one table. Framework Mode defaults to file routing. Self-maintained URLPatternList is a strategic core asset derived from Justin Fagnani's implementation and informed by Luca Casonato's proposals, not an upstream-only dependency or a second URLPattern engine.
Execution
Every replacement includes deletion of the displaced owner and its obsolete callers/checkers/docs. Cleanup starts Beta.2.1; Beta.2.3 closes remaining repository/governance work. Measure reduced ownership and operational surface, not deletion quotas.
Three working days from implementation start is the target. Public beta.2.1/.2/.3 checkpoints require their own evidence; do not publish solely for ceremony. Enter 1.0.0-alpha.1 only after admission. Real-app hardening, broad benchmarks and further qualification continue in 1.0 Alpha, then evidence-gated RC/Stable. The former Beta.3 lane is retired; remaining work is preserved in the Alpha milestone.
This planning issue closes when
Train root #1155; Beta.2 umbrella #1288. Project: https://github.com/orgs/open-element/projects/3
Authority: maintainer-approved 2026-09-07 plan, ADR-0152 and docs/current/VERSION_PLAN.md (documentation PR linked on the train root). Planning is not implementation or release evidence.
Delivery
Documentation/tooling PR: #1342
Commit: 8e4132a. The planning deliverables are prepared and published for review; this issue remains open/In Progress until the PR is accepted. Product implementation issues remain Todo/open.
Project 3 contains 44 unique issues with Stage and Status populated (1 planning In Progress, 43 Todo). Four new issues (#1338-#1341) are linked into the existing issue hierarchy. Populated milestones were reconciled rather than abandoning their unfinished work.
Validation: 54 release-tool tests and 30 doc/version/release-truth tests passed; workflow, current/strategic/role-neutral docs, version anchors, release truth/state replay, changed-file format/Markdown lint and relative links passed. Retired the obsolete Alpha-topology checker/task/test instead of restoring superseded prose. Actual package/publication versions are unchanged. PR CI remains authoritative and is tracked on the PR.
Two-core-product refinement (2026-09-07)
Maintainer-approved refinement: two core products (Element and Router, including Framework Mode); UI is dogfood/reference. The existing 44-item Project and three-day Beta.2.x plan remain; #1338/#1339/#1340 now cover standalone Element delivery, private-compiler distribution, versioned artifacts and foreign CE boundaries. No additional umbrella or full UI migration is introduced. Updated documentation continues in PR #1342.
Accepted refinement — 2026-09-08 (supersedes conflicting earlier scope)
Approved 2026-09-08 scope: beta.2.1 public maintained matching fork + Router/SSG/navigation repairs + Element tooling; beta.2.2 Native/Lit first-class Framework Mode target + Document/public metadata; beta.2.3 dual-mode hardening/independent products/cleanup/admission.
Governing plan (2026-09-08)
Maintainer-approved: ADR-0152, docs/current/VERSION_PLAN.md and #1341. Execution: https://github.com/orgs/open-element/projects/3. Acceptance checkpoints replace the three-day schedule. No automatic beta.2.4. Native/Lit are formal Framework Mode targets, not already-shipped support. Existing release records/versions remain unchanged; no closure without final-SHA evidence. examples/** stays frozen.
Alpha/RC dependency correction — 2026-09-08
#1340 -> Alpha real application #1179 + qualification rounds #1234-#1242 + release hardening #1187 -> RC admission #1243 -> freeze #1178 -> soak/install/triage #1244-#1246 -> human GO #1180 -> Stable gate #37. Alpha permits evidence-driven API/architecture changes; RC freezes the contract. Preserve fourteen-day soak and separate Native/Lit qualification. Product performance, fork maintenance and independent onboarding are qualified by their actual owners.
Authority and evidence
Maintainer-approved Alpha/RC refinement, 2026-09-08: ADR-0152, docs/current/VERSION_PLAN.md, #1341 and #1155. Beta.2.x proves integrated capability; Alpha may revise architecture based on application evidence; RC freezes the admitted public contract. All qualification identifies exact artifacts/dependencies. No automatic completion, publication, provider switch or release GO. Existing quality requirements remain unless explicitly superseded here.
Accepted upstream-contribution priority — 2026-09-08
Maintainer approves sustained useful upstream contribution as Beta.2.x tool-selection priority. WTR selected for Lit/Modern Web alignment; URLPatternList follows Node upstream harness; Oxc/TS7 feasibility only in Beta.2.2 and full migration separately in Alpha. Update ADR/plan/roadmap/deletion map/Project without completing implementation tasks.
Use docs/architecture/infrastructure-reduction.md and VERSION_PLAN as scope. Prepare useful generic fixes for contribution through normal authorization; no invented bugs, cosmetic PR quota, or upstream-response release dependency. No migration is completed by this update.
Approved executable maturation — 2026-09-09
Reconcile VERSION_PLAN, ADR-0152, product model, roadmap, issue map, architecture navigation, status and bilingual /roadmap with the approved executable maturation plan. Project 3 is primary execution; Project 1 remains portfolio. Preserve historical releases, unfinished statuses and #1343 actual-review requirements. No implementation completion or publication is implied.
Scope: docs/architecture/alpha-maturation.md and VERSION_PLAN (planning PR #1342). Upstream contribution potential can justify bounded extra integration cost; no invented defects, PR quota or upstream-response release dependency. This update changes planned work, not implementation status.
Current supplemental review policy — confirmed 2026-09-09
Supersedes earlier AI-review availability merge prerequisites in this issue. Third-party AI review is supplemental and non-blocking. Report provider/API errors visibly; wrapper SUCCESS is not completed review and provider failure contributes zero independent review evidence. Required CI, fresh verifier and human review remain the merge gates. Retain #1343 (comment) as historical evidence. No provider/model switch or billing action is authorized.
Approved direction — 2026-09-07
Two core products: Element and Router; UI is dogfood/reference with Route Mode and Framework Mode. Router has a universal record-based core; explicit records and file-generated records converge on one table. Framework Mode defaults to file routing. Self-maintained URLPatternList is a strategic core asset derived from Justin Fagnani's implementation and informed by Luca Casonato's proposals, not an upstream-only dependency or a second URLPattern engine.
Execution
Every replacement includes deletion of the displaced owner and its obsolete callers/checkers/docs. Cleanup starts Beta.2.1; Beta.2.3 closes remaining repository/governance work. Measure reduced ownership and operational surface, not deletion quotas.
Three working days from implementation start is the target. Public beta.2.1/.2/.3 checkpoints require their own evidence; do not publish solely for ceremony. Enter 1.0.0-alpha.1 only after admission. Real-app hardening, broad benchmarks and further qualification continue in 1.0 Alpha, then evidence-gated RC/Stable. The former Beta.3 lane is retired; remaining work is preserved in the Alpha milestone.
This planning issue closes when
Train root #1155; Beta.2 umbrella #1288. Project: https://github.com/orgs/open-element/projects/3
Authority: maintainer-approved 2026-09-07 plan, ADR-0152 and docs/current/VERSION_PLAN.md (documentation PR linked on the train root). Planning is not implementation or release evidence.
Delivery
Documentation/tooling PR: #1342
Commit: 8e4132a. The planning deliverables are prepared and published for review; this issue remains open/In Progress until the PR is accepted. Product implementation issues remain Todo/open.
Project 3 contains 44 unique issues with Stage and Status populated (1 planning In Progress, 43 Todo). Four new issues (#1338-#1341) are linked into the existing issue hierarchy. Populated milestones were reconciled rather than abandoning their unfinished work.
Validation: 54 release-tool tests and 30 doc/version/release-truth tests passed; workflow, current/strategic/role-neutral docs, version anchors, release truth/state replay, changed-file format/Markdown lint and relative links passed. Retired the obsolete Alpha-topology checker/task/test instead of restoring superseded prose. Actual package/publication versions are unchanged. PR CI remains authoritative and is tracked on the PR.
Two-core-product refinement (2026-09-07)
Maintainer-approved refinement: two core products (Element and Router, including Framework Mode); UI is dogfood/reference. The existing 44-item Project and three-day Beta.2.x plan remain; #1338/#1339/#1340 now cover standalone Element delivery, private-compiler distribution, versioned artifacts and foreign CE boundaries. No additional umbrella or full UI migration is introduced. Updated documentation continues in PR #1342.
Accepted refinement — 2026-09-08 (supersedes conflicting earlier scope)
Approved 2026-09-08 scope: beta.2.1 public maintained matching fork + Router/SSG/navigation repairs + Element tooling; beta.2.2 Native/Lit first-class Framework Mode target + Document/public metadata; beta.2.3 dual-mode hardening/independent products/cleanup/admission.
Governing plan (2026-09-08)
Maintainer-approved: ADR-0152, docs/current/VERSION_PLAN.md and #1341. Execution: https://github.com/orgs/open-element/projects/3. Acceptance checkpoints replace the three-day schedule. No automatic beta.2.4. Native/Lit are formal Framework Mode targets, not already-shipped support. Existing release records/versions remain unchanged; no closure without final-SHA evidence. examples/** stays frozen.
Alpha/RC dependency correction — 2026-09-08
#1340 -> Alpha real application #1179 + qualification rounds #1234-#1242 + release hardening #1187 -> RC admission #1243 -> freeze #1178 -> soak/install/triage #1244-#1246 -> human GO #1180 -> Stable gate #37. Alpha permits evidence-driven API/architecture changes; RC freezes the contract. Preserve fourteen-day soak and separate Native/Lit qualification. Product performance, fork maintenance and independent onboarding are qualified by their actual owners.
Authority and evidence
Maintainer-approved Alpha/RC refinement, 2026-09-08: ADR-0152, docs/current/VERSION_PLAN.md, #1341 and #1155. Beta.2.x proves integrated capability; Alpha may revise architecture based on application evidence; RC freezes the admitted public contract. All qualification identifies exact artifacts/dependencies. No automatic completion, publication, provider switch or release GO. Existing quality requirements remain unless explicitly superseded here.
Accepted upstream-contribution priority — 2026-09-08
Maintainer approves sustained useful upstream contribution as Beta.2.x tool-selection priority. WTR selected for Lit/Modern Web alignment; URLPatternList follows Node upstream harness; Oxc/TS7 feasibility only in Beta.2.2 and full migration separately in Alpha. Update ADR/plan/roadmap/deletion map/Project without completing implementation tasks.
Use docs/architecture/infrastructure-reduction.md and VERSION_PLAN as scope. Prepare useful generic fixes for contribution through normal authorization; no invented bugs, cosmetic PR quota, or upstream-response release dependency. No migration is completed by this update.
Approved executable maturation — 2026-09-09
Reconcile VERSION_PLAN, ADR-0152, product model, roadmap, issue map, architecture navigation, status and bilingual /roadmap with the approved executable maturation plan. Project 3 is primary execution; Project 1 remains portfolio. Preserve historical releases, unfinished statuses and #1343 actual-review requirements. No implementation completion or publication is implied.
Scope: docs/architecture/alpha-maturation.md and VERSION_PLAN (planning PR #1342). Upstream contribution potential can justify bounded extra integration cost; no invented defects, PR quota or upstream-response release dependency. This update changes planned work, not implementation status.
Current supplemental review policy — confirmed 2026-09-09
Supersedes earlier AI-review availability merge prerequisites in this issue. Third-party AI review is supplemental and non-blocking. Report provider/API errors visibly; wrapper SUCCESS is not completed review and provider failure contributes zero independent review evidence. Required CI, fresh verifier and human review remain the merge gates. Retain #1343 (comment) as historical evidence. No provider/model switch or billing action is authorized.