Ten digital twins.
The simulators are the digital twins — the mirror of the network's state. The Reality Twin reads them.
The frame: a digital twin says what the network should be. These ten simulators are exactly that — coverage, CRM, demand, incidents, telemetry, MCX, core provisioning — mirroring state and dynamics. The Reality Twin reads across them (and the real, physical signals) and writes down what is actually happening. The twins are the ground; the narration stands on them.
The constellation
Ten simulator concepts, all packaged as darknoc-twin-* Atlassian Forge apps. Each runs independently; together they form a bidirectional fabric.
| Slug | What it twins | Key surface |
|---|---|---|
| coverage-twin | RF coverage + propagation | Coverage heatmap, gap detector |
| crm-sim (darknoc-twin-crm) | Customer relationship + lifecycle | TMF v5.0 CRM signal source |
| demand-sim (darknoc-twin-demand) | Subscriber demand + capacity | Forecast + bottleneck view |
| growth-launch-sim (darknoc-twin-growth) | Growth + launch dynamics | Split-view: network-flow + compartmental model |
| incident-sim (darknoc-twin-incident) | Incident detection + escalation | Live event timeline |
| mcx-sim (darknoc-twin-mcx) | Mission-critical voice/data flow | 14-node network visualisation |
| oss-ran-sim | OSS-side RAN operations | Performance + config drift |
| security-breach-sim (darknoc-twin-security) | Security operations centre | Breach replay + containment |
| telemetry-sim (darknoc-twin-telemetry) | Telemetry ingestion + alerting | Stream replay + threshold tuning |
| core-prov-sim | Core network provisioning | Tenant + service activation |
The cascade
The differentiator of this concept is that the sims are wired into each other. The output of one is the input of another.
- Three sims act as data providers:
coverage-twin,demand-sim,telemetry-sim. incident-simconsumes the three providers.security-breach-simis the hub — consumes all five upstream sims.growth-launch-simconsumescrm-simvia TMF APIs.- Push channel:
security-breach-sim → incident-simviaincident-feed.
Common features
Bidirectional sync
A change in one split-view reflects immediately in the others.
Compartmental models
Adjustable flow rates across each lifecycle (awareness, consideration, subscription, churn, reactivation).
Real-time KPIs
Per-sim KPI strip: subscribers, pipeline, at-risk, MRR-equivalents.
Time control
Simulation speed 1× to 10×, scrubbable.
Conversational query
Agent interface for ad-hoc analysis and what-ifs.
Forge-hosted
Each sim runs as an independent Atlassian Forge app.
Why the concept matters
- Bidirectional sync turns sims from siloed demos into a working concept fabric.
- TMF v5.0 signal flows mean the same agent code can be exercised against either synthetic or live signals.
- Compartmental modelling layered onto network-flow visualisation gives operators and execs a shared lens.