The problem you are accountable for
A government programme sponsor commits funding over decades. Delivery status, operational readiness, upgrade progress, and sustainment cost all flow upward as reporting — narratives prepared by the prime, reviewed by the programme office, consolidated into briefing packs. The information is accurate as far as it goes. It is also presented through the prime’s lens, at the level of detail the prime has chosen to surface, and in the format the prime’s reporting process produces.
When Parliament asks why a decision was made, or an inquiry examines a cost overrun, or a partner nation asks for assurance that the sovereign programme record is independently held — the answer cannot be “the contractor prepared a document.” The programme knowledge must be in a system the government controls, in a format that does not depend on the continued cooperation of the organisations that delivered the work.
Three structural problems follow:
Contractor-mediated visibility
Programme status is what the prime has chosen to report. Not what the programme record contains.
Delivery status, configuration state, and modification progress all arrive as reporting artefacts — formatted, summarised, and filtered through the prime's programme management process before they reach the sponsor. The structured record beneath the report — what was actually delivered, what is currently fitted, what decisions were made and why — is in the prime's systems, not yours.
Knowledge sovereignty gap
When the contract ends, the programme knowledge the contractor holds leaves with them.
The accumulated engineering decisions, trade studies, configuration rationale, and modification history of the programme exist in contractor-operated tools under licensing arrangements that expire when the contract does. The government holds data sovereignty. It does not hold knowledge sovereignty — the reasoning behind the programme's most consequential decisions, in a system the government controls, accessible to successors and accountability bodies regardless of which contractors are no longer operating.
Audit as a reconstruction exercise
Every formal review requires documentation preparation. The evidence chain is assembled for the inquiry, not retrieved from a live record.
When a programme review is called, or a parliamentary committee asks questions, or a partner nation requests assurance — the programme office prepares documentation. The effort is not in holding the evidence; it is in reconstructing it into the format the review requires. More oversight of a structurally flawed process produces more audited evidence of structural failure. It does not address the cause.
What Clarity provides
Structured programme views — lightweight, role-appropriate, independent of contractor narrative. Programme sponsors, capability managers, and oversight bodies access Clarity through views scoped to their accountability level. Delivery configuration: what was contracted versus what was delivered, at configuration item level. Upgrade and modification pipeline: what changes are approved, in progress, and closed, with their decision records. Operational status: the current as-maintained configuration against the as-delivered baseline. These are not reports — they are live views of the programme record that the prime and sub-contractors are operating in.
Knowledge sovereignty by architecture. Clarity runs in a government-controlled AWS environment, encrypted with government-held KMS keys, in the sovereign jurisdiction. The programme record — every engineering decision, its evidence chain, its options considered, its approval authority — is owned by the government, not by the vendor or the prime. When a contractor transitions, the knowledge they accumulated under the contract remains in the government’s programme record. The new contractor does not begin from blank paper.
Audit readiness as a permanent state — not a documentation exercise. When Parliament asks why a decision was made, the answer is a navigation through the live programme record — not a reconstruction from artefacts. When a programme is scrutinised by an inquiry, or a partner nation requests assurance, the evidence chain is present and retrievable without preparation. The sponsor does not need to request a report from the prime. The record is there.
Contractor access scoped to programme accountability. Prime contractors and sub-contractors operate Clarity within their designated scope. The programme office has a structured view across all contractor work, at the level of detail and classification their role warrants. No contractor can see another contractor’s work unless the programme office has explicitly granted access. No contractor departure removes data from the programme record. The programme knowledge belongs to the programme.
Visibility into what is being funded
The most expensive programme failures are the ones where nobody can answer why a decision was made. Every time the answer is “we will need to ask the prime to reconstruct the original intent” — that is a cost. Multiplied across a 30-year platform life, across dozens of major decisions, across contractor transitions, it is a very large cost.
The decisions being made today about a capability that will be in service until 2055 will be questioned by future programme sponsors, by accountability bodies that do not yet exist, by partner nations whose requirements will change. Clarity ensures those decisions are in a system the government controls — as a record, not a reconstruction.
“Knowledge that is not in a system the government controls is not sovereign.”
Programme accountability infrastructure for the decisions that will be questioned in 2045.
Clarity’s three independent enforcement layers — IAM inline deny, S3 bucket policy, and schema-level classification enforcement — are each independently auditable by ASD or a DISP-qualified assessor without reading application source code. For classified programmes: AWS Australia air-gapped regions, no outbound connectivity required, government-held KMS keys, zero Clarity access to programme data.
The programme knowledge of a sovereign capability belongs to the Commonwealth — by architecture, not by vendor promise.