Skip to content

Commit f95447e

Browse files
TheHiddenObserverTheHiddenObserver
authored
Merge pull request #89 from TheHiddenObserver/agent/rebuild-roadmap-v0.2.4
docs: rebuild development roadmap for 0.2.4
2 parents 0aeeb95 + d0ee8f8 commit f95447e

5 files changed

Lines changed: 580 additions & 174 deletions

File tree

‎dev/plans/ISSUES.md‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# statgpu Roadmap Issue Index
2+
3+
> Last synchronized: **2026-08-06**
4+
> Roadmap PR: **#89**
5+
> Baseline release: **0.2.4**
6+
7+
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.
8+
9+
## Active issues
10+
11+
| Priority | Issue | Work package | Dependencies |
12+
|---|---:|---|---|
13+
| P0 | #90 | Synchronize benchmark dashboard PR #76 with the 0.2.4 `master` baseline | PR #89 planning reference |
14+
| P1 | #91 | Add a canonical cross-validation benchmark source and dashboard coverage | #90 |
15+
| P1 | #92 | Complete dashboard production QA, cross-browser smoke, accessibility, and documentation integration | #90; preferably #91 before final QA |
16+
| P1 | #93 | Complete Panel Tier-1 shared framework, diagnostics, fit statistics, and covariance support | Independent of dashboard lane |
17+
| P2 | #94 | Implement Kaplan-Meier and Nelson-Aalen estimators | Independent; shares survival result design with future work |
18+
| P2 | #95 | Implement initial Weibull, log-normal, and log-logistic AFT family | May proceed independently; sequence after #94 unless resources justify parallel work |
19+
| P2 | #96 | Design and implement unpenalized multinomial logistic regression Phase 1 | Non-tunable base contract; prerequisite for #98 |
20+
| P2 | #98 | Implement the complete penalized multinomial suite with direct-fit/CV closure | #96; sparse input remains blocked on #97 |
21+
| 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 |
22+
23+
## Recommended sequencing
24+
25+
### Product and benchmark lane
26+
27+
```text
28+
#90 → #91 → #92 → propose PR #76 for master integration
29+
```
30+
31+
Do not add new benchmark families during #90. Do not perform final dashboard QA on a stale or unsynchronized branch.
32+
33+
### Statistical workflow lane
34+
35+
```text
36+
#93
37+
#94 → #95
38+
#96 → #98
39+
#97 → future sparse estimator issues
40+
```
41+
42+
#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.
43+
44+
These issues may proceed in parallel only when they do not compete for the same backend, inference, solver, or review surface.
45+
46+
## Issue maintenance rules
47+
48+
- Keep one primary issue per statistical or product contract.
49+
- Split an issue only when doing so does not produce a partially advertised capability or violate direct-fit/CV closure.
50+
- Add explicit links when an issue blocks or is blocked by another issue.
51+
- Update `ROADMAP.md`, `TO_DO.md`, and this file when priorities change.
52+
- Roadmap and issue scope may narrow work but may not weaken `.claude` or `dev/AGENTS.md` hard gates.
53+
- Close issues only with merged implementation evidence, required CI, external alignment where applicable, physical-GPU validation, and synchronized documentation.
54+
- Do not close an issue solely because a class, function, parser, or frontend control exists.

‎dev/plans/README.md‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# statgpu Development Plans
2+
3+
This directory contains the project roadmap, execution backlog, and historical design notes.
4+
5+
## Authority by responsibility
6+
7+
There is no single global precedence order across documents with different responsibilities. Use the authority that matches the question being answered.
8+
9+
### Hard development and completion gates
10+
11+
1. Applicable `.claude/workflows/` and `.claude/skills/` protocol.
12+
2. `dev/AGENTS.md`.
13+
3. The mandatory checklist in [`TO_DO.md`](TO_DO.md), which summarizes but does not weaken the two sources above.
14+
15+
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`.
16+
17+
### Current public capability
18+
19+
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.
20+
21+
### Current priority and sequencing
22+
23+
Use [`ROADMAP.md`](ROADMAP.md). It selects what should be worked on next; it does not redefine development-completion requirements.
24+
25+
### Executable scope and dependencies
26+
27+
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.
28+
29+
### Research and historical context
30+
31+
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.
32+
33+
## Verified baseline
34+
35+
- Last verified release: **statgpu 0.2.4**
36+
- Last verified commit: `0aeeb95b60e3e274053b8f1b6427ae50c8eec015`
37+
- Verification date: **2026-08-06**
38+
- Release workflow, PyPI wheel/sdist publication, clean production installation, and representative model smoke tests passed.
39+
40+
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.
41+
42+
## Document status
43+
44+
| Document | Status | How to use it |
45+
|---|---|---|
46+
| `ROADMAP.md` | Canonical priority source | Current priorities, sequencing, dependencies, and roadmap-level definition of done. |
47+
| `ISSUES.md` | Canonical navigation | Maps roadmap work packages to executable GitHub issues and dependency order. GitHub issue state remains authoritative for execution. |
48+
| `TO_DO.md` | Mandatory summary checklist | Compact hard-gate checklist plus active queue; subordinate to `.claude` and `dev/AGENTS.md`, not a weaker alternative. |
49+
| `panel_framework_proposal.md` | Active design reference | Shared panel architecture and Tier-1 diagnostics proposal. Validate details against current code before implementation. |
50+
| `plan_survival.md` | Active module reference | Cox Phase 1 status and Survival Phase 2+ scope; last materially updated 2026-07-12. |
51+
| `cran_r_package_mapping.md` | Comparative reference | Method-family gap map. Some individual rows may lag current implementation. |
52+
| `plan_anova.md` | Historical research plan | Its early implementation-status header is stale; use implemented-methods/model docs for current ANOVA support. |
53+
| `plan_covariance.md` | Historical research plan | Its early implementation-status header is stale; current covariance estimators are documented elsewhere. |
54+
| `plan_krr.md` | Historical research plan | Nystroem, KernelPCA, and chi-square kernel status in the old checklist is stale. |
55+
| `plan_spline.md` | Historical research plan | SplineTransformer, cyclic, and thin-plate status in the old checklist is stale. |
56+
| `plan_unsupervised.md` | Historical phase record | Useful for benchmark and algorithm history, not the current priority queue. |
57+
| `plan.md` | Historical delta | Superseded by `ROADMAP.md`. |
58+
| `archive/` | Archive | Completed or superseded planning material. |
59+
60+
## Planning rules
61+
62+
A roadmap item becomes executable only after it has a GitHub issue that defines:
63+
64+
- user or developer problem;
65+
- scope and explicit non-goals;
66+
- public API and failure behavior;
67+
- NumPy, CuPy, and Torch backend contract;
68+
- direct-fit/CV closure for every tunable capability;
69+
- inference and formula implications where applicable;
70+
- external baselines and normalization/alignment settings;
71+
- unit, regression, compatibility, and physical-GPU validation;
72+
- documentation and benchmark deliverables;
73+
- dependencies and completion criteria.
74+
75+
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.

0 commit comments

Comments
 (0)