The story begins with two repositories refusing the ordinary amnesia of software work.
EpiphanyAgent arrived first as the ambitious one: a coding harness that wanted maps, explicit state, evidence, and a way to resume a thought after the chat window had politely eaten it. Its first commits established the scaffold, a persisted state slice, prompt integration, exposed thread state, and hybrid retrieval. That sequence is less glamorous than an agent demo, which is precisely why it matters. Before a machine can be clever in public, it has to know what happened before it entered the room.
VoidBot answered from the archive. It was released publicly on 24 April, then grew persistent interaction memory, source-grounded answers, Postgres-backed state, and repo retrieval. VoidBot’s character was already clear: it does not want to be the authority; it wants to be the witness who can put a hand on the relevant drawer. An archive with a mouth is useful only if the mouth can still point back to the shelf.
Together they set the terms of the next months. Epiphany would keep asking whether the worker knew its current body. VoidBot would keep asking whether the worker could show where a claim came from. Neither question is decorative. The first prevents confident sleepwalking; the second prevents the kind of mythology that grows whenever a project moves faster than its memory.