@@ -184,8 +184,7 @@ import BrandWordmark from './BrandWordmark.astro';
{`description: Math evaluation
-execution:
- target: default
+target: default
tests:
- id: addition
diff --git a/apps/web/src/content/docs/docs/next/guides/enterprise-governance.mdx b/apps/web/src/content/docs/docs/next/guides/enterprise-governance.mdx
index 663565fad..12ee529e1 100644
--- a/apps/web/src/content/docs/docs/next/guides/enterprise-governance.mdx
+++ b/apps/web/src/content/docs/docs/next/guides/enterprise-governance.mdx
@@ -58,7 +58,7 @@ system:
last_reviewed: 2026-04-24
```
-The full example, including comments, is in the agentv repo at
+The full example, including comments, is in the AgentV repo at
`examples/governance/ai-register/.ai-register.yaml`.
### Why these fields
@@ -71,7 +71,7 @@ The full example, including comments, is in the agentv repo at
exercised by its evals.
- **`last_reviewed`** — a date. Aggregators flag entries older than
whatever cadence your governance team works to.
-- **`evals.path`** — a pointer to the agentv evals that exercise this
+- **`evals.path`** — a pointer to the AgentV evals that exercise this
system. The aggregator does not run them; it just records that they exist.
## Aggregating across the org
@@ -111,7 +111,7 @@ That's the whole loop.
## Relationship to evaluation
-agentv does not parse `.ai-register.yaml`. The convention is **orthogonal**:
+AgentV does not parse `.ai-register.yaml`. The convention is **orthogonal**:
- The manifest documents **which AI systems exist**, who owns them, and
which controls they are accountable for.
diff --git a/apps/web/src/content/docs/docs/next/guides/workspace-architecture.mdx b/apps/web/src/content/docs/docs/next/guides/workspace-architecture.mdx
index 4fabfa5de..6846c4921 100644
--- a/apps/web/src/content/docs/docs/next/guides/workspace-architecture.mdx
+++ b/apps/web/src/content/docs/docs/next/guides/workspace-architecture.mdx
@@ -244,7 +244,7 @@ On Windows, the drive type materially affects file-write throughput during check
[Windows Dev Drive](https://learn.microsoft.com/en-us/windows/dev-drive/) uses the Resilient File System (ReFS) with a performance mode that reduces antivirus filter overhead for developer workloads. If you evaluate large repos frequently, relocating `~/.agentv` to a Dev Drive volume can meaningfully reduce per-run setup time.
-To relocate the agentv home directory, set `HOME` or `USERPROFILE` to point to the Dev Drive path before running `agentv eval`:
+To relocate the AgentV home directory, set `HOME` or `USERPROFILE` to point to the Dev Drive path before running `agentv eval`:
```powershell
$env:USERPROFILE = "D:\Users\$env:USERNAME"
diff --git a/apps/web/src/content/docs/docs/v4.42.4/guides/enterprise-governance.mdx b/apps/web/src/content/docs/docs/v4.42.4/guides/enterprise-governance.mdx
index 6ddc0c236..66f162d01 100644
--- a/apps/web/src/content/docs/docs/v4.42.4/guides/enterprise-governance.mdx
+++ b/apps/web/src/content/docs/docs/v4.42.4/guides/enterprise-governance.mdx
@@ -61,7 +61,7 @@ system:
last_reviewed: 2026-04-24
```
-The full example, including comments, is in the agentv repo at
+The full example, including comments, is in the AgentV repo at
`examples/governance/ai-register/.ai-register.yaml`.
### Why these fields
@@ -74,7 +74,7 @@ The full example, including comments, is in the agentv repo at
exercised by its evals.
- **`last_reviewed`** — a date. Aggregators flag entries older than
whatever cadence your governance team works to.
-- **`evals.path`** — a pointer to the agentv evals that exercise this
+- **`evals.path`** — a pointer to the AgentV evals that exercise this
system. The aggregator does not run them; it just records that they exist.
## Aggregating across the org
@@ -114,7 +114,7 @@ That's the whole loop.
## Relationship to evaluation
-agentv does not parse `.ai-register.yaml`. The convention is **orthogonal**:
+AgentV does not parse `.ai-register.yaml`. The convention is **orthogonal**:
- The manifest documents **which AI systems exist**, who owns them, and
which controls they are accountable for.
diff --git a/apps/web/src/content/docs/docs/v4.42.4/guides/workspace-architecture.mdx b/apps/web/src/content/docs/docs/v4.42.4/guides/workspace-architecture.mdx
index 41c6f068b..13c9b487b 100644
--- a/apps/web/src/content/docs/docs/v4.42.4/guides/workspace-architecture.mdx
+++ b/apps/web/src/content/docs/docs/v4.42.4/guides/workspace-architecture.mdx
@@ -197,7 +197,7 @@ On Windows, the drive type materially affects file-write throughput during check
[Windows Dev Drive](https://learn.microsoft.com/en-us/windows/dev-drive/) uses the Resilient File System (ReFS) with a performance mode that reduces antivirus filter overhead for developer workloads. If you evaluate large repos frequently, relocating `~/.agentv` to a Dev Drive volume can meaningfully reduce per-run setup time.
-To relocate the agentv home directory, set `HOME` or `USERPROFILE` to point to the Dev Drive path before running `agentv eval`:
+To relocate the AgentV home directory, set `HOME` or `USERPROFILE` to point to the Dev Drive path before running `agentv eval`:
```powershell
$env:USERPROFILE = "D:\Users\$env:USERNAME"
diff --git a/examples/governance/ai-register/README.md b/examples/governance/ai-register/README.md
index f229ec8fe..d563a3897 100644
--- a/examples/governance/ai-register/README.md
+++ b/examples/governance/ai-register/README.md
@@ -51,16 +51,16 @@ manifest and the aggregator workflow file.
| `limitations` | NIST RMF MEASURE-1.1; EU AI Act Annex IV §2 | Known failure modes and out-of-scope uses |
| `human_oversight` | EU AI Act Art. 14; NIST RMF GOVERN-4 | Required for `risk_tier: high`. Document override authority and escalation triggers |
| `models[]` | — | Versioned model identifiers so auditors can reconstruct which model was running at any point in time |
-| `evals.path` | — | Path to agentv evals that exercise this system |
+| `evals.path` | — | Path to AgentV evals that exercise this system |
| `controls[]` | — | `-:` strings; same format as eval result JSONL |
| `last_reviewed` | NIST RMF GOVERN-1.3; ISO 42001 Clause 7 | Aggregators flag entries older than your governance cadence (90 days typical) |
-## Why this stays out of agentv core
+## Why this stays out of AgentV core
-agentv does not parse `.ai-register.yaml`. The convention is deliberately
+AgentV does not parse `.ai-register.yaml`. The convention is deliberately
free-standing: if you later adopt a governance platform (Credo AI, OneTrust,
ServiceNow AI Control Tower, IBM watsonx.governance), these manifests are
your import source — not a thing you need to migrate away from.
If the convention grows, that growth happens in conversation between teams
-adopting it; agentv stays lightweight.
+adopting it; AgentV stays lightweight.
diff --git a/examples/red-team/README.md b/examples/red-team/README.md
index 0e7aa6467..3dfe75736 100644
--- a/examples/red-team/README.md
+++ b/examples/red-team/README.md
@@ -4,7 +4,7 @@ Opt-in adversarial eval suites tagged against public AI-safety taxonomies. Copy
this directory into your own repo, point a target at it, and you have a starting
red-team baseline drawn from the corpora the field has converged on.
-## How this fits agentv design
+## How this fits AgentV design
This pack is **content, not core**. There are no changes to `packages/core` or
`apps/cli`; the suites compose existing primitives — `llm-rubric`,
diff --git a/examples/showcase/bug-fix-benchmark/README.md b/examples/showcase/bug-fix-benchmark/README.md
index 34e540e88..85f4de754 100644
--- a/examples/showcase/bug-fix-benchmark/README.md
+++ b/examples/showcase/bug-fix-benchmark/README.md
@@ -53,7 +53,7 @@ agentv results compare \
## Test Case: Issue #912
-The eval includes a real bug from the agentv repo:
+The eval includes a real bug from the AgentV repo:
- **Issue**: [#912 — CLI provider retries don't preserve workspace cwd](https://github.com/EntityProcess/agentv/issues/912)
- **Base commit**: `6e446b72` (before the fix)
diff --git a/examples/showcase/bug-fix-benchmark/evals/bug-fixes.eval.yaml b/examples/showcase/bug-fix-benchmark/evals/bug-fixes.eval.yaml
index 63686c943..61135038c 100644
--- a/examples/showcase/bug-fix-benchmark/evals/bug-fixes.eval.yaml
+++ b/examples/showcase/bug-fix-benchmark/evals/bug-fixes.eval.yaml
@@ -35,7 +35,7 @@ tags: [ coding, bugfix, benchmark, swe-bench ]
tests:
# Issue #912: CLI provider retries don't preserve workspace cwd
- # A real bug from the agentv repo. The fix is in packages/core/src/evaluation/providers/cli.ts
+ # A real bug from the AgentV repo. The fix is in packages/core/src/evaluation/providers/cli.ts
# where invokeBatch() uses this.config.cwd instead of request.cwd.
#
# This is the same task that was used in the hivespec session:
diff --git a/examples/showcase/cross-repo-sync/README.md b/examples/showcase/cross-repo-sync/README.md
index 6d48bfc5b..f7a2cc849 100644
--- a/examples/showcase/cross-repo-sync/README.md
+++ b/examples/showcase/cross-repo-sync/README.md
@@ -4,7 +4,7 @@ Evaluates whether a coding agent can keep two public repos in sync after one cha
## Scenario
-When **agentv** (EntityProcess/agentv) ships a feature, the **agentevals** (agentevals/agentevals) spec docs must be updated to reflect the change. This eval measures how well an agent handles that cross-repo synchronization.
+When **AgentV** (EntityProcess/agentv) ships a feature, the **agentevals** (agentevals/agentevals) spec docs must be updated to reflect the change. This eval measures how well an agent handles that cross-repo synchronization.
## Workspace Features Demonstrated
diff --git a/examples/showcase/cross-repo-sync/evals/suite.yaml b/examples/showcase/cross-repo-sync/evals/suite.yaml
index 28e2cc53d..509738b0d 100644
--- a/examples/showcase/cross-repo-sync/evals/suite.yaml
+++ b/examples/showcase/cross-repo-sync/evals/suite.yaml
@@ -1,5 +1,5 @@
name: cross-repo-sync
-description: Evaluate agent ability to sync agentv implementation with agentevals spec
+description: Evaluate agent ability to sync AgentV implementation with agentevals spec
version: "1.0"
tags: [ showcase, workspace, cross-repo ]
@@ -25,7 +25,7 @@ tests:
input:
- role: user
content: |
- agentv just merged eval spec v2 (PR #262). Update the agentevals
+ AgentV just merged eval spec v2 (PR #262). Update the agentevals
spec docs to reflect: 4 new deterministic assertion types, required
gates, assert field at test/suite level, tests-as-string-path.
assert:
@@ -48,7 +48,7 @@ tests:
input:
- role: user
content: |
- agentv renamed cases→tests in the eval schema (PR #240).
+ AgentV renamed cases→tests in the eval schema (PR #240).
Update all agentevals spec docs to match.
assert:
- metric: sync-check
@@ -68,7 +68,7 @@ tests:
input:
- role: user
content: |
- agentv renamed schema fields: eval_cases→cases, expected_outcome→criteria
+ AgentV renamed schema fields: eval_cases→cases, expected_outcome→criteria
at case level, expected_outcome→outcome at rubric level (PR #202).
Update agentevals spec docs accordingly.
assert:
diff --git a/examples/showcase/cross-repo-sync/workspace-template/AGENTS.md b/examples/showcase/cross-repo-sync/workspace-template/AGENTS.md
index fbf79dc69..a5cf43878 100644
--- a/examples/showcase/cross-repo-sync/workspace-template/AGENTS.md
+++ b/examples/showcase/cross-repo-sync/workspace-template/AGENTS.md
@@ -14,7 +14,7 @@ Key docs paths:
### agentv/ (EntityProcess/agentv)
TypeScript/Bun evaluation framework. Reference implementation of the agentevals spec.
-Source of truth — when agentv ships features, the agentevals spec must be updated.
+Source of truth — when AgentV ships features, the agentevals spec must be updated.
Key source paths:
- `packages/core/src/evaluation/types.ts`
diff --git a/examples/showcase/cross-repo-sync/workspace-template/skills/cross-repo-sync.md b/examples/showcase/cross-repo-sync/workspace-template/skills/cross-repo-sync.md
index 420e2e105..68b03a29a 100644
--- a/examples/showcase/cross-repo-sync/workspace-template/skills/cross-repo-sync.md
+++ b/examples/showcase/cross-repo-sync/workspace-template/skills/cross-repo-sync.md
@@ -1,11 +1,11 @@
# Cross-Repo Sync
-Synchronize agentevals spec docs when agentv implementation changes.
+Synchronize agentevals spec docs when AgentV implementation changes.
## Process
-1. **Read the prompt** to understand what changed in agentv
-2. **Examine the agentv checkout** to see the actual implementation changes
+1. **Read the prompt** to understand what changed in AgentV
+2. **Examine the AgentV checkout** to see the actual implementation changes
3. **Find corresponding spec/docs files** in the agentevals checkout
4. **Make updates** preserving existing Starlight/MDX conventions