The redacted, checksummed corpus behind one rule's published precision — downloadable without credentials
Public-safe
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| ruleId* | query | string | — |
| rule_id | query | string | Deprecated alias for `ruleId`, accepted so verifiers published before #9962 (which asked for this spelling and got a 400) work unchanged. `ruleId` wins if both are given. |
Responses
- 200{ ruleId, windowDays, caseCount, truncated, readFailed, checksum, cases: [{ ruleId, outcome, label, firedAt, decidedAt, metadata?: { confidence } }] } — `targetKey` and every other metadata key are DROPPED, not hashed, so no repo or PR identity is published; `metadata.confidence` stays nested where buildConfidenceThresholdClassifier reads it. Timestamps are truncated to the UTC day. `checksum` is sha256 over canonicalJson(cases), i.e. it commits to the artifact you can actually download. `readFailed` is true when the corpus is empty because the history read failed rather than because the rule has no cases — no commitment is published for such a corpus
- 400`ruleId` (or its `rule_id` alias) is required — a corpus is only meaningful for one rule
- 404Public stats are disabled for this deployment