3.3.1. Missing data policy

Missing data is treated as a risk signal, not neutrality.

• If data is missing and the absence itself is meaningful (e.g., treasury reporting), the report records that as a weakness.

• Where data is incomplete but partially usable, the report states what is missing, why it matters, and what conclusions are still safe.

Source expansion rule: If a chapter’s key question cannot be answered with Measured/Documented evidence, the workflow requires generating a Data Request Pack proposing new sources (dashboards, indexers, partner data, exchange indicators, dev telemetry, etc.) before final conclusions are written.

3.3.2. Bias controls for chat logs and stakeholder testimony

• Chat logs are Reported evidence by default.

• Do not generalize from loud minorities.

• Use chats to identify issues and stakeholder experience—not to “prove” measurable facts.

3.3.3. Conflicts between sources

Rely on Measured/Documented when possible. If unresolved, label as “contested/uncertain” and specify what data would resolve it.

3.3.4. Corrections policy (no update commitment)

This report makes no commitment to periodic updates.

If factual errors are found post-publication, errata may be issued limited to factual/calc/misattribution/clarification fixes.

In addition, the Primary Source Corpus register (3.1.2 + Appendix Sources Register) will be finalized at publication to reflect the complete set of evidence used.