Skip to content
rd-skills
Documentation

Assurance

Scorecard

This handwritten table defines release expectations. It is not generated

docs/SCORECARD.md

This handwritten table defines release expectations. It is not generated status and not a current-tree pass report. Current status comes only from fresh producer output and the generated or captured artifacts indexed in Reports.

DimensionRequired evidenceRelease expectation
Registriesfour registry validators1 Control, 25 Professional, 150 Foundation, and 13 Domain Skills: 189 total and 188 non-Control
Runtime and Agent Profilesbuild, Profile, and prompt validatorsone Runtime with 26 top-level Skills, exactly four bounded Agent Profiles, and one authoritative control prompt
Contractstask-contract validatorMarkdown Direct Task, Engineering Brief, Task DAG, and Review Handoff
Routingdeterministic routing evaluatorone primary Professional Skill per task; 233 canonical entries and 62 capability entries; 429 admissions are 105 Professional, 276 Foundation, and 48 Domain; the Foundation projection covers 141 unique Foundation Skills in the 163-entry Layer 3 catalog
Capability coverage125-entry matrix and deterministic coverage validators125 entries classify as 81 covered, 39 partial, 0 missing, and 5 intentionally unsupported; covered is catalog/routing evidence, not Professional Completeness
Contentlink, size, audit, readability, and professionalism checksno broken references, release-blocking readability disposition, or unresolved professional defect
Testsfull unit suiteall applicable tests pass on the final material edit
Code generationdefinition and harness validationchecked-in harnesses run and assertions reject incomplete starters
Buildfixed Runtime plus temporary Layer 3 completeness validator26/154/9 top-level/targeted/routing-only delivery; 163 Foundation/Domain sources remain complete; no Layer 3 top-level or packaged surface
Installationsimulated installation validator and doctorexpected host-specific Skills/Profiles and no obsolete managed residue

Record producer command, source commit or diff state, freshness, skipped checks, and proof limits in the release handoff. Any skipped check, stale report, or partial suite is explicit unverified scope. Do not convert this expectations table into a manual green status.

The scorecard cannot prove real-host Profile startup, wall-clock performance, production accuracy, provider behavior, or installed user experience. See Validation, Benchmarks, and Release.