Captures public state
Each run preserves visible domain-layer posture before report language or interpretation is applied.
About .auDO
An independent public-interest observatory preserving public evidence of visible change across a fixed panel of .au domains.
Start with why the observatory exists. How to use it, stewardship and independence, and project history remain available as separate reader paths.
Purpose
Why .auDO exists
.auDO exists to make an important but difficult-to-see domain trust layer more observable, explainable and useful without turning public signals into scores, allegations or claims they cannot support.
It independently observes public domain-layer signals across a deliberately stable panel, preserves evidence of visible change over time, and publishes bounded summaries that keep observation separate from interpretation.
Compares change
Repeated snapshots make movement, persistence, gaps and recurring patterns easier to inspect over time.
Publishes cautiously
Reports, State pages, cohort views and explainers distinguish retained evidence from analytical context.
Boundaries
A fixed-panel evidence resource, not a rating system
The fixed panel supports repeated observation of the same domains. External auDA registry statistics provide namespace-scale context only; they are not .auDO observation evidence.
- Population
- A deliberately stable observation panel, not whole-namespace measurement or a statistically representative sample.
- Evidence
- Public DNS, registration, mail and infrastructure signals only; .auDO does not inspect private systems.
- Purpose
- Longitudinal evidence and explanation, not registry authority, regulation, audit, assurance, certification or real-time incident monitoring.
- Claims
- No whole-namespace prevalence, organisational risk, compliance, compromise, fault or internal governance quality is inferred from the public evidence alone.
The Observation Panel owns current population and stewardship detail. Methodology explains collection, preservation, classification and interpretation boundaries.
How to use .auDO
Begin with the question you are trying to answer
The public site separates current posture, dated evidence, research questions, signal definitions, method and published uses so readers can enter at the layer they need.
What is visible now?
Use State of .au for derived summaries of the current visible posture of the observed panel.
What changed, and when?
Use reports for dated evidence records, monthly briefs, quarterly reviews and featured analysis.
What are we trying to learn?
Use the Research Agenda for the standing questions against which longitudinal evidence accumulates.
What does a signal mean?
Use the Signals library and explainers for canonical definitions, interpretation boundaries and plain-language context.
How is the evidence produced?
Use Methodology for panel scope, collection, preservation, architecture, classification and publishing controls.
How is .auDO used and cited?
Published uses show substantive research and analysis; media and research resources provide approved descriptions, citation guidance and identity assets.
Stewardship and independence
Independent operation with transparent service dependencies
External funders, clients, partners, providers and observed organisations do not direct .auDO's scope, method, findings, language, publication timing or corrections.
Stewardship and editorial authority
.auDO was founded and is stewarded by Bryan Chetcuti, who holds final responsibility for scope, analytical method, signal selection, publication timing and corrections.
Commercial separation
Advisory work undertaken by Bryan Chetcuti or The Vigo Group is structurally separate and does not purchase access, priority or influence over .auDO observations or publications.
Operational support and service dependenciesImportant operating relationships remain public without dominating the first read.
Operational support. Operational services and project costs are provided by The Vigo Group as an in-kind contribution under a replaceable arrangement that confers no governance or editorial authority.
Infrastructure services. Supabase, GitHub and Cloudflare provide technical services for storage, automation, preservation and delivery. They do not sponsor, review, approve or endorse the observatory's analysis.
Accountability
Go deeper where the responsibility sits
Trust and transparency
How evidence integrity, method transparency, stewardship and service transparency fit together.
Security
How to report issues affecting .auDO-operated services and where the observatory's security responsibility stops.
Privacy and terms
Visitor-data handling, enquiry handling, public-observation boundaries, use limitations and disclaimer terms.
Contact
Questions, corrections, research enquiries and collaboration proposals can be routed through the public contact pathways.
Project history
A sparse provenance record
Milestones are recorded when they materially change how the observatory's maturity or evidence history should be understood. This is not a feature changelog.
Concept and design begin
.auDO concept and design work began in February 2026, establishing the public-interest observatory model before retained repeated collection commenced.
Repeated observation begins
Repeated data collection began on 26 March 2026, which is the start of the retained reporting baseline used for longitudinal analysis.
Six months of retained observation
26 September 2026. Repeated data collection began on 26 March 2026. Six months later, .auDO has established a retained longitudinal evidence base across its fixed 100-domain Observation Panel.
The milestone records continuity of observation. It does not change the Observation Panel, Public Methodology or interpretation boundaries. Longitudinal interpretation remains with periodic reporting, including the first July-September 2026 Quarterly Trust Signals Review.