framework
Agent orchestration framework cited as the concrete example where short-term memory is maintained as part of a thread's state and a checkpointer saves graph-state snapshots organized into threads.
A paper scores five agent interoperability protocols against six governance dimensions and finds they coordinate tasks without expressing who may approve, how dissent survives, or when a human is called.
Reality
AgentCore runtime instances stretch agent sessions from eight hours to fourteen days. The architecture problem becomes a configuration choice, and a utilisation bet.
Reality
A developer wired runtime schema introspection, vector field matching and a local LLM repair loop into Odoo 17, then published the failure list. The failures define the boundary.
Reality
Microsoft's agentic retrieval is now callable from any MCP client, so non-Microsoft agent stacks can stop rebuilding chunking, embedding and permissions. The edges are where the work moved.
Reality
A field guide on dev.to describes a logistics agent that cleared 94% of test cases and 11% of 4,000 real tickets a day. The model was fine. Nobody designed the system around it.
Reality
Graph engineering acquired guides and comparison tables within weeks of a tweet that was mocking the field's renaming habit. The tweet's author later called the hype silly.
Reality
Mads Thines has shipped an open-source memory layer for coding agents that starts on local disk. The design bet is that a record of past mistakes should be inspectable and portable.
Reality
A dev.to explainer splits state, memory and checkpointing into three separate definitions. The split matters most at the point the excerpt stops: what happens when you resume.
Reality