agent-stack

Shape: static. Reference material, not a run. What varies is which reference a task loads, which the SKILL.md table decides in advance.

/agent-stack — how an agent system is built, judged and metered

• when: the thing being built is an agent
• decline it: «без агентного слоя».

If agent-stack is installed, building an agent SYSTEM goes through it — the orchestrator's loop and the shape of its work as a graph, what the agent is told (system prompts, tool descriptions, workflow versus agent), the evals that say whether it got better, the protocols it speaks outward (MCP, A2A, the registry, the gateway), and the wallet under reselling LLM access. It owns the failures that surface only under load: a parallel layer consumed with no checker before it, a memory layer that never decays, a trajectory judged by its final answer alone, tokens metered after the provider already charged for them.

The boundary — "an agent system is being BUILT, not used." NOT through it: a single LLM call in a script, the wording of one prompt, the interface a person sees (super-ux, sheleg-design), taking the money — sheleg-dev charges the card and this meters what was burned behind it — and coordinating the agents editing THIS repository, which is agent-sync. Routing every sentence with the word "agent" in it here is how you teach an agent to route around it.

Refusal phrase: «без агентного слоя».

Among the routers: agent-sync says who is holding this file right now; agent-stack is about the agent being built. The first coordinates the work, the second is what the work produces.