Skip to content

agent-ecosystem.md

Latest commit

 

History

History
67 lines (50 loc) · 5.36 KB

agent-ecosystem.md

File metadata and controls

67 lines (50 loc) · 5.36 KB
title Agent standards ecosystem
description Mutual links across Agent Knowledge, Agent UI, Agent Runtime, Agent Evidence, Agent Policy, Agent Artifact, Agent Tool, and Agent Context.

Agent Standards Ecosystem

The Agent standards ecosystem splits agent products into portable contracts. Each standard owns one layer of meaning and links to the others through stable refs instead of swallowing their responsibilities.

This page is the public friend-link map for the current standards. Use it to discover the adjacent protocols and to decide which standard should own a new concept.

Where Agent Knowledge fits

Agent Knowledge owns source-grounded knowledge packs: source material, compiled runtime views, citations, status, review records, and safe loading rules.

Knowledge tells agents what durable facts and source-grounded context they may use.

Current standards

Standard Role Site LLM context Repository
Agent Knowledge Source-grounded knowledge packs for agents. site llms-full repo
Agent UI Interaction surfaces for agent products. site llms-full repo
Agent Runtime Execution facts, controls, tasks, tools, and recovery. site llms-full repo
Agent Evidence Evidence, provenance, verification, review, replay, and export. site llms-full repo
Agent Policy Risk, permission, approval, retention, waiver, access, and policy decision facts. site llms-full repo
Agent Artifact Durable deliverables, versions, parts, previews, exports, source links, and handoff packages. site llms-full repo
Agent Tool Tool declarations, surfaces, invocations, progress, results, permissions, and audit refs. site llms-full repo
Agent Context Context surfaces, items, source refs, selection, budgets, assembly, injection, compaction, and missing-context facts. site llms-full repo

Boundary rule

Agent Knowledge -> what durable source-grounded context an agent can use
Agent Runtime   -> how agent work is accepted, executed, controlled, and resumed
Agent UI        -> how agent work is projected into user-visible surfaces
Agent Evidence  -> why an agent outcome can be trusted, reviewed, replayed, and exported
Agent Policy    -> whether an agent action may proceed and under which constraints
Agent Artifact  -> what durable deliverable the agent produced and how it changes
Agent Tool      -> what capability was exposed, invoked, progressed, and returned
Agent Context   -> what context was available, selected, assembled, compacted, missing, and injected

No standard should become the whole stack. A compatible implementation should preserve native ids and link across standards with refs.

Future standard candidates

Candidate Why it may become a standard
Agent Evaluation Acceptance scenarios, rubrics, eval runs, quality gates, and evidence-backed benchmark records.
Agent Workflow Portable multi-step work plans, scene launches, background jobs, and handoff states.
Agent Model Routing Task profiles, model candidates, routing decisions, fallback, quota, and cost records.

These candidates should remain design notes until they can be specified without relying on one product implementation.

External alignment

Reference Used for
Agent Skills Skill package format, authoring style, and AI-friendly docs reference.
Model Context Protocol Tool, resource, prompt, and JSON-RPC capability reference.
Agent2Agent Protocol Peer agent tasks, messages, artifacts, and native id reference.
OpenTelemetry GenAI Trace, span, GenAI operation, and telemetry correlation reference.
CloudEvents Portable event envelope reference.
W3C PROV Entity, activity, agent, derivation, and attribution reference.

External protocols are references, not ownership transfers. The Agent standards should preserve their native ids and semantics while defining agent-specific relationships.