License and Support

Abstract

Explain the license, support boundaries, and how users should ask for help.

This page should make the support posture explicit so adopters know what they can rely on and where to file problems.

Audience

Developers, engineering leads, security reviewers, and open-source contributors.

Support Policy

1. Report bugs and docs issues in the project issue tracker.
2. Use the security disclosure process for sensitive vulnerabilities.
3. Expect best-effort community support in alpha, not a formal SLA.
4. Expect maintainers to triage, clarify, and close issues that are out of scope or not reproducible.
5. Do not expect support for unsupported stacks or custom integrations that are not documented.

License

1. State the project license plainly.
2. Link to the canonical license file.
3. Call out whether dependencies or bundled artifacts carry separate terms.

Content Outline

1. State the project license and link to the license file.
2. Explain where to ask questions, report bugs, and request features.
3. Define the support boundary for alpha users.
4. Link to security disclosure and contribution guidance.
5. Explain how maintainers triage issues and releases.

Evidence To Add

• Maintainer-approved license wording.
• Issue templates and support links.
• Security disclosure process.