Repository navigation
Roadmap and user stories (as of 0.13) - #342
Merged
Merged
Conversation
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
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brings
ROADMAP.mdandstories/ontodev. They were written on 4 October, as of 0.12, on the unmerged branchesclaude/roadmapandclaude/maintenance-economics-stories. This PR updates them to 0.13 and what is merged ondevfor 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.mdnow says (#334): RePyability works in model time, and dates and calendars belong to the application."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:
NodeStatehasvirtual_age(Fitted repairable models (GeneralizedRenewal, CrowAMSAA, Duane, HPP) as RepairableRBD components #269), so it is no longer listed as missing. Fitted repairable-unit models (Fitted repairable models (GeneralizedRenewal, CrowAMSAA, Duane, HPP) as RepairableRBD components #269) and degradation lives (Replacement on condition driven by a fitted degradation model's level #271) are added to "What exists".Not planned, recorded:
repyability.maintenancestays in RePyability.Stories:
dev.offset_shares=.README: a "Roadmap" section links both, placed before "Related".
Type of change
Checklist
test_docs_examples.pyandtest_readme_capabilities.pypass with the README change: 51 passed🤖 Generated with Claude Code
https://claude.ai/code/session_019Km2eWBiPJ5JNkme3vRg4B