PowerChain documentation is organized by system layer so protocol, governance, developer, and enterprise material can evolve independently while remaining cross-linked.
- Introduction
- Vision
- Architecture
- Energy Protocol
- Governance
- Improvement Proposals
- Developer documentation
- Roadmap
- Tracked work
- Glossary
Every technical document should distinguish among:
- Implemented — present in the repository and supported by tests or operational documentation.
- Experimental — implemented but subject to breaking changes.
- Planned — a design target that is not yet available.
- Research — exploratory work without a committed delivery date.
Claims about throughput, finality, compliance, interoperability, certification, or production readiness must link to evidence or be labeled as a target.
- Use relative links.
- Prefer SVG for diagrams.
- Keep one canonical definition for shared terms.
- Add security and compatibility sections to protocol specifications.
- Include version and status metadata in proposal documents.