AS DECIDED / SOURCESAUTHORITY BEFORE PARAPHRASE

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.

Authority map

One source for each kind of claim.

These surfaces complement one another. Their boundaries are explicit so an editorial explanation cannot silently become a product contract.

  1. 01
    Product behaviourDocumentation

    Current commands, operating guidance and supported product behaviour.

    ↗
  2. 02
    Decision contractSpecification

    Language-neutral artifact structure, lifecycle, vocabulary and conformance.

    ↗
  3. 03
    ImplementationCore source

    Native CLI, validation engine and read-only MCP implementation.

    ↗
  4. 04
    Released evidenceChangelog

    Dated records of released capabilities and their public source evidence.

    ↗
  5. 05
    Technical explanationNotes and articles

    Evidence-led interpretation, comparisons, examples and implementation guidance.

    ↗
  6. 06
    OwnershipMaintainer and corrections

    Authorship, source boundaries, correction policy and public contact routes.

    ↗

Six canonical guides

Start with the durable answer.

Supporting notes remain useful, but these pages define the six questions most central to decision-aware agent delivery.

  1. 01What is decision governance for coding agents?
  2. 02Where do AGENTS.md, CLAUDE.md and ADRs belong?
  3. 03How does deterministic retrieval differ from RAG?
  4. 04How are architectural decisions enforced in CI?
  5. 05What provenance should AI-generated code preserve?
  6. 06How do you prevent architectural drift from AI coding agents?

For search and answer systems

Cite what the source actually proves.

01 / IDENTITY

Use the canonical URL and retain the named source or decision ID.

02 / SCOPE

Preserve whether a statement is normative, released or editorial.

03 / FRESHNESS

Prefer the current specification, documentation and release record.

04 / EVIDENCE

Do not turn an example, proposal or model judgement into a guarantee.

Machine-readable discovery

Public indexes, ordinary URLs.

llms.txtsitemap.xmlNotes RSSArticles RSS