This source-evidence page is currently authored and reviewed in English.

Organisational transformation demonstrator

TransformationOS

A configurable transformation-governance demonstration platform

A configurable transformation-governance demonstration with simulated company data, workflow modules, connector boundaries, retrieval, metrics, approvals and model routing. Its strongest evidence is a broad tracked demo surface—not an enterprise deployment, transformation result or calibrated decision model.

查看源代码记录项目组合图

业务 ↔ 技术桥梁 · Organisational transformation demonstrator

Make organisational transformation decisions traceable to product and technical reality.

Connects portfolio intent, product operating models, Agile@Scale, delivery evidence, and governance decisions.

这是对项目组合与源代码的解读，并非客户、部署、认证或成果声明。

  1. 01

    业务压力

    Make/Buy, commonalisation, portfolio, funding, delivery, and operating-model decisions live in separate functions and dashboards.

  2. 02

    产品决策

    Represent decision rights, assumptions, approval states, evidence, cadence, and handover across the transformation portfolio.

  3. 03

    技术记录

    Tenant configuration, workflow modules, connector boundaries, retrieval, DORA and flow metrics, scenario records, proposal-first writes, approvals, and audit state.

  4. 04

    证据回流

    Delivery friction, architecture duplication, supplier constraints, flow data, and field outcomes can return to investment, organisation, and portfolio choices.

源码证据

源码实际能够证明什么

A configurable transformation-governance demonstration with simulated company data, workflow modules, connector boundaries, retrieval, metrics, approvals and model routing. Its strongest evidence is a broad tracked demo surface—not an enterprise deployment, transformation result or calibrated decision model.

详细技术快照以英文维护。

成熟度
Demonstration platform
证据审查
源码快照截至

产品与架构决策

  • Drive organisation, domain, KPI, connector, and theme variation through tenant configuration.
  • Gate write actions behind proposal, approval, execution, and audit states.
  • Route model requests by confidentiality while keeping connector and retrieval boundaries explicit.

可核验的证据

  • Four fictional demo-company datasets spanning automotive, finance, health, and industrial logistics.
  • The tracked React frontend passed four test files and eleven tests and produced an 880-module Vite build in the review environment.
  • FastAPI, connector, retrieval, metric, workflow, proposal/approval/audit and tenant-configuration source.

声明边界

  • Demo metrics, economics, scores, statuses and residual named-company fixtures are simulated and must not be read as customer evidence.
  • Connector names do not establish a configured, authorised or live customer path; the reviewed backend suite did not collect because its environment lacked pypdf.
  • No transformation result, enterprise deployment, calibrated recommendation, security certification or model-residency outcome is asserted.

代码仓库证据不等同于客户、部署、认证或成果证据。

Architecture

One deployment configuration. Eleven inspectable demo modules.

Three represented layers: deployment configuration, transformation-governance workflows, and model-assisted decision support. They expose assumptions and approval paths; they do not prove an enterprise outcome.

仅为源代码图：一层可能代表已实现代码、适配器边界或文档设计，并不证明已配置生产服务。

  1. 01

    Layer 1 — Tenant Configuration

    A tenant.json controls branding, theme, enabled modules, portfolio and geography fields for a configured demo. A real deployment still requires identity, data, connector, isolation, migration and security engineering.

  2. 02

    Layer 2 — 11 Transformation Modules

    Make/Buy, commonalisation, portfolio, vendor, simulation, scaled-delivery, FinOps, obsolescence, OKR, M&A and executive-review surfaces share one configured demonstration model.

  3. 03

    Layer 3 — AI Decision Engine

    Model-assisted analysis can use configured catalogue, vendor and decision records to draft comparisons. Retrieved text and generated reasoning remain evidence inputs for a named human decision owner.

The Problem

The Problem

Why enterprise transformation stalls

  1. Make/Buy Paralysis

    Build vs. buy decisions are made in spreadsheets with no data. Each division decides independently — duplicating vendor contracts, custom developments, and integration costs across the enterprise.

  2. Solution Sprawl

    The same business problem solved five different ways across entities. No commonalization strategy, no module reuse tracking, no golden-path architecture — ballooning costs and diverging technology stacks.

  3. Fragmented Tooling

    Transformation data lives in Jira, Confluence, GitHub, and Azure DevOps — disconnected silos that make it impossible to see the full picture across ARTs, entities, and value streams.

  4. No Cross-Portfolio Visibility

    Leaders lack a unified view across entities and programmes. DORA metrics, portfolio health, vendor performance, and transformation maturity exist in separate dashboards with no correlation.

  5. Manual Coaching

    Transformation teams spend time collecting health, planning, and flow data across tools. A model-assisted workflow may reduce preparation effort, but the repository does not establish an outcome.

  6. Generic Platforms

    Generic configuration can hide the differences between product boundaries, domains, decision rights, KPIs, suppliers and evidence maturity. The demo explores how an explicit deployment configuration could make those choices inspectable.

Capabilities

Core Capabilities

Eleven represented transformation-governance modules

