Current collection — 6 September 2026

Three active essays: staged paths, programme studio, and wildlife crossing. The studio is repaired; wildlife is rebuilt as a compatible component calculation. Rail simulator, incremental upgrade and transit trade-offs are retired, with explanatory pages at their existing addresses and historical sources in version control. Their best explanations are preserved in the studio and staged-path method. See the curation and preservation record.

The five original generic-gallery addresses continue to point to their corresponding dedicated-site routes, carrying query and fragment. Three now end at retirement records; old settings are not treated as input to a different model. No moved cards are reintroduced to the generic or mirrored catalogues.

Historical consolidation record

The following describes the earlier migration before the critical model review; it is retained as history, not current endorsement of six active apps. The earlier rail simulator had no genuine stage-commit controls; its original table entry below is corrected accordingly.

This dedicated foray brings six independent experiments together. Their calculation models remain separate: the outputs answer different questions.

Experiment Contribution Origin
Staged paths Generates legal construction histories and exact finite resource frontiers under a service floor, commissioning review, crew and access caps. Project-web-apps: rail-staged-codesign
Incremental upgrade Shows how platform, signalling and power requirements constrain one another, including discrete catalogues. Project-web-apps: monotone_codesign_rail_upgrade
Programme studio Compares package catalogues, four prescribed staging strategies, governance and illustrative feedback assumptions. Retained March 2026 rail studio, prepared for this site
Earlier rail simulator Explored catalogue alternatives, resource trade-offs and an approximate tier-spread timeline. Project-web-apps: monotone_codesign_rail
Simple transit trade-offs Introduces monotone subsystem relationships through a smaller model. Project-web-apps: monotone-codesign-rail-transit
Wildlife crossing Applies co-design to crossing, fencing and monitoring requirements. Project-web-apps: animal_crossing_codesign

The staged solver’s mathematical engine is unchanged by migration. Its model and verification note defines its finite exactness. The programme studio retains its distinct template and feedback model; its figures must not be pooled with the staged solver’s frontier.

The migration publishes and verifies this receiver first. It then replaces the five old public app addresses with redirects to their matching experiments, preserving URL query and fragment settings, and removes their cards from the generic Project Apps catalogue and the dynamically mirrored All Project Apps page. One entry in Forays & Side Projects provides the collection route. More Project Apps and React Project Apps contained no additional co-design example to migrate; their unrelated tools remain in place.

The older apps add site navigation and mobile layout repairs. The earlier rail simulator now keeps the selected plan visible, and the wildlife example uses the correct catalogue threshold so that a selected bridge meets the requested capacity. Other inherited calculations are retained. Preparation of the March studio repairs stage-start timing, stale selections/results, invalid-input recovery and exact objective lenses; it also labels synthetic risk and staging assumptions explicitly. These are illustrative models, with no real-world engineering or human-use validation implied.