chore(directives): S33-A — verascore schema alignment + A2A#1631 reply

decisions/2026-05-18-CEO-directive-S33-A-verascore-schema-alignment.md

@@ -0,0 +1,73 @@
+# CEO Standing Directive S33-A — Verascore Schema Alignment + A2A#1631 Reply
+
+**Issued:** 2026-05-18
+**Slug:** `s33-a-verascore-schema-alignment`
+**Target:** Builder
+**Auto-archive:** When conformance result posted to A2A#1631 (mark EXECUTED in run log)
+
+---
+
+## Context
+
+In A2A#1631 (a2aproject/A2A), eriknewton (Verascore) shipped `verascore-evidence-schema-v0.1` on 2026-05-17 with six named evidence-class conformance fixtures including `dominion_telemetry`. He explicitly invited the Observatory to validate its `/api/trust` output against the specimen shape and post the replace-with-production-signed-envelope result.
+
+The Observatory already has a named slot in the schema. This is not outreach — it is a short validation task that closes the loop eriknewton opened.
+
+vdineshk's last comment in A2A#1631 was 4 days ago (2026-05-14) and is unanswered by eriknewton's 2026-05-17 update. No reply should be posted until the validation is complete and the result is in hand.
+
+---
+
+## What Builder must do (one-time, next available run)
+
+### Step 1 — Fetch the schema
+
+```
+GET https://verascore.ai/schemas/verascore-evidence-schema-v0.1.json
+```
+
+Save the schema. Also fetch the conformance fixtures doc:
+```
+GET https://verascore.ai/docs/evidence-schema-v0.1
+```
+
+Focus on the `dominion_telemetry` evidence class definition specifically.
+
+### Step 2 — Fetch a live Observatory trust response
+
+```
+GET https://dominion-observatory.sgdata.workers.dev/api/trust?url=https://sg-cpf-calculator-mcp.sgdata.workers.dev
+```
+
+(Use any tracked server URL — the field shape is what matters, not the specific server.)
+
+### Step 3 — Diff and note mismatches
+
+Map the Observatory `/api/trust` response fields against the `dominion_telemetry` specimen shape in the schema. Note:
+- Fields that map cleanly (no change needed)
+- Fields that need renaming or restructuring
+- Required fields in the schema that the Observatory doesn't currently emit
+- Observatory fields with no schema equivalent (flag as extensions)
+
+Document the result at: `fixtures/verascore-dominion-telemetry-conformance.md`
+
+### Step 4 — Post in A2A#1631
+
+Post the following comment in a2aproject/A2A#1631 (use WebFetch or note the result for Strategist to post if GitHub access is restricted):
+
+> @eriknewton — validated `/api/trust` output against `dominion_telemetry` in verascore-evidence-schema-v0.1. [Summary of clean mappings / mismatches / any proposed field additions]. Conformance fixture at [link to fixtures/verascore-dominion-telemetry-conformance.md in repo or paste inline]. Happy to coordinate on the specimen payload before the multi-class fixture publishes.
+
+Keep it short — one paragraph. Do not re-introduce the Observatory. The thread already knows who vdineshk is.
+
+---
+
+## Constraints
+
+- **C2 compliant:** This is a technical reply to an explicit technical invitation, not a sales motion. No human procurement path.
+- **P-021D:** This is not content investment. It is closing a loop on an existing distribution surface that named the Observatory unprompted.
+- **Builder moratorium:** If the builder moratorium is still active, this task is explicitly authorized under S33-A (same override logic as S32-A for x402 Foundation). The work class is schema-validation + a single technical comment, not a new primitive ship.
+
+---
+
+## Priority
+
+Low-medium. This does not block PRIMARY KPI (M2 external agent_id). Do not delay x402 spec v0.2 drafting or LF submission monitoring for this. Run it as a secondary task in the same run if token budget allows, or dedicate a short run to it within 7 days.