Evidence integrity
Public state is captured and retained before interpretation. Dated artefacts, manifests and provenance keep published claims traceable to observed evidence.
Inspect the evidence
Trust and transparency
Trust should be inspectable.
Digital trust is not a badge .auDO awards itself. It comes from evidence, method, stewardship, responsible operation and clear limits that readers can inspect for themselves.
Observable. Governable. Explainable.
The trust surface
Trust is a set of visible commitments, not a single claim
.auDO exists to make one layer of digital trust more observable. The same principle applies to the observatory itself: its evidence, operating method, dependencies, limitations and routes for challenge should also be visible.
Method transparency
The fixed panel, collection model, signal definitions, classification rules and interpretation boundaries are documented rather than hidden behind a score.
Read the methodologyIndependent stewardship
Scope, analytical method, language, publication timing and corrections remain under transparent editorial stewardship. Service providers do not direct findings.
Read about stewardshipResponsible operation
Privacy boundaries, security reporting, correction routes and use limitations are published so readers know how the observatory handles concerns and where its responsibilities stop.
Security and disclosureService transparency
Infrastructure dependencies are named and operational status is visible. Technical services support delivery but do not sponsor, approve or endorse the analysis.
View service statusInspect the operating model
Follow the part of the trust surface you need
These are distinct governance surfaces. They are linked here so readers do not need to infer how evidence, operation and accountability fit together.
Purpose and independence
Why .auDO exists, what it does not claim, who stewards it and how external service or commercial relationships are separated from editorial authority.
About .auDOMethod and architecture
How the panel is selected, public signals are collected, evidence is preserved, changes are classified and publication is bounded.
MethodologyPrivacy
How visitor request data, email enquiries and publicly visible domain-layer observation data are handled.
PrivacySecurity
How to report a security issue affecting .auDO-operated services, and the boundary between .auDO infrastructure and third-party domains it observes.
SecurityTerms and limitations
The interpretation limits and use conditions that apply to public observations, summaries, reports and guidance.
Terms / DisclaimerQuestions and corrections
Route general enquiries, research questions, publication corrections and other concerns to the appropriate contact path.
Contact .auDOTrust boundary
Confidence should remain proportional to the evidence
What .auDO can make visible
Repeated public domain-layer observations, preserved evidence, aggregate posture, visible change and carefully bounded analytical context across the fixed panel.
What .auDO cannot establish
Private-system state, organisational intent, control effectiveness, compliance, fault, compromise, whole-namespace posture or a complete measure of organisational trust.
No trust score
.auDO does not convert public signals into an organisational trust rating. Its role is to make evidence and change easier to inspect, not to collapse uncertainty into a grade.
A practical standard
The observatory should be held to the same principle it advocates
Digital trust should be observable, governable and explainable.
Where .auDO falls short of that standard, its methods, publications and operating practices should be open to challenge and correction.