Reading AARO: an analytical guide to what the office says and doesn't

AARO operates with two distinct epistemological postures that get conflated in popular write-ups. The first is the *case-disposition* posture: when AARO reviews a specific reported incident, it commits only to a categorical assessment — typically 'resolved' (identified to a specific conventional cause), 'unresolved' (data insufficient to identify), or 'case open' (under active analysis). The office will not, in case-disposition mode, speculate about any phenomenon class.

The second is the *programmatic* posture: when AARO speaks about UAP as a phenomenon class — in its Historical Record Report, in its Annual Reports to Congress, in director-level testimony — it makes evaluative claims about the categorical state of the evidence. These claims are bounded by the office's analytical conventions but are noticeably more cautious than the per-case dispositions. The Historical Record Report Volume I's overall finding ('no verifiable evidence that any UAP has represented off-world technology') is in programmatic mode, not case-disposition mode.

Conflating the two leads to predictable confusion. AARO saying 'this specific case is unresolved' is not AARO saying 'we are agnostic about the phenomenon class.' AARO saying 'no verifiable evidence of off-world technology' is not AARO saying 'no case in our archive is unresolved.' Both statements coexist in the published record without contradiction inside AARO's analytical frame.

AARO's published case-resolution criteria require a categorical identification matched to a documented cause: a specific aircraft type with a flight track that overlaps the observation window, a balloon launch with a documented release point and trajectory, a meteor with a corresponding observation network or seismic signature, a satellite re-entry with a documented orbital decay, or a hardware-malfunction signature consistent with the sensor platform.

What AARO does *not* allow itself in 'resolved' is what one might call narrative resolution — the identification of a plausible mundane cause that fits the report but cannot be matched to specific corroborating evidence. The office's analytical convention is that an unmatched plausible cause leaves a case in 'unresolved,' not 'resolved.' This is stricter than what most popular UAP write-ups use as their threshold and is part of why AARO's resolved-case rate is lower than headline coverage often implies.

The current published resolution rate (per the FY2024 Annual Report) sits at approximately 50% of cases initially reported. That number does not mean the other 50% are non-conventional. It means the office's evidence standard for 'identified' has not been met. There is a sizable analytical gap between 'not identified to the satisfaction of AARO' and 'inexplicable in conventional terms,' and AARO does not publish per-case detail at a granularity that would let an outside reader collapse that gap themselves.

The most-quoted line from the Historical Record Report Volume I — 'AARO has found no verifiable evidence that any UAP sighting has represented off-world technology' — is a careful sentence and rewards careful reading. Three terms do work: 'verifiable', 'evidence', and 'off-world technology'.

'Verifiable' is the constraint that the underlying claim be testable against independent records — declassified DoD logs, sensor archives, contemporaneous reports — without reliance solely on individual testimony, regardless of how credible the witness. This excludes a substantial class of claims that have been publicly made by named former officials but where the supporting records remain classified or have not been independently authenticated.

'Evidence' is used in the analytical-tradecraft sense — material that, on its own, would carry an inference. Claims of secondhand briefings or program-existence assertions do not, in this register, constitute evidence; they constitute reports of evidence, which is a different category that AARO handles separately under its whistleblower-intake function.

'Off-world technology' is the narrowest possible framing. It excludes a number of adjacent hypothesis classes that the same review process could in principle examine: human-origin black programs not yet publicly attributed, sensor-physics artefacts not yet characterised, atmospheric phenomena outside current meteorological models, and so on. The sentence as written does not address any of those.

What the sentence is, in effect, is a narrow disclaimer about one specific hypothesis class, conducted under a specific evidentiary standard, in a specific documentary corpus. That is a meaningful statement. It is not the unconditional disclaimer it is sometimes read as.

AARO's release cadence — what gets published when — is itself part of how the office communicates. Per the FY2024 Annual Report and the EFOIA Reading Room rhythm, the office publishes (a) the annual congressional report each January, (b) Historical Record Report volumes on a roughly two-year cadence, (c) individual case-resolution statements ad hoc as cases close, and (d) cleared-imagery additions to the public Official UAP Imagery library as material is declassified.

The release velocity tells the careful reader what AARO is prioritising. The Historical Record Report Volume I emphasised the long historical chain (Sign through AAWSAP) and the negative finding on off-world technology. The FY2024 Annual Report emphasised case-resolution methodology and the integration of the civilian-aviation pipeline. The cleared-imagery cadence has emphasised resolved-case footage over unresolved-case footage by roughly four-to-one. None of those emphases is accidental, and each carries an institutional signal that supplements the document text itself.

Three practical heuristics. First, separate case-disposition statements from programmatic statements before drawing inferences. Two statements in the same paragraph may be in different analytical registers. Second, treat every qualifier — 'verifiable,' 'currently,' 'within the dataset reviewed' — as a substantive constraint, not boilerplate. AARO's analytical conventions make qualifiers load-bearing. Third, attend to what the document does not address; the structural absences carry as much signal as the explicit content. A document that resolves a specific case without engaging the question of whether the case was correctly assigned to AARO's portfolio in the first place is saying something about scoping decisions that are themselves part of the modern UAP record.