agency-rules 0.0.0-stage → 0.3.2

package/CHANGELOG.md

@@ -0,0 +1,77 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.3.2](https://github.com/deuriib/agency-rules/compare/v0.3.1...v0.3.2) (2026-10-31)
+
+
+### Bug Fixes
+
+* **ci:** completely remove NODE_AUTH_TOKEN to enforce OIDC ([59b966d](https://github.com/deuriib/agency-rules/commit/59b966dbdf29502b127f5b271de42f9ca56687f9))
+* **ci:** completely remove NODE_AUTH_TOKEN to enforce OIDC ([a8229a7](https://github.com/deuriib/agency-rules/commit/a8229a7fc912f26b34dec9a2735a659ce63d12a9))
+
+## [0.3.1](https://github.com/deuriib/agency-rules/compare/v0.3.0...v0.3.1) (2026-10-31)
+
+
+### Bug Fixes
+
+* **ci:** resolve npm E404 by enforcing OIDC trusted publishing ([4266f4a](https://github.com/deuriib/agency-rules/commit/4266f4afd6a933c1835973e52ce09b4e620221a4))
+
+## [0.3.0](https://github.com/deuriib/agency-rules/compare/v0.2.0...v0.3.0) (2026-10-31)
+
+
+### Features
+
+* **skills:** add writing-rules skill for rule authoring ([41b99d7](https://github.com/deuriib/agency-rules/commit/41b99d7416fa52463303fc150e237fbc26ba90e1))
+
+
+### Bug Fixes
+
+* **ci:** correct labels config file extension ([51617c6](https://github.com/deuriib/agency-rules/commit/51617c68abcf95b13040b1cfeadcbf52013ff9d4))
+* **ci:** use node 24 for npm trusted publishing ([cf49055](https://github.com/deuriib/agency-rules/commit/cf4905539693f5a1d38ed902abc5a5c7c32d1635))
+
+## [0.2.0](https://github.com/deuriib/agency-rules/compare/v0.1.0...v0.2.0) (2026-10-31)
+
+
+### Features
+
+* bootstrap agency-rules with mise and four harness renderers ([c1bf3c9](https://github.com/deuriib/agency-rules/commit/c1bf3c9f078d84f578f2e37633dcc87fc98f3831))
+* **install:** add interactive mode and harness/scope parameters ([e1996be](https://github.com/deuriib/agency-rules/commit/e1996bec3da5a34db23c06181dcb0071b35f5eff))
+* **rules:** enforce conventional commits standard ([53f78b9](https://github.com/deuriib/agency-rules/commit/53f78b97a8669db60b7ac2110f10d9ad5658df39))
+
+
+### Bug Fixes
+
+* **ci:** add missing mise sidecar for biome ([ded656e](https://github.com/deuriib/agency-rules/commit/ded656e16acc862ef975069459bc8dd324adc051))
+* **install:** resolve biome linting errors and formatting ([04f4fee](https://github.com/deuriib/agency-rules/commit/04f4feeabcd2667d66b95865d0b7dd687cdd4798))
+
+## [Unreleased]
+
+### Added
+
+- Initial scaffold.
+- Conversion engine driven by `tools.json`.
+- Renderers for **Google Antigravity**, **pi-agent**, **oh-my-pi (omp)**,
+  and **OpenCode** (via `opencode-rules`).
+- `mise.toml` with toolchain (`node@22`), tasks (`validate`, `convert`,
+  `install`, `test`, `ci`), and post-install hook.
+- Test suites for frontmatter parsing and every renderer.
+- Documentation: architecture, rule spec, harness extension guide.
+
+### Changed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+---
+
+## [0.1.0] — TBD
+
+First tagged release. Reserved for the v0.1.0 cut once the harness set is
+stable.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Deuri Vasquez
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,145 @@
-# Temporary Holding Version
+# agency-rules
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+**Write rules once. Run them everywhere.**
+
+`agency-rules` compiles a single set of generic Markdown rules into the
+native formats expected by **Google Antigravity**, **pi-agent**,
+**oh-my-pi (omp)**, and **OpenCode** (via the `opencode-rules` plugin).
+
+The whole pipeline — toolchain, environment, and tasks — is managed by
+[mise](https://mise.jdx.dev), so every collaborator and CI runner uses the
+exact same Node version and the exact same commands.
+
+---
+
+## Why
+
+Every coding agent has its own rule format:
+
+| Harness | Format | Location |
+| --- | --- | --- |
+| Google Antigravity | YAML frontmatter with `trigger` | `.agents/rules/*.md` |
+| pi-agent | Per-rule directory with `RULES.md` | `.pi/rules/<slug>/RULES.md` |
+| oh-my-pi (omp) | Markdown with frontmatter | `.omp/rules/*.{md,mdc}` |
+| OpenCode | Markdown via `opencode-rules` plugin | `.opencode/rules/*.md` |
+
+Writing the same rule four times is a maintenance nightmare. `agency-rules`
+lets you write it **once** in a neutral format and compile it to all four
+with a single command, driven by a declarative contract (`tools.json`).
+
+---
+
+## Quick Start
+
+```bash
+# 1. Install toolchain + dependencies (one time)
+git clone https://github.com/<your-org>/agency-rules.git
+cd agency-rules
+mise install
+
+# 2. Compile rules to every harness
+mise run convert
+
+# 3. Install into harnesses detected on your machine
+mise run install --scope project
+```
+
+That's it. Your rules are now live in `.agents/`, `.pi/`, `.omp/`, and
+`.opencode/` (and the `opencode-rules` plugin is registered in
+`opencode.json` automatically).
+
+---
+
+## Repository layout
+
+```
+agency-rules/
+├── rules/              ← source of truth (Markdown + YAML frontmatter)
+├── integrations/       ← compiled output (generated, gitignored)
+├── scripts/            ← convert, install, validate + renderers
+├── tests/              ← node:test suites for renderers and parsing
+├── docs/               ← architecture, spec, extension guide
+├── tools.json          ← the conversion contract
+└── mise.toml           ← toolchain + tasks
+```
+
+---
+
+1. **Validate**: `mise run validate`.
+2. **Convert**: `mise run convert` and inspect `integrations/`.
+3. **Test**: `mise run test`.
+
+## Commands
+
+All commands go through mise:
+
+| Command | What it does |
+| --- | --- |
+| `mise run setup` | Install Node dependencies (`npm ci`) |
+| `mise run validate` | Validate every rule's frontmatter against `rules/_schema.json` |
+| `mise run check` | Format + lint + organize imports with Biome (write mode) |
+| `mise run convert` | Compile `rules/` → `integrations/<harness>/` |
+| `mise run convert:dry-run` | Preview which files `convert` would write (no writes) |
+| `mise run install` | Copy compiled output into harness directories |
+| `mise run install:dry-run` | Preview which files `install` would copy (no writes) |
+| `mise run test` | Run the Node test suite |
+| `mise run ci` | Full pipeline (`validate` → `check` → `convert` → `test`) |
+
+See `mise tasks` for the up-to-date list.
+
+### Dry-run workflow
+
+The typical inner loop uses dry-runs first to inspect what will change
+before anything hits disk:
+
+```bash
+mise run convert:dry-run            # see generated file paths + sizes
+mise run convert                    # actually write to integrations/
+mise run install:dry-run -- --all   # see copy destinations
+mise run install -- --all           # actually copy into harness dirs
+```
+
+---
+
+## Adding a rule
+
+1. Create `rules/<category>/<slug>.md` following
+   [`docs/RULE-SPEC.md`](docs/RULE-SPEC.md).
+2. Run `mise run validate` — it must pass.
+3. Run `mise run convert` — inspect `integrations/` to sanity-check output.
+4. Open a PR.
+
+---
+
+## Adding a harness
+
+See [`docs/ADDING-A-HARNESS.md`](docs/ADDING-A-HARNESS.md). It's roughly:
+
+1. Add an entry in `tools.json`.
+2. Add a renderer in `scripts/lib/renderers/`.
+3. Register the renderer in `scripts/lib/renderers/index.mjs`.
+4. Add tests in `tests/convert.test.mjs`.
+
+The conversion engine itself never changes.
+
+---
+
+## Documentation
+
+- [Architecture](docs/ARCHITECTURE.md) — data flow, contracts, caching.
+- [Rule spec](docs/RULE-SPEC.md) — the neutral frontmatter format.
+- [Adding a harness](docs/ADDING-A-HARNESS.md) — extension guide.
+
+---
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). Pull requests welcome.
+
+## Security
+
+See [SECURITY.md](SECURITY.md) for responsible disclosure.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

package/docs/ADDING-A-HARNESS.md

@@ -0,0 +1,170 @@
+# Adding a Harness
+
+This guide walks through adding support for a new coding agent. The example
+uses a hypothetical harness called **`example-agent`**.
+
+---
+
+## Prerequisites
+
+Read [`ARCHITECTURE.md`](ARCHITECTURE.md) first. You need to understand:
+
+- Why `tools.json` is a contract (not a list).
+- What renderers do (pure functions, no I/O).
+- What the installer does (copies per manifest).
+
+---
+
+## Step 1 — Add an entry to `tools.json`
+
+Add a new key under `harnesses`. Every field matters:
+
+```json
+"example-agent": {
+  "id": "example-agent",
+  "label": "Example Agent",
+  "format": "md-example",
+  "installKind": "per-rule",
+  "integrationPath": "{{slug}}.md",
+  "detect": { "dirs": [".example", "~/.example"] },
+  "dest": {
+    "project": ".example/rules/{{slug}}.md",
+    "user": "~/.example/rules/{{slug}}.md"
+  },
+  "frontmatter": {
+    "required": ["description"],
+    "map": {
+      "description": "string",
+      "globs": "array<string>|string"
+    }
+  }
+}
+```
+
+Field checklist:
+
+- [ ] `id` — matches the key, kebab-case.
+- [ ] `label` — human-readable name.
+- [ ] `format` — you will use this string as a key in `renderers/index.mjs`.
+- [ ] `installKind` — currently only `per-rule` is implemented.
+- [ ] `integrationPath` — path under `integrations/<id>/`. Use `{{slug}}`.
+- [ ] `detect.dirs` / `detect.files` — where the harness lives.
+- [ ] `dest.project` / `dest.user` — install destinations.
+- [ ] `frontmatter.required` — fields the harness cannot run without.
+- [ ] `frontmatter.map` — documentation of supported fields.
+- [ ] `plugin` — only if the harness needs a plugin registered.
+
+---
+
+## Step 2 — Create the renderer
+
+Create `scripts/lib/renderers/example-agent.mjs`:
+
+```js
+import { wrap } from './_util.mjs';
+
+export function renderExampleAgent(rule, _harness) {
+  const d = rule.data;
+  const fm = { description: d.description };
+  if (d.globs !== undefined) fm.globs = d.globs;
+  return wrap(fm, rule.body);
+}
+```
+
+Rules for renderers:
+
+- Pure. No `fs`, no `process`, no globals.
+- Signature is `(rule, harness) => string`.
+- Read only the fields your harness understands. Drop the rest silently —
+  other harnesses may need them.
+- Use `wrap()` from `_util.mjs` for consistent frontmatter formatting.
+
+---
+
+## Step 3 — Register the renderer
+
+Edit `scripts/lib/renderers/index.mjs`:
+
+```js
+import { renderExampleAgent } from './example-agent.mjs';
+
+export const renderers = {
+  // ...
+  'md-example': renderExampleAgent,
+};
+```
+
+The key must be the exact string from `tools.json`'s `format` field.
+
+---
+
+## Step 4 — Add tests
+
+Edit `tests/convert.test.mjs` and add a block:
+
+```js
+import { renderExampleAgent } from '../scripts/lib/renderers/example-agent.mjs';
+
+test('example-agent: emits description', () => {
+  const fm = matter(renderExampleAgent(baseRule)).data;
+  assert.equal(fm.description, 'Rules for TS.');
+});
+
+test('example-agent: preserves globs as-is', () => {
+  const fm = matter(renderExampleAgent(baseRule)).data;
+  assert.deepEqual(fm.globs, ['**/*.ts', '**/*.tsx']);
+});
+```
+
+Cover:
+
+- A rule with only the required fields.
+- A rule with every optional field your harness supports.
+- The "body preserved verbatim" test in the shared block.
+
+---
+
+## Step 5 — Verify end-to-end
+
+```bash
+mise run validate        # schema must still pass
+mise run convert         # your harness should appear in the summary
+ls integrations/example-agent/
+mise run test            # all renderer tests, including yours
+mise run install --harness example-agent --scope project
+```
+
+Inspect `integrations/example-agent/<slug>.md` and confirm the output matches
+your harness's expected format.
+
+---
+
+## Step 6 — Update docs
+
+- Add a row to the compatibility matrix in `docs/RULE-SPEC.md`.
+- Add a row to the harness table in `README.md`.
+- Update the "Adding a rule — checklist" in `CONTRIBUTING.md` if the new
+  harness changes requirements.
+
+---
+
+## Step 7 — Open a PR
+
+Title: `feat(harness): support example-agent`
+
+Include in the description:
+
+- Link to the harness's documentation.
+- A sample compiled output.
+- Screenshot or log from `mise run install` (optional but helpful).
+
+---
+
+## Supported harnesses (current)
+
+| Harness | `format` | `installKind` | Path |
+| --- | --- | --- | --- |
+| Google Antigravity | `md-yaml-trigger` | `per-rule` | `.agents/rules/*.md` |
+| pi-agent | `md-rules-dir` | `per-rule` | `.pi/rules/<slug>/RULES.md` |
+| oh-my-pi (omp) | `md-or-mdc` | `per-rule` | `.omp/rules/*.md` |
+| OpenCode | `md-plugin` | `per-rule` | `.opencode/rules/*.md` |

package/docs/ARCHITECTURE.md

@@ -0,0 +1,130 @@
+# Architecture
+
+This document explains how `agency-rules` turns one set of generic rules into
+four native harness formats, and why the pipeline is shaped the way it is.
+
+---
+
+## Data flow
+
+```
+         rules/*.md                     tools.json
+         (source of truth)              (contract)
+              │                              │
+              │                              │
+              ▼                              ▼
+    ┌────────────────────────────────────────────┐
+    │  scripts/validate.mjs  (schema + uniqueness)│
+    └────────────────────────────────────────────┘
+                        │
+                        ▼
+    ┌────────────────────────────────────────────┐
+    │  scripts/convert.mjs                        │
+    │    for each harness:                        │
+    │      render = renderers[harness.format]     │
+    │      for each rule:                         │
+    │        write render(rule, harness)          │
+    │      write _manifest.json                   │
+    └────────────────────────────────────────────┘
+                        │
+                        ▼
+              integrations/<harness>/...
+              (compiled, gitignored)
+                        │
+                        ▼
+    ┌────────────────────────────────────────────┐
+    │  scripts/install.mjs                        │
+    │    detect harnesses                         │
+    │    copy files to harness.dest[scope]        │
+    │    register plugins (opencode)              │
+    └────────────────────────────────────────────┘
+                        │
+                        ▼
+                  user's harness dirs
+```
+
+---
+
+## Layers
+
+| Layer | File(s) | Responsibility |
+| --- | --- | --- |
+| **Source** | `rules/**/*.md` | Generic Markdown + YAML frontmatter. |
+| **Schema** | `rules/_schema.json` | JSON Schema enforcing the neutral format. |
+| **Contract** | `tools.json` | Declares each harness: format, integration path, install destinations, frontmatter mapping, plugin metadata. |
+| **Engine** | `scripts/convert.mjs` | Iterates over rules × harnesses, calls the right renderer, writes output + manifest. |
+| **Renderers** | `scripts/lib/renderers/*.mjs` | Pure functions: `(rule, harness) → markdown string`. No I/O. |
+| **Installer** | `scripts/install.mjs` | Detects harnesses, copies compiled files to real destinations, registers plugins. |
+| **Validator** | `scripts/validate.mjs` | Runs the schema and checks slug uniqueness before anything else runs. |
+| **Orchestration** | `mise.toml` | Pins Node version, defines tasks, composes `ci`, wires the `postinstall` hook. |
+
+Each layer has exactly one job. Renderers never touch the filesystem; the
+engine never hardcodes a harness; the installer never renders.
+
+---
+
+## Why `tools.json` is the single source of truth
+
+Every harness-specific decision lives there:
+
+- **Which renderer** to use (`format`).
+- **What path** the output takes inside `integrations/<harness>/` (`integrationPath`).
+- **Where** the file ultimately lands for `project` and `user` scopes (`dest`).
+- **Which frontmatter fields** are required and how they map (`frontmatter`).
+- **Whether** plugin registration is needed (`plugin`).
+
+Adding a harness is additive: one `tools.json` entry + one renderer +
+one test. The engine, installer, and validator never change.
+
+---
+
+## Determinism guarantees
+
+- **Pure renderers.** Same input → same output byte for byte. No timestamps,
+  no random ordering. Manifests are sorted by slug.
+- **Full reset on convert.** `integrations/<harness>/` is deleted before
+  being rewritten. No stale files survive a rename.
+- **Manifest as index.** `integrations/<harness>/_manifest.json` records
+  every file the installer should copy. The installer trusts the manifest,
+  not a directory walk.
+- **Locked toolchain.** `mise.lock` pins exact versions of Node and any
+  installed CLIs. CI uses `mise install --locked` to fail on drift.
+
+---
+
+## Caching
+
+`mise run convert` declares:
+
+```toml
+sources = ["rules/**/*.md", "tools.json", "scripts/lib/**/*.mjs"]
+outputs = ["integrations/**/*"]
+```
+
+If no source has changed since the last run, mise skips the task entirely.
+This keeps the inner loop fast as the rules tree grows.
+
+---
+
+## OpenCode plugin registration
+
+OpenCode needs `opencode-rules` registered in `opencode.json`. The installer:
+
+1. Reads (or creates) `opencode.json`.
+2. Ensures `config.plugin` is an array.
+3. Appends `"opencode-rules@latest"` if it isn't already present.
+4. Writes the config back with 2-space indentation.
+
+If the file exists but is invalid JSON, the installer warns and skips rather
+than overwriting — a corrupted config is never silently clobbered.
+
+---
+
+## Security considerations
+
+- Rule slugs are validated against `^[a-z][a-z0-9-]*$` before they reach the
+  filesystem, preventing path traversal via `{{slug}}` substitution.
+- `install.mjs` only reads from `integrations/` and writes to paths derived
+  from `tools.json` — it never reads arbitrary user input paths.
+- Renderers do not execute rule content; they only stringify it. No `eval`,
+  no shell, no dynamic imports.

package/docs/RULE-SPEC.md

@@ -0,0 +1,135 @@
+# Rule Specification
+
+The neutral format for a rule: **Markdown with YAML frontmatter**.
+Every rule compiles to every harness, so the frontmatter must carry enough
+information to derive each harness's expectations.
+
+---
+
+## File layout
+
+```
+rules/
+├── _schema.json
+├── <category>/
+│   └── <slug>.md
+```
+
+- `_schema.json` is the JSON Schema. It is not a rule and is skipped.
+- Any file starting with `_` is skipped.
+- `<slug>` should equal the frontmatter `name`.
+
+---
+
+## Frontmatter fields
+
+| Field | Required | Type | Description |
+| --- | --- | --- | --- |
+| `name` | ✅ | string, `^[a-z][a-z0-9-]*$`, ≤64 | Unique identifier. Used as the slug. |
+| `description` | ✅ | string, 1–1024 | **When** the rule applies (not what it says). Harnesses use this for matching. |
+| `globs` | ❌ | string \| string[] | File patterns that trigger the rule. |
+| `alwaysApply` | ❌ | boolean | If `true`, ignore `globs` and always apply. |
+| `trigger` | ❌ | `always_on` \| `glob` \| `model_decision` \| `manual` | Explicit trigger for Antigravity. Overrides auto-derivation. |
+| `match` | ❌ | `any` \| `all` | OpenCode: match any glob or all globs. |
+| `tags` | ❌ | string[] | Freeform metadata. Ignored by all harnesses. |
+| `tools` | ❌ | string[] | pi-agent: tools the rule provides. Preserved verbatim. |
+
+---
+
+## Body
+
+The body is Markdown. It is copied verbatim into every compiled output.
+Don't put harness-specific syntax here — anything that must differ goes in
+the frontmatter and is handled by the renderer.
+
+---
+
+## Compatibility matrix
+
+| Field | Antigravity | pi-agent | oh-my-pi | OpenCode |
+| --- | --- | --- | --- | --- |
+| `name` | (derived) | ✅ used | ✅ used | — |
+| `description` | ✅ emitted | ✅ emitted | ✅ emitted | ✅ used for matching |
+| `globs` | ✅ joined as string under `trigger: glob` | ✗ dropped | ✅ preserved | ✅ preserved |
+| `alwaysApply` | ✅ → `trigger: always_on` | ✗ dropped | ✅ preserved | ✗ dropped |
+| `trigger` | ✅ emitted | ✗ dropped | ✗ dropped | ✗ dropped |
+| `match` | ✗ dropped | ✗ dropped | ✗ dropped | ✅ preserved |
+| `tags` | ✗ dropped | ✗ dropped | ✗ dropped | ✗ dropped |
+| `tools` | ✗ dropped | ✅ preserved | ✗ dropped | ✗ dropped |
+
+"✗ dropped" means the field is not emitted in that harness's output. It does
+not mean it's an error to set it — other harnesses may need it. The renderer
+picks what its harness understands.
+
+---
+
+## Antigravity trigger precedence
+
+Antigravity requires a `trigger` field. The renderer resolves it in this
+order:
+
+1. Explicit `trigger` in the rule.
+2. `alwaysApply: true` → `always_on`.
+3. `globs` present → `glob`.
+4. Only `description` → `model_decision`.
+5. Nothing → `manual`.
+
+When `trigger: glob`, the renderer joins the `globs` array with commas into a
+single string, which is the format Antigravity's YAML parser expects.
+
+---
+
+## Examples
+
+### Always-on baseline
+
+```markdown
+---
+name: coding-standards
+description: Baseline rules applied to every edit regardless of file type.
+alwaysApply: true
+tags: [base]
+---
+
+# Coding Standards
+...
+```
+
+Compiles to Antigravity `trigger: always_on`, oh-my-pi `alwaysApply: true`,
+and pi-agent / OpenCode with just `name` + `description`.
+
+### Scoped to file globs
+
+```markdown
+---
+name: typescript
+description: Mandatory rules for editing TypeScript and TSX files.
+globs:
+  - "**/*.ts"
+  - "**/*.tsx"
+tags: [language, typescript]
+---
+
+# TypeScript Rules
+...
+```
+
+Compiles to Antigravity `trigger: glob` + `globs: "**/*.ts,**/*.tsx"`,
+oh-my-pi and OpenCode with the original array, pi-agent without `globs`.
+
+### Description-only (model decision)
+
+```markdown
+---
+name: api-review
+description: Use this rule when reviewing REST API endpoint definitions.
+---
+
+# API Review
+...
+```
+
+Compiles to Antigravity `trigger: model_decision`. Other harnesses get just
+`name` + `description`.
+
+```