Evidence protocol

Trace the claim to the strongest available source.

Technical reporting is only as useful as its source hierarchy, date control, limits, and translation from a specification to an operational consequence.

Source hierarchy

Research begins with primary sources: laws and official rules, regulator guidance, standards, government or academic research, technical documentation, manufacturer datasheets, and project records. High-quality secondary reporting can provide context, but it does not replace the underlying record when that record is available.

Currency and version control

Rules, proposed rules, software, product specifications, and program status are dated. A proposal is not described as a final rule. A research target is not described as achieved product performance. Software behavior is tied to a documented version when the distinction matters.

Comparison method

Comparisons start with the mission and decision criteria, then examine the complete system. Relevant dimensions can include environment, range, endurance, payload, latency, accuracy, integrity, interfaces, size, weight, power, compute, support equipment, staffing, recovery, and failure behavior.

A table is an editorial synthesis. Its cells must remain traceable to cited facts or clearly stated analysis. Product classes are not ranked when the evidence does not support a stable, general ordering.

Manufacturer information

Manufacturer sources are appropriate for current specifications, interfaces, supported features, and stated use. They are treated as manufacturer claims unless independently verified. Marketing language, ideal-condition performance, and compatibility claims are not repeated without the conditions needed to interpret them.

Source and asset records

Each launch article carries a machine-validated source registry. Editorial images have a local provenance record with creator, rights, source file, dimensions, alt text, and caption. Remote hotlinks and unverified demo media are not part of the production output.