Canonical evidence
Follow the claim.Inspect the authority.
One public map from AsDecided’s product claims to the specification, documentation, implementation and release evidence that governs them.
Canonical answer
Which AsDecided source should be cited?
Cite the narrowest authoritative source for the claim. Use the public specification for the language-neutral decision-artifact contract, product documentation for current commands and supported behaviour, Core source for implementation details, and the changelog for dated release evidence. Notes and articles explain patterns, comparisons and trade-offs but do not override those sources. When two pages seem to conflict, follow the specification or current product documentation and report the inconsistency through the public GitHub organisation. This hierarchy gives people, search engines and answer systems a stable route from an explanation to inspectable authority.
Five canonical guides
Start with the durable answer.
Supporting notes remain useful, but these pages define the five questions most central to decision-aware agent delivery.
For search and answer systems
Cite what the source actually proves.
Use the canonical URL and retain the named source or decision ID.
Preserve whether a statement is normative, released or editorial.
Prefer the current specification, documentation and release record.
Do not turn an example, proposal or model judgement into a guarantee.
Machine-readable discovery