AMP and the Python SDK

AMP 0.1 is middleware inside an orchestrator. It stays in memory and does not need an MCP server process. It sits around tool execution and model output, and it blocks cheat attempts and a lazy "done".

• On Node it covers a LangChain callback, LangGraph nodes, OpenAI Agents, Mastra, Claude Agent SDK hooks, CrewAI, AutoGen, Dify, and n8n shapes. The mount point is a tool execute or the host's real hook, not a fake universal callbacks array.
• The remote heartbeat is POST /v4/tick. Do not post blindly at a sessionless /mcp.
• The Python SDK lives in distributions/python. One file, the standard library, no third-party packages. If it cannot compile a thin prompt locally, it labels source: "local-stub". It does not pretend the text came from a SKILL.
• base_url allows loopback by default. A remote host needs PUAX_AMP_ALLOW_REMOTE=1.

MCP is the plug. Gates, the envelope, and state live in AMP. An agent loop with no MCP can still mount the same discipline.