Evaluated Organizations: Respond to an HXR Record
Organization response pathway
Correct the Record, Add Evidence, Remedy Harm, or Demonstrate Reform
Organizations discussed in an HXR Evaluation or Incident are invited to participate in the record. You may correct facts, submit supporting or challenging evidence, explain constraints, document an individual remedy, propose reform, show implementation, or ask HXR to verify a change. Responding does not require admitting fault and does not give HXR or the organization control over the other's conclusions.
What HXR promises when an organization responds
Private-by-default review
HXR does not publish an unverified contact, respondent identity, or submitted material merely because someone contacts us. The Shopify storefront may run ordinary site analytics, so the first-contact form is not a confidential evidence-transfer channel.
Manual governed intake
The form delivers a first contact to HXR; it does not automatically create a governed record or durable HXR receipt. HXR has adopted and made available a manual governed-intake procedure. When a contact is suitable for intake, the procedure requires Sean or another expressly authorized operator to submit it to the HXR intake agent and create or reconcile the private canonical response record. Only after that manual canonical reconciliation may HXR separately deliver the assigned HXR-RESP reference. HXR’s private response ledger and manual handling procedure are in place. The current public contact step has not yet been validated through a complete sender-facing acknowledgment and readback transaction. A storefront success message is transport confirmation only, not a governed HXR receipt. After manual reconciliation, HXR sends the stable reference directly to the sender; private receipt identifiers are not published.
Fair correction
A supported HXR error receives a dated correction. Prior versions remain traceable so corrections do not become silent rewrites.
Contrary evidence is allowed
Evidence that challenges HXR is evaluated using the same relevance, provenance, reliability, and scope standards as evidence that supports it.
Permissions stay granular
Authority, organization attribution, quotation, evidence publication, confidentiality, and redaction are tracked separately.
No pay-to-change outcome
Payment, refund, settlement, donation, purchase, or commercial relationship cannot buy deletion, suppression, favorable wording, or a favorable verification result.
Response types remain separate
A factual correction is not the same thing as disagreement. An individual remedy is not the same thing as organization-wide reform. A reform proposal is not implementation. Implementation is not verified reform until it passes the stated acceptance test within a defined scope.
- Correct Facts
- Add Evidence
- Address the Individual
- Improve the System
- Verify the Change
What may an organization submit?
- specific factual corrections with checkable support;
- supporting, challenging, or contrary evidence;
- technical, policy, legal, operational, staffing, safety, or other constraint explanations;
- an organization position or disagreement;
- an individual remedy or restitution proposal;
- a reform proposal or implementation plan;
- evidence that a reform has already been implemented;
- positive-practice evidence HXR has not yet considered;
- a request for HXR to test or verify a claimed change; and
- instructions about what may remain private, be attributed, quoted, summarized, redacted, or published.
How authority verification works
HXR does not label a message as an official organization response merely because someone says they represent the organization. We verify authority proportionately using the respondent's role, organization-controlled contact information, public staff or department information, confirmation through an authoritative channel, or other suitable evidence.
An individual employee may provide useful evidence without being authorized to speak for the organization. HXR preserves that distinction.
What happens to the response?
- The first-contact form delivers a private-by-default message to HXR; the form itself does not create a governed response record or durable receipt.
- Sean reviews the contact. When it is suitable for HXR intake, the adopted procedure requires Sean or another expressly authorized operator to submit it manually to the governed intake agent.
- Only after manual canonical reconciliation does the procedure require HXR to preserve the contact and available delivery timestamp, assign or reconcile its HXR-RESP reference, and separately deliver an acknowledgment containing that reference. HXR’s private response ledger and manual handling procedure are in place. The current public contact step has not yet been validated through a complete sender-facing acknowledgment and readback transaction. A storefront success message is transport confirmation only, not a governed HXR receipt. After manual reconciliation, HXR sends the stable reference directly to the sender; private receipt identifiers are not published.
- Authority and source provenance are reviewed.
- The response is classified by what it actually does: correction, evidence, disagreement, remedy, reform, implementation, verification request, or another category.
- HXR records what publication permissions were granted.
- Material claims are checked against the existing evidence record.
- HXR records a reasoned disposition and updates the public record when warranted.
- Later implementation, verification, monitoring, and regression remain append-only events rather than erasing earlier history.
Private evidence and sensitive material
Courtesy invitation and governed fair notice are different
Courtesy Invitation
HXR may tell an organization that a public Evaluation exists and invite review or response. There is no deadline and no public “failed to respond” inference attached to a courtesy invitation.
Governed Fair Notice
A formal HXR response window is a separate authorization-controlled process. HXR preserves the exact notice, verifies delivery, starts Day 1 on the next calendar day, normally allows 30 calendar days, records a reminder around Day 21, and tracks reasonable extensions.
How organizations receive visible recognition
The governed recognition ladder contains exactly nine evidence-based milestones: Organization Responded; Evidence Supplied; Individual Remedy Offered; Individual Remedy Completed; Contributor Made Whole; Reform Plan Published; Implementation Documented; Acceptance Test Passed; and Verified Reform.
Organization Responded and Evidence Supplied are neutral procedural facts. Individual Remedy Offered and Reform Plan Published record proposals or commitments, not completed results. Strong positive recognition begins with completed remedy, documented implementation, passed acceptance tests, and verified reform. Regression Detected is a separate monitoring state, not a recognition milestone.
These labels are not certifications, seals, scores, endorsements, legal judgments, or externally reusable badges. Payment cannot purchase a milestone, deletion, or favorable treatment.
Start with a private first contact
Include the HXR Evaluation or Incident ID, your organization and role, what type of response you are making, and a brief description of what you want reviewed. Do not include sensitive attachments or confidential records in the first message.
Are you a contributor or potential contributor?
You may use the same manual first-contact form to share a story, correct or supplement an existing contribution, change future-use or publication permissions, report a remedy update, request reconsideration, or register interest in later notifications. Copy any stable Incident or Evaluation ID from the public page into the message field; HXR keeps record IDs out of the URL.
The form does not automatically open a case or create a governed receipt. Sean reviews the contact and, when appropriate, manually submits it to the HXR intake agent. HXR's current contributor target is a manual summary after governed intake. The canonical contributor structure now supports acknowledgment, stable-reference, delivery, and granular-permission fields, so structural parity is available; no real end-to-end contributor acknowledgment and readback transaction has yet been proven. Sending a story does not guarantee investigation or publication.