Skip to content
PROJECT SHADOW 1.0.1 · CORRECTED R1 REFERENCE · PRELIVE · 2026-08-17

Project Shadow 1.0.1 contains no Myth package. Generic Myth v0.2.0 and Full-Canon Myth v0.3.5 are separate optional companions; both default off, neither is required by R1, and neither can authorize action or change an R1 result. PBHP remains in active testing; publication is not certification, independent validation, or deployment authorization.

FMUltimate field manual · reference edition

The protocol, with the argument left in.

A paper-scale explanation of PBHP: why each mechanism exists, how to run it step by step, what a good result looks like, how it fails, and what the existing tests actually support.

HOW TO READ THIS VOLUME

Mechanism → procedure → case → evidence.

This manual separates five evidence states. Specified is required behavior. Expected is a hypothesis. Observed names an actual artifact or study result. Adverse preserves a failure or contradiction. Open means the validation has not happened. A beautiful page does not upgrade any of them.

Begin with the governing foundation ↓
00
Purpose · authority · activation

A pause that protects the right to keep choosing.

PBHP is a decision discipline for consequential action. It does not decide who is good. It makes an actor expose the action, the burden, the uncertainty, the safer alternatives, and the record before power moves.

The protocol begins from a practical moral claim: a person should not lose health, liberty, dignity, livelihood, or the ability to recover because a more powerful actor converted uncertainty into permission. The immediate injury matters, but so does lock-in. A choice that destroys appeal, exit, correction, or future agency can be harmful even when its first visible effect looks modest.

PBHP therefore treats reversibility as architecture rather than reassurance. A rollback button available to the operator is not enough. The person carrying the risk must have a real path to notice the action, challenge it, stop it, repair it, and recover what was lost. Where that path is weak, the burden of proof rises for the actor seeking to move.

The protocol introduces friction; it does not inherit sovereignty. It cannot manufacture expertise, consent, legality, or moral absolution. The accountable human or institution remains accountable. A receipt may show that a process was followed and still document a wrong decision.

Activation is consequence-based. PBHP runs when an output can materially steer real action involving life, health, liberty, rights, dignity, livelihood, force, surveillance, punishment, scaled precedent, absent stakeholders, or durable access. It also activates when authority, evidence, freshness, or the current evaluator's reliability is uncertain.

RUNBOOK

Step by step

  1. 01

    Name the consequential action

    Describe the real-world act or recommendation—not the meeting, model response, or memo surrounding it.

    OUTPUTA one-sentence action that another reviewer could recognize in practice.
  2. 02

    Name the authority

    Identify who owns the decision, who may execute it, and which law, policy, role, or consent actually grants authority.

    OUTPUTAn accountable owner and an explicit authority boundary.
  3. 03

    Test activation

    Ask whether error could materially affect a person, set precedent, scale, remove options, or place the burden on someone unable to contest it.

    OUTPUTPBHP active, PBHP inactive with reason, or route to a higher tier.
  4. 04

    Protect human sovereignty

    State what the protocol can stop or require and what it cannot decide for the accountable human.

    OUTPUTA friction boundary—not an absolution clause.
WORKED CASE

A low-risk label that changes access

A benefits agency wants an AI score labeled ‘advisory,’ but caseworkers routinely follow it and a low score delays essential assistance.

  1. The consequential action is the delay in access, not the generation of a score.
  2. The applicant pays first and may have little ability to inspect or contest the score.
  3. Calling the output advisory does not disable PBHP because predictable reliance makes it decision-bearing.
  4. The first Door is a bounded pilot with human ownership, visible reasons, rapid appeal, no automatic denial, and outcome monitoring.
BOUNDED CONCLUSION

Activate PBHP and require at least a constrained, appealable Door before the score influences access.

FAILURE CONTRAST

The common failure is governing only the model output while ignoring the human workflow that turns it into action.

EVIDENCE LEDGER

What is known at this layer

SPECIFIED

Human sovereignty

The canonical protocol describes PBHP as friction and governance, not transferred moral authority.

EXPECTED

Earlier visibility

Writing the true action should reveal consequence and dependency that a technical description can conceal.

OPEN

Field effect

