L32 BOUNDARY CASES WORKSHEET
Label: No AI. The reasoning is yours.

All four cases are constructed for this course. The organizations are invented.

The placement scale
  A  Automated: the system acts; no person looks at individual cases.
  B  Automated, with exceptions to a person: the system acts; flagged or
     contested cases go to a person who can override.
  C  Person decides, system recommends: nothing happens until a person
     decides; the system's output is advice.
  D  Person only: no system output is used for the decision.

For each case write:
  PLACEMENT (A-D):
  THE DECISION THAT NEEDS JUDGMENT (name it exactly; it may be one part of the process):
  WHO BEARS A WRONG DECISION, AND CAN IT BE UNDONE?
  WHAT WOULD MAKE YOU MOVE ONE STEP TOWARD A? ONE STEP TOWARD D?
  WHAT THE PERSON MUST BE SHOWN, AND WHETHER THEY CAN SAY NO:

Case 1. Hiring screen
  PLACEMENT:
  JUDGMENT:
  WHO BEARS IT / UNDO:
  TOWARD A / TOWARD D:
  SHOWN / CAN SAY NO:

Case 2. Loan decisions
  PLACEMENT:
  JUDGMENT:
  WHO BEARS IT / UNDO:
  TOWARD A / TOWARD D:
  SHOWN / CAN SAY NO:

Case 3. Medical scheduling
  PLACEMENT:
  JUDGMENT:
  WHO BEARS IT / UNDO:
  TOWARD A / TOWARD D:
  SHOWN / CAN SAY NO:

Case 4. Content moderation
  PLACEMENT:
  JUDGMENT:
  WHO BEARS IT / UNDO:
  TOWARD A / TOWARD D:
  SHOWN / CAN SAY NO:

REVISING YOUR L29 DECISION POINTS
For each L29 proposal: keep, change or drop it, and name the configuration
feature (permission, bound, stopping condition, approval prompt) that would
make it real.

1.

2.

3.
