[Roadmap]

PYNE forward plan — completed consolidation items, remaining performance, DX, and integration work.

Roadmap

Abstract

The roadmap is a living prioritization document, not a contract. Source: docs/ROADMAP.md (updated 2026-07-13 consolidation) plus subsequent surface work. Many historically “remaining” items — Jupyter, linter, data providers, strategy events, pine-worker skeleton, deep strategy runtime — are done. What remains clusters into performance, packaging polish, and ecosystem integration.

Conceptual model

Interface surface

Status snapshot

ComponentStatus
Parser ANTLR4✅
Evaluator✅ incl. var/varip / reassign
Builtins / TA / collections✅ broad
Strategy events + parity✅
pine-worker (TS + converter)✅ colocated tool (port ongoing)
Drawing/input/request✅ (plots registry; data mock/feed)
Linter / Jupyter / data providers✅
LSP advanced features✅ core set
Numba compile path✅ MVP
Full TV platform identity⚙️ out of scope

Completed themes (do not re-plan as greenfield)

  • Error message / typing hygiene
  • %%pinescript Jupyter magic + sample data helpers
  • pynescript lint
  • Yahoo / AlphaVantage / CCXT + realtime datafeed wiring
  • StrategyEvent emission + parity fixtures
  • pine-worker extra tool + Python→TS converter

Remaining high-value work

Phase A — Performance

  • JIT / deeper numba coverage beyond MVP paths
  • Vectorized array hot loops
  • Caching for repeated calculations

Phase B — Developer experience

  • Deeper debugging / profiling tools
  • Docs: tutorials, interactive examples (this Mintlify tree is part of that)
  • Editor client polish beyond VS Code

Phase C — Integration

  • Hardened REST API productization (auth, SLOs)
  • Webhook alerts beyond stubs
  • Cloud deploy recipes (see DevOps)

Phase D — Longer horizon

  • Pine v5 ↔ v6 converter maturity (scripts/convert_pine_version.py started)
  • Automatic refactor / optimization suggestions
  • Parallel / distributed evaluation experiments

Priority recommendation (from source)

HorizonFocus
ShortAPI server productization, LSP/editor depth
MediumPerformance (JIT, cache, vectorize), advanced stats/ML wrappers
LongConverters, parallel execution

Internals

PathRole
docs/ROADMAP.mdCanonical roadmap prose
docs/PROGRESS_REPORT.mdHistorical completion narrative
docs/COMPILER_PLAN.mdCompile/numba plan
.opencode/plans/Engineering plans (strategy events, consolidation)
pine-worker/TS port track

Invariants & edge cases

  1. Roadmap dates lag code — always diff against missing_features.md and tests.
  2. Sister repos (pyne-worker, hoox-setup, pine-worker packaging) may absorb “integration” items.
  3. AXIS is a separate product tree (docs/axis) — chart UX roadmap is not PYNE-core.
  4. Avoid reintroducing deleted backups (builder.py.bak, etc.) as “plan items.”

Worked examples

Track a roadmap item with a test

# pick a gap, write failing test first, implement, update missing_features.md
pytest tests/test_v6_features.py -k footprint -v

pine-worker maturity gate

cd pine-worker && bun test && bun run typecheck
# future: bun run parity once harness lands

Failure modes

Anti-patternWhy it hurts
Planning features already ✅Duplicated work
Roadmap without testsUnverifiable “done”
Ignoring by-design limitsInfinite platform chase

See also