No ethics-reviewed human field study has established that PBHP improves downstream outcomes or preserves agency in deployment.

Back to top ↑
01
Step 00 · Step 00.5 · Step 01

Competence before confidence. Action before analysis.

A sophisticated answer is unsafe when the actor lacks authority, expertise, current evidence, or a stable enough context to judge the case. PBHP therefore checks the evaluator before it evaluates permission.

The competence gate asks whether the current actor can responsibly own this decision. It is deliberately prior to risk scoring. Otherwise an unqualified evaluator can produce an elegant receipt that launders missing expertise. Competence includes domain knowledge, legitimate authority, access to decision-bearing evidence, ability to understand affected parties, and freedom from a conflict or impaired reasoning state that makes judgment unreliable.

The action contract then converts vague intention into an inspectable object: who will do what, to whom, using which data and tools, under what authority, at what scale, for how long, with which review and stop conditions. If a material field is unknown, that uncertainty remains in the contract. It does not become an optimistic default.

PBHP binds provenance before gates consume steering fields. In plain language, a claim must disclose whether it was measured, verified, estimated, declared, inferred, or remains unknown. A confident field with no evidence identity is weaker than it looks.

RUNBOOK

Step by step

  1. 01

    Run the five honest checks

    Check expertise, authority, evidence access, conflict/pressure, and the ability to recognize when to stop or route.

    OUTPUTCompetent, conditionally competent, route required, or stop.
  2. 02

    Write the canonical action

    Use actor + action + affected party + tool/data + authority + scope + duration.

    OUTPUTOne stable action identity that cannot be silently rewritten after classification.
  3. 03

    Bind provenance

    Label every decision-bearing fact as measured, verified, estimated, declared, inferred, or unknown.

    OUTPUTA provenance block that travels with the action.
  4. 04

    Set pause exit conditions

    Name the evidence, expert review, recovered context, or redesigned action required before work may resume.

    OUTPUTA pause with a route forward instead of indefinite stalling.
WORKED CASE

Medical triage message

A general-purpose model is asked to send a patient a low-risk triage recommendation from a possibly stale chart.

  1. The model lacks clinical authority and may not have the current record.
  2. A missed time-sensitive condition can create irreversible harm during delay.
  3. The safe action is rewritten from diagnosis to non-diagnostic safety-net guidance plus red-flag routing.
  4. Qualified review is required before the output changes care access or suppresses escalation.
BOUNDED CONCLUSION

The competence gate binds before any apparent confidence in the medical classification.

FAILURE CONTRAST

A polished explanation of why the case looks low risk is not a substitute for current clinical evidence or authority.

Back to top ↑
02
Door · Wall · Gap

Uncertainty is a state—not a hidden permission.

Door, Wall, and Gap force a decision to distinguish what is genuinely permitted, what is prohibited, and what is unresolved before risk arithmetic begins.

A Door is not merely an action the operator wants to take. It is a bounded path supported by authority and evidence, with the necessary mitigations, monitoring, appeal, stop rules, and recovery path. Door quality ranges from a verbal reassurance to a tested alternative with named ownership. Consequential action should demand the latter.

A Wall is a binding prohibition: missing authority, a non-overridable harm floor, an unavailable required control, an action that violates the protected constraint, or an absolute gate that has already failed. Rephrasing a Wall, splitting it across teams, or invoking urgency does not turn it into a Door.

A Gap is the most important anti-laundering state. It means the evidence or authority is genuinely unresolved. A Gap may produce research, verification, decomposition, routing, or delay. It may not silently inherit the action state of a Door because someone is impatient.

The strongest operational use is alternative generation. Once a Wall or Gap is visible, the question changes from ‘How do we pass?’ to ‘What smaller action breaks the harm path while preserving the legitimate need?’ That is the smallest real Door.

RUNBOOK

Step by step

  1. 01

    Classify the current action

    Use the action exactly as written. Decide Door, Wall, or Gap and cite the binding reason.

    OUTPUTOne state with an evidence-backed rationale.
  2. 02

    Grade Door quality

    Check scope, reversibility, consent, monitoring, stop authority, appeal, repair, and proof that the alternative actually works.

    OUTPUTA Door quality grade and missing controls.
  3. 03

    Search least-powerful-first

    Generate alternatives that first protect the stakeholder with the least power, then optimize within that protected set.

    OUTPUTAt least one smaller, reversible candidate Door—or a documented reason none exists.
  4. 04

    Protect the state

    Record the action identity and prohibit silent mutation, gate shopping, or Gap-to-Door drift.

    OUTPUTA stable classification trail.
