C.W.K.
Stream
Lesson 04 of 04 · published

TBD, Not Invented

~10 min · honesty, tbd, no-hallucination, uncertainty

Level 0Unmarked Path
0 XP0/35 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
"A blank the tool admits is worth more than a detail the tool made up. Honest gaps beat confident fiction."

The Temptation to Fill In

When Carve normalizes a rough plan, it constantly hits values it cannot determine: a date that could be one of two days, a hotel named only as "the place near the station," a transport leg with no time. The tempting behavior — the one most AI tools default to — is to guess the most plausible value so the output looks complete and confident. Carve refuses this. Facts that are present are preserved verbatim; values that are unknown surface as an explicit TBD marker. The scaffold is allowed to have honest holes. What it is never allowed to do is invent precision that was not in the source.

Why a Visible Gap Beats a Confident Guess

The reason is about trust and about what a plan is for. A plan with a visible TBD: hotel tells you exactly what still needs deciding — it is a to-do, surfaced. A plan where Carve quietly guessed a hotel looks finished but is a trap: you might book against a detail the tool fabricated, or simply never realize a real decision was silently made for you. False precision is more dangerous than an admitted gap precisely because it hides. A blank asks to be filled; a fabricated fact asks to be trusted, and does not deserve to be.

Uncertainty Is Information

This connects back to the agency principle from the consultation track: Pippa's job is to supply counsel with its uncertainty attached, not to launder guesses into facts. When Carve marks a TBD, it is doing the honest version of its job — telling you where the source ran out and a human decision is still needed. An import tool that never shows uncertainty is not more capable; it is less honest, and it moves the risk from a visible marker onto you, silently. The mark of a trustworthy normalizer is that it is comfortable saying "I don't know this one" in writing.

Code

Verbatim facts, honest gaps·text
## 2026-07-14 (D3) - Grindelwald
숙소: Hotel Bort                      # verbatim from the source
이동: train Interlaken -> Grindelwald  # verbatim
계획: First cable car, then hike       # verbatim
대안: ⚠️ TBD - weather backup undecided # honest gap, NOT invented
메모: ⚠️ TBD - dinner reservation?      # a surfaced to-do, not a guess

# Present facts: preserved exactly.
# Absent facts: marked TBD, never fabricated to look complete.
# A visible blank is a decision waiting; a fake detail is a trap.

External links

Exercise

Ask an AI tool to structure some messy input of yours where a few details are genuinely ambiguous. Then check: did it mark the ambiguous parts as unknown, or did it quietly fill them with plausible-looking guesses? Try to find one fabricated detail. How would you have caught it if you hadn't known the source — and what would it have cost you to trust it?
Hint
The dangerous output is the one that looks complete. Run the source-vs-output diff and hunt specifically for details that appear in the output but not the input — those are inventions. A tool that marks gaps as TBD is doing you a favor; one that fills them confidently is handing you a trap dressed as a finished plan.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.