{ "schema_version": "newruntime-agent-readable-v0.1", "type": "pattern_collection", "count": 10, "items": [ { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "agent-ready-software-exposes-capabilities", "title": "Agent-ready software exposes capabilities", "description": "Software is becoming easier for agents to use when it exposes explicit operations, schemas, temporary identity, and isolated execution instead of only adding a chat widget.", "thesis": "The agent-ready product boundary is a small set of observable, permissioned capabilities that external agents can compose safely.", "status": "published", "confidence": "high", "first_seen": "2026-06-23", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2581", "tg-2711", "tg-2514", "tg-2660", "tg-2686", "tg-2530" ], "related_posts": [ "agent-api-design", "hilos-development-control-plane" ], "counter_evidence": [ "Human-oriented applications still need visual workflows, explanation, recovery, and controls that a narrow agent API does not provide.", "Exposing more capabilities can increase attack surface and operational complexity when identity, authorization, and audit are weak." ], "revision_trigger": "Revise the thesis if embedded assistant interfaces consistently outperform explicit capability APIs on interoperability, reliability, permission control, and integration cost.", "topics": [ "agent-ready", "api-design", "agent-infrastructure" ], "source_urls": [ "https://blog.cloudflare.com/code-mode-mcp", "https://x.com/EnoReyes/highlights", "https://blog.cloudflare.com/temporary-accounts", "https://trycase.dev/docs", "https://github.com/tencentcloud/CubeSandbox" ], "routes": { "html": "https://newruntime.com/patterns/agent-ready-software-exposes-capabilities/", "markdown": "https://newruntime.com/patterns/agent-ready-software-exposes-capabilities.md", "json": "https://newruntime.com/patterns/agent-ready-software-exposes-capabilities.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "ai-native-orgs-move-to-review-and-orchestration", "title": "AI-native organizations move toward review and orchestration", "description": "When implementation and document production accelerate, organizations spend more scarce human attention on goals, judgment, review queues, process design, and accountability.", "thesis": "AI-native operating models are reorganizing work around specifying, routing, verifying, and owning agent output rather than maximizing individual production speed.", "status": "published", "confidence": "medium", "first_seen": "2026-06-18", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2455", "tg-2509", "tg-2562", "tg-2620", "tg-2702", "tg-2709" ], "related_posts": [ "ai-native-engineering-team", "coinbase-ai-era-interviews" ], "counter_evidence": [ "Many teams still gain useful local productivity without changing reporting lines, hiring, incentives, or release ownership.", "Premature orchestration roles can add coordination overhead before agents are reliable enough to justify organizational redesign." ], "revision_trigger": "Revise the thesis if sustained AI adoption raises throughput without shifting review load, role definitions, decision rights, process metrics, or management practices.", "topics": [ "ai-native-organization", "engineering-management", "human-review" ], "source_urls": [ "https://claude.com/blog/running-an-ai-native-engineering-org", "https://anthropic.com/research/claude-code-expertise", "https://anthropic.com/research/economic-index-june-2026-report", "https://jeffgothelf.com/blog/how-to-write-okrs-for-an-ai-product" ], "routes": { "html": "https://newruntime.com/patterns/ai-native-orgs-move-to-review-and-orchestration/", "markdown": "https://newruntime.com/patterns/ai-native-orgs-move-to-review-and-orchestration.md", "json": "https://newruntime.com/patterns/ai-native-orgs-move-to-review-and-orchestration.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "company-memory-needs-write-loops", "title": "Company memory needs write and correction loops", "description": "Retrieval is only one stage of memory; durable organizational knowledge also needs scoped writes, corrections, provenance, versioning, and invalidation.", "thesis": "Company memory becomes useful when real work continuously updates a governed knowledge layer, not when an agent merely searches a larger document pile.", "status": "published", "confidence": "high", "first_seen": "2026-06-24", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2703", "tg-2695", "tg-2625", "tg-2525", "tg-2631" ], "related_posts": [ "shared-document-human-agent", "unabyss-shared-context-layer" ], "counter_evidence": [ "For stable reference material, ordinary retrieval over maintained documents can be sufficient and cheaper than a dedicated memory lifecycle.", "Automatic memory writes can amplify mistakes, stale assumptions, privacy violations, and unauthorized knowledge sharing." ], "revision_trigger": "Revise the thesis if retrieval-only systems match governed write-loop systems on repeated correction rate, freshness, provenance, access control, and rollback quality.", "topics": [ "company-memory", "agent-memory", "knowledge-systems" ], "source_urls": [ "https://promptql.io/", "https://aclanthology.org/2024.acl-long.747", "https://github.com/OpenDataBox/MemoryData", "https://careersatdoordash.com/blog/doordash-unified-consumer-memory-for-personalization-at-scale", "https://github.com/langchain-ai/openwiki" ], "routes": { "html": "https://newruntime.com/patterns/company-memory-needs-write-loops/", "markdown": "https://newruntime.com/patterns/company-memory-needs-write-loops.md", "json": "https://newruntime.com/patterns/company-memory-needs-write-loops.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "harness-architecture-outlives-model-choice", "title": "Harness architecture outlives model choice", "description": "Rules, tools, permissions, memory, evaluation, execution, and recovery are becoming a stable runtime layer while models remain replaceable components.", "thesis": "For production agents, the harness is becoming a more durable product boundary than the identity of the model running inside it.", "status": "published", "confidence": "high", "first_seen": "2026-06-28", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2708", "tg-2692", "tg-2678", "tg-2582", "tg-2567", "tg-2607" ], "related_posts": [ "agent-api-design", "claude-code-subagents-memory", "hilos-development-control-plane" ], "counter_evidence": [ "Provider-native harnesses can exploit proprietary model behavior and product features that portable runtimes cannot reproduce.", "Model changes still alter tool use, planning, latency, and safety enough that switching is not operationally free." ], "revision_trigger": "Revise the thesis if model-provider coupling consistently produces better reliability and lower total migration cost than portable rules, tools, traces, and execution contracts.", "topics": [ "harness-engineering", "agent-runtime", "model-routing" ], "source_urls": [ "https://opencode.ai/docs/models", "https://github.com/NousResearch/hermes-agent", "https://github.com/langchain-ai/deepagents", "https://github.com/rivet-dev/agentos", "https://docs.inference.net/introduction" ], "routes": { "html": "https://newruntime.com/patterns/harness-architecture-outlives-model-choice/", "markdown": "https://newruntime.com/patterns/harness-architecture-outlives-model-choice.md", "json": "https://newruntime.com/patterns/harness-architecture-outlives-model-choice.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "model-answers-become-task-interfaces", "title": "Model answers become task interfaces", "description": "Generative systems increasingly return maps, forms, dashboards, controls, and structured pages instead of forcing every result into a text response.", "thesis": "Natural language is remaining a general input while the output is shifting toward bounded interfaces assembled for the task at hand.", "status": "published", "confidence": "medium", "first_seen": "2026-06-20", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2705", "tg-2694", "tg-2478", "tg-2466" ], "related_posts": [ "gemini-enterprise-agent-platform-demos", "shared-document-human-agent" ], "counter_evidence": [ "Chat and documents remain better for ambiguous exploration, explanation, and tasks whose control surface cannot be known in advance.", "Generated interfaces can hide uncertainty or provenance if visual polish replaces explicit evidence and state." ], "revision_trigger": "Revise the thesis if generated task interfaces fail to improve completion, comprehension, correction, or approval quality over chat and conventional fixed product surfaces.", "topics": [ "generative-ui", "post-app", "agent-interfaces" ], "source_urls": [ "https://monogram.ai/blog/introducing-monogram", "https://arxiv.org/abs/2606.31031", "https://claude.com/blog/artifacts-in-claude-code", "https://github.com/vercel-labs/json-render" ], "routes": { "html": "https://newruntime.com/patterns/model-answers-become-task-interfaces/", "markdown": "https://newruntime.com/patterns/model-answers-become-task-interfaces.md", "json": "https://newruntime.com/patterns/model-answers-become-task-interfaces.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "skills-become-portable-capability-layer", "title": "Skills become a portable capability layer", "description": "Instructions, scripts, tools, and resources are being packaged as discoverable capabilities that can move across sessions, agents, and model providers.", "thesis": "Agent skills are emerging as a portable capability layer, but their value depends on progressive disclosure, provenance, security review, and behavioral evaluation.", "status": "published", "confidence": "medium", "first_seen": "2026-06-28", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2707", "tg-2666", "tg-2673", "tg-2559" ], "related_posts": [ "claude-code-subagents-memory", "agent-api-design" ], "counter_evidence": [ "Provider-specific tools, hooks, context models, and permission systems still limit true portability between agent runtimes.", "A poorly designed or malicious skill can reduce task performance, consume context, or execute unsafe commands." ], "revision_trigger": "Revise the thesis if cross-harness reuse remains rare or if evaluated skill packages fail to outperform simpler local instructions and typed tools.", "topics": [ "agent-skills", "evals", "context-engineering" ], "source_urls": [ "https://github.com/benchflow-ai/skillsbench", "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices", "https://github.com/shadcn/improve", "https://pydantic.dev/articles/pydantic-ai-capabilities" ], "routes": { "html": "https://newruntime.com/patterns/skills-become-portable-capability-layer/", "markdown": "https://newruntime.com/patterns/skills-become-portable-capability-layer.md", "json": "https://newruntime.com/patterns/skills-become-portable-capability-layer.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "verification-bandwidth-is-the-scarce-resource", "title": "Verification bandwidth is the scarce engineering resource", "description": "As coding agents accelerate implementation, specifications, review judgment, evaluation coverage, and release accountability become the binding constraints.", "thesis": "The primary bottleneck in agentic software delivery is moving from code production to the human and machine capacity required to verify it.", "status": "published", "confidence": "high", "first_seen": "2026-06-23", "last_verified": "2026-07-16", "supporting_signals": [ "tg-2709", "tg-2672", "tg-2668", "tg-2588", "tg-2503" ], "related_posts": [ "ai-coding-workflow-verifiable-work", "senior-engineers-read-large-codebases" ], "counter_evidence": [ "For small, low-risk, well-tested changes, generation and automated checks can still remove most of the human review burden.", "Better models may reduce defect rates enough that review effort falls even while generated code volume grows." ], "revision_trigger": "Revise the thesis if organizations sustain higher agent-generated change volume without increasing review queues, rollback rates, escaped defects, or evaluation investment.", "topics": [ "coding-agents", "evals", "engineering-management" ], "source_urls": [ "https://addyo.substack.com/p/own-the-outer-loop", "https://databricks.com/blog/benchmarking-coding-agents-databricks-multi-million-line-codebase", "https://hamel.dev/blog/posts/eval-smell", "https://addyosmani.com/blog/new-sdlc-vibe-coding", "https://anthropic.com/research/AI-assistance-coding-skills" ], "routes": { "html": "https://newruntime.com/patterns/verification-bandwidth-is-the-scarce-resource/", "markdown": "https://newruntime.com/patterns/verification-bandwidth-is-the-scarce-resource.md", "json": "https://newruntime.com/patterns/verification-bandwidth-is-the-scarce-resource.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "agent-economics-moves-to-completed-work", "title": "Agent economics moves to completed work", "description": "Token prices and subscription fees are weak proxies when turns, retries, delegation, verification, latency, and successful outcomes drive the real cost.", "thesis": "The economically meaningful unit for agent systems is becoming cost per verified completed task rather than cost per token or model call.", "status": "published", "confidence": "high", "first_seen": "2026-06-27", "last_verified": "2026-07-15", "supporting_signals": [ "tg-2696", "tg-2668", "tg-2676", "tg-2646", "tg-2545" ], "related_posts": [ "coding-agent-cost-environment-config", "ridge-ai-spend-process-cost", "model-match-effort-selection" ], "counter_evidence": [ "Token accounting remains necessary for capacity planning and can approximate cost in simple, stable, single-call workflows.", "Task-level attribution can be expensive or ambiguous when one agent run contributes to several downstream outcomes." ], "revision_trigger": "Revise the thesis if token-level optimization reliably predicts lower total task cost without measuring failures, retries, human review, or completion quality.", "topics": [ "agent-economics", "model-routing", "product-metrics" ], "source_urls": [ "https://cognition.com/blog/making-fable-cheaper-than-opus", "https://databricks.com/blog/benchmarking-coding-agents-databricks-multi-million-line-codebase", "https://claude.com/blog/claude-model-and-effort-level-in-claude-code", "https://platform.claude.com/docs/en/agents-and-tools/tool-use/advisor-tool", "https://engineering.ramp.com/post/ai-spend-value" ], "routes": { "html": "https://newruntime.com/patterns/agent-economics-moves-to-completed-work/", "markdown": "https://newruntime.com/patterns/agent-economics-moves-to-completed-work.md", "json": "https://newruntime.com/patterns/agent-economics-moves-to-completed-work.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "goal-scoped-loops-replace-manual-continuation", "title": "Goal-scoped loops replace manual continuation", "description": "Long-running agent work is moving from repeated continue prompts toward explicit goals, stopping conditions, schedules, task state, and evaluator-driven retries.", "thesis": "An autonomous loop becomes operationally useful when completion is an external contract rather than a model's subjective decision to stop.", "status": "published", "confidence": "high", "first_seen": "2026-05-14", "last_verified": "2026-07-07", "supporting_signals": [ "tg-2338", "tg-2434", "tg-2480", "tg-2554", "tg-2622", "tg-2628" ], "related_posts": [ "claude-code-long-running-loops", "linear-loops-agent-workflows", "sierra-horizon-long-running-agent" ], "counter_evidence": [ "Open-ended research and product judgment often lack a machine-checkable completion condition and still require interactive steering.", "A measurable target can be gamed or optimized at the expense of unmeasured quality, safety, and maintainability." ], "revision_trigger": "Revise the thesis if unsupervised continuation prompts match goal contracts on completion quality, budget control, recovery, auditability, and operator effort.", "topics": [ "agent-loops", "goals", "automation" ], "source_urls": [ "https://code.claude.com/docs/en/goal", "https://github.com/steipete/agent-scripts", "https://cursor.com/changelog/06-18-26", "https://github.blog/changelog/2026-06-17-github-copilot-app-generally-available" ], "routes": { "html": "https://newruntime.com/patterns/goal-scoped-loops-replace-manual-continuation/", "markdown": "https://newruntime.com/patterns/goal-scoped-loops-replace-manual-continuation.md", "json": "https://newruntime.com/patterns/goal-scoped-loops-replace-manual-continuation.json" }, "source_format": "markdown" }, { "schema_version": "newruntime-agent-readable-v0.1", "type": "trend_pattern", "slug": "design-systems-become-agent-context", "title": "Design systems become executable agent context", "description": "Design systems are expanding from component libraries into agent-readable rules, references, registries, review loops, and constraints that preserve product character.", "thesis": "The useful design system for an AI development workflow is an executable context package, not only a visual component catalog.", "status": "published", "confidence": "medium", "first_seen": "2026-05-06", "last_verified": "2026-06-26", "supporting_signals": [ "tg-2293", "tg-2301", "tg-2365", "tg-2392", "tg-2463", "tg-2538" ], "related_posts": [ "shared-document-human-agent" ], "counter_evidence": [ "A detailed design package cannot replace visual judgment, product context, user research, or careful review of rendered interfaces.", "Too many rigid rules can make generated work consistent but generic, preventing deliberate exceptions and new visual language." ], "revision_trigger": "Revise the thesis if agents using only component APIs match agents using references, design rules, browser verification, and feedback loops on quality and brand fidelity.", "topics": [ "design-systems", "agent-context", "frontend" ], "source_urls": [ "https://youtube.com/watch?v=hQFEAZK__q0", "https://styles.refero.design/", "https://shadcn.run/", "https://stitch.withgoogle.com/", "https://github.com/senlindesign/taste-skill" ], "routes": { "html": "https://newruntime.com/patterns/design-systems-become-agent-context/", "markdown": "https://newruntime.com/patterns/design-systems-become-agent-context.md", "json": "https://newruntime.com/patterns/design-systems-become-agent-context.json" }, "source_format": "markdown" } ] }