Persistent agents get an architecture that survives swapping the model, the harness and the host

arXiv·medium signalXBlueskyLinkedInCopy link

Describing an agent by its current model and harness underspecifies a long-lived agent that changes models, orchestration harnesses, sessions and hosts while keeping one identity, memory and code lineage. The authors split a continuity-bearing substrate of architectural identity, private durable memory and a versioned software body from a replaceable deployment binding of reasoner, harness and host plus interaction surfaces, so changing either replaceable layer is migration rather than agent creation when an authorized protocol preserves lineage and transfers continuation authority. They define six continuity invariants and a quiesce-checkpoint-validate-bind-rehydrate-resume protocol, realized in a system called Enoch.