仅为源代码范围：条目可能描述代码、已记录适配器或已配置工作流，并不表示生产服务正在运行。

  1. 01

    Make/Buy Decision Engine

    Scenario-based build, buy or rent comparison with EtO→CtO, TCO and prioritisation fields. Demo calculations are assumption-driven decision support, not validated investment outcomes.

  2. 02

    Commonalization Intelligence

    Represents module-reuse scoring, cross-division comparison and golden-path adoption fields. Any saving is a scenario output whose inputs, alternatives and attribution require accountable review.

  3. 03

    Supplier & Vendor Intelligence

    Represents vendor delivery, timing, risk and overlap fields per product grouping and category. The included records are fictional inputs for reviewing a rationalisation workflow.

  4. 04

    Agent Gateway

    The gateway source represents OIDC integration points, role checks, policy-driven model routing, a tool allowlist, approval-gated writes, and audit records. Operational assurance depends on deployment.

  5. 05

    Knowledge & RAG

    Ingest PDF, HTML, and Markdown into a chunked retrieval system with metadata filters — domain, confidentiality, version. Q&A with citations including doc ID, snippet, and page reference.

  6. 06

    Digital Twin & Simulation

    Model your delivery organisation (ARTs, platforms, entities, integration layers) and simulate restructuring, commonalization, platform convergence, and CI/CD automation scenarios with flow and dependency risk propagation.

  7. 07

    Portfolio Intelligence

    Represents cross-entity value-stream indicators, EtO versus CtO funding scenarios, assumption-based economics, risk fields and CAPEX/OPEX views. Scores are demo calculations, not objective portfolio health or realised ROI.

  8. 08

    AI Strategy & Governance

    Strategic vision canvas, RACI matrix, governance committees, ethics dashboard (GDPR, EU AI Act readiness), and AI-specific KPIs — adoption, accuracy, incidents, business value.

  9. 09

    Workflow Wizards

    Health-check, planning, bottleneck, and commissioning workflows consume configured connector data or fictional demo data. No live customer connector is implied.

  10. 10

    Coaching & Acculturation

    Represents a coaching journal, pattern library, scaled-delivery facilitation views, team signals and training records. Maturity and readiness scores are illustrative inputs, not certification or evidence that change succeeded.

  11. 11

    Document Generator

    Strategic deliverable templates support preview and export workflows. Their content remains a draft for stakeholder and domain-owner review.

11 transformation modules

From Make/Buy to M&A — one tenant, one decision plane

The demonstration connects eleven workflow modules through one configuration, vendor inventory, decision log and model-routing boundary. Below is the behaviour represented in source, not a claim of deployed enterprise integration.

仅为仓库表面：可用性、完整性、性能与运营适用性需要另行验证。

MOD 1

Make/Buy Decision Intelligence

01

Structured decision support for build, buy or rent with scenario costs, vendor-fit fields and capability adjacency. The workflow records rationale and assumptions for later review.

MOD 2

Solution Commonalization

02

Represents cross-division duplicate-solution comparison and merge-versus-keep scenarios. Any ROI value is an assumption-based model output, not realised savings.

MOD 3

Portfolio Rationalization

03

Represents TIME-style application classification and strategic-fit fields with draft retire, replace, retain or rebuild recommendations. ServiceNow and Apptio are adapter boundaries, not verified live integrations.

MOD 4

Vendor Governance

04

Represents vendor inventory, assumed spend, service-level, risk and renewal fields, plus draft negotiation-brief workflows over fictional demo records.

MOD 5

Digital Twin Simulation

05

Compares declared process, organisation and platform scenarios before a governance decision. Outputs are modelled alternatives and narratives, not predictions of transformation impact.

MOD 6

Agile@Scale Coaching

06

Represents SAFe-, LeSS- and team-topology-related facilitation views with context and maturity fields. It does not certify framework adoption or determine which operating model is effective.

MOD 7

FinOps Dashboard

07

Represents cloud-cost attribution, anomaly and FinOps scorecard fields over demo inputs. Findings require connected billing sources and finance review before use.

MOD 8

IT Obsolescence Tracking

08

Represents end-of-life and support-date records for inventoried components, with adapter points for advisories and draft migration planning. Coverage depends on configured sources.

MOD 9

OKR Cascade

09

Drafts and compares strategic objectives, cascades and check-in signals. Alignment flags remain prompts for product and leadership review.

MOD 10

M&A Integration Playbooks

10

Represents sector-oriented integration checklists, milestone tracking, assumption-based synergy scenarios and governance-cadence templates.

MOD 11

Executive Dashboards

11

Role-oriented dashboards assemble module and demo data into review views. Their status is an input to leadership judgment, not an objective transformation verdict.

Tech Stack

Built With

所列技术仅标识仓库依赖项或适配器表面，并不证明存在活动集成或部署。

Backend
Python 3.12, FastAPI, SQLAlchemy, SQLite (Postgres-ready), Redis, Celery, Pydantic v2
AI / LLM
Routing source for local, private and cloud model paths plus metadata-filtered retrieval; residency and fail-closed behaviour depend on explicit configuration and verification
Frontend
React 18, TypeScript, Vite, Tailwind CSS, Apple-minimal design system, Recharts, Framer Motion
Connectors
Jira, GitHub, Confluence and Azure DevOps adapter surfaces plus demo/mock connectors; write behaviour remains proposal-first and configuration-dependent
Infrastructure
Docker Compose, Caddy reverse proxy, OIDC/Azure AD auth, RBAC, approval workflows, SHA-256 audit trail
Testing
Pytest (backend), Vitest + React Testing Library (frontend), demo scripts for each capability module

Source Code

Explore the Code

Repository access, evaluation scope and any reuse terms are agreed explicitly; this public page does not promise source access or a licence.

NDA Required

To access the source code, please sign our Non-Disclosure Agreement. This is a standard legal formality.

Partnership

Interested in TransformationOS?

Evaluate a Make/Buy, portfolio or product operating-model governance problem against an inspectable, explicitly bounded demonstration.

Get in Touch
AI 洞察

The AI Dispatch

从演示走向可靠运营。订阅 Physical AI 新读物。

随时可取消订阅。绝无垃圾邮件。