Contributing to HXR

HXR is in Private Alpha, and limited real-world submissions are open. The project is being engineered and tested in public, and the intake process now needs a small, varied stream of real experiences to expose missing entities, relationships, evidence boundaries, vocabulary, and safeguards.

Share an Experience with HXR is the public starting point. Its button opens an external Jotform form that sends your account to an HXR operator by email for human review. A short account is enough; non-sensitive supporting files are optional. Sending the form does not automatically create an HXR record, publish anything, or contact the organization. You can add to an existing Evaluation or describe a new topic without deciding how HXR should classify it.

Share What Worked, What Was Difficult, or What Was Mixed

You can submit an experience involving an app, website, business, government service, street condition, customer-service interaction, positive outcome, frustrating outcome, mixed outcome, or an ordinary interaction that made you wonder whether the system could work better. Positive experiences matter because HXR also wants to identify practices that preserve agency and deserve replication.

Evaluations are the main analytical records these contributions can help build. A bounded Case may preserve what happened in one experience; an Evaluation brings relevant Cases and other evidence together to examine a practice or question over time. Your contribution may help recognize something worth preserving, explain an improvement, identify a limit, or change an earlier finding.

Outside sandboxed regression testing, HXR uses real submissions rather than invented case stories. A real submission may lead to internal case, institution, system, evidence, pathway, or research records. Being mentioned or involved does not automatically make an organization responsible for an outcome.

Submission and Publication Are Separate

Sending material does not automatically create a public case and does not authorize publication. Intake, consent and use authorization, privacy review, evidence analysis, and public release are separate decisions. During Private Alpha, public release remains human-gated.

Contribute at the Level You Have Capacity For

You do not need to prepare a complete narrative or upload a folder of evidence before your experience can matter. Different contribution levels add different kinds of knowledge.

Current pilot: HXR uses one human doorway rather than asking people to choose from a menu of record types. Send your story to Sean/HXR in ordinary language. Sean or another expressly authorized operator will then open the current intake agent and manually create or reconcile the private Intake Session, privacy/use state, candidate record relationships, and any supported evidence links. The public contact step does not automate this handoff and is not a secure evidence portal. HXR should do the classification work behind the scenes and ask only the smallest useful follow-up. The public submission form provides access to this human review process; it does not automate the canonical intake handoff. Further automation should be added only when real use establishes a need.

Examples of what a contribution may contain:

• Ten seconds: say what worked well, whether an experience also happened to you, whether a workaround helped, or how your experience differed.
• One minute: add a date range, jurisdiction, system version, wait time, quoted phrase, or final outcome.
• A few minutes: describe the objective, what helped or hindered you, the sequence, and the result in your own words.
• Evidence you already have: tell HXR what screenshot, email, chat log, receipt, notice, photograph, recording, or system record exists. Do not send sensitive material through a general contact form; HXR should arrange an appropriate bounded transfer when the evidence is genuinely needed.
• Expertise or inside knowledge: explain the mechanism, legitimate constraint, responsible function, or implementation risk.
• Follow-up evidence: help test whether a good practice or claimed improvement works under the stated conditions and remains in place.

A one-tap signal is not a vote. A screenshot does not prove every interpretation. A counterexample can be as valuable as a matching incident because it may prevent HXR from overstating the evidence.

See the complete contribution ladder, the motivations behind each on-ramp, and how even a small contribution can help HXR learn and improve systems.

Ways to Contribute

• Share a real experience: serious or casual, positive or negative, as long as it is yours to share.
• Review the method: challenge evidence boundaries, privacy controls, attribution, governance, terminology, and claims of maturity.
• Program or design: help build intake tooling, structured review, deterministic broker checks, automation, testing, accessibility, data modeling, and public interfaces.
• Bring domain knowledge: help HXR understand institutions, public systems, healthcare, finance, consumer services, accessibility, research methods, auditing, law, journalism, or other applicable fields without converting expertise into unreviewable authority.
• Improve verification: help design blind re-grading, inter-grader agreement checks, privacy tests, duplicate handling, and audit-friendly automation.
• Document reforms and good practice: point to institutions or systems that have measurably improved or already handle people well.

