# Report a defect or unclear rule

**Selected public reporting destination: Eziah.dev.**  
**Designated entry point: https://eziah.dev/report**  
**Current status: selected for implementation; live intake has not been verified.**

Eziah.dev is the public home for Eziah Accord releases and their reporting
channel. A public entry point does not require reports to be publicly visible.
The planned intake sends reports to a private owner-accessible queue for review.
The page and a successful submission must be checked before publication calls
this a working reporting channel. Until then, preserve the report locally and
return it through the existing project review conversation.

## What to include

Use [reproduction/FINDING-TEMPLATE.json](reproduction/FINDING-TEMPLATE.json),
or the equivalent fields on the reporting page:

- Publication ID and archive SHA-256, if known.
- Relevant rule and component version.
- A short description and steps to reproduce using synthetic data.
- Expected decision, reason, and effects.
- Actual decision, reason, effects, and delivery status.
- Runtime, command, evidence references, and what evidence is unavailable.

Finding types are specification ambiguity, implementation defect, environment
failure, evidence gap, and unsafe authority expansion. These labels are not
new protocol reason codes. Do not include credentials, private keys, personal
records, or data you lack permission to disclose. The initial web form should
accept text and optional contact details; it need not accept file uploads.

## What submission means

A receipt confirms that the report was stored. It does not confirm the finding,
promise a response time, establish a bounty, or grant authority. Submitted
content is untrusted input. It must not automatically run commands, fetch linked
files, update the specification, change expected results, activate code, or
alter authority. Findings reach the release record only after review.

If an action's authority is unclear, stop that protected action and preserve
state. Do not change permission or evidence to obtain a passing result. Keep
the first result separate from later fixes and retests. Preserve
`INDETERMINATE` when delivery is unknown; do not replace it with a zero-effect
claim.

The public page must accurately describe who can access reports and what is
stored. No unverified confidentiality, retention, response-time, or deletion
promise is established by this document. Public disclosure of submitted details
requires a separate review of the content and the reporter's permission.

Machine-readable channel status is in [REPORTING.json](REPORTING.json).