Trend memory · the second loop
Trends
Where the stack is going, tested against the news
Each shift is a before-and-after change we track over months; each thesis is a claim the week's Field Notes either support or weaken. When the evidence turns, they are revised, not quietly dropped.
Last revised Sep 30, 2026
01Shifts, from tremor to ambient
All shiftsCode production → verification ownership
BeforeEngineers are accountable mainly for code they personally produce and review
AfterEngineers own specifications, evidence, acceptance, and release of agent-produced changes
high
acceleratingAnswer → generated interface
BeforeText answer or static result page
AfterTask-specific interface assembled around intent
medium+1 now possible2 fading
acceleratingCoding tool → general-purpose workbench
BeforeCoding agents are developer tools that mainly edit code inside an IDE or terminal
AfterPeople across roles use context-aware agents to assemble, inspect, and revise working artifacts
medium
acceleratingModel API → compute-backed product contract
BeforeAPI price and limits look like stable product settings
AfterAccess depends on constrained inference capacity and compute supply
medium
emergingBorrowed human credentials → delegated agent identity
BeforeAgents borrow human sessions, shared API keys, or generic service accounts
AfterEach agent has scoped identity, delegation mode, sponsor, expiry, revocation, and audit
high
emergingClient-local memory → shared context infrastructure
BeforeEach AI client keeps its own incomplete project memory
AfterShared context layer with provenance, governance, and portability
medium+2 now possible1 fading
emergingFixed teams → executable mandates
BeforeGoals live in documents and queues while durable teams route and retain the work
AfterBounded executable mandates assemble temporary execution topologies and persist accepted state
medium
emergingManual continue prompting → goal-scoped agent loops
BeforeHuman repeatedly nudges one long chat forward
AfterAgent loop runs against an explicit goal, budget, checks, and stop condition
medium+1 now possible1 fading
emergingRented intelligence → owned learning loop
BeforePrompts, corrections, memory, and successful behavior accumulate inside one model provider
AfterA user-owned evaluation and trace layer improves and compares replaceable models
medium
02What changes for builders
Now possible
- Runtime memory becomes inspectable behaviorAn operator can review memory actions, cost, confidence, and their role in a run.Client-local memory → shared context infrastructure
- Agent-first API makes retries deterministicAgent can correct the next tool call from explicit machine-readable facts.Answer → generated interface
- Attacker-first agents turn vuln triage into repair candidatesThe workflow can move from exploit-oriented analysis to proposed code change faster.Manual continue prompting → goal-scoped agent loops
- Shared context lets AI clients stop starting from zeroDifferent agents can reuse the same governed project context.Client-local memory → shared context infrastructure
Fading
- Conversational document-schema creation is already a general capability delta
Promote a same-vendor launch and duplicate signal pair into a durable, general capability delta.Keep the launch as a source-inspected signal; publish a delta only when independent implementations demonstrate the same bounded capability with inspectable reliability limits.Answer → generated interface - Hand-crafted OCR pipelines are already being replaced
Treat product launches for conversational extraction as evidence that manual OCR and schema pipelines have broadly been displaced.Track bounded document-extraction capabilities as signals or deltas until independent deployments demonstrate durable workflow replacement and measurable error and review behavior.Answer → generated interface - Manual context handoff between AI clients
Copy architecture notes, task state, constraints, and decisions between Claude, Codex, Cursor, chat, and docs.Governed shared context layer that multiple AI clients can read with explicit provenance and access rules.Client-local memory → shared context infrastructure - Reading every changelog bullet to understand capability
Read raw changelog bullets and infer what changed for real workflows.Interpreted release note that separates announced, inspected, installed, smoke-tested, workflow-tested, and reproduced behavior.Manual continue prompting → goal-scoped agent loops
03Working theses, by weight of evidence
All patternsBar = supporting records. Open a thesis to see the claim and what would make us revise it.
Agent security moves to runtime boundaries7
The durable security boundary for an agent is the runtime that constrains what it can read, remember, execute, and authorize, not the prompt that asks it to behave.
Would change ifRevise the thesis if prompt-only controls consistently match isolated runtimes on containment, credential safety, recovery, auditability, and resistance to poisoned skills or memory.
Open the patternAgent-ready software exposes capabilities6
The agent-ready product boundary is a small set of observable, permissioned capabilities that external agents can compose safely.
Would change ifRevise the thesis if embedded assistant interfaces consistently outperform explicit capability APIs on interoperability, reliability, permission control, and integration cost.
Open the patternGoal-scoped loops replace manual continuation6
An autonomous loop becomes operationally useful when completion is an external contract rather than a model's subjective decision to stop.
Would change ifRevise the thesis if unsupervised continuation prompts match goal contracts on completion quality, budget control, recovery, auditability, and operator effort.
Open the patternHarness architecture outlives model choice6
For production agents, the harness is becoming a more durable product boundary than the identity of the model running inside it.
Would change ifRevise the thesis if model-provider coupling consistently produces better reliability and lower total migration cost than portable rules, tools, traces, and execution contracts.
Open the patternAgent economics moves to completed work5
The economically meaningful unit for agent systems is becoming cost per verified completed task rather than cost per token or model call.
Would change ifRevise the thesis if token-level optimization reliably predicts lower total task cost without measuring failures, retries, human review, or completion quality.
Open the patternCompany memory needs write and correction loops5
Company memory becomes useful when real work continuously updates a governed knowledge layer, not when an agent merely searches a larger document pile.
Would change ifRevise the thesis if retrieval-only systems match governed write-loop systems on repeated correction rate, freshness, provenance, access control, and rollback quality.
Open the patternVerification bandwidth is the scarce engineering resource5
The primary bottleneck in agentic software delivery is moving from code production to the human and machine capacity required to verify it.
Would change ifRevise the thesis if organizations sustain higher agent-generated change volume without increasing review queues, rollback rates, escaped defects, or evaluation investment.
Open the patternScientific agents need artifact evidence4
The useful unit of scientific-agent progress is an evidence package that another researcher can inspect, test, rerun, and revise.
Would change ifRevise the thesis if answer-level agents produce reliable scientific gains without reusable procedures, artifacts, citations, or independent validation across domains.
Open the pattern
Generative media becomes application infrastructure8
Generative media becomes durable when applications can compose it as controllable infrastructure rather than asking a standalone model for a one-off artifact.
Would change ifRevise the thesis if media models remain mostly one-off creation tools and fail to sustain reproducible, programmable, rights-aware workflows inside production applications.
Open the patternAgent protocols become the interoperability layer7
The durable integration surface for agentic software is becoming a small family of protocols that separate models and harnesses from tools, services, interfaces, and other agents.
Would change ifRevise the thesis if MCP, A2A, ACP, and similar contracts remain isolated ecosystems or add more operational cost than direct APIs across real multi-tool and cross-agent workflows.
Open the patternAI-native organizations move toward review and orchestration6
AI-native operating models are reorganizing work around specifying, routing, verifying, and owning agent output rather than maximizing individual production speed.
Would change ifRevise the thesis if sustained AI adoption raises throughput without shifting review load, role definitions, decision rights, process metrics, or management practices.
Open the patternDesign systems become executable agent context6
The useful design system for an AI development workflow is an executable context package, not only a visual component catalog.
Would change ifRevise the thesis if agents using only component APIs match agents using references, design rules, browser verification, and feedback loops on quality and brand fidelity.
Open the patternModel answers become task interfaces4
Natural language is remaining a general input while the output is shifting toward bounded interfaces assembled for the task at hand.
Would change ifRevise the thesis if generated task interfaces fail to improve completion, comprehension, correction, or approval quality over chat and conventional fixed product surfaces.
Open the patternSkills become a portable capability layer4
Agent skills are emerging as a portable capability layer, but their value depends on progressive disclosure, provenance, security review, and behavioral evaluation.
Would change ifRevise the thesis if cross-harness reuse remains rare or if evaluated skill packages fail to outperform simpler local instructions and typed tools.
Open the patternMachine readers need operator identity3
A machine-readable web needs an operator identity layer because useful bots cannot be governed reliably through user-agent strings and blunt allow-or-deny rules alone.
Would change ifRevise the thesis if cryptographic request verification and policy negotiation remain rare while simple network controls reliably distinguish legitimate machine readers from abuse.
Open the pattern