Organization Responses, Corrections, Reform Evidence, and Recognition

Purpose

Human Experience Reform (HXR) is the governed public identity for this documentation and evaluation project. UXR is retained only as the stable record namespace in existing Incident identifiers such as UXR-2026-0812-0001; it is not a separate public organization. HXR invites an evaluated organization to correct facts, add supporting or challenging evidence, explain constraints, offer an individual remedy, report reform, and ask HXR to verify improvement. Responding does not require an admission. A well-supported response can materially improve the public record without erasing the starting condition or transferring editorial control. HXR is editorially independent in a bounded sense: an evaluated organization and a contributor may supply evidence, correct errors, and request reconsideration, but neither controls HXR findings or publication history. HXR is currently founder-led, not institutionally independent; a materially conflicted operator cannot be the sole final reviewer of a disputed factual disposition, an acceptance-test pass, or a Verified Reform claim. HXR is not a regulator, court, law firm, adjudicator, certification body, or substitute for legal advice.

Separate accountability states

Every public record must keep these tracks separate:

1. Record accuracy — no correction requested; correction received; under review; supported correction published; or correction not supported on the available evidence.
2. Individual restitution — no organization remedy; remedy offered; partial delivery; remedy completed; or contributor made whole.
3. Organizational reform — no reform demonstrated; reform proposed; reform plan published; implementation documented; acceptance test passed; or verified reform.
4. Verification — not requested; test planned; testing in progress; failed; partially passed; passed; or reverification needed.
5. Monitoring — not started; planned; active; recurrence detected; stable; or cycle complete.

A correction does not establish restitution. Payment or a one-person remedy does not establish reform. A policy or promise does not establish implementation. Implementation does not establish that an acceptance test passed. A passing test does not establish durability outside the stated scope or observation period. Organization-notice and organization-response status are displayed separately from all five tracks.

Are you the evaluated organization?

Use the dedicated first-contact form at https://mintytees.com/pages/hxr-respond or email submit@mintytees.com. Identify the Case or Evaluation ID and the capacity in which you are responding. Show or copy stable record IDs into the message body manually; do not carry them in URL query strings, URL fragments, or prefilled mailto links. You may submit:

• a precise factual correction and its basis;
• evidence that supports, narrows, challenges, contradicts, or reattributes a finding;
• an explanation of relevant facts or constraints;
• an individual remedy offer or completion evidence;
• a reform plan with owner, scope, mechanism, implementation date, and test;
• implementation evidence; or
• a request for HXR verification.

Include your name, role, organization, authority to respond, the exact record element addressed, the response type, and what may be public versus what you ask HXR to keep private. An earlier Shopify contact transport passed one controlled message-delivery and internal-recovery test. The current HXR response page and its separate manual acknowledgment leg have not yet completed end-to-end validation. The current form provides only a generic success message. It does not automatically create a canonical response record or show a governed response ID. This is a pilot first-contact route, not a secure evidence-upload portal. The Shopify first-contact page may run ordinary storefront analytics. Do not submit sensitive evidence, confidential communications, settlement terms, customer/account identifiers, or other restricted material through it. Copy the relevant record IDs into the message itself and state your authority to respond; do not place record IDs or response content in URL query strings, fragments, or prefilled mailto links. HXR has adopted a required manual bridge: an authorized operator preserves the message and original received time, submits it through the current intake agent, creates or reconciles the private canonical response record, and sends a separate acknowledgment identifying the generated stable `HXR-RESP-N` reference. The ledger fields needed to record that acknowledgment are structurally available, but a real organization-response transaction had not yet completed the separate acknowledgment and full canonical readback as of September 2, 2026. Until that acknowledgment is delivered and recorded, the form success state is not a governed receipt.

Private intake and editorial independence

