Skip to content
Michael Rishi Forrester

Agentic Covenants

Agentic Charter Matrix

Who is allowed to put this agent into the world, under what authority, accountable to what policy, with what retirement criteria?

Filter

All 15Agent charterDomain charterOrganizational charterIdentityAuthorizationBlast radiusApproval gatingSupply chain

Layers, by what they can actually enforce

  • Agent charter — advisory

    What the agent's own charter declares. Scope it claims for itself.

  • Domain charter — deterministic-when-invoked

    The domain or team that operates the agent, and the policy they set.

  • Organizational charter — deterministic-and-external

    Authority above the operator. Organizational policy the operator cannot waive.

Showing 3 of 15.

  • Supply chain at Organizational charter

    Org-wide allowlist of approved foundation models. Org-wide policy on MCP server approval, third-party dependency approval, vendor risk assessment integrated with procurement.

  • Supply chain at Domain charter

    Inherits org-wide approved-model list, adds domain-specific restrictions (e.g., "no models that train on user data", "SOC 2 Type II vendors only"). Approves or denies MCP servers for the domain.

  • Supply chain at Agent charter

    Specific dependencies declared. Named foundation model and version, named MCP servers (with hashes from Covenants L2-C5), named base images, named tool versions. Dependency changes require charter amendment.