You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sequencing rule: performance optimization is the final phase. Earlier phases establish soundness, contracts, CI, API vocabulary, and documentation first.
Merge protocol
Create one focused branch per issue, or one explicitly documented tightly-coupled issue cluster.
Open implementation PRs with base umbrella/issue-burndown-2026-08, not main.
Keep the umbrella branch green after every merge: cargo fmt --all -- --check and cargo test --workspace; run feature, safety, docs, or benchmark gates appropriate to the issue.
Resolve conflicts and cross-issue API decisions on the umbrella branch.
Do not merge optimization work until Phases 1–3 are green.
After the final optimization phase and cross-phase audit, open one final PR from the umbrella branch to main.
No item in this phase lands before Phases 1–3 are green. Apply the shared need-before-implementation and paired-experiment protocol; microbenchmarks alone are insufficient.
Outcome
This umbrella replaces the superseded retirement umbrella #199 and inventories every issue that was open on 2026-08-10.
origin/mainatdc0a8e03286c61a84d56446b5cc2c53295f75d76umbrella/issue-burndown-2026-08Merge protocol
umbrella/issue-burndown-2026-08, notmain.cargo fmt --all -- --checkandcargo test --workspace; run feature, safety, docs, or benchmark gates appropriate to the issue.main.Phase 0 — closed or rejected inventory
Phase 1 — soundness and boundary correctness
These block every later phase.
StridedView: Sendbound.Phase 2 — contracts, API decisions, and CI foundations
These define the execution and public contracts that later implementation must follow.
strided-perm.parallelfeature.copy_into_col_majorpolicy-aware or remove the duplicate API.ActiveBackendmigration policy.MaybeUninittracker; remains blocked until upstream exposes a sound overwrite API.Phase 3 — documentation, organization, and repository hygiene
Complete this phase before performance work so benchmarks and optimization PRs use stable rules, APIs, and CI.
# Errorssections and runnable doctests.Debugimplementations.Phase 4 — performance optimization (final phase)
No item in this phase lands before Phases 1–3 are green. Apply the shared need-before-implementation and paired-experiment protocol; microbenchmarks alone are insufficient.
reduce_axis.Dependency summary
Each retained issue has a current-state audit comment and an implementation handoff pointing to this umbrella and branch.