Publish incumbent-comparison scorecards (schema + pointer + validator)

.github/workflows/validate-scorecards.yml

@@ -0,0 +1,22 @@
+name: Validate scorecards
+
+# Published scorecards are a read-only contract for downstream consumers
+# (e.g. the calibration-diagnostics dashboard). This gate runs the stdlib
+# validator on every change so a malformed or internally-inconsistent
+# scorecard or pointer cannot land on main.
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - name: Validate scorecards and pointers
+        run: python tools/validate_scorecard.py

README.md

@@ -23,6 +23,7 @@ historical candidate scorecards, and audit-only scripts belong here.
 | Area | Path | Purpose |
 | --- | --- | --- |
 | US incumbent comparison | `benchmarks/us/incumbent-comparison/` | Compare candidate Populace-US artifacts with the certified production incumbent on the frozen target surface. |
+| Published scorecards | `archive/us/<build-id>/scorecard.json` + `benchmarks/us/incumbent-comparison/latest.json` | Machine-readable head-to-head results (schema + `latest.json` pointer) consumed by downstream dashboards. |
 | Historical archives | `archive/` | Small scorecards and run notes that document past candidate decisions. Large HDF5 artifacts stay in object storage or the local artifact cache. |
 
 ## Promotion Rule