Walkthrough · registry 1.11.0
From what you saw to what you can test
Select your witnessed observations (rejection notices, uncompensated tasks, pipeline silences). The analyzer identifies compatible root mechanisms, active double binds, and bounded diagnostic probes without speculative guessing.
Runs in your browser · nothing is sent anywhere
Structure a complaint or social post
Paste a first-person account. hoba separates directly reported facts from causal claims, then compares only the mapped facts with validated cases.
Runs locally in your browser. Contact details and usernames are redacted before this result is rendered; do not paste names, addresses, or identifiers.
Paste the rejection itself
The steps below ask you to translate what happened into the atlas’s vocabulary. This does it the other way round: paste the message you received and the atlas finds the trace, if it holds one.
Read in your browser. Nothing is sent anywhere and nothing is stored, which is why it is safe to paste a letter that names the company.
Step H — What actually happened?
Select the observations you witnessed yourself. Do not guess at intent.
Automated Rejections & Emails4
Holds, Silences & Ghosting4
Job Postings & Requirements3
Assessments & Interview Panels4
Offers, Comp & Down-Levelling6
Nearby validated cases
These cases share facts with yours. They are structural comparisons, not estimates of what caused your outcome.
A nearby case can show what else to check. It does not establish that the same mechanism operated in your case.