Why Clarity
What actually is Clarity?
The product intelligence layer that sits above your PLM, ERP, MES, and requirements tools. Not a replacement for any of them — the structured decision record that none of them were designed to hold: what was decided, on what evidence, by whom, connected to the configuration it produced.
Who is it for?
The whole programme team — not just engineers. Programme managers, configuration managers, commercial leads, safety, risk, finance, and compliance all work from the same underlying programme model at the layer relevant to their accountability. No MBSE expertise required.
What problem does it actually solve?
The most expensive sentence in programme management is “we’ll need to reconstruct the original intent.” Clarity makes that sentence structurally impossible. Every decision carries its evidence chain permanently — retrievable in 2050 by people who were not in the room in 2026.
Is this just another reporting tool?
Decision support gives you better information before you decide. Decision intelligence makes the act of deciding itself an accountable, auditable, and structurally immutable record. The DeZolve truth vector computes live evidence coverage before the decision authority commits — so the decision is made with full visibility of what it is and is not based on. A reporting tool tells you what your data says. Clarity tells you whether your decision is evidenced enough to commit.
Why hasn’t a PLM vendor already built this?
A well-resourced competitor starting today cannot replicate any single element without the others already in place. The Lx chain requires 30 years of programme delivery knowledge to encode. Sovereign architecture requires zero vendor access to programme data — which ends the PLM vendor’s licensing model. PLM vendors cannot price down without destroying their existing revenue base. Clarity was built from the opposite direction: serverless-native, AI-native, with no legacy architecture to protect.
Existing Tools
We already have PLM — Teamcenter, Windchill, or similar.
PLM manages the product structure. It was never designed to hold the decision that produced that structure — what options were evaluated, what constraints applied, what the approval authority decided, and why. Clarity is the layer above PLM that holds that reasoning. Your PLM keeps doing what it was designed to do.
We have DOORS for requirements and SAP for procurement. Do we need to replace them?
No. Clarity sits above your existing tools via Diodes and Airlocks — policy-governed connectors that control what data crosses each boundary and in which direction. DOORS keeps managing requirements. SAP keeps managing procurement. Clarity builds the decision layer above them that none of them were built to provide.
We have Palantir for programme intelligence.
Palantir is rear-facing — it tells you what happened across your data estate. Clarity is forward-facing — it structures the reasoning at the moment a decision is being made, so evidence coverage is computed before commitment, not reconstructed afterwards. There is also a structural sovereignty difference: Palantir is US-controlled, which disqualifies it for sovereign 14 Eyes non-US programme intelligence requirements. Clarity is sovereign by architecture.
We already use SharePoint and Excel.
That is the de-facto situation for most engineering SMBs. The cost is measurable: 60–80% of engineering lead time in unstructured document management; no unbroken evidence trail from requirement to decision. Clarity automates what SharePoint and Excel do — and a great deal more. Same-day deployment, no systems integrator, first structured deliverable in hours.
We have cMRO or an EAM for maintenance records.
cMRO and EAM hold the maintenance records correctly — that is not in dispute. What they cannot hold is the design decision that constrains what the repair authority can and cannot modify. The connection between as-maintained reality and the design decisions that produced it does not exist in your maintenance system. Clarity provides that connection above them.
The Big 4 consulting firms already provide this kind of programme governance.
Consulting firms promote endless customisation of legacy systems — brittle, inflexible, and anchored to flawed business objects. The decision chain does not leave when the engagement ends, because it is in the programme model, not in a consultant’s report. Big 4 firms remain relevant as delivery partners for implementation and change management. What they cannot provide is a structurally immutable evidence chain that persists after the engagement ends, independently auditable without the original advisers being available.
The Bridge
What is “the bridge”?
Defence capability today spans two worlds: legacy programmes (AUKUS submarines, Hunter frigates, Collins Class — 30–40 year lifecycles, institutional accountability, PLM/ERP/MES/cMRO infrastructure) and new disruptors (next-generation sovereign manufacturers, software-defined platforms, modular systems built at speed). Clarity sits above both as the product intelligence layer — so fast manufacturers can carry the accountability legacy programmes require, and legacy programmes can access disruptor speed without abandoning institutional accountability.
Legacy programmes are inherently slow. Doesn’t Clarity just add more process?
Legacy programmes are not inherently slow — they are made slow by the reconstruction tax: having to reconstruct context every time a decision is needed, because that context lives in retiring engineers’ heads and disconnected document stores. Clarity removes the reconstruction tax. There are no workflow gates, no mandatory process steps, no approval queues built into the platform. You move as fast as your data will allow you — the only constraint is the quality of the evidence you bring, not the system’s tolerance for your pace. When institutional knowledge is in the programme model rather than in people’s heads, the programme moves at the speed it should naturally operate at.
We’re a fast-moving manufacturer. This sounds like legacy bureaucracy.
Your speed is an asset. The question is whether your products can carry the accountability the programmes you integrate into require — without slowing you down. A subsystem integrated into a Hunter frigate still needs a 30-year certification record. Clarity creates that record at the point of integration without requiring you to adopt legacy tooling or change your development model. This approach has been proven at Amazon scale — where product provenance, configuration traceability, full lifecycle configuration management, and decision accountability operated at a speed and volume that legacy PLM was never designed to reach. Fast is not the problem. Untraced is.
How is Clarity different from what Anduril is doing?
Anduril lets the warfighter move at speed. Clarity gives the warfighter the confidence that what they receive is fit for purpose — that the configuration is correct, the decision chain is intact, and the evidence is there when accountability is required. These are complementary, not competing. Where Clarity changes the equation for capability owners and the supply chain is the Speed of Slow Work bypass: the reconstruction tax, the document round-trips, the “let’s establish what is actually fitted before we start” delay that precedes every modification programme — these are the frictions Clarity removes. The warfighter gets speed from Anduril. They get confidence in what they are operating from Clarity.
Doesn’t the bridge positioning threaten the PLM vendors?
No. PLM vendors are below Clarity and are not displaced — they become a data source for the layer above them. Consulting firms remain relevant as implementation partners. Disruptors need Clarity to work at programme scale and speed. The one genuine parallel competitor is Palantir: rear-facing analytics vs forward-facing decision intelligence, US-controlled vs sovereign by architecture. The bridge position threatens no one except a US-controlled analytics platform that cannot occupy the sovereign role.
For Our Stakeholders
What does the programme sponsor or CASG get from Clarity?
Structured views of delivery configuration, upgrade pipeline, and operational status — independent of what the prime chooses to report. Audit readiness as a permanent state, not a documentation exercise before the review. Programme knowledge that belongs to the government, not the vendor or the contractor.
What does the Sustainment Director get?
A live L10 As-Operated baseline connected back to L7 As-Built and L9 As-Deployed — so the configuration the maintainer is working against reflects what is actually fitted, not what was delivered. When a modification programme starts, the L11 As-Updated record provides the starting-point configuration. When a field modification happens, it flows into the programme record via Diodes rather than accumulating as silent drift against a baseline that no longer matches the platform.
As a Tier 2/3/4 supplier, can we afford this?
One AUKUS contract at AUD $2–10M covers multiple years of Clarity licensing. The cost of being unable to produce a traceable evidence pack is the bid itself — typically $70K–$280K per failed submission. Clarity deploys same-day, without a systems integrator. The onboarding cost does not exceed the margin on the first contract it enables.
Our engineers will resist another tool.
Clarity automates the connections that engineers cannot make manually and do not want to — cross-layer traceability, evidence coverage scoring, configuration drift detection, and impact analysis across a programme model that no individual can hold in their head. The question is not whether engineers will adopt another tool. It is whether they want to keep doing by hand what Clarity does automatically. For the wider programme team — programme managers, configuration managers, risk leads, commercial, compliance, and governance — Clarity gives them direct access to the programme model without going through an engineering intermediary. No SysML expertise required. No specialist modeller. Plain English and uploaded documents produce structured, traceable outputs.
Security & Sovereignty
Can we use Clarity with classified programme data?
For classified deployments: Clarity runs in your AWS account, in your jurisdiction, encrypted with your KMS keys. Air-gap capable — no outbound connectivity required. Clarity has zero access to your programme data. Bring your own AI model — Clarity’s AI provider is configuration, not code, so sovereign or air-gapped deployments supply their own approved model endpoint rather than routing to a commercial API. Designed to be 14 Eyes compliant by architecture, not by documentation — three independent enforcement layers independently auditable by ASD or a DISP-accredited assessor without trusting the vendor’s word.
How is sovereignty enforced — not just asserted?
Clarity runs entirely within your chosen AWS region — no routing to US endpoints, no third-party services calling home to Slack, GitHub, Atlassian, or any external platform. Even our support and update pipelines run from your chosen AWS region. Every request stays inside your sovereign boundary. Three independent enforcement layers — IAM inline deny, S3 bucket policy, and schema-level classification enforcement — are each auditable without reading application source code. An application bug cannot bypass IAM. An IAM misconfiguration cannot bypass S3. Any two can fail simultaneously and the third still enforces the boundary. That is not achievable by adding security features to a legacy product built on US-routed third-party dependencies. It requires building the product around the boundary from first principles — which is what Clarity did.
What happens to our data if Clarity stops operating?
Your programme state is stored as open-format JSON in S3 under your account and your keys. Readable without Clarity’s continued operation, by any authorised party, at any future time. No vendor dependency for access, licensing, or continuity. Open data format — your records remain structured and auditable across the full platform life, outlasting any individual technology. AUKUS · Five Eyes · 14 Eyes · Air-Gap Ready · ASD ISM pathway. No incumbent can make this claim without ending their own revenue model.
We have ITAR and export control obligations on cross-border programme data.
Export control enforcement is structural in Clarity, not procedural. Classification is a typed field at every data layer. The Diode pattern makes write-back structurally impossible at the IAM and bucket policy level — not configured away. The Airlock pattern requires documented approval from both parties before data crosses any boundary; either party can suspend instantly; the connector fails closed on infrastructure failure. A bilateral audit trail records every exchange — neither party can forge or deny it occurred.
We’re concerned about US control of the software supply chain.
Clarity is an Australian-operated sovereign product. For Australian, UK, and Five Eyes non-US sovereign requirements, an Australian-operated product intelligence layer that is not US-controlled has a structural market position that no US-controlled vendor can replicate. Sovereignty is architectural — your account, your keys, your jurisdiction — and independently auditable. Clarity runs entirely within your chosen AWS region: no routing to US endpoints, no third-party services calling home to Slack, GitHub, Atlassian, or any external platform. Even support and update pipelines run from your chosen AWS region. There is no point in the stack where your programme data leaves your sovereign boundary.
For AWS APN Partners & ProServe
Why should an AWS account team bring Clarity into a defence or public sector opportunity?
Clarity is the product intelligence layer that sits above the legacy systems AWS customers cannot easily replace — PLM, ERP, MES, cMRO — and connects them across the full programme lifecycle without requiring migration or rearchitecture. The integration mechanism is Clarity Diodes and Airlocks: isolated transit factories that extract, classify, and deliver structured data across system and sovereignty boundaries without exposing either side to the other. Legacy systems stay running. Clarity builds the connected decision record above them. AWS handles where workloads run. Clarity handles whether the decisions that govern those workloads are traceable, auditable, and sovereign — from stakeholder intent at L0 through to disposal at L12, across every supplier and contractor in the programme.
What AWS services does Clarity run on?
IAM, KMS, S3, Lambda, EventBridge, Bedrock, Amplify, DynamoDB, CodePipeline, WAF, ACM, CloudWatch, and CloudTrail — or a customer-supplied AI model or SageMaker endpoint for air-gapped deployments. Every component is AWS-native and runs within the customer’s account. No shared tenancy, no routing outside the customer’s sovereign boundary, no Clarity-managed infrastructure to explain to a security authority. 14 Eyes compliant by design using 100% AWS services — making Clarity straightforward for account teams to position alongside existing AWS public sector and GovCloud architectures.
Where does Clarity fit alongside a ProServe transformation engagement?
ProServe drives the migration and modernisation. The persistent gap is programme decision loss — the decisions made during the transformation that disperse when the engagement ends. Clarity overlays governance: decision evidence stays in the customer’s environment after ProServe leaves. It is an accelerator for transformation programmes, not a competing delivery model. ProServe and ATO partners are ideally placed to build and maintain Clarity Diodes and Airlocks — the isolated transit factories that connect legacy systems to the Clarity product intelligence layer — embedding that integration work as a durable programme asset rather than a one-time deliverable. The ProServe team gets a repeatable outcome story; the customer retains the institutional knowledge the engagement produced.
How does Clarity align with AWS NatSec priorities?
AWS NatSec priorities — decision advantage, data mastery, sovereignty, AI governance, mission velocity — map directly to what Clarity delivers. Decision advantage through structured evidence chains before commitment. Sovereignty through customer-account, customer-keys, no-external-routing architecture. AI governance through typed provenance at every data layer. Mission velocity by bringing speed to slow work — removing the reconstruction tax that grounds programmes before they start. Clarity is not infrastructure competition — it is the decision intelligence layer that makes AWS-hosted mission systems accountable, auditable, and sovereign by design.
What is the co-sell opportunity?
Defence primes and Tier 2–4 suppliers entering the AUKUS industrial base. Government programme offices requiring full lifecycle configuration management and decision accountability across contractor supply chains. Sustainment organisations needing connected as-built to as-maintained configuration traceability. Next-generation sovereign manufacturers interfacing with legacy programme baselines. Clarity sits above their existing tools wherever those tools are hosted — on-premises, cloud, or air-gapped — accessing only the data it needs via Clarity Diodes and Airlocks. ASD ISM pathway, AUKUS, and Five Eyes classification requirements met by design.
How is Clarity different from the large SIs AWS also partners with?
Large SIs deliver transformation programmes on engagement models that depend on ongoing teams. The capability they build often disperses when the team rotates out. Clarity is software, not a services engagement — the decision chain does not leave when the project ends. Open data format — your records remain structured and auditable across the full platform life, outlasting any individual technology. For select customers, Clarity offers white-glove onboarding and rollout support — working directly alongside the programme team to establish the product intelligence layer, configure Diodes and Airlocks, and ensure the first structured deliverables land before the engagement hands over. AWS account teams can position Clarity as the persistent layer that makes SI-delivered transformations durable: the governance infrastructure that outlasts any individual engagement and gives the customer something to show a parliamentary inquiry or certification authority in 2040.
Have a question that isn’t here?
Request a Strategic Briefing — 30 minutes with the founder. Direct conversation, no sales process.