Authoring Policy Rule Definitions

Gating: @WsdlGuard("EnforceOMatic.orgCanUsePolicyRuleMDAPI") = OrgPermissions.EnforceOMatic && OrgPermissions.PolicyRuleMDAPI Min API version: 64.0 (66.0 for conditions using PolicyJsonExpression)

For human maintainers (not the agent): the Java source-of-truth lives at enforce-o-matic-impl/java/src/enforce/o/matic/metadata/ and reference fixtures at enforce-o-matic-impl/test/func/filemetadata/<name>/. The agent should rely on the templates and reference docs in this skill bundle — those impl paths are not readable from the Vibes/MCP runtime.

This skill covers the on-disk metadata XML format for authoring policies. Use it whenever a task asks to write a *.policyRuleDefinition or *.policyRuleDefinitionSet file, add a fixture under test/func/filemetadata/, or ship a metadata package. The runtime side (RuleProvider, hooks) is out of scope.

Eval coverage: This skill is exercised by the team's ADK eval framework, not by tests/evals/ under the skill directory. Five datasets covering the ACCESS / GOVERNANCE / RECORD / TRANSFORM variants live in packages/adk-eval/eval/domains/platform-policy-rule-generate/datasets/.

1. Package Layout

A deployable package always contains: