Align ops-hub activity-core contract vocabulary

docs/research/ops-hub-evidence-intake-current-state.md

@@ -1,6 +1,7 @@
 # Ops Hub Evidence Intake - Current State
 
 Date: 2026-06-15
+Updated: 2026-06-27
 
 Workplan: `IHUB-WP-0022`
 
@@ -17,6 +18,26 @@ slice is therefore contract-first:
 - wait on live ops-hub manifest/widgets, key provisioning, and production
   smoke before enabling per-entity Inter-Hub submission.
 
+
+## 2026-06-27 Live Vocabulary Alignment
+
+Public production probes now show an `ops-hub` row and public registry
+vocabulary on `https://hub.coulomb.social`. The live ops-hub seed vocabulary
+supersedes the early activity-core proposal for several names:
+
+| Early proposal | Live target |
+| --- | --- |
+| `ops-service-observed` | `ops-service-discovered` |
+| `ops-inventory-drift` | `ops-drift-detected` |
+| `ops-access-path-checked` | Deferred; no live access-path event or widget type |
+| `ops-evidence` policy scope | Use declared scopes such as `ops-production`, `ops-registry`, or `ops-backup-retention` |
+| card-style widget types | Use live widget types such as `ops-service`, `ops-endpoint`, `ops-backup-set`, `ops-readiness-gate`, and `ops-risk` |
+
+The contract docs have been revised to target the live seed vocabulary and to
+keep access-path evidence on the State Hub fallback path until ops-hub either
+adds access-path vocabulary or records an explicit readiness/risk mapping
+decision.
+
 ## Inter-Hub API Surface
 
 The current repo supports the necessary primitives through `/api/v2`.
@@ -119,30 +140,39 @@ Known gates before per-entity Inter-Hub submission can be treated as live:
 
 ## Recommended Manifest Vocabulary
 
-Use one policy scope for the first slice:
+Use the live ops-hub manifest vocabulary rather than the early proposal names.
+The current target is:
 
-- `ops-evidence`
+Policy scopes:
 
-Use one annotation category:
+- `ops-local`
+- `ops-transitional-prod`
+- `ops-production`
+- `ops-threephoenix`
+- `ops-registry`
+- `ops-secrets`
+- `ops-backup-retention`
 
-- `ops-risk`
+Widget types for activity-core evidence:
 
-Use these widget types unless the operator prefers to keep a smaller aggregate
-surface:
+- `ops-service-catalog`
+- `ops-service`
+- `ops-endpoint`
+- `ops-backup-set`
+- `ops-readiness-gate`
+- `ops-risk` when risk-specific drift representation is needed
 
-- `ops-service-card`
-- `ops-endpoint-card`
-- `ops-access-path-card`
-- `ops-backup-card`
-- `ops-drift-card`
+Event types for the first Inter-Hub activity-core slice:
 
-Use the activity-core event types exactly as published:
-
-- `ops-service-observed`
+- `ops-service-discovered`
 - `ops-endpoint-verified`
-- `ops-access-path-checked`
-- `ops-backup-verified`
-- `ops-inventory-drift`
+- `ops-backup-verified` after a backup-set widget exists
+- `ops-drift-detected`
+
+Keep `ops-access-path-checked` deferred until ops-hub declares access-path
+vocabulary or a separate decision maps those checks to readiness/risk events.
+Do not seed the old `ops-evidence` policy scope unless the manifest is
+explicitly expanded to include it.
 
 ## Open Questions