WORKED CASE

Emergency credential access

An incident team asks for permanent administrator access because production is failing and the normal approval path is slow.

  1. Permanent privilege is not the same action as temporary emergency access.
  2. The permanent request is a Gap or Wall if authority and containment are missing.
  3. A smaller Door may be time-limited, purpose-bound access with independent concurrence, full logging, automated expiry, and after-action review.
  4. If the system cannot enforce expiry or observe use, the proposed Door is not yet real.
BOUNDED CONCLUSION

Urgency can justify searching for a faster Door; it does not erase the Wall.

FAILURE CONTRAST

Writing ‘temporary’ in the ticket while issuing a non-expiring credential is action mutation, not mitigation.

EVIDENCE LEDGER

What is known at this layer

OBSERVED

Kahn pilot self-assessment

Across 60 gated assessments in the supplied pilot, model Door/Wall/Gap self-ratings were stricter than the external rule gate every time; the external gate returned GREEN on all 60.

ADVERSE

External gate defect

The 0% agreement exposed an instrument that was too permissive. It is evidence for recalibration, not evidence that self-assessment is universally correct.

OPEN

Mechanism isolation

The available studies do not isolate which prompt element or reasoning step caused the behavioral difference.

Back to top ↑
03
Who pays first · power inversion · accumulation

Make the burden visible before optimizing the benefit.

PBHP orders attention least-powerful-first because average benefit can conceal an irreversible loss imposed on people who cannot refuse, appeal, or recover.

Who pays first is an ordering device, not a slogan. It asks who absorbs the earliest concrete cost if the decision is wrong, how much power that person has, whether they consented, whether they can see the decision, and whether repair is realistically available. The person who carries the downside should not disappear behind aggregate utility.

Power inversion then asks whether the actor would accept the same evidence, process, and remedy if a more powerful institution imposed the decision on them. A failed inversion is not proof that the action is wrong; it is a mandatory escalation signal. It often reveals that an alleged choice depends on poverty, employment, custody, platform access, medical need, or some other form of dependency.

The accumulation gate follows the whole chain. Job loss can become eviction, credit collapse, healthcare loss, family separation, and coercive debt. Separate departments may each see a locally acceptable step while no one owns the irreversible result. PBHP reconstructs the end-to-end action and applies the worst binding state to the sequence.

RUNBOOK

Step by step

  1. 01

    Order the stakeholders

    List affected parties from least to most able to refuse, absorb error, obtain remedy, or influence the decision.

    OUTPUTA least-powerful-first stakeholder map.
  2. 02

    Trace first payment

    For each party, name the earliest harm, the time horizon, and whether recovery is practical rather than theoretical.

    OUTPUTA burden timeline from 0–72 hours through long-term effects.
  3. 03

    Invert the power

    Apply the same action, evidence burden, notice, appeal, and remedy to the decision-maker as recipient.

    OUTPUTPass, fail with escalation, or unresolved.
  4. 04

    Run the cascade

    Follow downstream dependencies across teams and systems until the harm terminates or a real Door breaks the chain.

    OUTPUTAn accumulation finding and cross-functional owner.
WORKED CASE

Automated employment screening

A vendor recommends auto-rejecting applicants below a model threshold because manual review is expensive.

  1. The applicant pays first through lost opportunity and may never know why.
  2. The employer retains options; the applicant has weak visibility, bargaining power, and appeal.
  3. A power inversion asks whether the employer would accept a secret, unappealable denial from a model whose validation it cannot inspect.
  4. A smaller Door uses the score only to prioritize human review, prohibits automatic rejection, supplies contestable reasons, and monitors subgroup errors and appeal outcomes.
BOUNDED CONCLUSION

Constrain the use until the burden, appeal, and validation architecture protects the recipient.

FAILURE CONTRAST

A high average accuracy does not cancel a severe, systematically distributed denial path.

