Contributor guide
The authoritative commands and PR process live in CONTRIBUTING.md, so documentation can evolve alongside code.
Start by reproducing a bug, improving setup documentation, testing keyboard accessibility, or taking an issue with clear acceptance criteria. Coordinate before major work; another contributor or agent may already be working in that area.
Explain the problem, resulting behaviour and checks actually run in your PR. Keep mechanical formatting separate from functional changes. Coding tools will be selected through issue #14.
AI-assisted contributions are welcome when the contributor understands and verifies the result. Use synthetic data, preserve copyright notices and follow the community code of conduct.
Nathan (@nathcymru) currently maintains Tocyn. Review timing depends on availability.
- System-architecture
- Architecture-and-tenant-isolation
- Channels-and-conversation-model
- AI-and-autonomous-operations
- Architecture-decision-records