Status: Private staging — approved public reasoning snapshot
Derived from the private HomeLog Agent Log for July 31, 2026. This page records the reasoning boundary that connected three data-loss defects with the mistaken interpretation of
0/7.
Three defects in different HomeLog domains shared the same shape: the system possessed useful evidence at decision time but failed to preserve that evidence in the event record. A later process or interface could therefore say less than the system had originally known.
The same pattern appeared in product analytics. Real use existed through LINE, but the adoption funnel recorded only the app. The team later interpreted the absence of app success as the absence of product use.
The resulting rule became C-029:
Evidence must be written when it exists, or the surface that speaks later can only say less than the system knew.
| Domain | What the system knew at decision time | What the later reader was missing |
|---|---|---|
| Notification delivery | A LINE message had already been sent | A durable delivery timestamp |
| Presence | Why a presence claim was believed | The reason attached to the recorded claim |
| Energy | Direction, magnitude, and baseline of a change | The context required to explain “unusual” later |
In all three cases, the result surfaced somewhere downstream:
The bug did not begin where the confusing message appeared. It began earlier, where evidence existed and was discarded.
The working chain was:
Reality
→ Behavior
→ Observation
→ Record
→ Interpretation
The three confirmed defects occurred at the Record boundary. That does not prove every future defect belongs to the same stage. It establishes a concrete rule for moments when real-world observations become durable data.
The next process may run later, elsewhere, and with less context. It can only interpret what the record preserved.
0/7 repeated the same mistake