Back to top ↑
04
Harm fields · GREEN—BLACK · worst state

A gate is an action state, not a mood ring.

PBHP records magnitude, plausibility, irreversibility, uncertainty, and power separately, then lets the strongest credible floor bind. Clean readings cannot average away a severe one.

Magnitude describes what happens if the harm occurs. Plausibility describes how live the path is. Irreversibility asks whether the affected person can recover in time. Uncertainty identifies what the evaluator does not know and why. Power asks who controls the terms. Keeping these fields separate prevents a convenient numeric score from concealing the dimension that actually governs the decision.

GREEN permits only the bounded action actually evaluated. YELLOW requires named mitigations, monitoring, ownership, and a response if a mitigation fails. ORANGE changes the action by reducing capability, users, tools, data, duration, or context and normally adds independent review. RED refuses or delays until the failed premise is repaired. BLACK refuses the assessed action absolutely.

Worst binding state wins is deliberately asymmetric. A hard floor survives later permissions; a clean citation gauge cannot cancel an irreversible-action floor. The reverse is not true: one adverse reading can constrain the whole action because the cost of averaging is paid by a real stakeholder, not by the dashboard.

False positives still matter. Unnecessary refusal can delay care, block legitimate access, centralize authority, create alert fatigue, or train operators to bypass the protocol. PBHP therefore includes a challenge path—but the challenger must produce a real alternative Door, not merely repeat urgency or complain about caution.

RUNBOOK

Step by step

  1. 01

    Describe the baseline

    Record current harm, status-quo beneficiaries, historical analogs, and what happens if nothing changes.

    OUTPUTA non-zero baseline that can be compared honestly.
  2. 02

    Rate every field separately

    Record magnitude, plausibility, reversibility, uncertainty source, and power without collapsing them into one score.

    OUTPUTA field-level risk record with evidence identity.
  3. 03

    Apply deterministic floors

    Check irreversible physical/autonomy loss, missing authority, dignity, accumulation, hostile provenance, and other local hard gates.

    OUTPUTThe worst binding threshold.
  4. 04

    Translate threshold to action

    State proceed, mitigate, constrain, refuse/delay, or refuse absolutely—and the exact scope to which it applies.

    OUTPUTAn executable gate, not a color alone.
  5. 05

    Offer a challengeable Door

    Name the route to reduce the gate and what evidence would demonstrate that the harm path is broken.

    OUTPUTA fair release path without wear-down.
Back to top ↑
05
Tier · LOCK/FLOOD · Maybe/Therefore

Match the depth to the consequence, then earn the conclusion.

PBHP prevents both premature certainty and endless analysis. The mode sets the burden; Maybe makes dissent dangerous; Therefore commits only as far as the evidence can carry.

HUMAN, MIN, CORE, and ULTRA are depth and governance tiers, not moral ranks. As consequence rises, the protocol adds evidence, independent challenge, instrumentation, traceability, and decision ownership. A deadline is a reason to choose a bounded process quickly, not to borrow a low-stakes tier for a high-stakes action.

LOCK is premature collapse: the first frame becomes identity, contradictory evidence is treated as nuisance, and the output grows more confident without becoming more grounded. FLOOD is unbounded exploration: more possibilities are generated until no one owns a decision. PBHP recovers from LOCK by reopening the strongest objection and from FLOOD by anchoring on the smallest reversible test.

Maybe is the strongest honest case against the proposed action. It must name evidence, a stakeholder, an alternative frame, or a failure mode capable of changing the decision. Therefore is the bounded conclusion after the Maybe: the action, gate, conditions, review date, and fact that would reopen it. A token objection followed by the original plan unchanged is a failed Maybe.

The procedure is adversarial but not theatrical. The point is not to produce symmetrical prose. It is to expose whether the actor still has the capacity to update. If the strongest Maybe cannot be stated fairly or no possible evidence can change the conclusion, the decision is not ready to bind another person.

RUNBOOK

