Engineering Notes
SAMP Engineering Notes #12
What does SAMP conformance actually mean? Explore role-specific tiers, mandatory requirements, reproducible test matrices, failure injection, and evidence-based interoperability claims.
The official SAMP technical article archive, featuring protocol engineering, AI agent management, security architecture, AgMS implementation experience, interoperability research, and practical lessons from experimental development.
Engineering Notes
What does SAMP conformance actually mean? Explore role-specific tiers, mandatory requirements, reproducible test matrices, failure injection, and evidence-based interoperability claims.
Engineering Notes
Receiving an event is not the same as recording it. Explore SAMP PUSH notifications, subscription ownership, duplicate delivery, recovery limits, and the boundary between events and durable audit records.
Engineering Notes
How SAMP treats agent profiles as versioned management contracts, with authenticated announcements, schema validation, revision-bound queries, and safe recovery without confusing capabilities with authority.
Engineering Notes
MCP, A2A and SAMP address different responsibilities in AI systems. Explore the distinction between tool integration, agent collaboration, and AI agent management.
Engineering Notes
Understanding an instruction is not the same as being authorized to execute it. Explore how SAMP separates authentication, trust, exact-action authorization, human authority, and policy enforcement.
Engineering Notes
What happens when an AI agent crashes, becomes unreachable, or leaves an operation's outcome uncertain? Explore SAMP failure management, recovery, trust, enforcement, and lessons from AgMS Alpha.
Engineering Notes
From protocol design to real-world experimentation. Discover how AgMS Alpha applies SAMP management concepts to heterogeneous AI agents, monitoring, operational events, and failure testing.
Engineering Notes
An authorized AI-agent operation is not necessarily executed, and execution is not necessarily verified. Explore how SAMP combines exact-action authorization, runtime evidence, recorded outcomes, and safe recovery.
Engineering Notes
An AI agent can be reachable but untrusted, trusted but offline, or quarantined without being isolated. Explore how SAMP separates trust, liveness, enforcement, and failure domains.
Engineering Notes
Inside the SAMP Management Plane: how Managers and Agents cooperate through eight protocol operations to provide discovery, monitoring, trust management, controlled execution, and operational accountability.
Engineering Notes
From managing routers and switches to managing AI agents. Discover how decades of network management experience inspired SAMP's approach to monitoring, trust, authorization, operational control, and failure handling.
Engineering Notes
From the first Internet-Draft to SAMP v0.2: five revisions exploring AI agent management, trust, authorization, runtime evidence, and operational resilience.