WHAT IT IS

The working A prototype: use its controls to test the build question.

WHY IT MATTERS

Show who can be affected by an AI workflow and how consequences travel to them.

RN'S ROLE

RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.

BOUNDARY

This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.

HOW TO USE THIS PAGE

Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.

WHERE TO GO NEXT

The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.

BUILD 022-A

Human Consequence Map for AI Workflows

Trace an AI-assisted workflow outward from its decision point to the people, households, workers, and communities who can experience its consequences.

MAP STATUS / 4 IMPACT NODES

REPRESENTATION GAPS

Exposure signal 66/100 · 8 disclosed gaps. This prioritization signal is a derived product heuristic, not a prediction of harm.

TRACE / DIRECT

Benefit applicants

A delayed or incorrect eligibility recommendation can interrupt access to support.

Recorded basis: Synthetic scenario for testing; real occurrence and magnitude are unknown.

Can these people see and shape the path?Meaningful notice existsThey can understand where AI affects the workflow and what the notice means.Affected-person knowledge is representedDesign and review include lived or directly affected expertise rather than assuming it.Correction or recourse existsA named, usable path can correct evidence, challenge an outcome, and obtain response.

Consequence controls · Build 012: Severity and affected-person controls rise with the bounded use.
Workflow propagation · Build 013: The map inherits the workflow path and its uncontrolled propagation checks.
Institutional transfer · Build 017: Notice, responsibility, evidence, acceptance, incident duty, and recourse survive the handoff.

Canon boundary: title, job, B-Web sentence, and lineage are frozen canon. The question, thesis, fixture, exposure formula, thresholds, labels, and explanatory interface copy are derived implementation copy. Everything runs client-locally; no data is submitted or retained.