MoreBC2 Writing Checklist

StatusFramework

Use this checklist before committing documentation changes.

Category

• The page has the correct category: Documentation, News, Research, Discussion, or History.
• The page is in the correct folder.
• The page status is clear: Draft, Framework, Partial, Needs Review, Reviewed, or Verified.
• Historical or superseded material is explicitly identified so it cannot be mistaken for current information.

Naming

• Uses BitcoinII for the project name.
• Uses BC2 for the ticker.
• Uses BitcoinII Core for the reference node/wallet software.
• Avoids Bitcoin2 unless quoting or documenting historical third-party usage.

Verification

• Technical claims have sources.
• Primary sources are used where possible.
• Community discussion is not presented as implementation.
• Research is not presented as current behavior.
• Historical content is labeled as historical.
• Uncertainty is stated plainly.

Sources

• Source links are included.
• Date reviewed is included.
• Source type is understood: source code, release, website, explorer, developer statement, community discussion, or third-party summary.

Tone

• Plain language.
• No price hype.
• No investment advice.
• No unsupported marketing claims.
• No unnecessary drama.

Structure

• Page answers: what is it?
• Page answers: why does it matter?
• Page answers: how does it work?
• Page answers: where can it be verified?
• Verification block is complete.

Before marking Verified

• Checked against the strongest available source.
• Reviewed for naming consistency.
• Reviewed for category placement.
• Reviewed for outdated assumptions.
• Open questions are listed rather than hidden.