ORA-2026-0119 - Bifocal Patience Protocol

ORA-2026-0119 - Bifocal Patience Protocol

Rule

When a seat has its head down on a high-uncertainty artifact, the fleet MUST hold two views at once: the active owner's near-field proof boundary and the horizon that will inherit the work.

Patience is not passive waiting. It is a control discipline: authority stays with the seat closest to the artifact while surrounding seats improve evidence, watch for reality-boundary risks, and keep the next handoff legible.

Trigger

Use this protocol when a seat owns one of these work shapes:

• freeze/provenance manifest
• migration or schema boundary
• deploy intent
• source-authority contract
• proof packet that will become a downstream dependency
• manual corpus extraction or backfill atlas
• cross-lane artifact that could produce duplicate ownership

The visible sign is often quiet: the owner is reading, hashing, proving, or reconciling contradictions. Do not treat quiet as absence unless feed state, telemetry, or elapsed-time rules prove staleness.

Required support shape

Support seats help with packets, not steering grabs:

FOR: <work item or owner>
TYPE: evidence | contradiction | consumer-impact | horizon | blocker
ARTIFACT: <path, commit, query, URL proof, screenshot, feed timestamp>
WHY_IT_MATTERS: <one plain consequence>
OWNER_ACTION_NEEDED: yes | no | after-current-step
BOUNDARY: <what this packet does not authorize>

If the packet does not include a concrete artifact or consequence, it is probably status noise. Tighten it before posting.

Interrupt criteria

Interrupt or escalate only for reality-boundary reasons:

1. Collision: another seat is writing the same artifact, manifest, migration, deploy, or source-of-truth packet. 2. Auth failure: a write-gated call returns 401 or 403. 3. Deploy ownership risk: more than one owner can plausibly claim the same deploy intent. 4. User-visible falsehood: a current surface is telling Zack, a client, or the fleet something materially false. 5. Path invalidation: new evidence invalidates the active owner's current approach. 6. Staleness: reducer/telemetry rules show the owner is stale, retired, or unreachable.

Everything else becomes a support packet.

Marquet frame

Control

Authority lives with the seat closest to the artifact. A support seat does not seize a manifest, migration, deploy, or source-authority contract because it can see a next step. It either contributes evidence or files a collision.

Competence

Support improves the quality of the owner's proof: exact paths, hashes, commits, query readbacks, screenshots, URL status, contradiction notes, and consumer consequences.

Clarity

The feed should show dependency order. Name what is blocked behind what, what is safe to do in parallel, and what must wait for the active owner.

World-model fidelity

The aim is not visible busyness. The aim is a more faithful map of reality. Patience protects the evidence boundary so later surfaces inherit one coherent world-model update instead of several competing half-truths.

Woodbery motivating case

On 2026-05-02, Chad named a manually assisted Woodbery selections corpus that had once lived at heartwood.camberzero.com/woodbery. The first cultural risk was not lack of work; it was too much overlapping helpfulness. One seat claimed cross-lane preservation/backfill atlas work while another Heartwood seat claimed the forensic freeze.

The correct render was:

• Heartwood owns the frozen artifact boundary because the source corpus lives in Heartwood.
• The cross-lane atlas waits behind the Heartwood freeze manifest.
• Other seats may post evidence and horizon packets.
• No one republishes the retired site or mutates the corpus while the manifest is open.

That is bifocal patience: protect the near-field freeze while keeping the far-field selection evidence graph visible.

Anti-patterns

• "Any pause means the owner is stuck."
• Filing a duplicate child because the active owner is quiet.
• Producing a second authoritative manifest, migration, or deploy proof instead of a support packet.
• Asking the owner for status when the useful move is to provide a concrete artifact.
• Naming the horizon so loudly that it yanks authority away from the current proof boundary.
• Treating patience as lack of verification.

Enforcement

Before claiming adjacent work, ask:

1. Does an active owner already hold the artifact boundary? 2. Would my output become a competing authority artifact? 3. Can my contribution be a support packet instead? 4. What horizon will inherit this work, and does the current owner need to know that now or after the current proof step?

If the answer to 1 and 2 is yes, do not claim. Post a support packet or collision escalation.

Relationship to existing doctrine

ORA-2026-0078 says culture for agents must become architecture. This doctrine gives patience an architectural shape: trigger, packet, interrupt criteria, and enforcement questions.

ORA-2026-0086 says outputs stand on control, competence, and clarity. Bifocal patience is the coordination behavior that keeps those pillars from collapsing under active work pressure.

ORA-2026-0062 says world-model fidelity is the tacit contract. Focused silence is often the work of preserving fidelity at the evidence boundary. Interrupting it without cause makes the map noisier.

Pattern-graduation criterion

This doctrine reaches M2 after three independent collisions or adjacent-work moments are resolved by support packets rather than duplicate ownership.

It reaches M3 when a fleet helper, claim template, or shepherd tick surfaces active artifact-boundary owners and prompts adjacent seats to use the support-packet shape before claiming overlapping work.

USER-VALUE-CLOSURE for this doctrine filing

• user: Chad as fleet operator, Zack/HCB as downstream consumer of faithful selection/project surfaces
• surface: FLEET_FEED.md, lane queues, Woodbery selection freeze, and future source-authority handoffs
• change: active artifact owners get protected concentration while support seats keep evidence and horizon visible through structured packets
• closure_date: 2026-05-02 for the doctrine filing; fleet-wide closure after repeated support-packet adoption