Skip to content

Roadmap and user stories (as of 0.13) - #342

Merged
derrynknife merged 3 commits into
devfrom
docs/roadmap
Oct 16, 2026
Merged

derrynknife merged 3 commits into
devfrom
docs/roadmap

Conversation

@derrynknife

Copy link
Copy Markdown
Owner

Summary

Brings ROADMAP.md and stories/ onto dev. They were written on 4 October, as of 0.12, on the unmerged branches claude/roadmap and claude/maintenance-economics-stories. This PR updates them to 0.13 and what is merged on dev for 0.14. The two original commits are kept as they were, with one correcting commit on top, so the corrections can be reviewed on their own.

Scope, as CLAUDE.md now says (#334): RePyability works in model time, and dates and calendars belong to the application.

  • A new "Scope" section in the roadmap says so.
  • The NPV simulator's phases 2 and 3 now use model time:
    • prices and value are functions of model time;
    • outages are times on the model's timeline;
    • nothing maps model time to dates, and there are no dated outages.
  • The stories' B2 and B3 change the same way, as do MX-02, MX-10 and MX-12. A question asked in dates (a month, a financial year) is turned into model time by the application that asks it.
  • The live-NPV time-base question now points to "duty" (Degradation processes as lives and replacement on condition by level (#271); unit fixes and duty cycles #276). Mapping dates to model time is the application's job.

Statuses:

Not planned, recorded:

  • Fitting stays in SurPyval.
  • Plotting stays outside RePyability.
  • No physics of failure.
  • Calendars and dates belong to the application.
  • repyability.maintenance stays in RePyability.

Stories:

  • IDs MX-01 to MX-25 are unchanged.
  • MX-03, MX-12, MX-18 and MX-19 are now partial, each saying what exists on dev.
  • MX-04 names offset_shares=.
  • MX-06's per-train allocation shipped in 0.12.
  • No story is fully met yet, so none is marked met.

README: a "Roadmap" section links both, placed before "Related".

Type of change

  • Bug fix
  • New feature
  • Documentation
  • Refactor / tooling
  • Breaking change

Checklist

  • No code changes
  • test_docs_examples.py and test_readme_capabilities.py pass with the README change: 51 passed

🤖 Generated with Claude Code

https://claude.ai/code/session_019Km2eWBiPJ5JNkme3vRg4B

claude and others added 3 commits October 16, 2026 20:28
Adds stories/, a home for the questions RePyability should be able to
answer, kept apart from issues (units of work). The first file records
MX-01 to MX-17: the net present value of maintenance plans, designs,
crews, spares and outage timing, each with a persona, the question in the
user's words, a concrete setting from the docs or an existing study,
acceptance criteria with independent checks, the building blocks it
needs, and its status.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SaNShfhc2gs7XtWma9z2sU
…MX-25

ROADMAP.md, in SurPyval's format, holds the larger ideas and their
designs: the NPV simulator for maintenance plans (designed, phased by the
stories' building blocks), live NPV that keeps a plan's value current as
readings, work orders, failures, refits and prices arrive (designed:
an event-sourced plant, incremental re-valuation, attribution,
re-optimisation, and who does what across SurPyval, RePyability and
Reliafy), decision analytics on the NPV, the simpler-implementations
issues (#204-#209), hardening practice (review rounds, scenario cards,

The maintenance-economics stories are brought up to 0.12 (discounted
total costs, train-wise allocation, staggered tests, pooled spares) and
gain building blocks B8-B10 and stories MX-18 to MX-25 for live
valuation. The README points to both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SaNShfhc2gs7XtWma9z2sU
The roadmap and stories were written on 4 October, as of 0.12. Brought up
to 0.13 and what is merged on dev for 0.14:

- Scope, as CLAUDE.md now says: RePyability works in model time, and
  dates and calendars are the application's. The NPV simulator's phases 2
  and 3 are restated so: prices as functions of model time, outages at
  given times on the model's timeline, no calendar mapping model time to
  dates; the stories' B2 and B3, and MX-02, MX-10 and MX-12, likewise.
- Done: the simpler implementations (#204-#209, 0.13) and the hardening
  items #239, #167 and #216 (0.13). NodeState has a virtual age (#269),
  so starting from one is no longer listed as missing, and the
  degradation lives (#271) and duty cycles (#276) are what exists.
- The maintenance module (#319) gets a short section: one use case at a
  time, what is built, and the calendar side left to the application.
- Not planned, recorded: fitting stays in SurPyval, plotting stays
  outside, no physics of failure, calendars and dates, and moving
  repyability.maintenance out.
- Story statuses: MX-03, MX-12, MX-18 and MX-19 partial with what is on
  dev; MX-04 names offset_shares=; MX-06's per-train allocation is 0.12's.
  None is met yet. Story IDs are unchanged.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019Km2eWBiPJ5JNkme3vRg4B
@derrynknife
derrynknife merged commit 25d3fc5 into dev Oct 16, 2026
derrynknife added a commit that referenced this pull request Oct 16, 2026
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016Ng6hwUY8zznhm1jRfZJqZ
@derrynknife
derrynknife deleted the docs/roadmap branch October 16, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants