01
Questions and design conversations
For usage questions or design discussions, use GitHub Discussions. Questions go to the Q&A category, in English or Portuguese; an early idea or a design question that is not ready for the idea form below goes to Ideas. Paste the command you ran and its output, without tokens or personal paths.
02
Report a documentation mismatch
If a command behaves differently from the documentation, open a problem report. Include the exact command and its output. Remove tokens and other secrets before posting.
03
Give feedback
If something was confusing, slower than it should be, or made you stop using a piece of the harness, open the feedback form. It needs no reproduction: a sentence is enough, and leaving a module out or turning a hook off counts. Run the command below and paste the report it prints into the form:
hpp doctor --reportIt prints the link to the form with the title filled in and, below it, the report: versions, Python, platform and the doctor's counts, with no path from your machine. The command makes no network call; nothing is sent until you open the link yourself. From a clone without the package installed, run python -m hpp doctor --report.
04
Propose an idea
For a capability, module or contract the harness should have, open the idea form. It asks for the failure the idea removes, what the harness would do differently, and the command or test that would prove it, with the negative case that would show it refusing. An idea also has to fit the honest limits, or say which one it would change and why. What is already planned, and what the project will not do, is in the roadmap.
05
Report a vulnerability
Do not open a public issue for a vulnerability. Use GitHub private vulnerability reporting or the contact channel on the project site, as described in SECURITY.md.