The disk specialist cannot resize the disk.

That is the envelope, not a promise in a slide. A specialist is a directed runbook: you decide who runs, with which role. Tools that are not declared are never constructed. Swarm routing is rejected in v0. The YAML is what you review.

In the Disk envelope

  • Enumerated pairs: DescribeInstances, DescribeVolumes, DescribeVolumeStatus, DescribeInstanceStatus, DescribeTags
  • CloudWatch GetMetricData, GetMetricStatistics, ListMetrics
  • PagerDuty incident read + note
  • New Relic NRQL + alert annotation
  • GitLab repo read + draft MR
  • Identities classified read-only or propose-only

Not a tool object

  • ModifyVolume, CreateSnapshot
  • GetSecretValue, decrypted SSM, instance userData
  • GetSessionToken, GetFederationToken, GetAuthorizationToken
  • lambda:GetFunction, DynamoDB Scan, S3 GetObject
  • merge, approve, resolve, reassign
  • phoneHome, Lightfoot-hosted gates, write-classified identities

The model emits a structured decision. It does not call PagerDuty or GitLab. The v0 gatekeeper matches (platform, action) against three rows: (pagerduty, annotate-incident), (newrelic, annotate-alert), (gitlab, draft-pr). Schema also allows comment plus GitHub / Jira / ServiceNow / Datadog; those connectors are in the license, not in that dispatch table yet.

Reject rules live in l1spec.