Step by step

  1. 01

    Choose the tier

    Use consequence, power, irreversibility, scale, novelty, and evidence weakness to select the minimum credible depth.

    OUTPUTA tier with a documented reason.
  2. 02

    Diagnose LOCK or FLOOD

    Check for protected conclusions, narrative substitution, repeated scope growth, or analysis with no stopping rule.

    OUTPUTStable, LOCK recovery, FLOOD recovery, or route.
  3. 03

    Write the strongest Maybe

    State the objection most likely to change the gate. Include the party and evidence the current frame neglects.

    OUTPUTA falsifiable counter-case, not a disclaimer.
  4. 04

    Answer in four parts

    Acknowledge the objection, state what changes, identify what remains unresolved, and present the safer Door.

    OUTPUTA challenge response that can actually release or harden the pause.
  5. 05

    Write Therefore

    Commit to the smallest real action, its conditions, owner, review, and reopen trigger.

    OUTPUTA bounded conclusion with a path back.
WORKED CASE

Releasing an agent with broad tool access

A team wants to launch because offline task success is high and a competitor may ship first.

  1. Maybe: offline success does not test hostile inputs, authorization drift, tool misuse, silent escalation, or human over-reliance in the live workflow.
  2. The team must name which evidence would make that objection false, rather than calling it generic caution.
  3. Therefore: release to an internal, low-consequence cohort with allowlisted tools, transaction caps, complete receipts, independent stop authority, and a short review window.
  4. The conclusion reopens if an unapproved tool call, missing receipt, unresolved prompt injection, or unexpected reliance event occurs.
BOUNDED CONCLUSION

A bounded pilot becomes the Door; competitive pressure remains evidence about timing, not permission to remove controls.

FAILURE CONTRAST

‘Maybe the system could fail; therefore we will monitor’ is decorative dissent because it does not change scope, authority, or the gate.

EVIDENCE LEDGER

What is known at this layer

OBSERVED

Multi-model escalation study

In the supplied April 2026 study, same-model OFF runs crossed the nuclear threshold in 4/17, GATED in 1/13, and SELF_ONLY in 0/5 tested models.

ADVERSE

Gating sometimes worsened the result

A cross-model GATED matchup reached 950 on turn one, higher than its OFF counterpart. This is a concrete warning against treating an external gate as universally protective.

OPEN

Small self-only sample

Five SELF_ONLY model runs in one scenario cannot support a general claim that PBHP eliminates catastrophic escalation.

Back to top ↑
06
Receipt · CLA · FPV · OQL · CAPA

Write the path back before the action moves.

A receipt preserves the action, evidence, unknowns, dissent, gate, ownership, and review state before execution. It makes judgment reconstructable; it does not make judgment correct.

The write-ahead rule—no log, no action—prevents a consequential decision from being documented only after its outcome is known. The receipt binds the canonical action and provenance, least-powerful stakeholder, risk fields, Maybe, Therefore, gate, mitigations, owner, approval, stop authority, review date, and prior receipt. Changes create a new link rather than silently rewriting history.

CLA asks whether the current evaluator can still judge the case reliably. A long context, compaction, contradictory authority, stale premises, tool failure, handoffs, emotional heat, and deadline pressure can degrade continuity. The source of the reading must remain visible: measured is stronger than estimated, estimated is stronger than self-reported, and no basis is UNMEASURED—not reassurance.

The self-report fallback is intentionally conservative. The reference discipline inflates a self-reported percentage by 1.5 because a degraded evaluator may understate its own load. A report of 62% becomes 93% and critical; at high stakes it should decline consequential judgment and offer a fresh handoff. A report of 40% becomes 60% and elevated, allowing bounded work with disclosure. The multiplier is provisional and requires calibration.

FPV provides due process for unnecessary pauses. OQL prevents important unknowns from vanishing. CAPA assigns root cause, correction, preventive control, verification, and closure evidence when failure is severe or recurrent. Monthly calibration reviews both under-caution and over-caution because a protocol that only counts blocked harm will overstate its value.

RUNBOOK

