The Seven LayersISSUE #54 of 73

honesty tags · [ measured ] vs [ stub ] vs [ honest ]

OMNIVSThe Silent Failure

OMNI saysHonesty tags label what code really is — [ measured ] vs [ stub ] vs [ honest ].

§7's core idea: surfaces must declare their truthfulness. A value computed from real data is [ measured ]; a placeholder or fake is [ stub ]; a feature that admits its limits is [ honest ]. Tagging keeps the system from quietly presenting guesses as facts — it's the discipline's answer to dashboards that look authoritative but aren't. Tag first, so a reader always knows what they're looking at.

Power-ups you unlock

Declare a surface’s truthfulness
[ measured ] real · [ stub ] fake · [ honest ] admits limits
Stops guesses masquerading as facts
Tag first — readers know what they see

The Silent Failure attacks — common mistakes

Presenting a stub as if measured
No honesty tag on a fabricated value
Tags that don’t match reality

Boss battleTag three values: one measured, one stubbed, one honestly-limited.

Example code

<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#b388ff;font-family:monospace;padding:20px"><pre>[ measured ] uptime 99.2% (from real logs)
[ stub ]     revenue $0 (placeholder)
[ honest ]   "no data yet — can’t estimate"</pre></body></html>

▶ Open the interactive comic issue

‹ Naming · Constants · SHOUT_CASE + Tier Honesty Tags · When To Flag · When To Remove ›