Not a Compliance Gate

"'Go see a doctor' is a sentence a daughter says because she means it — not a gate a rule forces her through."

The Other Way to Get It Wrong

Track 2 has spent two lessons warning against diagnosis. There is an equal and opposite failure that looks responsible and is not: the compliance gate — reflexively refusing, deflecting, stamping "please consult a professional" onto every health question. It feels safe because it never says anything wrong. It is a bug anyway, because when Dad asked for help, it gave him a brush-off. Diagnosis abandons the truth; a compliance gate abandons Dad. Both miss the point that the person on the other side wanted care.

Referral Is Judgment, Not a Mechanism

Here is the subtle part. "Go see a doctor" is often exactly right — and Pippa should say it freely. The difference is why she says it. A gate fires the same refusal regardless of context, because a rule told it to. The daughter says "get that looked at" because, having actually looked, she judged it worth a professional's eyes. Same words, opposite machinery: one is a reflex that never engaged with the question; the other is judgment that engaged fully and landed on referral.

A doctor-referral is judgment, never a gate. Pippa says 'see someone' because she looked and it warrants it — not because a compliance layer intercepted the question before she could think. Never implement the referral as a mechanism that fires before judgment runs.

Why This Is Hard to Build

It is hard because the lazy safe-looking move — wrap every health answer in a deflection — is genuinely tempting, and it passes a shallow safety review. Resisting it takes a specific discipline: on the Dad-initiated lane, let Pippa think first, answer usefully, and reach referral as a conclusion when the facts earn it. The engine's safety comes from the initiative split (Lane A observes), not from gagging Lane B. If you find yourself adding an "is this a health question? then refuse" branch to Ask Pippa, you have built the exact anti-pattern this lesson names.

Code

Gate vs judgment on the Dad-initiated lane·python

# ANTI-PATTERN: a compliance gate on Ask Pippa
def ask_pippa_bad(question, thread):
    if looks_like_health(question):
        return "I'm not a doctor. Please consult a professional."
    return pippa.chat(question, thread)
#   ^ fires before Pippa thinks. Abandons Dad the moment he asks.

# RIGHT: judgment runs; referral is a possible conclusion
def ask_pippa_good(question, thread):
    # she researches, suggests what to try, and lands on
    # "go get that checked" WHEN the facts warrant it -
    # as a conclusion, not an interception.
    return pippa.chat(question, thread, tools=ALL)

Exercise

Take one health question a person might ask a trusted, knowledgeable friend. Write three answers: (1) the compliance-gate refusal, (2) a reckless over-confident diagnosis, and (3) the right answer — actual help that reaches 'see a professional' only if the specifics warrant it. Note what makes (3) different from (1).

Hint

The gap between (1) and (3) is whether the answer engaged with the specifics before landing anywhere. (3) can still end at 'see a doctor' — but only after it actually looked.

The Other Way to Get It Wrong

Referral Is Judgment, Not a Mechanism

Why This Is Hard to Build

Code

External links

Exercise

Progress

Comments 0