Claiming Your AI Rights

Two algorithmic rejections in one week — an auto-loan denial and a New York hiring auto-rejection. The discipline either transfers across domains or only worked once.

Three modules in, you've learned to tell aspirational AI principles from enforceable sectoral law, to detect when an automated system is in the loop even when no one tells you, and to run the four-step playbook when an automated decision goes against you. This capstone is the week your knowledge meets two algorithms in two different domains. You've been between jobs since a car accident totaled your car last month. You applied for an auto loan online Tuesday to replace it — the lender rejected you in thirty seconds. Friday afternoon, an NYC employer's automated screen rejects your application before a human ever reads it. The clock is running on next week's interviews and on the dispute windows that protect you. The playbook either holds across domains or only worked once. Five nodes. The first three walk the playbook on the loan; the fourth tests whether the discipline transfers to the job; the fifth asks you to name what you just did, operationally. Pick the path you can defend.