White papers, reference architectures and technical briefs
Written for chief information officers, programme directors, procurement teams and the technical advisers who evaluate them.
Request access
Some documents are released on request so we know who holds our architecture material.
Contact usCapability statements
CAP‑01
Qcuboyds Corporate Capability Statement
Company overview, disciplines, methodology, certifications and programme experience. The document to attach to a pre-qualification response. [PLACEHOLDER — attach PDF]
CAP‑02
Systems Integration Capability — Discipline Sheets
Two pages per discipline: identity, biometrics, borders, PKI, health, cloud and network. [PLACEHOLDER — attach PDF set]
Reference architectures
RA‑01
National Digital Platform Reference Architecture
Foundational identity, functional layers, the enterprise integration layer and the shared national foundations beneath them. [PLACEHOLDER — attach PDF]
RA‑02
Vendor-Neutral Integration Layer — Design Patterns
API gateway, event bus, canonical data model, consent and audit, and the abstraction patterns that keep components replaceable. [PLACEHOLDER — attach PDF]
RA‑03
Offline-First Field Architecture
Deterministic reconciliation, conflict resolution rules and device attestation for environments without reliable connectivity. [PLACEHOLDER — attach PDF]
White papers
WP‑01
Why Technology Selection Should Be the Third Decision
The sequencing argument: mission, requirements, architecture, then technology — and what goes wrong when the order is reversed. [PLACEHOLDER — attach PDF]
WP‑02
Measuring Lock-In: A Practical Assessment Framework
A structured method for quantifying a government’s exposure to a single supplier across data, interfaces, commercial terms and knowledge. [PLACEHOLDER — attach PDF]
WP‑03
Biometric Accuracy in the Field vs. on the Benchmark
Why published accuracy figures rarely survive contact with a real population, and how to benchmark before committing. [PLACEHOLDER — attach PDF]
WP‑04
Designing for the Public Inquiry
Building national systems whose decisions, evidence and arithmetic remain defensible years after the staff who built them have moved on. [PLACEHOLDER — attach PDF]
Procurement aids
PR‑01
Writing a Vendor-Neutral Technical Specification
Guidance and clause examples for specifying an outcome without inadvertently specifying a product. [PLACEHOLDER — attach PDF]
PR‑02
Technology Evaluation Matrix — Template
Criteria, weighting and scoring structure, with worked examples for biometric matching and PKI selection. [PLACEHOLDER — attach spreadsheet]
PR‑03
Exit & Transition Provisions: A Drafting Checklist
The contractual provisions that preserve a state’s ability to change supplier, written to be adapted by government legal teams. [PLACEHOLDER — attach PDF]
Platform documentation
Documentation for our two proprietary platforms is handled by the respective programme offices, where each request is reviewed before release.
WP‑00
A Secure Voting System Using Encrypted QR Codes and Blockchain Principles
The STAR™ secure voting architecture in full: seven modules, cryptographic identity control, the write-once hash ledger, observer oversight, sealed finalisation, and a candid account of what the architecture does and does not prove. Published openly — no request required.
STAR
STAR™ Electoral Integrity Platform
Chain of custody, offline-first accreditation, reference architecture and the public verification API. Four white papers.
NVDIS
NVDIS™ Non-Intrusive Vehicle Document Inspection System
The executive summary is available to mandating authorities on request. Technical specifications — operational methodology, software architecture, security framework, communication protocols and implementation model — are proprietary and disclosed only under confidentiality arrangements.
1. Place approved documents in
assets/docs/ and update each
href. 2. Decide per document whether it downloads directly or is gated
behind the contact form — capability statements are usually open; architecture and
electoral material is usually gated. 3. Add a published date and version number to every
document so buyers can tell whether they are reading the current version.