§01 · Delivery sequence

Five waves

Each wave ends at an acceptance gate before the next begins. Scientific engines ship only when their calibration fixtures pass; nothing else is claimed as calculated.

  1. Wave 1

    In progress

    Brand + scientific design system + public flagship

    • Design tokens, typography, evidence-status badge system
    • Public flagship: home, methodology, pathways, case study, roadmap
    • Auth entry point, workspace shell

  2. Wave 2

    Planned

    Workspace, forms, contextual data and harmonisation

    • Project workspace, versioned scenarios, audit trail
    • Assessment mode: new plant vs existing plant + learning
    • Live-data gateway (FX, inflation, electricity, grid CI, water, routing)
    • EUR 2024 → project year/currency harmonisation engine

  3. Wave 3

    Planned

    Scientific pathway engines: production, storage, transport

    • Versioned equation registry
    • PEM / AEL / SOEC production with degradation & stack replacement
    • Preliminary production-only decision gate
    • Storage (tank, lined rock, salt cavern) with feasibility gating
    • Transport (road, pipeline, rail); shipping benchmark-only
    • Integrated mass, energy, loss and cost balance

  4. Wave 4

    Planned

    Finance, impacts, uncertainty, learning, decision intelligence

    • Full financial cash flow (NPV, IRR, payback, levelized margin)
    • Environmental + social screening with evidence tiers
    • Monte Carlo uncertainty, tornado sensitivity, propagation
    • Existing-plant + learning mode; scale/learning decomposition
    • New indicators: DHVM, Evidence Coverage Score, Confidence-weighted LCOH
    • Multi-criteria decision + scenario comparison dashboard

  5. Wave 5

    Planned

    Reports, open API, governance, validation, launch

    • Technical report generator (PDF, DOCX, CSV, JSON)
    • Open API /v1/{production,storage,transport,impacts,finance,scenarios,learning}
    • Admin console: equation registry, data catalogue, changelog
    • Reference regression fixture must pass on every deploy
    • Feedback + service-rating; trademark clearance; launch