DarkNOC Twin — 10 simulators, one Reality Twin.

Not a digital twin. A Reality Twin: signals in, models in the middle, agents acting back out — explored as an open concept.

The frame: The Reality Twin closes the loop a digital twin only mirrors. Signals (TMF v5.0, telemetry, RF, CRM) flow in. Compartmental + network-flow models sit in the middle. Agents decide and act back out into ops. Each simulator below is one altitude of that same loop.

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-sim consumes the three providers.
security-breach-sim is the hub — consumes all five upstream sims.
growth-launch-sim consumes crm-sim via TMF APIs.
Push channel: security-breach-sim → incident-sim via incident-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.

darknoc.org/simsBrowse the catalogue, filter by data shape. darknoc.dev/simulatorsData contracts, mocks, sample fixtures. The Reality Twin (post)The framing every DarkNOC piece leans on. The cascade (post)Provider, consumer, hub — the wiring explained.