An unverified submission remains private until HXR verifies the respondent's identity and authority and separately reviews provenance, privacy, quotation, attribution, redaction, and publication basis. Authority verification establishes who is speaking; it does not establish that a claim is true or grant publication permission. Express granular respondent permission is the default basis for publishing a response or respondent-supplied evidence. HXR may use a different basis only after separately documenting a lawful, governed basis and completing necessity, proportionality, provenance, privacy, redaction, fairness, and accurate-representation review; silence, a public-safe draft, or verified authority is not that basis. Confidential or restricted material remains private. Potential evidence follows the governed chain: Source → Source Snapshot → Evidence Item → Evidence Contribution. Materially distinct claims or artifacts are separated. A submission is not automatically published, accepted, or treated as dispositive. A factual correction supported by the evidence is appended and credited. Unsupported disagreement may be summarized fairly with its limits. An organization may challenge evidence and method but receives no veto over evidence-supported findings, earlier versions, or append-only publication history. Responding does not require an admission. Payment, settlement, sponsorship, purchase, or any other financial relationship cannot buy deletion, suppression, a correction unsupported by evidence, favorable treatment, recognition, or a faster status.

HXR response-handling commitments

When a submission enters governed intake, HXR commits to:

1. Acknowledgment — manually preserve the original received time and exact submission, identify the record IDs received, create or reconcile the canonical response record, and send a separate acknowledgment containing its stable `HXR-RESP-N` reference. The public form's generic success state is not that acknowledgment.
2. Identity and authority verification — verify who is responding and the basis for organizational authority before attributing a statement to the organization.
3. Fair review — review supporting, challenging, favorable, and unfavorable material under the same provenance, relevance, privacy, and evidence rules.
4. Privacy and publication permission — keep supporting information private unless publication is authorized, and record quotation, organization attribution, representative attribution, each evidence item, remedy-status publication, and reform-plan or implementation publication separately. Permission to publish a remedy status does not publish settlement terms; permission to publish reform activity does not establish implementation, acceptance-test passage, or verification.
5. Accurate, contextual representation — distinguish quotation, organization-stated material, evidence, contributor account, and HXR analysis; represent the organization's position in context and avoid selective quotation that materially changes its meaning.
6. Prompt correction of HXR errors — append a supported correction without conditioning it on admission, payment, settlement, or withdrawal of criticism.
7. Claim mapping — identify which public claims, evidence items, remedy questions, or reform questions the response addresses.
8. Evidence-decision explanation — explain whether submitted material was accepted, narrowed, deferred, rejected, or kept private and why, subject to privacy and security limits.
9. Response classification — distinguish a correction, disagreement, contrary evidence, explanation, remedy, reform plan, implementation evidence, and verification request.
10. Append-only history — preserve the prior public state and add dated corrections, organization statements, remedy events, reform evidence, verification results, and reversals.
11. Reconsideration path — allow a respondent to identify a material review error or new evidence and request a second bounded review by a person or process not relying solely on the original conclusion.

An earlier Shopify contact transport passed one controlled message-delivery and internal-recovery test. The current HXR response page and its separate manual acknowledgment leg have not yet completed end-to-end validation. The canonical response and fair-notice ledgers now exist, but the public route does not populate them automatically and is not a secure evidence-transfer service. HXR has adopted the following required manual procedure: an authorized operator preserves the received message and time, creates or reconciles the `HXR-RESP-N` record through the intake agent, applies private defaults, records authority and permissions separately, assigns append-only claim labels, sends the response reference, and reads the transaction back. The necessary record fields are structurally available; end-to-end validation remains pending until a real transaction completes acknowledgment, exact recovery, and canonical readback. HXR will not represent a message as a governed organization response until the applicable authority, publication-basis, provenance, privacy, claim-level review, and disposition controls are recorded.

Contributor-equivalent continuity

A contributor may use the same human doorway to correct or supplement an account, supply later evidence, change a permission, report remedy progress, raise safety or unwanted-contact concerns, or request reconsideration. HXR routes that material through the existing private Intake Session and correction/update structure rather than the organization-response ledger. The Intake Session now has fields to record acknowledgment state, sent time, private outbound delivery reference, and the stable receipt reference communicated to the contributor. The adopted procedure requires a manual acknowledgment stating the stable Intake Session ID, original received time, privacy/use defaults, what HXR recorded, and the next step, but no real contributor transaction had yet completed acknowledgment plus full canonical readback as of September 2, 2026. This is intended structural parity and a continuity aid, not proof of operational parity or a publication, response, remedy, or outcome promise. A contributor is not required to contact the organization, negotiate publicly, reveal sensitive information, or rebut every organization claim. When safety and privacy permit, HXR should give the contributor reasonable notice before a material public change based on an organization response. Neither side receives control over evidence-supported findings.

