Source Policy

Dev Error DB prefers public, durable, developer-relevant sources. The best references are official documentation, public issue trackers, release notes, changelogs, vendor status or support pages, and reproducible public examples.

How sources are used

Sources are used to confirm that an error signature or failure pattern is real and to shape the debugging checklist. The site should not copy source text wholesale, claim endorsement, or stretch a source beyond what it supports.

Evidence labels

Dev Error DB derives page evidence labels at build time from existing Markdown records. A source-backed page has public URLs under a Sources checked section. A partial-source page has public URLs but lacks a complete source block. A general guidance page has no public source URL in the current record. A needs-source page has a source section without a usable public URL.

These labels are metadata for reader caution, not a guarantee that a fix is correct for every version, provider, account, or deployment environment.

Missing evidence

If a page lacks source-backed detail, the template should either omit the unsupported section or label the guidance as general troubleshooting. It should not display empty source lists, null values, or invented references.

Corrections

Send source corrections to contact@dev-error-db.com. Include the page URL and the public source that supports the change.