1. SnapState — the memory seam goes vendoredA Launch HN debuted SnapState today: persistent state for AI agent workflows, framed as durable context across sessions. It is the third substrate-layer launch in three days from the agent-as-environment camp — Runtime gave each teammate a sandbox, Superset rebuilt the IDE shell, Kanbots scoped each card as an agent's job, and now SnapState fills the memory layer. The pattern is no longer hypothetical. "Shell over model" is the actual shape of the launches. SnapState is the bet that durable agent memory becomes a vendored service rather than a roll-your-own bolt-on — the same posture LangSmith took for tracing two years ago. Why it matters: The Sunday call: is your agent's memory still a roll-your-own bolt-on? If yes, name one substrate vendor to pilot this week — SnapState if memory is the seam you've been patching every sprint. Read more → 2. Six months in production — the framework wasn't itA widely-shared writeup posted simultaneously to r/AI_Agents and r/artificial: after six months of running agents in production, the framework you pick is a near-irrelevance; the actual failure mode is elsewhere. It is the sharpest version yet of the production-reckoning thread that has been building all week — yesterday's "two weeks burned on full-auto" postmortem from a different altitude, the Anthropic and Replit and Cursor pattern from the days before that. The failure isn't acute. It's accumulated. And the framework-vs-framework arguments dominating r/AI_Agents subthreads all year now read as a category error. Why it matters: The Sunday call: which agent-framework debate has the team spent the most hours on this quarter — and what seam did those hours displace? Write the answer down tonight; the displacement is the actual cost. Read more → 3. Governance layer — every action policy-checkedAn r/SideProject post introduced a governance layer that intercepts every agent action and runs it through a policy check before execution. Yesterday's RADAR carried a one-time admin approval gateway for prompt-injection abuse in group chats — a single-purpose seam guard. Today's item generalizes the move: every action, not just sensitive ones, runs through the same gate. The shape worth naming is that this is a kernel system-call interface for agents — the agent doesn't get to do anything directly; it requests an action, and the policy layer either lets it through, denies it, or asks for approval. Why it matters: The Sunday call: does your agent's action surface have a gate, or does it call the world through whatever client library it was handed? If the latter, the governance layer is the cheapest seam to put under discipline this week. Read more → | 
