Credible Source Template 1
Credibility sentence: [Source] is appropriate for [claim] because [relevant authority/provenance] and [evidence/method].
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Credibility is not a permanent badge attached to a domain or format; a source is credible for a claim when the source has relevant expertise or provenance, transparent support, appropriate methods, and enough context to justify that specific claim.
Credibility sentence: [Source] is appropriate for [claim] because [relevant authority/provenance] and [evidence/method].
Limitation sentence: The source is useful for [purpose], but it cannot establish [broader claim] because [limitation].
Authority check: [Author/organization] has relevant expertise in [field/context], demonstrated by [role/work/provenance].
Evidence check: The claim is supported by [dataset/document/method], which can be inspected at [source/location].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].