Blunder accepts focused issues and pull requests that strengthen its evidence-bound engineering model.
- Read
SECURITY.md,LICENSE, and the relevant architecture or roadmap document. - Describe the intended outcome, mutation boundary, authority impact, validation plan, and rollback.
- Keep the change minimal and preserve unrelated behavior.
- Prefer integration, recovery, adversarial, and smoke proof over coverage-only tests.
- Run the native suite and the smallest affected desktop or runtime check.
- Never include credentials, private memory, operator approvals, provider reasoning, workstation paths, or generated runtime evidence.
Changes that weaken constitutional, evidence, isolation, review, recovery, or operator-integration boundaries will not be accepted.
Submitting a contribution indicates agreement with the contribution terms in
LICENSE.