Skip to content
RS.00Research library

Eight long-form papers, from the platform councils.

Architecture deep-dives, regulatory analyses, sector-specific patterns and security runbooks — written for procurement, security and architecture teams that need more than a marketing page. Citation-ready PDFs, refreshed quarterly.

RS.LBPaper library
  • RS.01Architecture
    2026-04-08·28p·38m

    The economics of sovereign platform substrate · 2026 outlook

    Sovereign datacenter deployment carries a specific cost geometry — capital up front, marginal-cost flat, recovery ahead of horizon-3 — that breaks the SaaS-only TCO model most public-sector procurement teams use. We model the break-even surface across L.04 / L.05 / L.06 programmes in EU, GCC, and East Africa.

    AuthorsPlatform Council · FlyttGo Technologies Group
  • RS.02Regulatory
    2026-03-22·22p·30m

    eIDAS 2.0 readiness · what relying parties need before 2026

    EU Regulation 2024/1183 mandates Member-State Digital Identity Wallets in production by 2026. We translate the Architecture Reference Framework into a relying-party readiness checklist with an issuer / verifier / wallet matrix, OID4VP integration patterns, and a per-jurisdiction trust list anchoring guide.

    AuthorsIdentra Trust Council · External counsel · pseudonymised
  • RS.03Architecture
    2026-02-18·34p·46m

    Multi-objective provider routing under regulatory constraints

    Provider routing in regulated mobility marketplaces optimises cost × time × coverage simultaneously while satisfying constraints that change per jurisdiction (cabotage, hazmat, weight-class, driver hours). We document the constraint solver architecture, the heuristic warm-start strategy, and the production telemetry that gets P99 routing latency to 184 ms across EU + MENA.

    AuthorsTransify Engineering Council
  • RS.04Sector
    2026-01-30·26p·35m

    GCC + MENA public-sector deployment patterns

    GCC + MENA public-sector procurement diverges meaningfully from EU norms in three places: data residency posture, arabic-first UX expectations, and SAMA-style payment-rail orchestration. We synthesise patterns observed across 7 GCC + MENA programmes, including the regulator hand-off protocol, the in-Kingdom sovereign substrate, and the Arabic localisation surface depth required.

    AuthorsMENA Platform Group · GCC Transport Authority (anonymised)
  • RS.05Security
    2026-01-12·31p·42m

    Post-quantum migration runbook for institutional platforms

    NIST FIPS 203/204/205 finalised in 2024; NSA CNSA 2.0 requires full PQ migration by 2030 (signing) / 2035 (everything). We document the FlyttGo migration runbook: hybrid-first sequencing, per-surface algorithm map, crypto-agility gateway architecture, and the test harness covering 8 cryptographic surfaces across the platform.

    AuthorsPlatform Security Council
  • RS.06Sustainability
    2025-12-04·18p·24m

    CSRD scope-3 attribution for platform-infrastructure tenants

    EU CSRD requires scope-3 emissions tracking from software vendors starting FY2026. Most platform vendors ship a single-figure annual disclosure; that does not meet auditor expectations at scale. We document the per-tenant per-region carbon attribution model, the SCI emission factors per workload type, and the auditor-friendly export pack.

    AuthorsSustainability Council
  • RS.07Architecture
    2025-11-15·24p·32m

    Agent-driven platform architecture · MCP + audit envelope

    AI agents (Claude, ChatGPT, Cursor) are moving from observation to operation against platform APIs. We document the architecture FlyttGo built to make agent-driven operations safe: workspace-scoped tokens, the same audit envelope humans use, per-tool rate caps, and the human-in-the-loop tier on high-impact surfaces.

    AuthorsPlatform Engineering Council
  • RS.08Deployment
    2025-10-22·20p·26m

    Deployment substrate selection · DM.01 / 02 / 03 / 04 decision framework

    Buyers regularly pick the wrong deployment substrate for their programme. We document the four-substrate decision framework — managed SaaS (DM.01), customer cloud (DM.02), sovereign datacenter (DM.03), and confidential compute (DM.04, planned) — with a 9-criterion scoring matrix that surfaces the right answer in under an hour.

    AuthorsPlatform Council