Current work
08
Private reference demonstrators
Selected internal synthetic testing and AI-assisted engineering support development of defined control behaviours and evidence handling.
Development and evidence / 17 September 2026
An explicit stage.
A reviewable proposition.
Private development and selected synthetic evidence provide a starting point for a bounded evaluation—not a claim of production acceptance.
To establish
Integration.
Performance.
Comparative value.
Production integration, enterprise-scale performance, independent security assurance and customer value remain to be established.
The website’s interactive scenario is explanatory presentation, not an operational control engine or measured product output.
02 / Evidence at its actual scope
Know what the result
does—and does not—show.
Described design
The proposed behaviours and development objectives. A description is not an implementation or an independently verified result.
Implemented demonstrator
Private reference work can illustrate selected behaviours in a controlled environment. Its scope, configuration and limitations matter.
Tested scenario
An internal test supports only the behaviour actually exercised and observed. A release test does not validate every lifecycle, fallback or recovery pathway.
Independent assurance
An external reviewer, defined scope, actual findings and completed acceptance are separate. No such assurance is claimed by this website.
03 / A scoped review
Ask a question
the evidence can answer.
A technical discussion can define the scenario, required behaviour, comparison, evidence inventory and reproducibility questions an evaluator would need to examine.
Sharing selected synthetic evidence or demonstrators requires a separate scope and permission. Public website contact provides no repository, source, prototype or implementation access.
Metrics should cover outcomes, unnecessary holds, end-to-end delay under load, review effort and full delivery cost. No transaction-capacity or percentile performance claim is made here.
Explore the comparison approach04 / Supporting objectives
Institutional control.
Long-lived verification.
Provider independence, sovereign deployability and cryptographic-transition continuity remain objectives requiring deployment-specific testing.
Reliable inputs, appropriate organisational rules and coverage of relevant action routes are prerequisites. A compromised source, inadequate rule or bypass can defeat the intended outcome.
The design does not establish legal compliance, universal model security, uninterrupted operation or permanently valid evidence.
Explore the resilience questions05 / Intellectual property
Patent-pending.
Evidence-led development.
The portfolio comprises six PCT applications and four Australian provisional applications. Applications are not granted rights; filed designs do not establish implemented performance or customer demand.
Public filing links will be added only against verified published records. No application-specific publication date is asserted here.
Start with a practical requirement
What would you need to see demonstrated?
Bring one workflow, one changing condition and the outcome that would make a difference.