Guide Evidence, Verification, and Known Limitations
Guide Evidence, Verification, and Known Limitations
Overview
This guide will help you understand which guide claims are source-confirmed, system-confirmed, database-confirmed, or awaiting product-owner confirmation.
Readers and maintainers can distinguish documented evidence from unresolved behavior.
Who can do this
You need access to None to read; executing check cases requires the relevant application and environment authority.
Before you start
Know the target version/build/channel/database revision and whether you are using production, test, or documentation data.
Where to find it
Help Center → Troubleshooting & Reference; internal maintainers use docs/source-coverage-ledger.md and phase analysis files.
Guide Evidence, Verification, and Known Limitations
Step 1: Treat Source-confirmed as behavior established by active code paths
Step 2: Treat Runtime-confirmed as observed safely on the target build
Step 3: Treat Database-confirmed as reconciled persistence, relationship, or posting evidence
Step 4: Treat Product-owner-confirmed as resolved intent/availability/version policy
Step 5: Read each draft warning and prerequisite before following it
Step 6: Do not use unverified financial, stock, tax, sync, restore, or
Do not use unverified financial, stock, tax, sync, restore, or deletion claims in production.
Check your work
Every published claim maps to evidence in the coverage ledger and unresolved discrepancies remain visible in editorial findings.
If something goes wrong
Related guides
- Version, Build, Database Revision, and Release Notes Reference
- Hidden, Deferred, Legacy, and Development-Only Features
- Data Safety, Privacy, Backup, and External-Effects Reference