MoreBC2 Documentation Philosophy
MoreBC2 exists because useful ecosystems need memory.
Discord conversations move fast. Social posts disappear. Links break. People forget why decisions were made. New users ask the same questions because answers are scattered across chats, repositories, explorers, release pages, and old screenshots.
MoreBC2 turns scattered knowledge into organized knowledge.
Documentation is infrastructure
Section titled “Documentation is infrastructure”Infrastructure is not only code.
Documentation, source registries, style guides, verification rules, templates, and contribution processes are infrastructure too. They make it easier for users to learn, developers to build, miners to participate, and service providers to integrate.
MoreBC2 explains, but does not define
Section titled “MoreBC2 explains, but does not define”MoreBC2 does not define BitcoinII.
BitcoinII source code, official releases, and official project resources remain authoritative. MoreBC2 exists to help people find, understand, and verify those sources.
Facts and ideas both matter
Section titled “Facts and ideas both matter”Facts and ideas both deserve a home, but not the same home.
- Current behavior belongs in Documentation.
- Dated updates belong in News.
- Technical analysis belongs in Research.
- Proposals and opinions belong in Discussion.
- Past context belongs in History.
This separation protects readers from confusing possibility with reality.
Good documentation admits uncertainty
Section titled “Good documentation admits uncertainty”A trustworthy page does not need to pretend it knows everything.
It should say:
- What is verified.
- What is not verified.
- Where the source is.
- What still needs review.
Admitting uncertainty is not weakness. It is how the project earns trust.
The goal
Section titled “The goal”The goal is not to be the loudest BitcoinII resource.
The goal is to be the clearest, most useful, and easiest to verify.
MoreBC2 succeeds when someone says:
I do not know. Let us check the source.