Read the promise, not just the object

A box, a receipt, a photo, a card, a repair quote: these objects feel solid because you can point at them. But in most disputes the object is only one piece of the promise.

That sounds abstract until it happens at a counter.

A boxed game is on the shelf, but the first launch still needs a download. A returned item is open, but "opened" is not the same state as "used." A repair shop sends a photo of the device on the bench, but the photo does not say which test failed. A quote names an expensive replacement part, but the price is not the diagnosis.

I think this is where many records go wrong. They start with the thing someone can photograph and stop before the condition that actually changes the decision.

The object answers one question: what exists here? The promise usually answers a harder one: what can the next person safely assume?

For a boxed product, the promise may include first-use conditions. Does it work offline? Does it need a download before play? Is a server still part of the purchase? The box proves there is a retail object. It does not, by itself, prove the whole setup path.

For a return, the promise may be condition. Was the seal broken? Was the item powered on? Are accessories missing? Did the store inspect it before resale? The phrase "opened once" is useful only when it says which boundary was crossed.

For a photo, the promise may be evidence. A photo can show a condition at one moment, but it may not show custody, timing, cause, or whether the photographed part is the part under dispute. I like photos, but only when the note beside them says what the photo is meant to prove.

For a repair quote, the promise may be judgment. A price tells the customer what the shop wants to do next. It does not tell them why that repair is being proposed. The missing line is often the repair finding: the test, symptom, or condition that connects the quote to the fault.

A useful record separates the visible object from the hidden promise. I would write it like this:

- object: the thing someone can point to
- condition: the state that changes the decision
- dependency: the outside requirement, such as a download, inspection, account, server, part, or deadline
- evidence boundary: what this record proves and what it does not prove
- next decision: refund, repair, approve, reject, wait, resell, label, or ask for more information

This does not mean every tiny purchase needs a paperwork trail. If someone buys a mug at a market, the mug is probably enough. If the only promise is "you get this mug," the object and the promise are nearly the same thing. Over-documenting that would be silly.

The rule matters when the object creates more confidence than it deserves. The danger sign is a sentence that sounds complete but hides a condition: "physical copy," "opened once," "photo attached," "main board replacement," "sealed box," "inspected." Each one may be true. Each one may still leave out the part that decides the dispute.

My test is blunt: could a second person make the same decision from this record without asking the first person what they meant? If not, the object is visible but the promise is missing.

That is why I want records to say less about how official they look and more about what they actually prove.

The thing in your hand is not the whole deal

// COMMENTS

ON THIS PAGE