DOMAINS

One thesis. Different semantic worlds.

Domain transfer is used as a falsification pressure: the common assurance responsibilities should survive only where the evidence supports them.

TRANSPORT / REFERENCE DOMAIN

Digital Traffic Regulation Orders

D-TRO is a particularly strong test because the authoritative legal instrument and the machine-readable representation are explicitly not the same thing.

Authoritative sourceTraffic regulation order and other governed source material.

Digital representationD-TRO machine-readable extract for use by downstream systems.

Research questionWhen may an extract-derived interpretation support a defined downstream use or action?

Failure of interestSyntactically valid data that remains semantically insufficient for a consequential conclusion.

DfT source boundary: Department for Transport guidance states that a D-TRO is not a legal document, but a digital extract of the legal order containing standardised machine-readable data for integration with other digital systems.

DfT D-TRO guidance ↗ · DfT public technical artefacts ↗

TELECOM / TRANSFER DOMAIN

Frameworx / ODA research domain

Telecom operations test the thesis against intent, distributed systems, service state, policy, automation and cross-domain action.

Public demonstratorUses synthetic content suitable for public research demonstration.

Transfer questionDo authority, warrant, reliance and action boundaries remain meaningful in autonomous operational flows?

Industry contextTM Forum publicly describes intent-based automation and an AI-native ODA direction that includes a governed execution layer for AI agents.

Research disciplineOverlap is investigated before any standards gap or novelty is claimed.

Independence: this is independent research. No TM Forum affiliation, endorsement or redistribution of licensed model content is claimed.

TM Forum intent-based automation ↗ · AI-native ODA roadmap announcement ↗

WHY TWO DOMAINS?

Portability is tested by changing the domain, not the claim.

Transport regulation and telecom operations differ materially in vocabulary, authority structures, temporal behaviour and operational consequences. A common kernel is useful only where domain-specific meaning remains governed rather than flattened.

SharedKernel != SharedMeaning CrossDomainReference != CrossDomainAuthority Representation != Authority