In short
Use six layers: Charter, Policies, Standards, Procedures, Guidelines, Records. Policies say what and why and rarely change; standards hold the numbers and named settings and change with the platform; every standard names the Microsoft control or record that proves it. If you are starting from nothing, write five documents first: an autonomy policy, a data and privacy policy, a build standard, a promotion procedure with a release certificate, and an incident, suspension and retirement procedure. All five are published in this library.
Why a pyramid at all
Most small firms govern agents with one long document that mixes beliefs, rules, settings and how-to notes. It fails in a predictable way: the settings change every month, so the whole document goes stale, and nobody can tell which sentence is a rule and which is advice.
A pyramid separates things by how often they change and who must approve them. The charter changes almost never. Standards change whenever Microsoft ships a new control. Records change every day. Keeping them apart means a platform update touches one standard, not the policy a client has signed.
The rule that holds it together is simple. Authority flows down: a standard may only make a policy concrete, never invent a new obligation. Evidence flows up: every standard names the Microsoft control that enforces it or the record that proves it. Whatever names neither is a guideline.
The six layers
Six layers is the smallest set that still separates the things that change at different speeds. Fewer, and settings leak into policy. More, and a one-founder company spends its week maintaining paper.
| Layer | Purpose | Approves | Review | Enforced by (Microsoft) |
|---|---|---|---|---|
| 0. Charter | States why Temei uses agents and the non-negotiables: autonomy is earned, a named human owns every agent, nothing starts above L1. | Founder | Yearly | No control enforces a charter. It is enforced by being cited: every policy must trace back to a charter line. |
| 1. Policies | Short statements of what is allowed and why. They change rarely and are written so a client director can sign them. | Founder; client accountable owner for client tenants | Yearly, or after an incident or a law change | Tenant scope: tenant-wide data policy, the setting that allows or blocks publishing of generative AI agents, Purview sensitivity labels and DSPM for AI, Entra Conditional Access on agent identities. |
| 2. Standards | The measurable minimums that make a policy true: numbers, lists, named settings. They change with the platform, which changes monthly. | Founder as platform owner | Quarterly, and whenever Microsoft ships a governance change | Environment groups and rules, advanced connector policies, classic data policies (including Copilot Studio virtual connectors and endpoint filtering), Agent access channels, Authentication for agents, Managed Environments sharing limits, embedded maker credential sharing control, agent credit limits. |
| 3. Procedures | The ordered steps for every moment that changes risk: create, change policy, publish, promote, suspend, retire. Each ends in a record. | Founder; executed by the builder | After any run that went wrong, otherwise yearly | Power Platform admin activity logs in Purview (policy and group changes are logged), publish blocked on data policy or sharing violations, Manage agents in the admin centre to turn an agent off, Agent ID lifecycle in Entra. |
| 4. Guidelines | Advice that makes good agents more likely: how to write instructions, design tools, curate knowledge. Optional by design. | Builder | Continuous | None by design. Checked indirectly by agent evaluation test sets and the activity map during review. |
| 5. Records | The evidence that the layers above were followed: cards, contracts, decisions, test results, certificates, incidents. | Whoever acts writes; founder reviews | Per event; register reviewed monthly | Purview audit for Copilot Studio activities and agent interactions, Entra sign-in logs for Agent IDs, Copilot Studio analytics and transcripts, the Temei decision log (Logos). |
A policy says what and why. A standard says how much. A procedure says in what order. A record proves it happened.
Where ENGRAM sits in the pyramid
ENGRAM is not a seventh layer. It runs through four of them, and that is exactly why it works as a method rather than a poster.
- Policy. The Agent Autonomy Policy makes the Trust Pyramid binding: nothing starts above L1, nothing rises without evidence, any reviewer may demote, only evidence promotes.
- Standard. The thresholds live here because they will be tuned. ENGRAM sets floors (for L2, at least three scored Quality Ledger sessions with R×U of 0.75 or more and no scope violation). Temei adds its own, stricter floor: twenty correct recorded decisions before L2. Floors may be raised, never lowered, by a standard.
- Procedure. The Agent Creation Gate is ENGRAM Step 0 to 2 (Register, Declare, Scope). The Promotion Procedure is Steps 4 to 6 (Score, Log, Promote).
- Records. The Registration Card, Trust Level Declaration, Quality Ledger and Logos entries are the evidence base.
What Microsoft actually enforces
The platform enforces standards, not policies. Knowing which control backs which line is the difference between governance and good intentions. Points worth building around, as of November 2026:
- Two connector policy systems can apply at once. In mixed mode, a connector or action is usable only when the advanced connector policy allows it and no classic data policy blocks it. Agent access channels and Authentication for agents also both apply alongside the matching Copilot Studio virtual connectors; if either blocks, access is blocked. Your standard must list both sides.
- Group rules override environment settings. A rule published on an environment group takes precedence and the environment-level setting becomes read-only. Standards are therefore written per group, not per environment.
- Changes are not instant. Microsoft says sharing rules can take up to an hour to be enforced. We observed data policy changes taking up to about 90 minutes to reach Copilot Studio, so the change procedure applies policy changes the day before a build.
- Sharing limits only bite on authenticated agents. Managed Environments sharing limits (Editor and Viewer rights, individuals only, maximum viewers) apply only to agents that require authentication. The Agent Build Standard must therefore require Entra ID authentication before it can rely on sharing limits.
- Maker credentials are a sharing risk. A separate control can block sharing and publishing of agents whose connections reuse the maker's credentials. It governs sharing and publishing, not runtime, so it complements the Write-Path Standard rather than replacing it.
- Every agent now has an identity. New Copilot Studio agents get a Microsoft Entra Agent ID automatically, with the owner added as sponsor and connector permissions visible as API permissions that Conditional Access can target. On the Microsoft Copilot harness the Agent ID is provisioned at first publish rather than at creation. Retirement must delete the agent so its Agent ID goes with it.
- Audit is there, if you look. Copilot Studio activities and agent interactions land in the Purview unified audit log, and Power Platform admin activity (data policies, groups and rules) is logged by default. Agent evaluation test sets give repeatable test evidence that can run from the API or a connector.
The document set
Twenty-eight documents make up the full pyramid. The ones marked with a link are published in this library as working drafts you can read in full and adapt. The rest are on our list.
| Layer | Document | What it fixes | In this library |
|---|---|---|---|
| Charter | Temei AI Charter | Purpose, principles, ENGRAM as the method, the red lines | Read it |
| Policy | AI Use and Acceptable Use Policy | Who may build and use agents, for what, what is forbidden | Not yet published |
| Policy | Agent Data and Privacy Policy | Which data classes an agent may read or write, UK GDPR basis, client data separation, retention of transcripts | Read it |
| Policy | Agent Autonomy Policy | Trust Levels L1 to L5 as binding rules, promotion on evidence, automatic demotion, no generic write tools | Read it |
| Policy | Supplier and Model Policy | Which models, harnesses and third-party connectors are acceptable and who decides | Not yet published |
| Standard | Environment and Data Policy Baseline | Environment groups, ACP plus classic data policy in mixed mode, allowed connectors and blocked actions, change lead time | Not yet published |
| Standard | Agent Build Standard | Naming, owner and sponsor, authentication, channels, sharing limits, knowledge sources, logging switched on | Read it |
| Standard | Write-Path Standard | Agents never hold generic write tools; writes go through a constrained workflow that enforces allowed fields and deduplication | Read it |
| Standard | Evaluation and Promotion Thresholds | Test set size, pass marks, the 20 correct recorded decisions before L2, demotion triggers | Read it |
| Standard | Logging and Audit Standard | What must be logged where, retention, who reviews and how often | Not yet published |
| Procedure | Agent Creation Gate | Registration Card, Trust Level declaration, scope, non-goals, acceptance contract before any build | Not yet published |
| Procedure | Data Policy and ACP Change Procedure | Change one thing, record it, apply a day before the build because propagation lags | Not yet published |
| Procedure | Publish and Share Procedure | Channel choice, authentication check, sharing within limits, first publish provisions the Agent ID on the Microsoft Copilot harness | Not yet published |
| Procedure | Promotion Procedure (L1 to L2 and up) | Evidence pack, reviewer, release certificate, Logos entry | Read it |
| Procedure | Incident, Suspension and Demotion Procedure | Who turns the agent off, how, who is told, what reinstatement needs | Read it |
| Procedure | Retirement Procedure | Remove sharing, delete agent and its Agent ID, archive records, close register entry | Read it |
| Guideline | Agent Operating Model | The 44 roles, guardian agents, how agents and humans hand off | Not yet published |
| Guideline | Instruction and Prompt Writing Guide | Structure, refusal wording, grounding, examples | Not yet published |
| Guideline | Tool and Workflow Design Guide | Narrow tools, Copilot Studio workflows as triggers on the Microsoft Copilot harness, idempotent writes | Not yet published |
| Guideline | Knowledge Curation Guide | Source selection, freshness, labels, what never goes into knowledge | Not yet published |
| Record | Registration Card | Step 0 of ENGRAM, one per agent | Not yet published |
| Record | Acceptance Contract and Scope | Acceptance criteria, scope control, non-goals | Not yet published |
| Record | Decision Log (Logos) | Every decision with date, evidence, reviewer | Not yet published |
| Record | Agent Register | One row per agent: owner, level, environment, channels, status | Not yet published |
| Record | Test Evidence and Quality Ledger | Evaluation runs, scored sessions, decision counts | Not yet published |
| Record | Trust Level Declaration | Signed level per agent per version | Not yet published |
| Record | Release Certificate | One page that says this version, at this level, passed these tests, approved by this person | Read it |
| Record | Incident and Exception Register | Incidents, waivers from a standard and their expiry | Read it |
Where to start
If you have agents running and none of this written down, do not try to write twenty-eight documents. Five carry most of the weight, in this order:
- An autonomy policy. Turns trust levels, the no-generic-write rule and automatic demotion into something a director can sign. Every procedure assumes it. Ours.
- A data and privacy policy. Which data classes an agent may touch at each level, lawful basis under UK GDPR, transcript retention, separation between your data and your suppliers'. The first question a data protection lead will ask. Ours.
- A build standard. The exact settings every agent must have: naming, owner, authentication, channels, sharing, knowledge sources, how writes are guarded, the tests it must pass. Ours.
- A promotion procedure with a release certificate. The evidence an agent needs before it touches live data, and the one page someone signs. Ours.
- An incident, suspension and retirement procedure. Who switches an agent off, where, who is told, and how an agent is removed completely. Ours.
Then write the charter that sits above them all. Ours.
Ownership in a small team
Today one person holds every role. That is acceptable only if the roles are written down separately, so that each decision is made deliberately in one capacity, and so that each role can be handed to someone else later without rewriting the pyramid.
| Role | Today | With clients | Holds |
|---|---|---|---|
| Governance owner | Founder | Founder for Temei; client's named accountable owner for their tenant | Approves charter, policies, exceptions; accountable for every agent |
| Platform owner | Founder | Client IT admin, advised by Temei | Approves standards; makes data policy, ACP and group changes |
| Builder | Founder, with AI assistance | Temei | Writes procedures and guidelines; builds; writes the records |
| Reviewer | Founder after a cooling-off period of at least one day, plus guardian agent checks | A client reviewer who did not build the agent | Signs promotion evidence and release certificates; may demote |
| Agent owner and sponsor | Founder | Named business owner in the client | Answers for one agent; is the Entra sponsor; receives incidents |
Two rules make this honest. First, the person who built an agent never approves its own promotion beyond L2 once a second person exists; until then, a one-day delay and a written evidence pack stand in for independence. Second, in a client tenant the client owns policies and the agent; Temei owns its methods and its records of what it did.
How it maps to frameworks
The pyramid is built for practice, not certification. It lines up with the main frameworks so that a client already working towards one recognises the structure. It does not make anyone compliant on its own.
| Framework | Where it lands |
|---|---|
| NIST AI RMF 1.0 | GOVERN: charter, policies, roles. MAP: Registration Card, scope, non-goals. MEASURE: evaluation thresholds, Quality Ledger, test evidence. MANAGE: promotion, incident, suspension, retirement. |
| ISO/IEC 42001:2023 | 5.2 AI policy (policy layer); 5.3 roles (ownership note); 6.1 risk and AI system impact assessment (Registration Card and Trust Level declaration); 7.5 documented information (the whole pyramid); 8 operation (procedures); 9 performance evaluation (records and reviews); 10 improvement (incident and change procedures). |
| EU AI Act | Relevant only where agents serve people in the EU. Article 4 (AI literacy) points to the AI Use Policy; Article 50 transparency, telling people they are talking to an AI, belongs in the Agent Build Standard for customer-facing channels. |
| UK approach | Principles-based, applied by existing regulators. The five principles (safety, transparency, fairness, accountability, contestability) map to the charter; UK GDPR and ICO guidance drive the Data and Privacy Policy. |
Sources
- Manage your Copilot Studio projects, an overview, Microsoft Learn
- Implement a zoned governance strategy, Microsoft Learn
- Secure your Copilot Studio projects, Microsoft Learn
- Advanced connector policies, Microsoft Learn
- Configure data policies for agents, Microsoft Learn
- Control how agents are shared, Microsoft Learn
- Microsoft Entra Agent IDs for Copilot Studio agents, Microsoft Learn
- Agent identities and authentication for Copilot Studio, Microsoft Learn
- Power Platform activity logs and auditing in Microsoft Purview, Microsoft Learn
- Use Microsoft Purview to manage data security and compliance for Copilot Studio, Microsoft Learn
- About agent evaluation, Microsoft Learn
- Manage Copilot Credits and capacity for Copilot Studio, Microsoft Learn
- NIST AI Risk Management Framework
- ISO/IEC 42001:2023 AI management systems
- Regulation (EU) 2024/1689, the AI Act
- UK AI regulation: a pro-innovation approach