Problem
Agent behavior was distributed across scripts, services, prompts, state and machine-specific assumptions, so no single boundary defined the actor.
Engineering Case Study
From agent scripts to bounded runtime.
Engineering case study: how persistent identity, authority, operational graphs, receipts and replaceable cognition converged into the AVSFT runtime model.
AVSFT runtime convergence
Agent behavior started scattered across scripts, services, prompts and machine-specific assumptions, which made it impossible to say what the actor actually was. Reconstructing the runtime lineage separated the mechanics that recur from the authority that must not, and the result is a runtime where identity, authority, state, tools and cognition are explicit.
Method
Lineage was reconstructed across runtime generations and recurring mechanics were separated from role-specific authority.
Result
The architecture now treats identity, authority, state, tools and model cognition as explicit runtime responsibilities.
Boundary
This is an engineering-system case study, not a customer deployment claim.
Current Evidence
Heartbeat, restart, receipts, replay and graph state recurred across separately evolved services.
Shared runtime mechanics never absorbed role-specific authority.
Behavioral continuity across model swaps remains a claim the paired tests must pass.