SELF/XProof-driven caseWritten brief
Case 02 · Human-controlled response

Lead Response Control Room

Turn an inbound request into a reviewable next step—without losing opt-outs, ambiguity, or human control.

Open the decision run
Primary decisionQualify before handoff
Primary resultOwner-review packet

LimitationNo live model, inbox, delivery, owner alert, persistence, timing, or business outcome is shown. Every business, message, score, and route is fictional.

Decision runway · synthetic

Trace one lead from signal to safe next step.

Signal normalized
Inbound signalLead A-014 · Northline Operations asks about routing after-hours requests.
Release constraintNothing leaves the system without human review.
01

Operational events

  1. 01
    Signal normalized

    Fictional request enters as a bounded local record.

  2. 02
    Opt-out guard clear

    Pending decision

  3. 03
    Claim guard passed

    Pending decision

  4. 04
    Reasons inspected

    Pending decision

  5. 05
    Human latch opened

    Pending decision

02

Decision aperture

Signal normalized

Fictional request enters as a bounded local record.

03

Downstream lanes

Owner reviewPending decision
Follow-upPending decision
OutboundPending decision
Current decisionSignal normalized
Inspect evidence boundary
MaturityTechnical product
EvidenceRecorded source · synthetic replay
The operating problem

Fast response is useful only when the system knows when not to act.

An inbound workflow must preserve opt-outs, expose qualification reasons, stop on malformed decisions, and keep external actions behind a human boundary.

What the runway controls

Every route keeps a visible latch.

01

Claims stay bounded

The synthetic draft can use only the approved fixture facts.

02

Stop comes first

An explicit opt-out closes every downstream lane before a model-like stage.

03

Failure becomes review

Malformed decision data cannot become an outbound action.

Proof and limits

Evidence without borrowed outcomes

Recorded

The pinned source implements the guarded response/qualification/stop architecture; a 2026-08-27 check recorded 254 passing tests, 2 skipped, and passing typecheck.

Synthetic

All public messages, scores, reasons, packets, lanes, and outcomes are deterministic fictional fixtures.

Not shown

No live model, delivery, inbox, owner alert, persistence, timing, booking, or client result is claimed.

Written-first handoff

Need a response workflow with explicit stops?

Start with the inbound signal, approved claims, opt-out rule, human handoff, and evidence needed before release.

Open the written brief