AX4 Operational Transformation — Designing the Boundaries

Challenge

A regulated field-service workflow produces several legitimate kinds of truth: commercial job state, client access, field evidence, sample records, approved register data, issued documents and delivery state. Early digitisation made a deeper problem visible: forcing all of those concerns into one universal application or database creates duplication, ambiguous ownership and unsafe hand-offs.

Dane’s role

Led the system direction for progressively digitising and integrating the operating workflow. Mapped which system should own which kind of truth, separated workflow surfaces from authoritative state, decomposed changes into bounded technical work, and used review and evidence to decide what could be accepted. The programme became an early proving ground for the source-of-truth, authority and verification principles later reused across other AI-assisted builds.

Architecture and operating model

• Separated operational/commercial state from client identity, access and delivery concerns
• Kept field evidence capture as a specialist bounded function rather than a universal database
• Separated document rendering from technical approval, issue and publication authority
• Established controlled handling for issued artefacts and current-version state
• Used workflow surfaces without allowing the interface itself to become a competing source of truth
• Introduced explicit human review, evidence and acceptance boundaries around AI-assisted implementation

Operational foundation

Before the register and QR layer, I helped design and refine AX4’s client-intake and market-intelligence systems. Months of testing and enquiry analysis were used to identify where the market was underserved, sharpen our positioning and guide the longer-term strategy. That foundation informed the broader operational build connecting intake, controlled evidence, reporting and service delivery.

• Client-intake funnel design and iterative refinement
• Market-intelligence and feedback systems for enquiry capture
• Testing and enquiry analysis informing positioning, targeting and longer-term strategy
• Intake, evidence, reporting and delivery connected as one operational architecture

Controlled Register & QR Access

As part of the AX4 operating-system transformation, I directed the design of a controlled compliance-register delivery layer that separates operational records, portal authority and issued-document state. The working pilot supports current and superseded register versions, controlled client access, QR-mediated register retrieval, token lifecycle controls and access logging, while preserving explicit authority over what constitutes the current issued record.

• Current and superseded register-version controls
• Controlled client access to approved register information
• QR-mediated retrieval with bounded token lifecycle controls
• Access logging and audit visibility
• Separation between operational truth, portal and access authority, and issued-document state
• Human-controlled publication and current-version authority

Delivery status

• Operational

  Client-intake and market-feedback foundation.

• Working pilot

  Hosted register database and QR-controlled external access. External access has been tested; final proofing and production refinement are still underway.

• In development

  Internal accounting workflow, automated report generation and a repeatable software-delivery process.

What this demonstrates