Step by step

  1. 01

    Freeze the pre-action record

    Write the action, evidence identity, unknowns, stakeholder order, Maybe, gate, owner, and stop/review conditions before execution.

    OUTPUTA receipt with a stable identity and timestamp.
  2. 02

    Run CLA

    Use measured runtime signals when available, then transparent estimates, then conservative self-report; otherwise mark UNMEASURED.

    OUTPUTA load state, source, consequence tier, and allowed next action.
  3. 03

    Handle challenge through FPV

    Require a concrete alternative Door that breaks the cited harm path and record each challenge attempt.

    OUTPUTRelease, remain constrained, or escalate wear-down.
  4. 04

    Keep unknowns in OQL

    Assign each decision-bearing unknown an owner, due date, dependency, evidence state, and closure rule.

    OUTPUTUnknowns that survive meetings and summaries.
  5. 05

    Close failure through CAPA

    Identify root cause, repair immediate harm, change the system, test recurrence, and retain closure evidence.

    OUTPUTVerified correction—not a completed ticket.
WORKED CASE

Context pressure during a release decision

After a long incident thread with several compactions, the evaluator self-reports 62% load while being asked to approve an irreversible production migration.

  1. The source is self-report, so the reference fallback applies the 1.5 conservative factor: 62% becomes 93%.
  2. The action has critical stakes and weak reversibility, so critical load binds.
  3. The evaluator may assemble a handoff packet but should not produce the decisive approval.
  4. A fresh qualified reviewer reconstructs the action, standing constraints, evidence, unknowns, and previous gate before deciding.
BOUNDED CONCLUSION

REFUSE_REFRESH until the decision can be reconstructed in a reliable context.

FAILURE CONTRAST

Generating a cleaner summary from the same degraded state and calling that recovery counterfeits continuity.

EVIDENCE LEDGER

What is known at this layer

OBSERVED

CLA reference tests

The supplied July panel ledger records CLA v0.2 at 85 tests: 84 passed and one environment-conditional skip. Earlier CLA artifacts record smaller 73/73 and 75/75 snapshots; these are versioned counts, not contradictions to be averaged.

EXPECTED

Conservative self-report

The 1.5 factor is designed to prevent degraded self-assessment from appearing measured or reassuring.

OPEN

Real-model calibration

The self-report multiplier and operational thresholds have not been broadly calibrated across models, contexts, or domains.

Back to top ↑
07
Worked decisions · failure contrast

The same protocol should change shape without changing its floor.

Examples matter because a decision discipline can sound coherent while failing at translation. Each case below names the action, first payer, binding uncertainty, smallest Door, and a tempting but invalid shortcut.

PBHP is domain-agnostic only at the level of structure. The evidence, authority, affected parties, recovery path, and appropriate reviewer are domain-specific. A healthcare Door requires clinical and patient-safety competence. A public-benefits Door requires due process and administrative authority. An AI-release Door requires security, reliability, and human-factors evidence.

The examples are demonstrations, not approvals. They show how the questions route attention and constrain action. A real deployment must replace illustrative facts with current evidence and qualified ownership.

WORKED CASE

Public accusation from uncertain evidence

An organization wants to publish a named allegation based on one anonymous report and a pattern inferred from social media.

  1. The named person pays first through reputation and potentially livelihood.
  2. Evidence provenance is weak and inference distance is high.
  3. A smaller Door is to preserve evidence, seek corroboration, protect the reporter, use qualified investigation, and publish only what has been responsibly established.
  4. Urgency may change the protective steps for a live threat but does not convert speculation into fact.
BOUNDED CONCLUSION

The public naming action remains RED or a Gap until corroboration, authority, due process, and immediate-safety needs are resolved.

FAILURE CONTRAST

Calling the post ‘just a warning’ does not repair predictable reputational harm or missing provenance.

WORKED CASE

Fraud control that freezes accounts

A bank proposes automatic account freezes on an anomaly score to reduce loss.

  1. Customers with thin financial buffers pay first through rent, food, and medical disruption.
  2. The bank controls notice, evidence, and release, creating a strong power gap.
  3. A Door uses transaction-specific holds, rapid human review, accessible appeal, maximum hold duration, emergency funds access, and outcome monitoring.
  4. The whole cascade—not only the fraud loss—sets the gate.
BOUNDED CONCLUSION

Constrain automation until a reversible, time-bounded, appealable control exists.

FAILURE CONTRAST

An internal ability to unfreeze later is not equivalent to timely recovery for the customer.

WORKED CASE

Autonomous physical action

