Roadmap status: This document describes possible directions, not promises, delivery dates, contractual scope, or commitments. Priorities may change without notice. See DISCLAIMER.md.
The playbook evolves through small, reviewable releases. Proposals should solve a recurring engineering problem, stay adaptable across projects, and avoid exposing confidential or client-specific information.
- Establish the operating model from discovery through operations.
- Publish reusable templates and fictional examples.
- Add contribution, security, licensing, trademark, and governance foundations.
- Automate structural and risk-language documentation checks.
- Engineering management and team-health guidance.
- Privacy engineering and data-retention guidance.
- Mobile and frontend delivery checklists.
- Platform engineering and cloud-cost guidance.
- Additional fictional examples spanning different risk profiles.
- Translations maintained with documented ownership and parity checks.
Maintainers consider:
- usefulness across more than one project;
- severity and frequency of the problem;
- clarity of ownership and maintenance cost;
- compatibility with the playbook's adaptable, non-contractual purpose; and
- contributor and community feedback.
Ideas are welcome through a guidance-improvement issue. Inclusion on this roadmap does not guarantee acceptance or implementation.