OpenSourceRail v0.2.0 - development baseline

v0.2.0 Release Pack

This is the release pack for the OpenSourceRail v0.2 development
baseline. It is intended for a GitHub release, citation, funder review,
and professional sharing. It is not a safety approval.

Release Title

OpenSourceRail v0.2.0 - development baseline

Recommended GitHub Description

Open-source urban rail design, simulation, operations, QA, maintenance,
and certification-evidence stack for locally manufactured light metro
systems.

Recommended Topics

rail
railway
urban-rail
public-transport
transit
rust
simulation
infrastructure
open-hardware
formal-methods
safety-case
asset-management
maintenance
sqlite
cad
operations

Release Assets

Attach or link these assets:

Asset	Path
Reader PDF	../../opensource-rail-docs-book.pdf
Introduction brochure	../brochures/open-source-rail-introduction.pdf
Samawah case	../../designs/west-asia/Iraq/Samawah/README.md
Simulator instructions	../../README.md#quick-start
Operations portal instructions	../../README.md#operations-portal
Acceptance evidence report	../operations-portal/acceptance-evidence-report.md
Evidence matrix CSV	../operations-portal/data/samawah-acceptance-evidence-matrix.csv
Release gaps	../certification/release-gap-register.md
Changelog	../../CHANGELOG.md

Copy-Paste Release Notes

OpenSourceRail v0.2.0 is a development baseline for an open urban-rail
stack: simulator, generated city designs, local-manufacture rolling-stock
package, hardware host classes, operations portal, QA/maintenance/
manufacturing schedules, and certification evidence scaffolding.

Highlights:

- Samawah reference case: 58.4 km, 31 stations, 86+10 trainsets, energy
  feasibility check, capacity model, and acceptance evidence matrix.
- SQLite-backed Ops Core portal for asset registers, work orders,
  manufacturing rows, QA gates, maintenance schedules, defects/NCR, and
  audit records.
- Reader-edition PDF and introduction brochure for professional review.
- Architecture pages now state the adoption wedge, deployment roles,
  liability boundary, and SIL-target-only status clearly.

Not certified:

This release is not a railway safety approval. Independent safety
assessment, residual-risk acceptance, pilot hardware evidence,
rolling-stock production release, field validation, station charging
studies, operations validation, insurance, and national authority
authorization remain deployment gates.

Publish Checklist

1. Ensure the working tree is clean except intended release changes.

2. Run:

   python3 scripts/repo-health.py --quiet
   PYTHONPATH=design-py/src pytest -q design-py/tests/test_rfc_drift.py
   python3 scripts/generate-doc-index.py
   python3 scripts/build-doc-book.py

3. Create the annotated tag:

   git tag -a v0.2.0 -m "OpenSourceRail v0.2.0 development baseline"
   git push origin v0.2.0

4. Publish the GitHub release:

   gh release create v0.2.0 \
     --repo modernecotech/OpenSourceRail \
     --title "OpenSourceRail v0.2.0 - development baseline" \
     --notes-file docs/releases/v0.2.md \
     opensource-rail-docs-book.pdf \
     docs/brochures/open-source-rail-introduction.pdf \
     docs/operations-portal/data/samawah-acceptance-evidence-matrix.csv

5. Apply repository metadata:

   gh repo edit modernecotech/OpenSourceRail \
     --description "Open-source urban rail design, simulation, operations, QA, maintenance, and certification-evidence stack for locally manufactured light metro systems." \
     --homepage "https://github.com/modernecotech/OpenSourceRail#readme" \
     --add-topic rail \
     --add-topic railway \
     --add-topic urban-rail \
     --add-topic public-transport \
     --add-topic transit \
     --add-topic rust \
     --add-topic simulation \
     --add-topic infrastructure \
     --add-topic open-hardware \
     --add-topic formal-methods \
     --add-topic safety-case \
     --add-topic asset-management \
     --add-topic maintenance \
     --add-topic sqlite \
     --add-topic cad \
     --add-topic operations

Known Limits To Keep In The Release

• No independent safety-assessor report yet.
• No national authority approval.
• Hardware host-class release gates remain open.
• Rolling-stock production release gates remain open.
• Samawah is a generated planning-grade reference case, not a surveyed
  alignment.
• gh must be authenticated before the release and metadata commands can
  run.