john-slop/CONTRIBUTING.md

1.1 KiB

Contributing

Contributions should preserve John Slop's explainable, local-first product boundary. Findings must describe observable signals without asserting AI authorship, model identity, or personal characteristics.

  1. Open an issue for behavior or public-contract changes before investing in a large patch.
  2. Create a focused branch and add tests at the lowest useful layer.
  3. Update user documentation, samples, and stable output snapshots together.
  4. Run the quality, supply-chain, fuzz-smoke, or benchmark commands relevant to the change as documented in Development.
  5. Submit small conventional commits and explain rule false-positive tradeoffs.

New heuristic rules require a stable lowercase kebab-case ID, conservative positive and realistic near-miss fixtures, scopes, a rationale and help text, and evaluation-corpus review. Default weights or thresholds require the documented sign-off process in Evaluation.

By participating, contributors agree to follow the Code of Conduct. Report vulnerabilities through SECURITY.md, not a public issue.