arknet is developed independently from ARK. Changes should preserve protocol contracts and include reproducible verification before application integration.
- Releases: version scope and deployment acceptance.
- Testing and validation: correctness coverage, sanitizer checks and local evidence.
- Production acceptance and ARK: acceptance criteria, direct replacement and business regression.
- Troubleshooting: symptoms, diagnostic steps and recovery.
- Architecture and extension: CRTP, components and ownership boundaries.
- Contributing: code style, builds, documentation and commit conventions.
- Roadmap and TODO: planned transports, protocols and coroutine APIs.
- Third-party notices: bundled and development dependencies.