Guarding a Ghost

Sat, 13 Jun 2026 00:00:00 +0000

Written with Claude.

The sentinel that existed to remember what the system forgot

The clearest example of a ghost-guard (a check that protects against a condition that no longer exists, or never should have) I’ve found is one the field-assessment platform created for itself. On every re-cost pass, the cost agent (the automated step that recalculates repair costs) re-emits an engineer’s years override under its own author tag. That one round-trip erases the human-authored signal from the append-only event log (a tamper-evident journal of every change, keyed by author and timestamp). The system then stamps a sentinel flag called _years_auto (a presence marker the gateway reads to infer ownership), so it can later infer whether an engineer or the agent wrote the value, because the round-trip already destroyed that information.

Event-Source on Chris Hughes | Development Journal

Guarding a Ghost

The sentinel that existed to remember what the system forgot