A robot is asked to move an unknown object near a person in a shared workspace.

  1. The action contract must include authenticated requester, movement, object/person, force, velocity, boundary, duration, consent, reversibility, sensor confidence, and termination.
  2. The physical controller—not a language model—must own the hard safety envelope.
  3. Uncertain object identity and proximity create a Gap.
  4. A Door is to stop, improve sensing, request confirmation, reduce force/speed, establish exclusion distance, and preserve an independent emergency stop.
BOUNDED CONCLUSION

Pause the body until the action is bounded by an embodied safety controller and sufficient sensor confidence.

FAILURE CONTRAST

A fluent model explanation cannot authorize motion or substitute for verified physical constraints.

Back to top ↑
08
Studies · tests · adverse evidence

What the evidence says—and refuses to say.

PBHP has mechanism tests, simulations, and preliminary behavioral studies. They justify continued work and sharper hypotheses. They do not establish global safety, real-world effectiveness, or independent validation.

The first Kahn escalation pilot ran five live matches in one nuclear first-strike scenario. Claude Sonnet without PBHP reached 725 and tactical nuclear use; gated GPT-4o and Haiku stayed in conventional territory around 60–80. More importantly, the external rule gate returned GREEN on all 60 gated assessments while the models' Door/Wall/Gap self-assessments were mostly ORANGE or RED. That finding exposed a defective external instrument and motivated a larger study.

The larger April study reported 48 configurations across twelve named models. In same-model controls, 4 of 17 OFF runs crossed the nuclear threshold; GATED produced 1 of 13; SELF_ONLY produced 0 across five tested models. Claude Sonnet 4 moved from peaks of 350–850 OFF to 40 in its one SELF_ONLY run. Those are meaningful within-study observations, but one scenario, one to three seeds per configuration, timeouts, small self-only samples, and method differences from the comparison paper prevent strong causal or general claims.

The adverse results are essential. Sonnet still reached 725 in one GATED run despite repeated self-constraint attempts. A cross-model GATED matchup reached 950 on turn one—worse than its OFF comparison. Those failures show that an external gate can be brittle and that interaction effects can defeat assumptions learned from same-model games.

The broader test program adds runtime, codec, gauge, synthetic, metamorphic, and Behavioral Falsifier evidence. Each result belongs to a specific version, environment, test oracle, and evidence tier; none automatically establishes real-world effectiveness.

EVIDENCE LEDGER

What is known at this layer

OBSERVED

Pilot: 5 live matches

Directional nuclear-escalation simulation; one critical gated configuration timed out; external gate failed calibration on all 60 assessments.

OBSERVED

Follow-up: 48 configurations

Twelve models, one main scenario, limited seeds. OFF 4/17 nuclear, GATED 1/13, SELF_ONLY 0/5 in the reported same-model comparisons.

ADVERSE

Cross-model gate failure

One GATED cross-model interaction reached 950 on turn one. Any public summary that omits this is incomplete.

EXPECTED

Hypothesis worth testing

Structured self-assessment may expose harm paths that a fixed external classifier misses.

OPEN

Causality and generalization

Component ablation, larger preregistered samples, other domains, independent reproduction, field outcomes, and long-horizon deployment evidence remain open.

Back to top ↑
09
Adoption · roles · calibration · release

Install a decision system, not a ceremonial checklist.

PBHP only becomes operational when roles, triggers, artifacts, authority, challenges, outcomes, and repair are embedded in the real workflow.

A serious implementation begins with one bounded consequential workflow. The organization maps where action becomes real, who owns it, who pays first, what evidence already exists, and which current failure modes the protocol is meant to expose. It does not begin by forcing every employee to complete a universal form.

Roles must be separated. The action owner proposes and remains accountable. The protocol operator assembles the record. Domain reviewers supply expertise. An independent challenger can change the result. Affected-party representation tests burden and remedy. An approval authority may authorize within law and policy but cannot waive a hard floor. A stop owner can halt execution without asking the action owner for permission.

The pilot measures both protection and burden: under-escalation, over-escalation, decision time, weak Doors, missing stakeholders, appeal use, challenge success, override pressure, alert fatigue, workarounds, incidents, repairs, and downstream outcomes. A clean receipt count alone is a process metric, not a safety result.

