Findings · policy
The rules we file under
Anyone can point a machine at a repository and open issues. The rules below are what stop that being a nuisance.
- A clock before anything is published. Fourteen days, or the project's own median release interval if it is longer, capped at sixty. The maintainer hears from us before the internet does.
- A cap on volume. At most five filings a week across all projects, and never more than three of ours open against one project at a time. If more than one in ten is discarded, the rate comes down automatically.
- Every filing has a reproduction. Minimal steps, the environment, and the frames showing expected against actual. A report a maintainer has to interview us about is not finished.
- We honour each project's own policy. Some forbid AI-assisted contributions; some forbid root-cause analysis in the issue. We read the policy, we follow it, and where analysis is unwelcome we file the observed behaviour and keep the analysis here.
- Filed under a person's name. Tim's, today. Not a bot account.
- Our precision is published, and so is its history. Not one flattering number — a dated series, with how many filings sit behind each point, updated by the pipeline rather than by hand.
- A do-not-test list, honoured on request. Ask and we stop, within one working day, no verification theatre for the asking itself.
The precision series starts empty because nothing has been filed. It appears here with the first filing, and we will not be publishing the first point on its own.
Want this on your product?
We are building the first version with a handful of teams. Tell us what you test with and what breaks.