{"core-extras.96d330537a":"Base IR","core-extras.bee831a169":"Substrate","core-extras.61a0822826":"Apps on Core","core-extras.15438cc098":"not supported","core-extras.ad565d9d01":"Feature","core-extras.0155bf03e5":"Segment legend","core-extras.8b7110078e":"Algorithm groups by data type","core-extras.25ab4276a6":"Scrollable capability matrix","page-breadcrumb.c766e66518":"Breadcrumb","section_st_a1_display-split.7c9a7c0610":"Detail","section_st_f1_cta-dark.90e40d5043":"Get started","trace-section.e257621ef4":"Constraint trace","uc-telecom-business-glyph.018d49d66b":"Core network","uc-telecom-business-glyph.0698618fb3":"your own perimeter","uc-telecom-business-glyph.0ccfcd0de4":"What changes","uc-telecom-business-glyph.175bc15ffa":"Same inputs, same decision","uc-telecom-business-glyph.1b6b19ef57":"no outbound link","uc-telecom-business-glyph.1d197d39c5":"Where it runs","uc-telecom-business-glyph.30689d3319":"Network decisions on record","uc-telecom-business-glyph.30fbcf34d2":"managed through Fabric","uc-telecom-business-glyph.3fe2fe497b":"EU-sovereign","uc-telecom-business-glyph.437296eb4d":"Incident review is reconstructed","uc-telecom-business-glyph.47178a3be3":"One surface, four perimeters","uc-telecom-business-glyph.56f8d9a226":"The NOC operator is named at the time","uc-telecom-business-glyph.5df2ebe7c0":"Air-gapped","uc-telecom-business-glyph.88bc7b8ac6":"routing, handover, spectrum, QoS","uc-telecom-business-glyph.8ac7aa173f":"What you get","uc-telecom-business-glyph.8ee83d43a7":"The operator is named afterwards","uc-telecom-business-glyph.9a45aebe5c":"integrate in place","uc-telecom-business-glyph.a6a803b670":"Answers drift between runs","uc-telecom-business-glyph.a843a8e1f3":"On Dweve Mesh","uc-telecom-business-glyph.b65b3bf8c4":"Signed network record","uc-telecom-business-glyph.d37bac1618":"Review opens the network record","uc-telecom-business-glyph.d3b607c3b9":"The rule lives in a runbook","uc-telecom-business-glyph.d8fae234c7":"Via API","uc-telecom-business-glyph.e9f0d84192":"on record","uc-telecom-business-glyph.f26d9a367f":"The rule is recorded with the decision","uc-telecom-consumer-glyph.0c63e75e27":"a specific answer, not a general one","uc-telecom-consumer-glyph.1f881ce91c":"your line","uc-telecom-consumer-glyph.35e0b10a1e":"Run in Europe","uc-telecom-consumer-glyph.3fabc84463":"The answer names what actually happened.","uc-telecom-consumer-glyph.456983fe84":"The node, the rule and the time are kept together.","uc-telecom-consumer-glyph.5107894be3":"You can ask","uc-telecom-consumer-glyph.5cc5c9f2ab":"Kept with your service record","uc-telecom-consumer-glyph.77452c3e04":"It moves","uc-telecom-consumer-glyph.7fb22949d9":"What happened to your connection","uc-telecom-consumer-glyph.d049ad879f":"Your connection hands over between network nodes.","uc-telecom-consumer-glyph.dabbdd5737":"Your connection moves between nodes, and every move is written down.","uc-telecom-consumer-glyph.e2c5987c88":"It is written down","uc-telecom-technical-glyph.07235a8030":"signed","uc-telecom-technical-glyph.0a1ae03ca2":"Decision log","uc-telecom-technical-glyph.0a5e38ec2c":"on Dweve Mesh","uc-telecom-technical-glyph.0f400122e3":"rule","uc-telecom-technical-glyph.1c54132b8e":"Record","uc-telecom-technical-glyph.1d197d39c5":"Where it runs","uc-telecom-technical-glyph.1d29441d57":"NOC operator","uc-telecom-technical-glyph.20574e525f":"Telecom decision path","uc-telecom-technical-glyph.341d953e69":"replay","uc-telecom-technical-glyph.36d34eb6e5":"routing, handover, QoS","uc-telecom-technical-glyph.39aa59d6fd":"Run and replay","uc-telecom-technical-glyph.3fe2fe497b":"EU-sovereign","uc-telecom-technical-glyph.4625793ffe":"Decision under test","uc-telecom-technical-glyph.53354e1327":"air-gapped","uc-telecom-technical-glyph.5f435eb302":"cell","uc-telecom-technical-glyph.6ead7dde6c":"model version","uc-telecom-technical-glyph.72b06baea0":"route held under policy","uc-telecom-technical-glyph.746269f8d4":"core network","uc-telecom-technical-glyph.7bc555991d":"fixed","uc-telecom-technical-glyph.7d50f37dd6":"handover","uc-telecom-technical-glyph.7f59a1f1d5":"Decision","uc-telecom-technical-glyph.828d338a9b":"source","uc-telecom-technical-glyph.9dac008c3e":"Reviews it feeds","uc-telecom-technical-glyph.9f00fad98b":"policy","uc-telecom-technical-glyph.a251a49e45":"via API","uc-telecom-technical-glyph.b65b3bf8c4":"Signed network record","uc-telecom-technical-glyph.bb9cf14180":"Policy","uc-telecom-technical-glyph.bbcf64a3a2":"Inputs","uc-telecom-technical-glyph.ce2879c184":"same inputs, same route","uc-telecom-technical-glyph.df6ad19037":"run","uc-telecom-technical-glyph.e2387f6c69":"Recorded with the decision","uc-telecom-technical-glyph.f03f93f349":"named version","uc-telecom-technical-glyph.f6798670ec":"Deterministic","uc-telecom-technical-glyph.f88f3065e1":"class kept for the session","uc-telecom-technical-glyph.fc166eb813":"route","use-case-telecom.f9ba98a069":"Telecom","use-case-telecom.14a29ba383":"Use Cases","use-case-telecom.146bb22e35":"Existing OSS, BSS, and SIEM systems keep working. Dweve wraps them in a deterministic\n            decision layer that records every netflow sample, every rule, and every NOC action\n            as the decision happens.","use-case-telecom.1c5ac0708c":"Telecom, technical","use-case-telecom.46f92ea598":"Your control","use-case-telecom.8bf34da1c7":"One platform","use-case-telecom.39c4ad47f2":"Closed bundle for the most sensitive netflow.","use-case-telecom.ec9dfc4fd3":"Fully offline","use-case-telecom.a2e24b45d1":"Run inside your perimeter on licensed nodes.","use-case-telecom.71be531a19":"Your core network","use-case-telecom.55423877a1":"Dweve-operated public Mesh; processing boundary documented in the agreement.","use-case-telecom.61810d3c5a":"Business Workspace","use-case-telecom.2b1884c5a7":"One platform, three postures","use-case-telecom.215475056e":"WHERE IT RUNS","use-case-telecom.92a16f5060":"SDK: TS/Python/Go/Rust","use-case-telecom.4b3258f7ec":"RFC 7807","use-case-telecom.92af23aac4":"PROTOBUF","use-case-telecom.dabbb6f4e1":"OPENAPI 3.1","use-case-telecom.f158a093e4":"Integrate via REST or gRPC against a typed OpenAPI 3.1 surface. Managed through Fabric on the public Dweve Mesh for pilots. Licensed for your core network. Air-gapped for the most sensitive netflow. Same API, same trace format, same replay packets across all three.","use-case-telecom.0ff8b5b425":"Three deployment postures.","use-case-telecom.94188e2c6c":"One API.","use-case-telecom.34bfbaefff":"How you integrate","use-case-telecom.80b30e032e":"Bit-identical output","use-case-telecom.40685beb3e":"Same rule","use-case-telecom.e3314d0208":"NOC operator signs the final decision.","use-case-telecom.8eeb40cd07":"Sign packet","use-case-telecom.e3dcc5480b":"Spectrum licence version applied.","use-case-telecom.596faf307d":"Apply licence","use-case-telecom.cfe406f6df":"Routing rule produces a raw decision.","use-case-telecom.b30b23e56e":"Run rule","use-case-telecom.432caa3a42":"Inputs logged before the rule runs.","use-case-telecom.9678dd9fa7":"Pin inputs","use-case-telecom.478360978f":"Four guarantees","use-case-telecom.c00f9811f5":"WHAT THE LAYER DOES","use-case-telecom.3b720bec28":"SIGNED REPLAY","use-case-telecom.6757848af7":"DETERMINISTIC","use-case-telecom.1d99f444ce":"Existing OSS, BSS, and SIEM systems keep working. Dweve wraps them in a deterministic decision layer that records every netflow sample, every rule, and every NOC action as the decision happens. The replay packet is the audit artefact. Inputs are logged before the rule runs, the routing rule produces the raw decision, the spectrum licence version in force is applied, and the NOC operator signs the packet.","use-case-telecom.fb834ca63c":"bit-identical replay.","use-case-telecom.6ecca58334":"OSS wrapped,","use-case-telecom.93638d9091":"Routing determinism","use-case-telecom.17721bb62b":"One signed handover","use-case-telecom.01c501a76c":"Four steps","use-case-telecom.58920d873e":"NOC operator signs; packet is the artefact.","use-case-telecom.42f50359cc":"Sign the decision","use-case-telecom.709be44aee":"Deterministic compute scores candidates.","use-case-telecom.f38b6ac2a8":"Run scoring","use-case-telecom.9ac314199c":"Each decision records the rule version used.","use-case-telecom.6368b90d30":"Pin to rule","use-case-telecom.bddbf95817":"Pull RSRP, RSRQ, SINR from UE.","use-case-telecom.b62b2803d6":"Ingest measurements","use-case-telecom.b31cf0d2d5":"HANDOVER","use-case-telecom.1779864412":"PINNED","use-case-telecom.104033a14a":"RSRQ","use-case-telecom.017c4b130a":"RSRP","use-case-telecom.91531865e4":"Handover decisions are the telecom workflow most damaged by float drift and measurement skew. Dweve runs the handover scoring on integer arithmetic, pins to a specific 3GPP rule version, and ships the same decision every time. The packet is the audit artefact when BEREC calls. RSRP, RSRQ and SINR come in from the UE, the rule version in force is recorded with them, the candidates are scored by deterministic compute, and the NOC operator on shift signs the result. The measurement report, the rule section that fired and the target cell selected stay in one packet.","use-case-telecom.e91ddb5145":"Handover decisions,","use-case-telecom.14dc06712f":"Handover analytics","use-case-telecom.8a544caab2":"The decision layer never crosses a trust boundary that fails the NIS2 or EECC rules.\n            The same topology ships on all three postures.","use-case-telecom.d5a9f6f81a":"Three postures","use-case-telecom.8ab2c84ed7":"One architecture","use-case-telecom.31f31cce7a":"No outbound calls. Optional EU-only BEREC endpoint.","use-case-telecom.8e05a902ed":"Egress","use-case-telecom.8c0e6f760f":"Signed packets written once, read many, EU-only replica.","use-case-telecom.dcf17fd359":"Packet store","use-case-telecom.6de6f8a697":"CPU-native engine, no GPU farm, no cloud ML APIs.","use-case-telecom.7f59a1f1d5":"Decision","use-case-telecom.7d853df929":"TLS terminate in EU, mTLS to the decision layer.","use-case-telecom.92096d78df":"Ingress","use-case-telecom.7f166ac611":"Four boundaries","use-case-telecom.338ac926aa":"TOPOLOGY","use-case-telecom.6b4217aac7":"EU ONLY","use-case-telecom.5e905a995e":"PACKET STORE","use-case-telecom.6d917c2df3":"CORE","use-case-telecom.138a224dc4":"DMZ","use-case-telecom.5ee3e94de3":"Three operating models, one evidence architecture. Managed Fabric runs on the public Mesh. Licensed operation brings direct products into your core network. Air-gapped operation protects the most sensitive netflow. Each model keeps decisions and evidence inside its declared trust boundary. Four boundaries hold that line. Ingress terminates TLS in the EU and speaks mTLS to the decision layer. The decision itself runs on a CPU-native engine, with no GPU farm and no cloud ML API in the path. Signed packets are written once and read many, on an EU-only replica. Egress makes no outbound calls, with an optional EU-only endpoint for BEREC. The same topology ships on all three postures, and only the boundary moves.","use-case-telecom.3ae8029f90":"per posture.","use-case-telecom.52c48d0dc9":"Where the layers sit,","use-case-telecom.f9790fb715":"Deployment topology","use-case-telecom.2c2bb99178":"Determinism is asserted in the suite, not promised in prose. The same oracle run on\n            your hardware produces the same answer as on ours.","use-case-telecom.064f903275":"Not aspirational","use-case-telecom.aed3b8c6a7":"Verified","use-case-telecom.ed0ff2382e":"No rounding error crosses the unit-of-last-place threshold.","use-case-telecom.aadefaf8ed":"Correctly rounded","use-case-telecom.cc376f246e":"Corners and ranges exercised automatically in CI.","use-case-telecom.e02eea5453":"Property tests","use-case-telecom.a24d9583df":"Each result compared to a high-precision reference.","use-case-telecom.47909e2975":"256-bit oracle","use-case-telecom.4ac72fd74a":"Bounded iteration count, no floating-point unit.","use-case-telecom.97dab07ad3":"CORDIC compute","use-case-telecom.b9a7f2f458":"How the bound is proven","use-case-telecom.dc0507035e":"VERIFICATION","use-case-telecom.481d3e216b":"PROPERTY TESTED","use-case-telecom.fdd71ee1c4":"MPFR 256-BIT","use-case-telecom.51ab88da6e":"0 ULP","use-case-telecom.bcde2c3d11":"Every numerical computation in the routing and handover path is verified against MPFR at 256-bit precision. The published result is 0 ULP, correctly rounded across the documented input domain, with property-based tests driving the corners on every release.","use-case-telecom.bed4aa0e07":"checked against an oracle.","use-case-telecom.0479003b2b":"0 ULP transcendentals,","use-case-telecom.4e8c678c76":"Verified routing","use-case-telecom.1c336bc636":"One signed view","use-case-telecom.dec6365835":"Years later, the same licence is pulled and replayed.","use-case-telecom.75180d9dcd":"Replay later","use-case-telecom.eb4dd6881a":"Deterministic compute allocates the band.","use-case-telecom.df139f4c03":"Run allocation","use-case-telecom.04fa0b8a80":"Each decision records the licence version that was active.","use-case-telecom.b856f541fe":"Pin to decision","use-case-telecom.cd58a42c5b":"Pull the current spectrum licence from the regulator.","use-case-telecom.a3a4fcf96a":"Load licence","use-case-telecom.b26daabfa7":"SPECTRUM","use-case-telecom.45bdfdeb50":"BAND","use-case-telecom.6e0ad2b047":"LICENCE","use-case-telecom.e6ab5abb7a":"AUCTION","use-case-telecom.709f950c22":"Spectrum bands are licensed per auction per country. Every QoS report and handover decision pins to a specific licence version, so the replay reconstructs the exact spectrum allocation in force on the date of the decision. The licence is pulled from the regulator publication and pinned to the decision as it is made, not looked up afterwards. The allocation itself is computed deterministically, and each one is logged with the regulator and the licence version beside it. Years later the same licence is pulled and the same band comes back.","use-case-telecom.d3b0a04d24":"pinned to a licence.","use-case-telecom.8f1f63e9c3":"Spectrum bands,","use-case-telecom.003e310a5b":"Spectrum allocation","use-case-telecom.f5d4349e08":"Full trace","use-case-telecom.3477f4d91d":"Same answer","use-case-telecom.7c11819b1a":"Managed Fabric, licensed on your core network, or air-gapped.","use-case-telecom.65cfa78989":"Sovereign","use-case-telecom.e56a362553":"OpenAPI 3.1 spec, typed errors (RFC 7807).","use-case-telecom.cb885a925a":"REST + gRPC","use-case-telecom.6d703b95ff":"Netflow source, rule, NOC operator, signature.","use-case-telecom.0788e3e212":"Signed packet","use-case-telecom.6cbcecba9f":"Same input, same output, every machine, every release.","use-case-telecom.02ae1c41fe":"Exact replay","use-case-telecom.0753940ae7":"Four properties","use-case-telecom.06ebfec4be":"WHAT IT GIVES YOU","use-case-telecom.46861816b1":"Every routing decision runs on a deterministic engine. Bit-exact replay across machines and releases. Same routing on the core network, in the cloud, and on a laptop. No floating-point drift, no chip-dependent rounding. Each decision leaves a signed packet carrying the netflow source, the rule, the NOC operator and the signature, whether it runs as managed Fabric, licensed on your core network, or air-gapped.","use-case-telecom.f8a7a03970":"Routing decisions,","use-case-telecom.1e4c76f918":"Deterministic routing","use-case-telecom.4dfa359a71":"You do not need to fight a chat box to challenge a QoS charge. The packet is in\n            plain language and the NOC operator, the rule, and the timestamp are named.","use-case-telecom.74bdcfb702":"Telecom, consumer","use-case-telecom.c605f28db5":"On the record","use-case-telecom.5a9f470750":"Your bill","use-case-telecom.6afbe8bfb3":"Same packet the court sees.","use-case-telecom.1c54132b8e":"Record","use-case-telecom.ec38d97eea":"Consumer court, no upfront fee.","use-case-telecom.65dfd1c042":"Court","use-case-telecom.3edbd0ad28":"EUR 0","use-case-telecom.d21ed45ac6":"National regulator consumer desk.","use-case-telecom.92a398b343":"BEREC","use-case-telecom.75f527181b":"Free","use-case-telecom.31c44fa0cf":"Named NOC operator per shift.","use-case-telecom.faa3d43edf":"NOC review","use-case-telecom.75e6a088a0":"Four routes","use-case-telecom.bc3e09058f":"YOUR PATHS","use-case-telecom.f687646ff3":"COURT","use-case-telecom.f3e33023a1":"NOC","use-case-telecom.39eea1adf7":"Every QoS decision your operator makes is appealable. The same record the NOC operator signed is the record you can challenge. If you disagree with the SLA breach, the handover, or the charge, the complaint path is on the bill. It starts with a review by the named NOC operator on shift, then the national regulator consumer desk, then a consumer court, and every step reads that one signed record.","use-case-telecom.573d91c3b3":"can challenge.","use-case-telecom.2d45c8d028":"A bill you","use-case-telecom.e2d8ea01ae":"Your complaint path","use-case-telecom.11234a16b5":"One record","use-case-telecom.55b46d0640":"One handover","use-case-telecom.3f3a2ed10d":"Your complaint gets a written answer.","use-case-telecom.6c2bb735a4":"Reply","use-case-telecom.5b1e563dae":"The NOC operator who signed off is named.","use-case-telecom.89ff31225c":"Owner","use-case-telecom.9759da6409":"The 3GPP rule that fired is attached, not separate.","use-case-telecom.78e1790e29":"Rule","use-case-telecom.ef055df2e9":"The handover was triggered with a reason.","use-case-telecom.92f5fe6952":"Four outcomes","use-case-telecom.a76f8ee287":"HOW IT WORKS","use-case-telecom.790392d6b8":"EXECUTE","use-case-telecom.02977df2c2":"DECIDE","use-case-telecom.0e81bff68c":"MEASURE","use-case-telecom.9a79079c97":"DETECT","use-case-telecom.70d3f7ab59":"A cell handover is no longer a black box. The detect, measure, decide, and execute steps each have a named operator, a timestamp, and a rule attached.","use-case-telecom.887040ad3d":"A cell handover is no longer a black box. The detect, measure, decide, and execute steps each have a named operator, a timestamp, and a rule attached. The handover is triggered with a reason, the 3GPP rule that fired travels with it instead of sitting in a separate system, and the NOC operator who signed off is named. Ask about it later and the answer is that same record, in writing.","use-case-telecom.dfb39fb4ea":"with its record attached.","use-case-telecom.98b084ae22":"A handover moves","use-case-telecom.cdc6d68b7d":"How handovers work","use-case-telecom.f470e8fe87":"Your service","use-case-telecom.e2069070de":"Delete means deleted.","use-case-telecom.993a665d35":"In charge","use-case-telecom.905cb326c7":"You","use-case-telecom.4e926425d9":"Data stays in EU jurisdiction.","use-case-telecom.ef5fdf226f":"Footing","use-case-telecom.c82d1b09cf":"EU","use-case-telecom.808030dc01":"The quality you are paying for.","use-case-telecom.62b12a5b3d":"SLA","use-case-telecom.8e16e5b2c4":"Real","use-case-telecom.1641a6eed5":"A reason, not a guess.","use-case-telecom.89b86ab0e6":"Language","use-case-telecom.34118050b2":"Plain","use-case-telecom.6a0b9b99b6":"When your operator runs on Dweve","use-case-telecom.f31727ff20":"WHAT YOU GET","use-case-telecom.126cbdcb1c":"EU DATA","use-case-telecom.e1d0c1568b":"NAMED OPERATOR","use-case-telecom.b838c172bb":"PLAIN LANGUAGE","use-case-telecom.79d90d42a8":"When your operator uses Dweve, your quality of service is not a guess from a machine. It is tied to a network node, a SLA, and a named NOC operator who can explain the bill. The answer names the cell you were on, the service level you pay for, and the person who was on shift. Your data stays under EU jurisdiction, and when you ask for it to be deleted, it is deleted.","use-case-telecom.6dfc6de514":"can read.","use-case-telecom.e662b37576":"A service you","use-case-telecom.7027e810a3":"Your side of the service","use-case-telecom.d568b6918d":"Every roaming call carries the same packet as every home call. The BEREC return is\n            a retrieval, not a reconstruction.","use-case-telecom.e2a2d62bd0":"Telecom, business","use-case-telecom.e63a99077f":"One signed chain","use-case-telecom.90efc21e83":"Four stages","use-case-telecom.c7cc76be6d":"Settlement signed, BEREC return filed.","use-case-telecom.3ebe66ce7c":"Settle","use-case-telecom.b680464546":"Clearing house exchanges TAP records.","use-case-telecom.719ea396ad":"Clear","use-case-telecom.0f9bfc7518":"Call / SMS / data session logged with rule.","use-case-telecom.1d4d43cc6f":"Use","use-case-telecom.cdef18cf6e":"Subscriber attaches to visited network.","use-case-telecom.7c9a8664b1":"Visit","use-case-telecom.a8076738c8":"ROAMING","use-case-telecom.06037ef476":"CLEARING","use-case-telecom.81adef392c":"INTERCONNECT","use-case-telecom.fecc6e8f86":"Roaming and interconnect are the workflows most damaged by billing system skew. Dweve wraps the roaming records in a deterministic decision layer so every call, every SMS, and every data session on a visited network carries the same signed packet through the clearing chain. The visited network writes the record once, at the moment the subscriber attaches. The clearing house exchanges TAP records against it, and the settlement is signed against that same packet rather than a second set of books. When the BEREC return is due, it is filed from the record, so the return is a retrieval rather than a reconstruction.","use-case-telecom.1fc1c04e13":"A roaming call","use-case-telecom.3cbfaca2cf":"Roaming and interconnect","use-case-telecom.6a29073a8d":"The network decision stays inside your jurisdiction. The same platform scales from a\n            single RAN pilot to a full core network without re-platforming.","use-case-telecom.4c38922528":"Run inside your perimeter on licensed nodes. Same API, same trace format.","use-case-telecom.0058df0a6e":"Dweve-operated public Mesh; processing boundary documented in the agreement.","use-case-telecom.971505e421":"CORE NETWORK","use-case-telecom.67b752639a":"MANAGED MESH","use-case-telecom.ba8273e11d":"Two questions decide procurement: where does it run, and which rules does it satisfy. It runs managed through Fabric on the public Dweve Mesh, on your core network, or fully air-gapped, with no re-platforming between tiers. GDPR, NIS2, EECC, and the EU AI Act are design constraints the platform satisfies by construction.","use-case-telecom.72bb84e413":"Run on your core network.","use-case-telecom.560486613b":"Start with the managed service.","use-case-telecom.1d197d39c5":"Where it runs","use-case-telecom.8b0c0e172f":"Four filings","use-case-telecom.93b48c8079":"One packet","use-case-telecom.c80735a412":"Lawful intercept and retention records linked per subscriber.","use-case-telecom.a5b7d57a85":"GDPR","use-case-telecom.d19fe5a3cd":"Roaming and interconnect returns linked per call.","use-case-telecom.50bb39e6dc":"QoS reports compile from the decision history.","use-case-telecom.aaa422e2b0":"EECC","use-case-telecom.25d1601bf2":"Incident reports pull from the same packets, no separate assembly.","use-case-telecom.e7595345e0":"WHAT CHANGES THIS QUARTER","use-case-telecom.4374bb4de9":"Every network decision flows into the regulatory filings the supervisor expects. NIS2 incident reports, EECC QoS reports, BEREC roaming returns, and GDPR lawful-intercept records all draw from the same decision packets. One source of truth, four filings. Incident reports pull from the packets instead of being assembled separately, QoS reports compile from the decision history, roaming returns link per call, and retention records link per subscriber.","use-case-telecom.56cb27e317":"attached per decision.","use-case-telecom.26f8cc0cce":"NIS2, EECC, BEREC, GDPR","use-case-telecom.0c743d5b34":"The compliance stack","use-case-telecom.5d1cc3c5c6":"Jurisdiction","use-case-telecom.8a1379821b":"Opaque decisions","use-case-telecom.f68cece41b":"Trace attached","use-case-telecom.3a869128a8":"Signed packet the supervisor replays in under a minute","use-case-telecom.4e250b4fde":"REPLAY","use-case-telecom.cad982a88d":"NOC operator shift 2, timestamp, sign-off","use-case-telecom.501e489055":"OWNER","use-case-telecom.f6e1c01815":"Handover rule HO-NL-2026-H1, section 4.2","use-case-telecom.aaa398a28b":"RULE","use-case-telecom.d667e5b8ea":"RSRP trace, measurement report, neighbour list","use-case-telecom.e9ae0ed784":"SOURCE","use-case-telecom.b58a1234ee":"ho-rule-2026-H1-4.2.pdf","use-case-telecom.9d21b8129e":"Handover rule HO-NL-2026-H1 section 4.2 applied because RSRP on source cell dropped below -110 dBm at 17:42:08. Target cell gNB-048 selected as the highest-scoring candidate from the measurement report. NOC operator shift 2 confirmed the handover. The same decision replays bit-identical, with the RRC reconfig, the rule, and the operator on one screen.","use-case-telecom.7f4a184ece":"THE RECORD SHOWS","use-case-telecom.fb1dcb24c9":"Why was handover HO-11448 routed to gNB-048?","use-case-telecom.9e7cf1b106":"THE REGULATOR ASKS","use-case-telecom.786a2f2594":"The decision record","use-case-telecom.30d53a80c7":"Every routing, handover, and spectrum decision leaves a signed packet: the netflow source, the rule that fired, the NOC operator, and a bit-exact replay. The supervisor opens one file and watches the same decision come back. No result arrives without the rule that produced it, and the record stays in the jurisdiction where the decision was made.","use-case-telecom.7f15a2e8ec":"The packet the supervisor replays in under a minute.","use-case-telecom.20074e4b81":"The routing table is the easy part. Reconstructing the why of every handover six\n              months later, in front of a BEREC reviewer, is the hard part.","use-case-telecom.afaa4aa8be":"Each blocks the review","use-case-telecom.ec95d99629":"Four gaps","use-case-telecom.e10fad6d31":"A chat log does not replay the same way twice.","use-case-telecom.fade4edeec":"No evidence","use-case-telecom.c55a4bff35":"Foreign-hosted netflow fails the NIS2 outsourcing rules.","use-case-telecom.e03947cc0c":"Sovereignty","use-case-telecom.c1d080fb62":"A score is not a routing decision a NOC can read.","use-case-telecom.8479f2b690":"Black box","use-case-telecom.48062f8549":"It invents a path instead of citing the BGP rule that fired.","use-case-telecom.a978d8e92c":"Hallucination","use-case-telecom.782cef5501":"Four structural gaps","use-case-telecom.9c07b860c3":"WHY GENERIC AI FAILS THE REVIEW","use-case-telecom.405ede95ba":"QOS","use-case-telecom.6c71776e29":"ROUTING","use-case-telecom.7f13c98a2e":"A head of network operations does not buy a platform. She survives a NIS2 incident review and a BEREC audit. EECC end-user rights, NIS2 essential-entity rules, and the EU AI Act each want the same thing: the rule, the source, the NOC operator, and the replay of every routing decision. Today that record lives in OSS, BSS, SIEM, and ticket systems that were never meant to agree. The routing table itself is the easy part. What takes the quarter is reconstructing why one handover went the way it did, six months later, with the rule version that fired and the operator who signed it.","use-case-telecom.5d041bdee1":"you can show BEREC.","use-case-telecom.5b40e4a8da":"A routing table","use-case-telecom.31bc1a0758":"The routing decision","use-case-telecom.a4fb970cd2":"See where it runs","use-case-telecom.03c7aa583d":"Talk to a telecom engineer","use-case-telecom.7b43fbf342":"Pick one workflow: routing, handover, spectrum allocation, or QoS reporting. Run it with your own network data and watch the review packet assemble as the work moves. Managed through Fabric on the public Dweve Mesh, on your core network, or air-gapped.","use-case-telecom.a195bf2970":"Start with the decision you most dread explaining.","use-case-telecom.d75a4de2ef":"EU AI Act","use-case-telecom.9620cf2803":"Spectrum","use-case-telecom.bb32c4a104":"Routing breakdown","use-case-telecom.70d4e24cea":"Bit-exact replay for routing, handover, and QoS decisions. 3GPP aware, NIS2 compliant, EU-sovereign. Integrate via API, host in the EU, or run air-gapped on the core network.","use-case-telecom.febec2a03f":"handover, and QoS.","use-case-telecom.cccf18ef98":"Replay routing,","use-case-telecom.d32d56032e":"Your service card","use-case-telecom.a5fef3e293":"If your connection slows or your bill changes, you should get more than a generic answer. Dweve links the service decision to the network node, your SLA, and the operator responsible, so the explanation is specific to what happened.","use-case-telecom.3b4172ef14":"to your connection.","use-case-telecom.d363b4919f":"See what happened","use-case-telecom.2f335b8616":"See routing decisions","use-case-telecom.75dc23a38a":"Keep routing, handover, spectrum, and QoS decisions moving while the rule, source, NOC operator, and model version are recorded with them. A NIS2 incident review or BEREC audit begins with the actual network record, not a reconstruction.","use-case-telecom.fa566b0d3e":"into review-ready records.","use-case-telecom.ef706ca193":"Turn network decisions","use-case-telecom.043fc53930":"Complaints answered by a named handler","use-case-telecom.9681152255":"REPLY","use-case-telecom.62708bf7df":"EU, data stays in NL jurisdiction","use-case-telecom.eb8d72238c":"JURISDICTION","use-case-telecom.b1be802507":"KPN NL, named NOC shift","use-case-telecom.a1f5629a44":"PROVIDER","use-case-telecom.87f3da851b":"GBR 99.96%, latency 8.4ms median","use-case-telecom.1f4a8eca0d":", region NL, sector A","use-case-telecom.a6d102dc1a":"5G NR n78","use-case-telecom.5f5cdfd63a":"SERVICE","use-case-telecom.41924156ee":"SLA MET","use-case-telecom.540bfd7d69":"Your service, on the record","use-case-telecom.df64006836":"Replay reconstructs the full sequence","use-case-telecom.6a74762cd2":"Each step has a named NOC operator and a timestamp","use-case-telecom.330322e4ae":"Handover triage, on the record","use-case-telecom.494feecaa8":"Handover executed, RRC reconfig signed.","use-case-telecom.6ea36ce8d4":"Execute","use-case-telecom.a4c87b5e27":"Target cell selected per handover rule.","use-case-telecom.a26b9b7477":"Decide","use-case-telecom.c913d9b58c":"Target candidates measured, RSRP logged.","use-case-telecom.d4fd0a232e":"Measure","use-case-telecom.9ee128dfb9":"Signal strength drop below threshold, source cell.","use-case-telecom.80628bd746":"Detect","use-case-telecom.11dc9e1952":"Status:","use-case-telecom.6d61ae9db8":"Subscriber data, lawful intercept, retention.","use-case-telecom.95465c62a6":"General Data Protection Reg.","use-case-telecom.7e891beb71":"Implementation guidelines, roaming, interconnect.","use-case-telecom.8d51a955c8":"Body of European Regulators","use-case-telecom.8fa34a8151":"End-user rights, QoS reporting, BEREC.","use-case-telecom.1388e58fd8":"European Electronic Comm. Code","use-case-telecom.928164d346":"Essential entity incident reporting, supply chain.","use-case-telecom.57ff65d964":"Network Information Security 2","use-case-telecom.916dcde8ce":"Replay reconstructs the same allocation","use-case-telecom.routing.ingress":"Traffic entering the decision","use-case-telecom.routing.voice":"Voice sessions","use-case-telecom.routing.data":"Data traffic","use-case-telecom.routing.priority":"Priority service","use-case-telecom.routing.policy":"Policy evaluation","use-case-telecom.routing.routes":"Available paths","use-case-telecom.routing.selected":"selected upstream","use-case-telecom.routing.standby":"segment route","use-case-telecom.routing.edge":"edge delivery","use-case-telecom.routing.input":"traffic class","use-case-telecom.routing.rule":"policy version","use-case-telecom.routing.owner":"NOC owner","use-case-telecom.routing.decision":"route recorded","use-case-telecom.spectrum.recorded":"allocation recorded","use-case-telecom.spectrum.publication":"publication","use-case-telecom.spectrum.version":"licence version","use-case-telecom.spectrum.bands":"bands shown","use-case-telecom.spectrum.review":"review cycle","use-case-telecom.spectrum.daily":"daily","use-case-telecom.b45b4d0ba5":"Each allocation logged with regulator + licence version","use-case-telecom.044785ef79":"RDI publication / daily","use-case-telecom.6d9bd9ce07":"Spectrum utilisation, NL","use-case-telecom.f5d40af42c":"Shared unlic.","use-case-telecom.5e23994e80":"60 GHz","use-case-telecom.941f1a07e8":"Vodafone (NL)","use-case-telecom.e0e4fda87c":"26 GHz","use-case-telecom.0bccb61710":"T-Mobile (NL)","use-case-telecom.da118194a8":"3.5 GHz","use-case-telecom.8a9be6dced":"KPN (NL)","use-case-telecom.93e43e6854":"700 MHz","use-case-telecom.f0108246d7":"Replay reconstructs the same routing","use-case-telecom.9f668d499b":"Every decision logged with rule, NOC operator, timestamp","use-case-telecom.72cd68083f":"core NL / upstream tier 1","use-case-telecom.30e6da6439":"Routing decisions this hour","use-case-telecom.c83903db17":"CDN offload","use-case-telecom.afe19a45e0":"Segment routing","use-case-telecom.bf29a40912":"BGP best path","use-case-telecom.d649ce4d56":"Equal-cost multipath","use-case-telecom.e5d59b1d13":"SIGNED / TRACEABLE / REPLAYABLE","use-case-telecom.127edee78d":"SIGNED","use-case-telecom.3da4667aa0":"NOC shift 2, named on record","use-case-telecom.c25992686c":"OPERATOR","use-case-telecom.7853827da5":"LICENSED","use-case-telecom.b6ab6379e6":"3.4 to 3.8 GHz, 80 MHz block","use-case-telecom.375a8bf8d5":"ABOVE SLA","use-case-telecom.c72633f673":"ACTIVE","use-case-telecom.8f33eb9f77":"5G NR n78, 124 handovers/hour","use-case-telecom.81711b7c71":"CELL","use-case-telecom.06385df81c":"region NL / sector A","use-case-telecom.9bddccf9ce":"NETWORK NODE / gNB-048","use-case-telecom.42972de55f":"NIS2","use-case-telecom.e4e8999a95":"3GPP","use-case-telecom.1dabba21cd":"✓","use-case-telecom.fbcec86144":"Business Workspace","use-case-telecom.70ea1983c9":"Core","use-case-telecom.c73cc64719":"Air-gap","use-case-telecom.869360a6f4":"Bit","use-case-telecom.c8e5998f6a":"API","use-case-telecom.9170a8b2fb":"EU","use-case-telecom.2876814bd7":"Integer","use-case-telecom.adbc560c32":"MPFR","use-case-telecom.f23ba2a6ee":"proptest","use-case-telecom.be258ce66f":"0 ULP","use-case-telecom.5d0b2f6bd4":"OBSERVED","use-case-telecom.80db3832a5":"OUTCOMES","use-case-telecom.feb892b2eb":"DEPLOYMENT","use-case-telecom.d072aa117d":"WORKFLOW","use-case-telecom.d918e63dd4":"SUBSCRIBER","use-case-telecom.95cbab8db0":"HANDOVERS","use-case-telecom.0ddc335dad":"APPEAL","use-case-telecom.6f38f66d9a":"PLATFORM","use-case-telecom.39bda14904":"EVERY RELEASE","use-case-telecom.5ce41bc339":"ARCHITECTURE","use-case-telecom.46b9927e1d":"DETERMINISM","use-case-telecom.30691c8ec5":"The packet the supervisor replays","use-case-telecom.954be12e60":"in under a minute.","use-case-telecom.0281f0ea3e":"A routing table is easy to print. The reason behind each handover is the hard part.","use-case-telecom.4f4f907b48":"The supervisor opens one file and watches the same decision come back.","use-case-telecom.31b2e560c6":"Four instruments, four filings, and one set of decision packets underneath them.","use-case-telecom.f5c4dc024c":"Procurement asks two questions: where it runs, and which rules it satisfies.","use-case-telecom.7da78bb8c8":"A visited network writes the record once and the settlement reads that same record.","use-case-telecom.a9f1244428":"Your quality of service is tied to a node, an SLA and a person who can explain it.","use-case-telecom.8883522764":"A handover is four named steps, each one with a time and a rule attached.","use-case-telecom.aaedf32494":"The record the operator signed is the record you can take further.","use-case-telecom.1250287533":"Same input, same output, on the core network, in the cloud and on a laptop.","use-case-telecom.bc950bdfad":"A replay is only exact if the licence version in force that day is pinned to it.","use-case-telecom.7305343e02":"Determinism is asserted in the suite, not promised in prose.","use-case-telecom.b49f9adb64":"The same topology ships on all three postures. Only the boundary moves.","use-case-telecom.5e2b238a62":"Handover scoring runs on integer arithmetic and pins to a 3GPP rule version.","use-case-telecom.0b04372da4":"The systems already running the network keep running. The layer wraps them.","use-case-telecom.f5540b5af6":"One API surface, three deployment postures, and the same replay packet from each.","use-case-telecom.66c1f5342b":"One file, opened once","use-case-telecom.b52cd346d2":"The same decision comes back","use-case-telecom.74dadcad52":"Traffic classes, the policies scored against them, and the paths available.","use-case-telecom.d5383ea7af":"Recorded","use-case-telecom.ec702db22c":"four policies scored","use-case-telecom.540dd570dd":"The question put, the answer returned, and the four timed lines behind it.","use-case-telecom.17d120d8bb":"Replayable","use-case-telecom.22b41fe7ba":"four timed lines","use-case-telecom.2a46d2fd83":"One packet, four filings","use-case-telecom.e11ea6cbf0":"The fields a decision packet holds, and which of them each filing reads.","use-case-telecom.a089f600e3":"Linked","use-case-telecom.8a6bcfef3d":"five fields, four filings","use-case-telecom.5424a47edc":"No filing assembles its own record. Each one reads the packet.","use-case-telecom.4f74dd78cc":"Three postures, three questions","use-case-telecom.ac879cf437":"no re-platforming","use-case-telecom.056a43fa24":"The posture changes where it runs, never what it produces.","use-case-telecom.a034938c08":"One packet across the clearing chain","use-case-telecom.b59b74c1eb":"Who writes each hop of a roaming session, and what it adds to the record.","use-case-telecom.6e3665d85f":"Signed","use-case-telecom.d5b18fd723":"four hops","use-case-telecom.0c50dfc332":"The BEREC return is a retrieval, not a reconstruction.","use-case-telecom.afc679c4ff":"The five fields behind an answer about your quality of service.","use-case-telecom.0ac805be1a":"five fields","use-case-telecom.11435e7b09":"Each line names something you can ask about.","use-case-telecom.28b5fdc8c5":"Four states: two closed, one current, one still ahead.","use-case-telecom.b6bd42e4e7":"In progress","use-case-telecom.3513831f64":"four states","use-case-telecom.85baed3921":"From the bill to a written answer","use-case-telecom.be3a967b2c":"The four steps a complaint takes, and what you hold at each one.","use-case-telecom.69f0fd3c18":"Open to you","use-case-telecom.de60e7db09":"four steps","use-case-telecom.e07aa02225":"Every step reads the same signed record.","use-case-telecom.af3b2686b1":"Four licensed bands on one axis, each with the holder recorded beside it.","use-case-telecom.f9312169ef":"Pinned","use-case-telecom.edbe566e4f":"four bands","use-case-telecom.8f58ab731c":"The layer sits over what already runs","use-case-telecom.a9611b19dd":"Systems of record, the decision layer above them, the packet out of the top.","use-case-telecom.5380d98727":"Wrapped","use-case-telecom.7f41e27990":"three bands, four fields","use-case-telecom.c21977a42a":"Nothing is replaced. The packet is what an audit reads.","use-case-telecom.c44e09534b":"Where the decision is computed, where the packet rests, and what has to change."}