What was actually observed?
Identify the visible signal, the observation date or defined window, and whether the evidence describes the fixed panel, a published cohort lens or another explicitly stated scope.
How to read a .auDO observation
.auDO records what was publicly visible at a point in time or across a stated observation window. An observation can show visible change, persistence or an aggregate pattern. It does not, by itself, explain why something happened or establish risk, effectiveness, compliance or intent.
Reading model
Ask three questions before adding meaning
Use a simple sequence: Observe → Scope → Compare → Describe cautiously. The aim is not to avoid interpretation, but to keep the interpretation proportionate to the public evidence.
Is it one observation or a pattern?
One observation records what was visible at that time. Repeated evidence can support stronger description, but it still does not establish cause or internal operation.
What does the evidence not tell me?
Public signals do not establish cause, approval, effectiveness, compliance, harm, intent or organisational governance quality on their own.
Keep the scope attached. Unless explicitly labelled as wider namespace context, .auDO observations describe the fixed Observation Panel or a published cohort lens, not the whole .au namespace.
Worked example
Reading a real name-server change
A retained observation from beyondblue.org.au shows how to move from visible DNS change to a proportionate reading without inferring cause or internal intent.
This is a real retained observation. The name-server values below are the public DNS values captured by .auDO. The provider labels are derived provider-resolution context and should not be read as proof of a contractual or direct customer relationship.
Earlier retained state
Delegated name-server set
ns0.telstra.net
ns1.telstra.net
Derived provider contextTelstra
Later retained state
Different delegated set
dns1.cscdns.net
dns2.cscdns.net
Derived provider contextCSC / Enterprise DNS
Observed change
.auDO recorded the delegated name-server set changing from ns0.telstra.net / ns1.telstra.net to dns1.cscdns.net / dns2.cscdns.net on 28 August 2026. In the same observation cycle, provider resolution changed its derived DNS-provider classification from Telstra to CSC / Enterprise DNS.
Reasonable reading
.auDO observed a public delegation change for beyondblue.org.au: authority moved from the retained Telstra-named name-server set to the retained CSC DNS name-server set.
Possible context, not conclusion
Taken with the same-cycle provider-resolution change, the evidence is consistent with a DNS authority or provider migration at the public delegation layer. It does not establish the internal reason, project scope or commercial relationship behind that change.
Not established
Public evidence does not show why the change occurred, whether it was planned, whether service was affected, or what approval, governance or internal process sat behind it.
Dated evidence
The date is part of the claim. Link the interpretation back to the retained 28 August observation so a reader can distinguish this example from a generic scenario.
Compare next
Use the direct signal definition first, then compare related provider context and dated evidence before adding further meaning.
Find the right context
Use the surface that owns the next question
The Observation Guide is a reading aid. Follow the evidence into the part of .auDO that owns the detail you need.
Signals
Understand what the evidence represents, how it is observed or derived, and its interpretation limits.
Explore SignalsState and cohorts
Place an observation in current aggregate context across the fixed panel or a curated analytical lens.
Reports
Inspect dated evidence, observed movement and longitudinal reporting across defined windows.
Read reportsMethodology
Understand collection, evidence layers, derivation rules, limitations and method governance.
Read MethodologySome derived State views use their own evidence classifications. Read the relevant State page for the definitions and limits that apply to that analysis.
Once a public observation is understood, the Domain Governance Baseline can help frame internal ownership and accountability questions that public evidence cannot answer.