agent-contracts 0.14.0 → 0.15.0

package/README.md

@@ -180,6 +180,7 @@ An **Agent** defines who an execution entity is:
 * permissions
 * constraints
 * behavioral rules
+* structured content sections (reference material, procedures, criteria)
 
 ### Task
 
@@ -317,6 +318,7 @@ Design regressions become testable.
 ## Features
 
 * **Declarative YAML DSL** for multi-agent development workflows
+* **Agent `sections`** for embedding structured reference material, procedures, and criteria directly in agent definitions
 * **Static schema validation**
 * **Reference integrity checks**
 * **Semantic linting**
@@ -574,9 +576,11 @@ agents:
     constraints:
       - "Never write code directly"
 
-    x-identity: |
-      You act as the Architect. You NEVER implement or test directly.
-      Instead you delegate to specialist sub-agents.
+    sections:
+      - title: "Delegation Protocol"
+        content: |
+          You act as the Architect. You NEVER implement or test directly.
+          Instead you delegate to specialist sub-agents.
 ````
 
 ---
@@ -912,6 +916,8 @@ npx agent-contracts
 The `[path]` argument defaults to `agent-contracts.yaml` in the current directory.
 If `-c` / `--config` is specified, the DSL path from the config file is used.
 
+All commands also accept `--team <id>` to limit execution to a single team when using a [multi-team configuration](#multi-team-configuration).
+
 #### `resolve` options
 
 | Option | Description |
@@ -919,6 +925,7 @@ If `-c` / `--config` is specified, the DSL path from the config file is used.
 | `--format <text\|json>` | Output format (default: `text`) |
 | `--expand-defaults` | Expand all Zod default values in output. Fields like `required_validations: []`, `tags: []`, and `can_read_artifacts: []` are written explicitly instead of being silently applied by schema defaults. |
 | `-c, --config <path>` | Path to `agent-contracts.config.yaml` |
+| `--team <id>` | Limit to one team (multi-team config only) |
 
 #### `score` options
 
@@ -927,6 +934,7 @@ If `-c` / `--config` is specified, the DSL path from the config file is used.
 | `--format <text\|json>` | Output format (default: `text`) |
 | `--threshold <number>` | Minimum score; exit 1 if below (for CI gates) |
 | `-c, --config <path>` | Path to `agent-contracts.config.yaml` |
+| `--team <id>` | Limit to one team (multi-team config only) |
 
 The score command evaluates 7 dimensions:
 
@@ -990,6 +998,60 @@ This lets you generate static outputs for:
 
 all from the same resolved DSL.
 
+### Multi-team configuration
+
+When several teams (for example backend, QA, infra) are managed from one workspace, you can list every team in a single config file instead of maintaining separate configs.
+
+````yaml
+teams:
+  _defaults:
+    bindings:
+      - ./bindings/cursor.yaml
+    vars:
+      language: TypeScript
+    paths:
+      cursor_root: .cursor
+    active_guardrail_policy: default-enforcement
+
+  backend:
+    dsl: ./teams/backend/agent-contracts.yaml
+    interface_output: ./teams/backend/team-interface.yaml
+    bindings:
+      - ./teams/backend/bindings/observability.yaml
+    vars:
+      team_name: backend
+
+  qa:
+    dsl: ./teams/qa/agent-contracts.yaml
+    vars:
+      team_name: qa
+````
+
+**`_defaults`:** Reserved meta-entry in the `teams` map. It uses the same schema as team entries except `dsl` is not required. Values are inherited by all teams. The underscore prefix avoids colliding with real team IDs.
+
+**Merge with `_defaults`:**
+
+* `bindings` — `_defaults` bindings are prepended before team-specific bindings
+* `vars` — shallow merge; team values win
+* `paths` — shallow merge; team values win
+* `active_guardrail_policy` — team wins when present
+
+All commands accept `--team <id>` to run against a single team:
+
+````bash
+agent-contracts validate -c config.yaml              # all teams
+agent-contracts validate -c config.yaml --team backend  # one team
+agent-contracts check -c config.yaml --team qa          # one team
+````
+
+The `check` command also validates that imported interface files exist on disk (cross-team references).
+
+**Design constraints:**
+
+* `dsl` and `teams` are mutually exclusive at the config root
+* Every team except `_defaults` must specify `dsl`
+* Existing single-team configs (top-level `dsl` only) remain valid unchanged
+
 ### Render target options
 
 Each entry in `renders` supports these fields: