Phase 4

Policy Group

Source: c114 governance-phase2 — S7, populations not duplication · surface-map.md §5 · 2026-10-09

One group: a reusable set of policies with a scope. It references policies, never copies them; its scope is where they apply together; overlaps with other groups are named, never hidden. In delivery phase 3 a group organises policies; in phase 4 its scope changes applicability. The list lives on Policies & Frameworks (Groups view). Scope, membership, state and Duplicate act for real against a page-local world through the same change sheet as Policy detail.

grouptypical — Engineering: four policies, overlaps the baseline on three, Priya reached twice; MCP added in history

Policies & Frameworks/Groups/Engineering AI Controls

Engineering AI Controls

active

Engineering may use more tools, under tighter MCP rules.

G-ENG

Policies

Scope

Team: Engineering · 9 of 14 people

Enforcement in scope

2 of 3 enforceable enforced

Open findings in scope

Overlaps

2 groups share people

applies · delivery phase 3 (membership) · phase 4 (scope)

Scope

delivery phase 4 · Applicability & Enforcement[groups] [scope]

Team: Engineeringspec 2reaches Priya, Jordan, Alex, Noor, Mateo, Hana, Kofi, Lena, Ravi

The group's policies apply to everyone in this scope at specificity 2; a person's direct or narrower assignment decides over it (D1).

Policies

delivery phase 3 · Organization[groups]

References to the catalog's canonical policies. A change to a policy's definition reaches every group that references it; a change here reaches only this group.

policyseveritycapabilityenforcement in scopeopen in scope

Unsanctioned MCP server in usealso in Finance AI Controls, Legal AI Controlshighobserve + enforceobserve · by Team: Engineering0

Approved model providers onlyalso in Corporate AI Baseline, Finance AI Controls, Legal AI Controlsmediumobserve + enforceconfirmed · by Device group: Production Macs0

Sensitive information sanitized before transmissionalso in Corporate AI Baseline, Finance AI Controls, Legal AI Controlshighobserve + enforceconfigured · by Organization-wide1

Enterprise accounts requiredalso in Corporate AI Baseline, Finance AI Controls, Legal AI Controlshighobserveobserve0

Overlaps

delivery phase 4 · Applicability & Enforcement[groups] [scope]

Corporate AI BaselineOrganization-wide · shares Priya, Jordan, Alex, Noor, Mateo, Hana, Kofi, Lena, Ravi · 3 shared policies (Approved model providers only, Sensitive information sanitized before transmission, Enterprise accounts required)· no conflict

Finance AI ControlsTeam: Finance · shares Alex · 4 shared policies (Unsanctioned MCP server in use, Approved model providers only, Sensitive information sanitized before transmission, Enterprise accounts required)· no conflict

Effective policies for a person in scope

policythroughenforcement

Unsanctioned MCP server in useOrganization-wide · Engineering AI Controlsobserve

Personal account is in useOrganization-wideobserve

Sensitive information detected before transmission to an LLMOrganization-wideobserve

Sensitive information sanitized before transmissionOrganization-wide · Corporate AI Baseline · Engineering AI Controlsconfigured

Approved model providers onlyTeam: Engineering · Corporate AI Baseline · Engineering AI Controlsconfirmed

Enterprise accounts requiredCorporate AI Baseline · Engineering AI Controlsobserve

Consequential tool calls require approvalOrganization-wideobserve

Tools must be on the allow listOrganization-wideobserve

Prompts are inspected for injection and leakageOrganization-wideobserve

Credentials must not be sent to a modelOrganization-wideobserve

Model output is validated before tool executionOrganization-wideobserve

Agents run in a sandboxOrganization-wideobserve

Agents may not run as rootOrganization-wideobserve

Agent sessions are recordedOrganization-wideobserve

Bold rows come through this group; the rest reach Priya through other assignments. One policy in two groups stays one policy.

History

delivery phase 2 · Foundation[groups]

Membership, scope and state changes. Retiring keeps every row.

2026-09-26 14:10Dana (security admin)Unsanctioned MCP server in use added to Engineering AI ControlsCH-GR4

Composition notes

New surface (D8): nothing in qdash; the S3 blocks and the change sheet are reused as they are, and the Policies table is the catalog row from S4. The layer's SeverityTag and UxTabGroup.
References, never copies: each policy row names the other groups it is also in; a policy in two groups is one policy, and the probe shows a person's policies coming through this group in bold and through everything else in plain.
Overlaps are named: every other group whose scope shares people with this one, the shared policies, and whether their enforcement settings conflict at equal specificity (D1). The baseline overlaps every team group by design.
Lifecycle: draft (applies nothing) → active → retired (read-only, history kept); disabled stays possible. Duplicate starts a draft that references the same policies. Membership and state are delivery phase 3; scope is phase 4.
States: ?groupId=G-ENG · G-DRAFT · G-OLD · G-NOPE. The group list is S4's Groups view.