A repository is three cities stacked. The lit streets you walk are a rendered overlay. The machine-city beneath stores everything by the hash of its own content — honest about what it holds, silent on whether it's true. And below that, the clockwork re-tunes the whole thing on a trigger, at 3am, while the operator's hand is off the wheel.
Push a commit yourself, or let the clock reach 3am and watch the machinery rebuild the city with no one at the keyboard.
Underneath: blobs, trees, commits, tags — each named by the hash of its own content, chained parent→child into the DAG. You cannot silently rewrite a stored field (the hash breaks — tamper-evident). But nothing verified the author or date when they were written (authenticity: none).
The autonomic layer. It acts on events, not commands — and the cron event acts on nothing but the clock. Configure it once; it runs itself forever, with no human in the loop. This is where the repo stops being a record and becomes an actor.
The streets are a brochure — curated, and willing to print a name nobody checked. The machine-city beneath freezes that name into a hash: you can never quietly change it, and nothing ever confirmed it was true. And the clockwork publishes it all to the world on a schedule, untouched, at an hour when no one is awake to witness the trigger.
Every automatic deploy is one junction — <• — an event, a workflow, and the unanswered question of who's accountable when the 3am cron ships something broken with the operator asleep. The Strangers are just cron with better coats.
three strata · presentation / integrity / autonomy · trust properties hashed-and-verified in node before drawn