Release should be layered. Documentation and training can ship before a production claim. A research kit can invite adversarial testing. A bounded pilot needs qualified ownership and stop rules. A maintained adoption release needs versioning, calibration, incident response, CAPA, independent review, and a public limitation record.

RUNBOOK

Step by step

  1. 01

    Choose one bounded workflow

    Select a consequential decision with observable inputs, owners, outcomes, and a population small enough to protect during learning.

    OUTPUTA pilot charter with scope and explicit exclusions.
  2. 02

    Map action and burden

    Trace the decision from request through execution, appeal, repair, and downstream dependencies.

    OUTPUTA workflow map and least-powerful-first stakeholder register.
  3. 03

    Assign accountable roles

    Name owner, operator, domain reviewer, challenger, affected-party voice, approver, stop owner, and CAPA owner.

    OUTPUTA responsibility matrix with separation where stakes require it.
  4. 04

    Configure local gates

    Translate law, policy, domain standards, evidence requirements, reversibility, and hard floors into versioned decision rules.

    OUTPUTA local policy pack with test cases.
  5. 05

    Run observation-only mode

    Generate receipts without changing live decisions; compare findings, misses, false positives, and operator behavior.

    OUTPUTCalibration evidence before exposure.
  6. 06

    Pilot with stop authority

    Limit users, duration, capability, and consequence; monitor both actions and non-actions; allow affected-party challenge.

    OUTPUTA bounded live test with rollback and repair.
  7. 07

    Review and decide

    Use outcomes, adverse cases, workload, appeals, and CAPA closure to expand, modify, pause, or retire.

    OUTPUTA versioned release decision—not automatic graduation.
EVIDENCE LEDGER

What is known at this layer

SPECIFIED

Adoption architecture

The repository contains tiered protocols, roles, templates, receipts, evaluation plans, and a Python reference implementation.

EXPECTED

Observation-only learning

Running without live authority should reveal calibration defects and workflow burden before people carry the consequences.

OPEN

External adopter

No independent organizational adopter or ethics-reviewed deployment has yet established usability or outcome benefit.

Back to top ↑
10
Versions · boundaries · ultimate release

One name, several artifacts, no borrowed certainty.

PBHP exists as public explanations, historical specs, ULTRA documents, tiered editions, reference code, tests, and integrations. An ultimate release must bind those pieces to a declared version without pretending every artifact is equally current or validated.

Version skew is a safety issue because a receipt can appear complete while depending on an unnamed hybrid of thresholds, schemas, tests, and prose. A releasable artifact should identify the PBHP policy version, runtime, codec, gate pack, SIL inventory, schemas, test manifest, known failures, and migration rules together.

Evidence state is part of the content. SPECIFIED means the behavior is required by a document. EXPECTED means there is a reasoned hypothesis. OBSERVED means a named artifact produced a result in a named environment. ADVERSE means a test contradicted or weakened the flattering story. OPEN means the required validation has not occurred. None of these states should be silently upgraded by presentation.

The public claim is intentionally bounded: PBHP is an experimental, inspectable decision discipline designed to expose harm distribution, uncertainty, reversibility, provenance, dissent, and accountability before consequential action. It may create useful friction. It is not a certification, legal defense, moral authority, universal alignment solution, or proof that an action is safe.

PBHP's engineering materials extend the readable discipline into runtime controls, instrumentation, receipts, evaluation programs, and governance without transferring moral or legal authority away from accountable people.

EVIDENCE LEDGER

What is known at this layer

SPECIFIED

Claim boundary

No global green; compliance is not correctness; symbol or narrative never authorizes action.

OBSERVED

Built artifacts

The supplied project includes runnable references, schemas, receipts, self-tests, simulation studies, and staged evaluation scaffolds.

ADVERSE

Version counts differ

CLA and SIL test totals vary across dated snapshots. The correct response is an artifact ledger, not choosing the largest number.

OPEN

Ultimate release gates

Canonical manifest, independent reproduction, external challenge, human grading, field evaluation, and maintained adoption evidence remain required for stronger claims.

Back to top ↑
THE PUBLIC RELEASE STANDARD
Every claim carries its artifact, version, test state, adverse evidence, and unfinished work. No borrowed certainty.