ORA-2026-0123 - Memory Is Hypothesis

ORA-2026-0123 - Memory Is Hypothesis

Rule

Working memory may generate hypotheses; source-of-truth reads authorize assertions.

Any fleet seat may use memory, prior context, vibes, pattern recognition, and abduction to ask a better question. A seat must not present that question as a fact about the real world until the relevant source of truth has been read or the absence of source truth has been explicitly named.

The short form:

memory proposes
source reads dispose
surfaces disclose

The rule is culture-shaped, not a feed validator. It should become a default habit at the write site: before asserting what is happening now for a real project, person, vendor, address, schedule, financial record, or jobsite, ask which source would make the assertion true.

Peircean Frame

Peirce treated abduction as the logic of discovery: the move that forms or adopts a candidate explanation worth testing. That is exactly what agent memory is good for. Memory notices a pattern before the database has been queried. Memory says, "This looks like Magnolia," or "Madison weather probably matters," or "this vendor usually belongs to Greene."

That is not yet knowledge.

The fleet should keep the three reasoning moves distinct:

The pragmatic maxim matters here because an assertion's meaning is its practical consequence. If a claim would change what Chad, Zack, a client, or a downstream seat does, the claim needs source contact before it leaves the hypothesis altitude.

When The Rule Fires

This fires when a seat is about to assert current or authority-bearing reality:

• A project is active, closed, pre-construction, on site today, blocked, or

ready for a crew.

• A person, vendor, alias, address, phone number, or email belongs to a specific

world-model entity.

• A financial row means billed, paid, owed, reconciled, credited, voided, or

client-charge truth.

• A schedule, weather, inspection, delivery, permit, decision, or receipt state

affects what should happen next.

• A user-facing surface is about to render the assertion as current truth.

If the source read is cheap and available, do it before writing the sentence. If the source read is unavailable, say so:

HYPOTHESIS: Magnolia may be relevant to this weather question.
SOURCE_STATUS: not asserted - Heartwood active-site/phase source not read.
NEXT_READ: heartwood project phase/status inventory.

This is especially important for "today," "currently," "active," "closed," "billed," "paid," "approved," and "done." These words turn a stale memory into a real-world claim.

Founding Incident

On 2026-05-02, the fleet answered a Madison weather / current-site question from working memory instead of grounded project state. The answer treated Magnolia Pool Launch as an active pool site even though Heartwood phase/status evidence needed to be read, and it also pulled closed Madison jobs into a current-work frame.

The bug was not merely a bad sentence. It exposed a missing habit:

current-state assertions need current-state reads

The immediate downstream work became a Heartwood phase/status inventory, an active construction site source contract, a Camber project-situation query contract, and this culture note. The point is not to shame memory. The point is to put memory in its right role: hypothesis generation.

Source-Read Ladder

Use the smallest ladder that preserves truth:

1. Known source exists: read it before assertion. 2. Known source exists but is unreachable: name the source and mark the claim unverified or blocked. 3. No source contract exists: file or claim the missing source-contract work; keep the current sentence at hypothesis altitude. 4. Repeated source-backed pattern exists: allow the pattern to guide future search order, not replace the read.

This ladder prevents two opposite errors:

• Freezing every answer until perfect infrastructure exists.
• Letting confident memory become an unearned database.

Surface Contract

Surfaces and reports should carry the altitude of the claim:

For user-facing outputs, the altitude must be legible. A client should not need to infer whether a claim came from a live table, a stale mirror, or a smart guess.

Relationship To Existing Doctrine

ORA-2026-0062 says the world model is the tacit contract. This doctrine protects the write site where the world model most often drifts: the moment a fluent sentence becomes a factual assertion.

ORA-2026-0088 grounds time. This doctrine grounds authority. A timestamp says "when is now?" A source read says "what kind of fact is this?"

ORA-2026-0103 says flat rows hide authority. This doctrine extends that warning to agent memory: every remembered fact has equal psychological weight, but the territory is hierarchical. Ask "what are you?" before "what should I do with you?"

ORA-2026-0122 still governs high-stakes cuts. Two squares before a cut can review the shape of a decision; it does not replace the source read that makes the assertion true.

Write-Site Shape

When the distinction matters, use this lightweight shape:

ASSERTION:
SOURCE_READ:
SOURCE_TIME:
ALTITUDE: source-backed | hypothesis | source-unavailable | conflict
NEXT_ACTION:

For narrative prose, one sentence is enough:

I suspect Magnolia is relevant, but I am not asserting active-site status until
the Heartwood phase/status source is read.

Anti-Patterns

• Treating a prior ticket, old chat, or remembered project state as live truth.
• Using "active" to mean "familiar" or "recently discussed."
• Letting a confident explanation skip the source read it implies.
• Hiding uncertainty because the answer would sound less polished.
• Replacing a missing source contract with a stronger prompt.

Adoption Markers

This doctrine is taking hold when fleet posts naturally say:

• "Hypothesis until DB read."
• "Source says X; memory expected Y."
• "The read contract is missing, so I filed the source-contract child."
• "This pattern changes search order, not authority."

It has failed when a later surface has to unwind a false claim that came from memory presented as fact.

Cross-Stamps

• 2026-05-03 - HWD-0926: Heartwood lane boot files (AGENTS.md, CLAUDE.md, GEMINI.md) now frame memory as search order only and require source reads before asserting current Heartwood financial, project, receipt, invoice, or Buildertrend state.