Framework

STACK

STACK is a five-layer architecture for repositories where humans and agents share work: Structure, Toolchain, Agent configuration, Connection, Knowledge and quality. The agent OS is versioned like the app.

When to use it

Use STACK when agents demo well and then rot the repo: rules in five tools, MCP without contracts, skills nobody owns. The disease is agentic repo debt, not a weak model.

The moves

  1. 1

    Structure

    Layout, entry points, workspaces, and boundaries an agent can navigate on its first minute in the repo.

  2. 2

    Toolchain

    The shells, commands, and CLI contracts an agent is allowed to run, written down instead of remembered.

  3. 3

    Agent configuration

    AGENTS.md, CLAUDE.md, rules, skills, and subagent charters as versioned standing context.

  4. 4

    Connection

    MCP servers, tool contracts, hooks, and guardrails with least privilege and a real failure story.

  5. 5

    Knowledge and quality

    Memory tiers, context budgets, evals, and CI, so a model upgrade does not silently lower the bar.

The book

Available now

The Agentic Codebase

The Five-Layer Architecture That Makes Agent Work Survive Production

Related frameworks

STACK is the five-layer model in The Agentic Codebase. It is not a generic "AI stack" diagram and not a vendor product line.

Citation

STACK (The Agentic Codebase). Len P. van der Hof, Systems for the Strategic Self. https://lenvanderhof.com/frameworks/stack/