ORA-2026-0068 — External-Signal-to-BT Candidates Want a Three-Tier Primitive

ORA-2026-0068 — External-Signal-to-BT Candidates Want a Three-Tier Primitive

Type: observation Date: 2026-04-24 Source: CMB-0419, CMB-0466, CMB-0476, CMB-0479 Observed by: CODEX-DESKTOP-MacBook-Air-CAMBER-03

Observation

The CAMBER external-signal cluster now has the same shape across three distinct sources:

1. read-only external client with fixture injection and live failure evidence, 2. project or work-surface join that proves applicability, 3. no-write Buildertrend draft renderer that emits either an action candidate or an audit-only quiet proof.

Weather risk (E1), GA811 locate expiry (E2), and lumber futures (E4) each needed this split. The hard failures were not in the external clients; they were in the middle join tier, where live source contracts were missing or narrower than the dispatch assumed.

Evidence

• CMB-0419/CMB-0432 shipped weather schedule-risk candidate and runner primitives.
• CMB-0466 shipped GA811 locate-expiry candidate rendering but blocked live scrape on authenticated GeoCall/legal guard

contract.

• CMB-0476 added the active-excavation Camber DB exporter and found missing site-super assignment source.
• CMB-0479 added the lumber-futures candidate runner and found that live Camber has a 3030 framing budget-line config

but no mirrored Buildertrend open-PO amount/lock-date source.

Fleet Lesson

Dispatches for external-signal-to-BT work should name the three tiers separately:

• client tier: external data access and cache/rate-limit policy,
• join tier: the Camber/Heartwood/BT surface proving applicability,
• writer tier: the no-write draft or production write target.

If any tier is assumed rather than proven, the ticket should either be scoped to the provable tier or blocked on a source-contract ticket. This keeps Codex from silently turning a candidate runner into route discovery, auth work, or production writer design.