Enterprise pilot notes:

- The chart does not provision Postgres. Production profiles expect an
  operator-managed Postgres/RDS database exposed through
  `AGENT_BOM_POSTGRES_URL`; see
  `deploy/helm/agent-bom/examples/postgres-secret.example.yaml` for the
  Kubernetes Secret shape and `site-docs/deployment/postgres-provisioning.md`
  for the ownership contract.
- Set `AGENT_BOM_AUDIT_HMAC_KEY` in the control-plane secret.
- Set `AGENT_BOM_REQUIRE_AUDIT_HMAC=1` to fail closed if the key is missing.
- Use Postgres for the pilot control plane; SQLite is not the multi-replica path.
- Prefer internal ingress / VPN-only exposure for the API and UI.
- Run Alembic before first multi-replica rollout: `alembic -c deploy/supabase/postgres/alembic.ini upgrade head`.
- For existing databases bootstrapped from `init.sql`, stamp the baseline first: `alembic -c deploy/supabase/postgres/alembic.ini stamp 20260416_01`.
- Label the namespace with Pod Security Admission restricted mode before applying sidecars:
  `kubectl label namespace {{ .Release.Namespace }} pod-security.kubernetes.io/enforce=restricted pod-security.kubernetes.io/audit=restricted pod-security.kubernetes.io/warn=restricted --overwrite`
- The focused EKS pilot values lock ingress down; adjust `networkPolicy.ingress` if your ingress controller does not run in `ingress-nginx`.
- For production operator defaults, start from `deploy/helm/agent-bom/examples/eks-production-values.yaml`.
- `sidecarInjection.enabled=true` requires cert-manager because the chart packages
  the webhook TLS certificate and CA injection path.