What Your Contribution Can Add

A contribution should not become a one-way transfer of personal effort into an invisible queue. Depending on the evidence, authorization, relevance, and current Private Alpha capacity, a contribution may:

• support, narrow, challenge, or contradict an active Evaluation;
• be preserved as one bounded Incident Case;
• document a practice that preserved dignity or agency and may be useful for others to learn from;
• connect with materially related incidents without turning contributor count into proof;
• add a verified workaround, failed approach, contact path, script, or other resolution knowledge;
• help identify which organization, department, system, mechanism, or governing layer controls the next step;
• invite an involved organization to document good practice or improvement, correct facts, explain constraints, or identify responsibility;
• remain connected to later outcomes, responses, corrections, verification, maintenance, or regression;
• produce an authorized public link that can be shared with affected people, organizations, regulators, employers, journalists, researchers, advocates, investors, or policymakers.

HXR cannot promise that submitting an incident will produce the person's immediate objective. It can build the structure that makes the effort cumulative, visible where authorized, and reusable instead of allowing it to disappear.

See how an HXR contribution differs from an ordinary complaint or grievance.

What HXR Should Give You Back

HXR's intended contributor experience includes a clear Contribution Impact Receipt. During the current manual pilot, HXR will use the existing Intake Session rather than build a separate receipt system. Intake Sessions now have fields for acknowledgment state, sent time, a private outbound-delivery reference, and the stable receipt reference communicated to the contributor. The adopted procedure requires the manual acknowledgment to state the stable Intake Session ID, original received time, privacy/use defaults, what HXR recorded, and the next step. This creates structural and intended parity with organization-response receipt handling, but no real contributor transaction had yet completed acknowledgment plus full canonical readback as of September 2, 2026. HXR's capacity-qualified target is to preserve and acknowledge contributor intake within 2 business days after receipt; it is a good-faith, noncontractual target, not a guarantee or a promise of publication, organization response, remedy, or outcome. For target calculation, 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. The accompanying plain-language summary should show whether the material remains private or anonymized, which Incident Case or Evaluation it may connect to, what it may add, and what it cannot establish alone.

A separate persistent receipt, automatic updates, and contributor portal should be built only if real use shows that the simpler summary is insufficient. The purpose remains the same: demonstrate that the contribution entered a consequential pathway rather than an invisible queue.

Your continuing path

After initial intake, a contributor may use the same human doorway to correct or clarify the account, supply later evidence or counterevidence, change a privacy or publication permission where the governing record permits, report whether a remedy was offered or completed, raise retaliation or unwanted-contact concerns, request reconsideration, and ask for an updated plain-language summary. You do not have to contact the organization, negotiate publicly, disclose sensitive information, or rebut every organization statement. When safety and privacy permit, HXR should give you reasonable notice before a material public change based on an organization response.

A documented organization response may add acknowledgment, correction, explanation, remedy, or reform. HXR reviews it claim by claim and preserves the contributor account, organization position, primary evidence, and HXR analysis as distinct sources. Neither the organization nor the contributor can buy or command a finding. A documented nonresponse after governed HXR notice, verified delivery, and the applicable response period is a response-state worth preserving, but silence does not automatically prove guilt, agreement, indifference, motive, or inability to reform.

What Contributors Should Expect

HXR is unfinished. Categories, schemas, analytical methods, and intake behavior may change as testing finds defects. The first manual regression baseline failed overall, and HXR is publishing that fact while keeping the answer key private. The project does not claim that its executable broker has been validated.

Capacity and Independence

HXR currently has no formal programming team, board, or dedicated domain. Human review is the pilot's throughput limit. Contributions can help the project grow, but no contributor, funder, institution, or technical partner receives authority to displace meaningful human agency as HXR's governing center.