agentic-scorecard 0.2.0 → 0.3.1

package/AGENT_PROMPT.md

@@ -1,65 +1,85 @@
-# Ask an AI coding agent to run ADRB v0.2
+# Ask an AI coding agent to run ADRB v0.3
 
 These prompts are vendor-neutral. The agent needs terminal access to the repository and permission
 to download the published npm package. The default benchmark runs locally, reads only tracked paths,
 invokes no model, uploads no source, and makes no network calls after installation.
 
-## Recommended: repository baseline
+## Recommended: complete agent-assisted assessment
 
 Copy and paste:
 
 ```text
-Assess this repository's readiness for AI-agent pull-request work.
-
-From the repository root, run:
-npx --yes agentic-scorecard@0.2.0 assess . --profile pr-creation --scope tracked --format markdown --output .agentic/reports/agentic-readiness-v0.2.0.md
-
-Do not change product source, configuration, policies, or tests. Do not invent evidence or mark an
-attestation as met. Read the report and tell me:
-1. the score and highest passed readiness profile;
-2. whether the pr-creation target passes;
-3. each target-profile blocker and its evidence scope;
-4. the five highest-value improvements in dependency order;
-5. which findings are repository gaps versus external or outcome evidence not yet established; and
-6. any likely false positive or false negative.
-
-Keep repository-detected, agent-collected, and human-attested evidence separate. Leave generated
-artifacts uncommitted unless I explicitly ask otherwise. If the command cannot run, explain the
-exact blocker without modifying the repository to work around it.
+Perform the complete ADRB v0.3 assessment of this repository for AI-agent pull-request work.
+
+Do not change product source, tests, configuration, policies, Git history, or the user's current
+checkout. First inspect the repository's commit, tracked-file status, upstream tracking branch, and
+ahead/behind state. If read-only network access is already authorized, fetch the upstream before
+comparing it. Select the commit before creating an assessment worktree. Default to the current HEAD;
+a dirty checkout does not change that selection, so assess HEAD from an isolated clean worktree. Use
+the fetched upstream commit only when I asked for the latest/current upstream state and the branch is
+behind. If the checkout is both dirty and behind, state both facts and preserve HEAD by default unless
+I explicitly asked for upstream or another commit. State the exact commit you selected and why.
+
+Before running the scorecard, choose and state an absolute durable artifact directory outside any
+temporary worktree. Do not delete that directory during worktree cleanup. In the commands below,
+replace `<artifact-dir>` with that path. The npm package version is 0.3.1, while report filenames use
+the immutable ADRB benchmark version 0.3.0.
+
+From that clean target, run the repository-only baseline:
+npx --yes agentic-scorecard@0.3.1 assess . --profile pr-creation --scope tracked --format markdown --output <artifact-dir>/agentic-readiness-v0.3.0-baseline.md
+
+Then prepare unresolved evidence:
+npx --yes agentic-scorecard@0.3.1 init-evidence . --output <artifact-dir>/agent-evidence.yaml --request-output <artifact-dir>/evidence-request.md
+
+Read the baseline, `<artifact-dir>/evidence-request.md`, and the empty target-bound
+`<artifact-dir>/agent-evidence.yaml`. Investigate nuanced repository-scoped requests only from
+tracked files at the selected commit. Before accessing Git hosting settings, CI, dashboards, logs,
+ticketing, or any other connected system, tell me exactly which least-privileged read-only tools,
+accounts, repositories, branches, dashboards, and time ranges you need, and why. Wait for my
+authorization.
+
+After authorization, attempt only eligible requests. For every attempted claim, record its status,
+scope, concise derivation, collection time, 30-day-or-shorter expiry, and durable privacy-safe
+references. Repository claims must use `repo:<path>[#Lx-Ly]`; do not merely restate a keyword match.
+A permission error, stale source, or inconclusive result remains unknown and records the error.
+Never infer a pass, invent an attestation, or treat unavailable evidence as a failure.
+
+Do not place credentials, prompts, source excerpts, raw logs, personal data, customer data, private
+URLs that reveal secrets, or sensitive dashboard contents in generated files.
+
+When authorized evidence collection is complete, run:
+npx --yes agentic-scorecard@0.3.1 assess . --profile pr-creation --scope tracked --agent-evidence <artifact-dir>/agent-evidence.yaml --format markdown --output <artifact-dir>/agentic-readiness-v0.3.0-assisted.md
+
+Tell me the repository-detected progress and normative score, the highest passed profile, whether
+pr-creation passes, every target blocker, and the five highest-value improvements. Compare baseline
+and assisted reports control by control. Keep repository-detected, agent-collected, and
+human-attested evidence separate; treat UNKNOWN as unresolved, not failed; and flag likely false
+positives or negatives. If I decline external access, stop after the baseline and label it clearly as
+a repository-only baseline. Before removing a temporary worktree, verify that every report, evidence
+request, and evidence bundle you cite exists in the durable artifact directory, then tell me that
+directory's absolute path. Leave generated artifacts uncommitted unless I explicitly ask otherwise.
+Do not describe any result as certified, compliant, safe, secure, or independently verified.
 ```
 
-## Agent-assisted external evidence
-
-Use this only after reviewing the repository baseline:
-
-```text
-Collect the external evidence that ADRB v0.2 could not establish from tracked repository files.
-
-First run:
-npx --yes agentic-scorecard@0.2.0 init-evidence .
-
-Read `.agentic/evidence-request.md` and the empty target-bound
-`.agentic/agent-evidence.yaml` bundle. Before accessing any connected system, tell me which
-read-only tools, accounts, repositories, branches, dashboards, and time ranges you need. Wait for
-my authorization.
+The agent is an evidence investigator. The scorecard remains the scoring authority.
 
-After authorization, use only least-privileged read-only operations. For each eligible control,
-record the source-backed status, scope, concise derivation, collection time, 30-day-or-shorter
-expiry, and durable privacy-safe references. Add only claims you actually attempted. Do not paste
-credentials, prompts, source excerpts, raw logs, personal data, or sensitive dashboard contents. A
-permission error or inconclusive result must remain unknown and include the error; never infer a
-pass.
+## Fast repository-only baseline
 
-Then run:
-npx --yes agentic-scorecard@0.2.0 assess . --profile pr-creation --scope tracked --agent-evidence .agentic/agent-evidence.yaml --format markdown --output .agentic/reports/agentic-readiness-v0.2.0-assisted.md
+Use this when you want an offline first look and accept that platform, organization, and outcome
+controls will remain unresolved:
 
-Summarize every score change and keep agent-collected evidence distinct from repository evidence and
-human attestations. Do not describe the result as certified, compliant, safe, secure, or
-independently verified.
+```text
+Run a fast repository-only ADRB v0.3 baseline for AI-agent pull-request work. Verify and state the
+selected commit and whether tracked files match HEAD, then run:
+npx --yes agentic-scorecard@0.3.1 assess . --profile pr-creation --scope tracked --format markdown --output .agentic/reports/agentic-readiness-v0.3.0-baseline.md
+
+Do not change repository files or invent evidence. Summarize repository-detected progress before
+the normative score, target-profile blockers, and the five highest-value repository improvements.
+Separate true repository gaps from platform, organization, and outcome evidence that this offline
+scan cannot establish. Treat UNKNOWN as unresolved, not failed, and call the result a repository-only
+baseline rather than a complete assessment. Leave generated artifacts uncommitted.
 ```
 
-The agent is an evidence investigator. The scorecard remains the scoring authority.
-
 ## Choose a different authority level
 
 Replace `pr-creation` with one of:
@@ -75,7 +95,7 @@ No benchmark profile grants production deployment authority.
 ## Guided remediation
 
 ```text
-Read the latest ADRB v0.2 report and create a remediation proposal for the failed target-profile
+Read the latest ADRB v0.3 report and create a remediation proposal for the failed target-profile
 controls. Do not implement changes yet. Group recommendations into repository changes, platform or
 organizational controls, and outcome measurement. For each include the control ID, risk reduced,
 systems affected, accountable role, verification method, dependencies, and effort estimate. Never
@@ -86,8 +106,9 @@ authorize.
 ## Reassessment
 
 ```text
-Re-run the pinned ADRB v0.2.0 benchmark for the same profile and tracked scope. Compare reports
-control by control. Explain changes using evidence and identify changed commit state, expired claims,
-scope differences, regressions, or newly established controls. Write a new dated report; do not
-overwrite the previous one.
+Re-run the pinned ADRB v0.3.0 benchmark with agentic-scorecard@0.3.1 for the same profile and tracked scope. Compare reports
+control by control. Explain changes using evidence and identify changed commit state, expired
+claims, scope differences, regressions, or newly established controls. Compare normative and
+repository-detected progress separately. Write a new dated report; do not overwrite the previous
+one.
 ```

package/README.md

@@ -16,26 +16,33 @@ The benchmark measures the harness, not the model brand. It assesses ten dimensi
 maturity levels and applies non-compensating floors to five autonomy profiles. A high total score
 cannot hide a critical security, testing, governance, or recovery gap.
 
-This repository is a **v0.2 reference implementation** intended for public review and piloting. It
-is not a certification standard. The immutable v0.1 benchmark remains available for historical
-reproduction; v0.1 and v0.2 scores are not directly comparable.
+This repository is a **v0.3 reference implementation** intended for public review and piloting. It
+is not a certification standard. The immutable v0.1 and v0.2 benchmarks remain available for
+historical reproduction; scores from different benchmark versions are not directly comparable.
 
 ## Ask your coding agent
 
-You do not need to install or learn the CLI yourself. Paste this prompt into Codex, Claude Code,
+You do not need to install or learn the CLI yourself. Paste this instruction into Codex, Claude Code,
 GitHub Copilot, Cursor, or another coding agent that has terminal access to your repository:
 
-> Assess this repository's readiness for AI-agent pull-request work. From the repository root, run
-> `npx --yes agentic-scorecard@0.2.0 assess . --profile pr-creation --scope tracked --format markdown --output .agentic/reports/agentic-readiness-v0.2.0.md`.
-> Do not change product source code or invent attestations. Read the resulting report and summarize
-> the score, highest passed profile, whether `pr-creation` passes, target-profile blockers, and the
-> five highest-value improvements. Separate repository gaps from external and outcome evidence, and
-> keep repository-detected, agent-collected, and human-attested evidence distinct. Flag likely false
-> positives or negatives. Leave generated artifacts uncommitted unless I ask you to commit them.
-
-That is the recommended first assessment. The agent downloads the pinned benchmark package, runs the
-read-only local collector, and explains the results. For alternate authority levels or a guided
-remediation session, use the prompts in [AGENT_PROMPT.md](AGENT_PROMPT.md).
+> Perform the complete ADRB v0.3 assessment of this repository for AI-agent pull-request work using
+> `agentic-scorecard@0.3.1`. First select and state the commit without modifying my checkout; preserve
+> HEAD when the checkout is dirty, and use upstream only if I requested the latest upstream state.
+> Assess it from a clean worktree and keep all generated artifacts in a durable directory outside any
+> temporary worktree. Run the tracked repository baseline, then run `init-evidence`, read its evidence
+> request, and tell me which least-privileged read-only connected systems you need. Wait for my
+> authorization before accessing them. After authorized collection, rerun the assessment and compare
+> the baseline and assisted reports control by control. Keep repository-detected, agent-collected, and
+> human-attested evidence separate; never invent evidence; treat UNKNOWN as unresolved; and leave
+> generated artifacts uncommitted.
+
+The complete copy-and-paste prompt, including privacy limits and exact commands, is in
+[AGENT_PROMPT.md](AGENT_PROMPT.md). It makes the evidence-assisted workflow the recommendation. A
+fast filesystem scan remains available, but it is explicitly a **repository-only baseline** and
+cannot establish platform, organization, or outcome controls by itself.
+
+The reference CLI/package is version 0.3.1. Generated report names use benchmark version 0.3.0
+because the patch release changed workflow guidance, not the immutable scoring benchmark.
 
 ## Feedback and community
 
@@ -70,7 +77,7 @@ A supported Node.js LTS release (20.19+, 22.13+, or 24+) is required. Assessment
 read-only, and offline by default.
 
 ```bash
-npx agentic-scorecard@0.2.0 assess /path/to/repository \
+npx agentic-scorecard@0.3.1 assess /path/to/repository \
   --profile pr-creation \
   --scope tracked \
   --format markdown \
@@ -80,7 +87,7 @@ npx agentic-scorecard@0.2.0 assess /path/to/repository \
 To record controls that repository inspection cannot prove:
 
 ```bash
-npx agentic-scorecard@0.2.0 init /path/to/repository
+npx agentic-scorecard@0.3.1 init /path/to/repository
 ```
 
 Complete `.agentic/attestations.yaml` with owners and durable evidence links, then assess again.
@@ -91,7 +98,7 @@ external systems, first generate a target-bound template. The repository must be
 with at least one commit so the bundle can bind to the exact assessed state:
 
 ```bash
-npx agentic-scorecard@0.2.0 init-evidence /path/to/repository
+npx agentic-scorecard@0.3.1 init-evidence /path/to/repository
 ```
 
 Ask the agent to review `.agentic/evidence-request.md`, obtain approval before using
@@ -99,19 +106,27 @@ least-privileged read-only connectors, add attempted claims to `.agentic/agent-e
 rerun with `--agent-evidence`. The default bundle path is loaded automatically. See
 [AGENT_PROMPT.md](AGENT_PROMPT.md) for the complete copy-and-paste workflow.
 
-### Migrating from v0.1
+### Migrating from v0.1 or v0.2
 
 Run a new tracked-scope baseline and retain the old report as historical evidence. Do not present the
-score change as improvement or regression because v0.2 changes evidence semantics. Re-review v0.1
-attestations before recreating them for v0.2; v0.2 repository-artifact controls cannot be overridden
-by declaration, and every human or agent-collected external claim must expire.
+score change as improvement or regression because v0.3 changes evidence and control semantics.
+Re-review prior attestations and agent evidence before recreating them for v0.3. All claims must
+expire, and repository-scoped semantic claims require tracked files to match the commit-bound target
+plus `repo:<path>[#Lx-Ly]` references whose optional line ranges exist in the cited tracked file.
+Untracked generated reports do not block this workflow.
+
+The default `.agentic/attestations.yaml` and `.agentic/agent-evidence.yaml` paths are migration-safe:
+if either contains an older benchmark version, v0.3 ignores that auto-loaded file and places a
+prominent warning in the report. Regenerate it with `init --force` or `init-evidence --force` before
+relying on those claims. An explicitly supplied `--attestations` or `--agent-evidence` file still
+fails closed on a version mismatch.
 
 For development from this checkout:
 
 ```bash
 npm ci
 npm run check
-npm run dev -- assess tests/fixtures/mature --profile pr-creation
+npm run dev -- assess tests/fixtures/mature --profile pr-creation --attestations tests/fixtures/mature/.agentic/attestations-v0.3.yaml
 ```
 
 ## What it assesses
@@ -157,22 +172,32 @@ No profile grants production deployment authority. Organizations should evaluate
 through a separate, system-specific safety case.
 
 The exact floors live in
-[`benchmark/v0.2/benchmark.yaml`](benchmark/v0.2/benchmark.yaml) and their rationale in
-[`benchmark/v0.2/scoring-policy.md`](benchmark/v0.2/scoring-policy.md).
+[`benchmark/v0.3/benchmark.yaml`](benchmark/v0.3/benchmark.yaml) and their rationale in
+[`benchmark/v0.3/scoring-policy.md`](benchmark/v0.3/scoring-policy.md).
 
 ## Evidence scopes and trust labels
 
 - **Repository-detected:** the local collector found qualifying evidence in the selected path scope.
   This proves an artifact match, not consistent practice or external enforcement.
-- **Agent-collected:** an authorized agent supplied a target-bound, expiring, source-backed external
-  claim. It is not independently verified.
+- **Agent-collected:** an authorized agent supplied a target-bound, expiring, source-backed semantic
+  repository or external claim for an explicitly eligible control. It is not independently
+  verified and is never relabelled as repository-detected.
 - **Human-attested:** an accountable owner supplied a dated evidence link or explanation.
 - **Unknown:** evidence is unavailable, expired, unauthorized, mismatched, or inconclusive.
 
 Controls also identify whether their evidence belongs in the repository, hosting platform,
 organization, or outcome systems. This prevents expected external unknowns from masquerading as
-missing files. Future independently conformant adapters require a separate protocol; v0.2 does not
-issue certification or independent-verification claims.
+missing files. Declarative detector adapters recognize common harness layouts without changing
+portable control outcomes; future independently conformant external adapters require a separate
+protocol. v0.3 does not issue certification or independent-verification claims.
+
+### Interpreting the two score views
+
+The normative score remains `N/40` and drives readiness profiles. v0.3 also reports
+`repository-detected progress: A/C`, where `C` is the maximum consecutive maturity the offline
+collector can establish without platform, organization, outcome, agent-collected, or human-attested
+evidence. This second view explains how complete the visible repository harness is; it does not
+normalize away UNKNOWNs, change readiness floors, or certify the project.
 
 ## Reports and CI
 
@@ -200,7 +225,8 @@ The default collector:
 - reads only Git-tracked paths and records commit and dirty-worktree metadata;
 - ignores `.git`, dependencies, build output, coverage, generated reports, attestations, and imported
   evidence bundles;
-- caps content-scanned files at 512 KB;
+- caps content scanning at 512 KB per file, 5 MB total, and 250 candidates per check, with v0.3
+  per-pattern balancing where configured;
 - reports file paths and match counts, never matching source snippets;
 - writes nothing unless `--output`, `init`, or `init-evidence` is explicitly requested.
 
@@ -211,7 +237,9 @@ access-controlled evidence instead. Report suspected vulnerabilities through [SE
 
 ```text
 benchmark/v0.1/       immutable historical v0.1 definition
-benchmark/v0.2/       current normative benchmark, schemas, and controls
+benchmark/v0.2/       immutable historical v0.2 definition
+benchmark/v0.3/       current normative benchmark, schemas, and controls
+  adapters/           declarative path/term aliases for recognized agent harness layouts
 benchmark/mappings/   informative mappings to external frameworks
 src/                  reference CLI and local evidence collectors
 templates/            adoption, preflight, attestation, and remediation templates
@@ -240,8 +268,9 @@ system, and keep exceptions narrow, owned, expiring, and visible.
 
 ## Status and roadmap
 
-v0.2 adds integrity-safe tracked-path collection, evidence scopes, precise co-located content
-matching, agent-collected external evidence, and transparent report grouping. Candidate next steps
+v0.3 adds portable harness discovery with declarative detector adapters, proximity-bounded content evidence, prioritized candidate
+selection for large repositories, source-backed semantic repository claims, and an explanatory
+repository-only score and ceiling. Candidate next steps
 include conformant signed adapters, SARIF/HTML reports, organization-level aggregation,
 statistically designed benchmark tasks, and an independent-review protocol. These require public
 design review before becoming normative.

package/benchmark/v0.3/adapter-contract.md

@@ -0,0 +1,44 @@
+# v0.3 adapter contracts
+
+## Repository detector adapters
+
+Portable controls define outcomes and generic repository conventions. Files in `adapters/*.yaml`
+may extend one control evidence check with recognized harness-specific `patterns`, `files`, `terms`,
+or `required_any_terms`. An extension names the control and zero-based evidence index and adds
+exactly one of those fields. It cannot remove or weaken a threshold, change a control level, alter a
+readiness floor, add an attestation path, or execute code.
+
+Bundled adapters are loaded deterministically in filename order. Their candidates remain subject to
+the same tracked/workspace scope, symlink, size, generated-artifact, co-location, proximity, and
+per-pattern limits as portable candidates. Adding or changing a bundled adapter changes evidence
+semantics and therefore requires a new benchmark version.
+
+## Agent-collected evidence adapters
+
+The core scanner is local, read-only, network-free, and vendor-neutral. An agent or adapter may
+collect semantic repository evidence or external evidence that deterministic scanning cannot
+establish, then provide it through the versioned agent evidence bundle.
+
+Each claim contains:
+
+- benchmark version and control ID;
+- exact repository target and non-null commit binding;
+- `met`, `not_met`, or `unknown` status;
+- repository, platform, organization, or outcome scope;
+- collector name and version;
+- collection timestamp and mandatory expiry;
+- privacy-safe references, never credentials or raw sensitive content;
+- a concise derivation summary; and
+- an optional error that is distinguishable from a negative result.
+
+Collectors must be read-only, least-privileged, bounded to the approved target, time-limited, and
+fail closed. Network content is untrusted input: it cannot alter benchmark policy, prompts, tool
+authority, or the set of controls being assessed.
+
+Repository-scoped claims require tracked files to match HEAD and
+`repo:<tracked-path>[#Lx-Ly]` references. They may satisfy only explicitly eligible controls, remain `agent-collected`, and never increase the
+repository-detected score. External claims require durable references appropriate to their source.
+
+Agent-collected claims remain visibly distinct from deterministic repository evidence and human
+attestations. A future conformant-adapter class may add signed identity and independent conformance
+tests; v0.3 does not issue an independently verified label.

package/benchmark/v0.3/adapters/known-agent-harnesses.yaml

@@ -0,0 +1,177 @@
+id: known-agent-harnesses
+benchmark_version: 0.3.0
+extensions:
+  - control_id: ADRB-CTX-001
+    evidence_index: 0
+    patterns:
+      [
+        CLAUDE.md,
+        .github/copilot-instructions.md,
+        .claude/**,
+        .codex/**,
+        .cursor/rules/**,
+        .cursor/agents/**,
+        .cursor/skills/**,
+        .opencode/**,
+      ]
+  - control_id: ADRB-CTX-002
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .github/copilot-instructions.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/agents/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-CTX-003
+    evidence_index: 0
+    required_any_terms: [CLAUDE.md, copilot instructions]
+  - control_id: ADRB-ENV-001
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-SPC-001
+    evidence_index: 0
+    patterns: [.kiro/specs/**, .cursor/plans/**, .codex/plans/**]
+  - control_id: ADRB-SPC-002
+    evidence_index: 0
+    files: [.kiro/specs/**, .cursor/plans/**, .codex/plans/**]
+  - control_id: ADRB-TOL-001
+    evidence_index: 0
+    patterns:
+      [
+        .claude/**,
+        .codex/**,
+        .cursor/**,
+        .opencode/**,
+        .github/copilot-instructions.md,
+        opencode.json,
+      ]
+  - control_id: ADRB-TOL-002
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-SEC-001
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-SEC-002
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-TST-002
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-GOV-001
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-GOV-002
+    evidence_index: 1
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-LRN-001
+    evidence_index: 0
+    patterns: [.claude/memory/**, .codex/memory/**, .cursor/memory/**, .opencode/memory/**]
+  - control_id: ADRB-LRN-002
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-OBS-001
+    evidence_index: 0
+    files: [.cursor/runs/README*, .codex/runs/README*, .claude/runs/README*]
+  - control_id: ADRB-OBS-002
+    evidence_index: 0
+    files: [.cursor/runs/README*, .codex/runs/README*, .claude/runs/README*]
+  - control_id: ADRB-RES-001
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]
+  - control_id: ADRB-RES-002
+    evidence_index: 0
+    files:
+      [
+        CLAUDE.md,
+        .claude/**/*.md,
+        .codex/**/*.md,
+        .cursor/agents/**/*.md,
+        .cursor/rules/**/*.md,
+        .cursor/skills/**/*.md,
+        .opencode/**/*.md,
+      ]

package/benchmark/v0.3/adapters/known-python-tooling.yaml

@@ -0,0 +1,18 @@
+id: known-python-tooling
+benchmark_version: 0.3.0
+extensions:
+  - control_id: ADRB-ENV-001
+    evidence_index: 0
+    files: [pyproject.toml]
+  - control_id: ADRB-ENV-001
+    evidence_index: 0
+    terms: [requires-python, uv sync, python]
+  - control_id: ADRB-TST-002
+    evidence_index: 0
+    files: [run_quality_checks.sh, scripts/**/quality*.sh, tox.ini, noxfile.py]
+  - control_id: ADRB-TST-002
+    evidence_index: 0
+    terms: [pytest, mypy, flake8, ruff, pyright, tox, nox]
+  - control_id: ADRB-TST-003
+    evidence_index: 0
+    terms: [pytest, mypy, flake8, ruff, pyright, tox, nox, pytest-cov]

package/benchmark/v0.3/adapters/known-security-tools.yaml

@@ -0,0 +1,6 @@
+id: known-security-tools
+benchmark_version: 0.3.0
+extensions:
+  - control_id: ADRB-SEC-003
+    evidence_index: 0
+    terms: [gitleaks, trufflehog]

package/benchmark/v0.3/agent-evidence-schema.json

@@ -0,0 +1,67 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://agentic-readiness.dev/schema/v0.3/agent-evidence.json",
+  "title": "ADRB v0.3 agent-collected evidence bundle",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["schema_version", "benchmark_version", "target", "collector", "claims"],
+  "properties": {
+    "schema_version": { "const": "0.3.0" },
+    "benchmark_version": { "const": "0.3.0" },
+    "target": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["repository", "git_head"],
+      "properties": {
+        "repository": { "type": "string", "minLength": 1 },
+        "git_head": { "type": "string", "minLength": 1 }
+      }
+    },
+    "collector": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["name", "version"],
+      "properties": {
+        "name": { "type": "string", "minLength": 1 },
+        "version": { "type": "string", "minLength": 1 }
+      }
+    },
+    "claims": {
+      "type": "object",
+      "propertyNames": { "pattern": "^ADRB-[A-Z]{3}-[0-9]{3}$" },
+      "additionalProperties": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["status", "scope", "summary", "references", "collected_at", "expires_at"],
+        "properties": {
+          "status": { "enum": ["met", "not_met", "unknown"] },
+          "scope": { "enum": ["repository", "platform", "organization", "outcome"] },
+          "summary": { "type": "string", "minLength": 1 },
+          "references": {
+            "type": "array",
+            "minItems": 1,
+            "items": { "type": "string", "minLength": 1 }
+          },
+          "collected_at": { "type": "string", "format": "date-time" },
+          "expires_at": { "type": "string", "format": "date-time" },
+          "error": { "type": ["string", "null"], "minLength": 1 }
+        },
+        "allOf": [
+          {
+            "if": { "properties": { "scope": { "const": "repository" } } },
+            "then": {
+              "properties": {
+                "references": {
+                  "items": {
+                    "type": "string",
+                    "pattern": "^repo:(?!/)(?!\\.{1,2}(?:/|#|$))(?!.*\\/\\.{1,2}(?:/|#|$))(?!.*\\\\)[^#]+(?:#L[1-9][0-9]*(?:-L?[1-9][0-9]*)?)?$"
+                  }
+                }
+              }
+            }
+          }
+        ]
+      }
+    }
+  }
+}