Skip to content

docs: rebuild development roadmap for 0.2.4 #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TheHiddenObserver merged 1 commit into from
Aug 6, 2026
Merged

docs: rebuild development roadmap for 0.2.4 #89

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 54 additions & 0 deletions dev/plans/ISSUES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
# statgpu Roadmap Issue Index

> Last synchronized: **2026-08-06**
> Roadmap PR: **#89**
> Baseline release: **0.2.4**

This file maps the canonical roadmap to executable GitHub issues. GitHub issue state is authoritative for execution; repository hard development gates remain authoritative for completion.

## Active issues

| Priority | Issue | Work package | Dependencies |
|---|---:|---|---|
| P0 | #90 | Synchronize benchmark dashboard PR #76 with the 0.2.4 `master` baseline | PR #89 planning reference |
| P1 | #91 | Add a canonical cross-validation benchmark source and dashboard coverage | #90 |
| P1 | #92 | Complete dashboard production QA, cross-browser smoke, accessibility, and documentation integration | #90; preferably #91 before final QA |
| P1 | #93 | Complete Panel Tier-1 shared framework, diagnostics, fit statistics, and covariance support | Independent of dashboard lane |
| P2 | #94 | Implement Kaplan-Meier and Nelson-Aalen estimators | Independent; shares survival result design with future work |
| P2 | #95 | Implement initial Weibull, log-normal, and log-logistic AFT family | May proceed independently; sequence after #94 unless resources justify parallel work |
| P2 | #96 | Design and implement unpenalized multinomial logistic regression Phase 1 | Non-tunable base contract; prerequisite for #98 |
| P2 | #98 | Implement the complete penalized multinomial suite with direct-fit/CV closure | #96; sparse input remains blocked on #97 |
| P2 | #97 | Define the shared sparse-array/backend contract with no silent densification | Prerequisite for HDFE, mixed models, sparse multinomial follow-up, and broad sparse estimator support |

## Recommended sequencing

### Product and benchmark lane

```text
#90 → #91 → #92 → propose PR #76 for master integration
```

Do not add new benchmark families during #90. Do not perform final dashboard QA on a stale or unsynchronized branch.

### Statistical workflow lane

```text
#93
#94 → #95
#96 → #98
#97 → future sparse estimator issues
```

#96 is strictly unpenalized and non-tunable. #98 owns the complete penalized multinomial matrix and may not close after only L2 or only direct-fit support. Every tunable penalty exposed by #98 must ship with CV selection and final refit in the same work package.

These issues may proceed in parallel only when they do not compete for the same backend, inference, solver, or review surface.

## Issue maintenance rules

- Keep one primary issue per statistical or product contract.
- Split an issue only when doing so does not produce a partially advertised capability or violate direct-fit/CV closure.
- Add explicit links when an issue blocks or is blocked by another issue.
- Update `ROADMAP.md`, `TO_DO.md`, and this file when priorities change.
- Roadmap and issue scope may narrow work but may not weaken `.claude` or `dev/AGENTS.md` hard gates.
- Close issues only with merged implementation evidence, required CI, external alignment where applicable, physical-GPU validation, and synchronized documentation.
- Do not close an issue solely because a class, function, parser, or frontend control exists.
75 changes: 75 additions & 0 deletions dev/plans/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
# statgpu Development Plans

This directory contains the project roadmap, execution backlog, and historical design notes.

## Authority by responsibility

There is no single global precedence order across documents with different responsibilities. Use the authority that matches the question being answered.

### Hard development and completion gates

1. Applicable `.claude/workflows/` and `.claude/skills/` protocol.
2. `dev/AGENTS.md`.
3. The mandatory checklist in [`TO_DO.md`](TO_DO.md), which summarizes but does not weaken the two sources above.

Roadmap priorities, issue scope, and module plans may narrow a task, but they may not weaken or override these hard gates. Any approved exception must follow the explicit approval and deferral contract in the applicable workflow and `dev/AGENTS.md`.

### Current public capability

Use the validated implementation and tests together with `docs/en/guides/implemented-methods.md` and the linked maintained model pages. When a capability claim conflicts with validated behavior, correct the stale documentation rather than treating the claim as implementation evidence.

### Current priority and sequencing

Use [`ROADMAP.md`](ROADMAP.md). It selects what should be worked on next; it does not redefine development-completion requirements.

### Executable scope and dependencies

Use open GitHub issues and active pull requests, summarized in [`ISSUES.md`](ISSUES.md). Issues may split or narrow roadmap packages, but may not declare work complete below the repository hard gates.

### Research and historical context

Module plans in this directory provide design, literature, and historical context. Their checklists are not a reliable current capability or priority inventory unless the document states a recent verification release and commit.

## Verified baseline

- Last verified release: **statgpu 0.2.4**
- Last verified commit: `0aeeb95b60e3e274053b8f1b6427ae50c8eec015`
- Verification date: **2026-08-06**
- Release workflow, PyPI wheel/sdist publication, clean production installation, and representative model smoke tests passed.

The release baseline does not imply that every historical plan item is complete. It establishes the code and documentation snapshot from which future work must branch.

## Document status

| Document | Status | How to use it |
|---|---|---|
| `ROADMAP.md` | Canonical priority source | Current priorities, sequencing, dependencies, and roadmap-level definition of done. |
| `ISSUES.md` | Canonical navigation | Maps roadmap work packages to executable GitHub issues and dependency order. GitHub issue state remains authoritative for execution. |
| `TO_DO.md` | Mandatory summary checklist | Compact hard-gate checklist plus active queue; subordinate to `.claude` and `dev/AGENTS.md`, not a weaker alternative. |
| `panel_framework_proposal.md` | Active design reference | Shared panel architecture and Tier-1 diagnostics proposal. Validate details against current code before implementation. |
| `plan_survival.md` | Active module reference | Cox Phase 1 status and Survival Phase 2+ scope; last materially updated 2026-07-12. |
| `cran_r_package_mapping.md` | Comparative reference | Method-family gap map. Some individual rows may lag current implementation. |
| `plan_anova.md` | Historical research plan | Its early implementation-status header is stale; use implemented-methods/model docs for current ANOVA support. |
| `plan_covariance.md` | Historical research plan | Its early implementation-status header is stale; current covariance estimators are documented elsewhere. |
| `plan_krr.md` | Historical research plan | Nystroem, KernelPCA, and chi-square kernel status in the old checklist is stale. |
| `plan_spline.md` | Historical research plan | SplineTransformer, cyclic, and thin-plate status in the old checklist is stale. |
| `plan_unsupervised.md` | Historical phase record | Useful for benchmark and algorithm history, not the current priority queue. |
| `plan.md` | Historical delta | Superseded by `ROADMAP.md`. |
| `archive/` | Archive | Completed or superseded planning material. |

## Planning rules

A roadmap item becomes executable only after it has a GitHub issue that defines:

- user or developer problem;
- scope and explicit non-goals;
- public API and failure behavior;
- NumPy, CuPy, and Torch backend contract;
- direct-fit/CV closure for every tunable capability;
- inference and formula implications where applicable;
- external baselines and normalization/alignment settings;
- unit, regression, compatibility, and physical-GPU validation;
- documentation and benchmark deliverables;
- dependencies and completion criteria.

Do not mark a module complete using only an implementation count or a passing CPU smoke test. Completion is contract-based, evidence-based, and subject to the hard workflow gates.
Loading
Loading