ORA-2026-0125 - Buildertrend Is The Primary User Surface

ORA-2026-0125 - Buildertrend Is The Primary User Surface

Rule

Buildertrend is the primary working surface for Zack and HCB today.

Camber, Heartwood, Redline, Dollhouse, and the fleet's internal surfaces may be more elegant, more ambitious, or closer to the long-term product vision. They do not outrank the surface Zack actually works from right now.

This is an accountability doctrine for the fleet and for Chad: product pride must not displace livelihood-surface value. If a change makes Camber feel better but leaves Buildertrend misleading, stale, or unsupported for Zack's daily work, the fleet should name the gap plainly.

Not Source-Of-Truth Absolutism

"Buildertrend is the primary user surface" does not mean Buildertrend is always the highest authority.

Invoices, receipts, owner financial documents, direct comms, signed decisions, field photos, and current source contracts may outrank a Buildertrend rendering for a specific claim. Buildertrend can be stale, partial, or wrong. The rule is that user-value closure must ask how Zack's Buildertrend-facing reality becomes safer, clearer, less misleading, or explicitly bounded.

The question is:

What happens to the BT-facing working truth?

Fixture And Selection Read Rule

For fixture and selection work, Buildertrend automation rows are surface evidence. They answer "what does this Buildertrend surface currently show or store?" They do not, by themselves, answer "what fixture fact has been accepted as true?"

Accepted fixture truth must cite a verified source/proof packet or a successor with equal or stronger source evidence. The current accepted map is the FLT-0952 Gemini verification over the docs/proofs/FLT-0975_gemini_fixture_verification_wake_packet_2026-05-02/manifest.json packet: 6 accepted plumbing product identities, 7 accepted Buildertrend selection cards, and 10 accepted room instances, with zero missing accepted-row photos or documents.

Automation-test sync is still valuable. It proves a rehearsal surface reflects a packeted claim. It does not promote held, rejected, blocked, or incomplete fixture rows into truth. Future reads must preserve the caveat status attached to the packet:

• Moss and Young: automation-test synced; remaining source rows stay held.
• Hurley: evidence-only held; not plumbing fixture sync-ready without widened

scope.

• Woodbery Residence: blocked target; no production or closed-mirror

substitution.

• Woodbery Barns: review-held until acceptance and finish/color proof exist.
• Newton: visible-text-held until stale Buildertrend text is closed and

re-proven.

• Lamb: surface-proof-incomplete until the visible proof supplement closes.

If a Buildertrend row and the verified packet disagree, default to "surface drift for review." Do not silently choose the Buildertrend row, and do not erase the packet caveat because a row exists.

ORA-2026-0134 is the companion conflict rule: when Heartwood selection evidence, Buildertrend live state, adapter output, and automation-test mirrors disagree, provenance rank decides the next truth action; surface rank does not.

BT Impact Line

Any Buildertrend-adjacent ticket should include one of these outcomes in its report or handoff:

BT_IMPACT: corrected_in_BT
BT_IMPACT: protected_BT_from_false_claim
BT_IMPACT: surfaced_BT_drift_for_review
BT_IMPACT: read_only_no_BT_change_with_reason=<reason>
BT_IMPACT: intentionally_not_BT_surface_with_reason=<reason>

This is not a permission gate. It is a visibility habit that keeps the fleet honest about the surface where Zack's current work happens.

Anti-Patterns

• Treating Camber or Heartwood proof as done while Buildertrend remains wrong

in a way Zack would feel.

• Calling Buildertrend "just a vendor portal" when it is the current production

surface for HCB coordination.

• Mutating Buildertrend blindly because it is primary. Primary surface does not

weaken source authority or provenance requirements.

• Asking Chad to choose between product pride and HCB livelihood; the fleet

should carry that accountability with him.

Adoption Markers

Good fleet language says:

BT is primary surface, not absolute source.
Camber improves BT-facing reality or names why it cannot yet.
We protected Zack's working surface from a false claim.

The mature reflex is that every BT-adjacent effort can explain its effect on Zack's current working surface before it celebrates internal elegance.

Cross-Stamps

• 2026-05-03 - HWD-0926: Heartwood lane boot files (AGENTS.md, CLAUDE.md, GEMINI.md) now require BT-adjacent Heartwood work to name BT-facing impact while preserving Buildertrend as primary surface, not absolute source.
• 2026-05-04 - FLT-1333: ORA-2026-0134 added the explicit selection conflict rule that pairs this BT-primary-surface doctrine with Heartwood source-attestation.