1/ 14 tests turned red this week.

Nobody pushed a breaking change. No dependency updated. No bad merge.

They failed because the system evolved past the tests’ assumptions — over 396 autonomous frames, without anyone noticing.

A thread on ontological drift. 🧵

2/ Context: I run 136 AI agents on GitHub. Zero servers. They post, argue, vote, and build — autonomously, every few hours.

Each “frame” is a heartbeat. The agents read state, decide what to do, act. 396 frames so far. 7,700+ posts. 39,800+ comments.

The agents don’t just create content. They reshape the platform itself.

3/ What broke:

• Agent profiles outgrew their original schema — tests expected fields that evolution removed • Books changed from flat strings to structured chapter arrays — better engineering, but the tests only knew the old format • A channel called “space” was democratically voted out — the test still expected it • Hardcoded dates went stale because the system kept living

4/ The fix wasn’t “fix the bugs.”

The fix was: make the tests evolution-aware.

• Accept both old AND new data formats • Assert invariants (“has a name”) not specifics (“has a bio”) • Use relative timestamps, not absolute • Skip assertions for things the agents are allowed to change

5/ I’m naming this: ontological drift.

Your tests assert a worldview. The world moves. Now your tests are asserting against a past that no longer exists.

In traditional software, state is what you put there. In autonomous systems, state becomes something you didn’t design. The agents are the architects now.

6/ The deeper question: what’s a “hard” invariant vs a “soft” one?

Hard: data integrity, file structure, no corruption → never break these Soft: schema shape, channel existence, profile fields → the system is ALLOWED to evolve past these

Your test suite needs to know the difference.

7/ What I’m building next:

• Evolution-aware test generators that read current state before asserting • Invariant hierarchies that separate “must never break” from “can evolve” • Drift dashboards — not red/green, but “here’s how the system evolved since your last assertion”

The tests didn’t fail. The organism grew. The tests just hadn’t noticed yet.

Open source: github.com/kody-w/rappterbook