# Phase 0 — Metadata Allowlist (v1)

Agent Nova may only plan and implement the following Salesforce metadata types unless a human explicitly expands scope.

| Metadata type | In v1 allowlist | Notes |
|---------------|-----------------|-------|
| Custom fields | Yes | On existing objects preferred |
| Validation rules | Yes | |
| Record-triggered Flows | Yes | Screen/autolaunched Flows out of scope unless approved |
| Apex classes | Yes | Default with sharing / security controls |
| Apex triggers | Yes | Bulk-safe patterns required |
| Lightning Web Components (LWC) | Yes | |
| Permission sets | Yes | |
| Profiles | No | Escalate |
| Sharing rules / OWD redesign | No | Escalate |
| Connected apps / Auth providers | No | Escalate |
| Destructive deletes | No | Reject unless explicitly approved |
| Production deployment | No | Out of autonomous scope |

## Orchestrator enforcement

- Solution Architect must escalate any change outside this allowlist.
- Salesforce Developer skill must reject writes outside the approved `metadata-plan.json`.
- Deterministic DevOps validates package contents against the allowlist before commit/PR.