Claim-level and append-only review

A multipart response receives stable claim labels such as `HXR-RESP-N/C01`, `C02`, and so on. Each claim is mapped to the relevant record, evidence, remedy component, reform target, or acceptance test and receives its own dated disposition and reason. Claim labels and dated dispositions are append-only: a later review creates a new dated entry that supersedes or narrows the earlier one rather than silently rewriting it. A top-level response disposition is only a roll-up and cannot erase mixed claim results.

Capacity-qualified service targets

During the founder-led Private Alpha, HXR uses capacity-qualified, good-faith operating targets, not guarantees or contractual service levels: preserve and acknowledge contributor intake with its stable Intake Session ID, original received time, privacy/use defaults, recorded summary, and next step within 2 business days of receipt; communicate an organization submission's `HXR-RESP-N` acknowledgment within 2 business days of receipt; request missing authority or permission information within 5 business days; triage a claimed material HXR factual or privacy error within 3 business days and target correction of a confirmed material HXR error within 5 business days; provide an initial claim-level disposition or meaningful status update within 15 calendar days after a submission is review-ready; update an open review at least every 14 calendar days; acknowledge reconsideration within 5 business days and assign a reviewer or provide reviewer status within 10 business days. For these targets, a business day is Monday through Friday excluding U.S. federal holidays, measured in Pacific Time; a message received after 5:00 p.m. Pacific Time is treated as received on the next business day. Safety, privacy exposure, irreversible harm, and correction severity may justify priority; payment, influence, praise, or willingness to admit fault may not. HXR records and communicates missed targets rather than concealing them.

Conflict and independent review

HXR records material personal and financial conflicts. For founder-involved or otherwise conflicted records, a materially involved operator may preserve intake, perform privacy triage, and complete administrative routing, but cannot be the sole final reviewer of a disputed factual disposition, an acceptance-test pass, or a Verified Reform claim. Until a second bounded reviewer without the material conflict is assigned and records a decision, the affected state remains Under review / independent review pending. Public text need not identify the reason for the conflict or expose contributor identity. The conflicted operator must not be described as an independent verifier, and HXR must not claim independent verification while the second review is pending. Independent review does not transfer editorial control to the organization or contributor.

Fair-notice protocol

Outreach is a separate authorization-controlled action. Publishing a response route does not mean HXR sent notice. For an HXR-authored fair-notice cycle:

1. Preserve the notice content, destination, recipient role, channel, dispatch date, and record IDs.
2. Verify delivery using a delivery artifact or an authority-confirmed acknowledgment. If delivery is not verified, publish Notice sent; delivery not verified; no response clock started.
3. When delivery is verified, Day 1 is the next calendar day. The standard response window is 30 calendar days, ending at 11:59 p.m. Pacific Time on Day 30.
4. Send no more than one reminder, ordinarily on calendar Day 21. Record its date and delivery state separately.
5. Record an acknowledgment separately from a substantive response. A substantive response addresses at least one material claim, evidence item, correction request, remedy question, or reform question. A reasonable extension requested before the deadline may be granted and must be published with the revised date.
6. If the window closes without a substantive response, use precise dated language: No substantive response received as of [date]. Do not say or imply that the organization ignored, refused, admitted, conceded, or was guilty.
7. Preserve every notice, reminder, response, extension, and status change in dated append-only history.

The 30-calendar-day period is HXR's general governed fair-notice policy for evaluated organizations; it was not invented for Empire. Historical contributor-authored notice remains attributed to the contributor and is not retrofitted into the HXR protocol. Missing delivery dates or artifacts remain visible limitations.

Dual-track remedy and reform review

Individual restitution

A remedy offer must state the scope, amount or service, conditions, responsible party, and completion method. HXR may record an offer without treating it as acceptance, delivery, or admission. Completion requires evidence that the promised payment, credit, repair, replacement, or service was delivered. Contributor Made Whole requires supported completion and contributor confirmation where appropriate; it is not inferred merely from an offer or payment. Private restitution negotiation is separate from the public organization response. HXR does not publish settlement terms, sensitive evidence, negotiating positions, or confidential communications without explicit permission. A public record may say Remedy discussion underway without identifying terms, implying agreement, or changing accuracy, reform, or verification status.

Organizational reform

A reform claim should identify the mechanism changed, implementation date and scope, accountable owner, affected service path, implementation evidence, acceptance test, and monitoring plan. It is evaluated against the published Evaluation benchmark. A response, apology, refund, single repair, policy announcement, training statement, or isolated example is not by itself verified reform.

Procedural milestones and positive credit

HXR displays each milestone only when supported, scoped, dated, and permissioned.

Neutral procedural facts

1. Organization Responded — an authority-verified representative supplied a substantive response.
2. Evidence Supplied — reviewable evidence with usable provenance was received.
3. Individual Remedy Offered — a specific remedy was offered with scope and terms; an offer is not completion.
4. Reform Plan Published — a bounded plan identifies mechanism, owner, scope, dates, and acceptance test; a plan is not implementation.

These facts improve record completeness but are not praise, certification, or proof that the underlying issue was resolved.

Strong positive credit

1. Individual Remedy Completed — supported evidence shows the promised remedy was delivered.
2. Contributor Made Whole — the supported remedy resolves the documented individual loss within the stated scope, with contributor confirmation where appropriate.
3. Implementation Documented — evidence shows the reform mechanism operating in the stated scope.
4. Acceptance Test Passed — reviewed evidence satisfies the Evaluation's published test for the stated sample and period.
5. Verified Reform — implementation and results are sufficiently corroborated and bounded, with monitoring or recheck conditions stated.

Positive credit is descriptive, evidence-based, scoped, dated, and reversible if later evidence contradicts it. It is not a certification, seal, score, externally usable badge, endorsement, compliance determination, warranty, or statement about every location, employee, customer, or future interaction.

Reserved descriptor: Model Accountability Response

Model Accountability Response is reserved for an unusually strong, evidence-supported response that addresses past harm, changes the relevant system, permits independent verification and monitoring, and does not require erasure or distortion of the original record. It is not established by a reply, promise, refund, or plan alone. This is a separate reserved descriptor, not a tenth recognition milestone, not a sixth strong-positive-credit rung, and not a certification, seal, score, badge, endorsement, warranty, or transferable claim. It may be used only when the full stated threshold is supported, scoped, dated, permissioned, and preserved through append-only history.

Publication and privacy

Public pages distinguish HXR analysis from primary evidence, show evidence status and limits, preserve stable IDs and URLs, and use append-only updates. Raw private artifacts are not published merely because they support a public finding. Public response text is reviewed for personal information, unsupported allegations, confidential content, provenance, and permissions. Favorable and unfavorable evidence receive the same bounded treatment.

Separate authorization boundaries

The following remain separate actions and require separate authorization: contacting an organization, sending formal notice or a demand, submitting to CSLB or another regulator, and filing or assisting with a court filing. Creating a public response route or packet does not authorize any of them.

Empire restitution-response options

For the Empire case family, the contributor’s restitution request has two components: $1,765 in presently quantified direct-service costs, plus additional historical maintenance restitution requested, amount pending record-based calculation. The total contributor restitution request is not yet fully quantified. A verified Empire representative may:

• reimburse the $1,765 direct-service component;
• provide the historical maintenance agreement and payment history;
• provide task-level records for prior maintenance visits;
• explain what Empire defines as included preventive maintenance and identify tasks performed at each visit;
• offer a partial or full refund for visits where service was materially incomplete;
• propose a record-based historical restitution calculation;
• dispute historical reimbursement with relevant service records; or
• enter private restitution discussion without automatically publishing settlement terms.

Absence of service records is not automatic proof that no maintenance occurred. If recurring preventive maintenance was sold but records are insufficient to demonstrate what was performed, HXR may preserve that as a distinct documentation, accountability, and customer-visibility issue. Payment of $1,765 alone completes only the direct-service component if historical maintenance restitution remains unresolved; in that state, Individual Remedy is Partial and Contributor Made Whole is No.

Empire launch boundary

The Empire Incident and Evaluation pages may link to this route. HXR has not independently contacted Empire as part of the publication work. No HXR fair-notice clock has started. No formal Empire response, supported correction, Empire remedy, reform implementation, passed acceptance test, or verified reform is currently recorded. The contributor-reported historical notice is preserved with its limits and is not treated as proof of motive, admission, refusal, or guilt.