diff --git a/registry/capabilities/capability.activity.event-coordinate.md b/registry/capabilities/capability.activity.event-coordinate.md
index fd0037a..0aa462d 100644
--- a/registry/capabilities/capability.activity.event-coordinate.md
+++ b/registry/capabilities/capability.activity.event-coordinate.md
@@ -1,12 +1,18 @@
 ---
 id: capability.activity.event-coordinate
-name: Organizational Event Coordination
-summary: Coordinate structured responses to cross-domain events through activity workflows and automation.
+name: Durable automation and bounded operations
+summary: Temporal/NATS/webhook/manual trigger, validated definitions and evidence/runtime
+  sinks.
 owner: activity-core
 status: draft
 domain: helix_forge
-tags: [activity, coordination, automation]
-
+tags:
+- activity
+- coordination
+- automation
+- security
+- netkingdom
+- framework-reuse
 maturity:
   discovery:
     current: D3
@@ -14,11 +20,13 @@ maturity:
     confidence: medium
     rationale: activity-core INTENT defines org-wide event response boundary.
   availability:
-    current: A1
+    current: A4
     target: A4
     confidence: low
-    rationale: Conceptual workflows exist; consumable API surface still emerging.
-
+    rationale: 'Source interface assessed 2026-10-14: Temporal/NATS/webhook/manual
+      trigger, validated definitions and evidence/runtime sinks. Availability describes
+      the delivery form, not production acceptance. Not a general shell executor;
+      first unassisted security-flow cadence acceptance remains open.'
 external_evidence:
   completeness:
     level: C1
@@ -26,52 +34,89 @@ external_evidence:
     confidence: low
     basis: scope_vs_intent_and_consumer_expectations
     satisfied_expectations:
-      - problem and boundary documented in INTENT
+    - problem and boundary documented in INTENT
     broken_expectations:
-      - no registry-native automation artifacts indexed yet
+    - no registry-native automation artifacts indexed yet
     out_of_scope_expectations:
-      - owning domain-specific business logic
+    - owning domain-specific business logic
   reliability:
     level: R0
     confidence: low
     basis: consumer_quality_signals
     known_reliability_risks: []
-
 discovery:
-  intent: >
-    Give the organization a structural home for responding to events across repos
-    and domains in an auditable, automation-ready way.
+  intent: Temporal/NATS/webhook/manual trigger, validated definitions and evidence/runtime
+    sinks
   includes:
-    - event-triggered coordination
-    - cross-domain maintenance workflows
+  - Temporal/NATS/webhook/manual trigger, validated definitions and evidence/runtime
+    sinks
   excludes:
-    - single-repo cron replacements only
-  use_cases: []
-
+  - Not a general shell executor; first unassisted security-flow cadence acceptance
+    remains open
+  use_cases:
+  - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and
+    verifies outcomes'
+  - 'U12: Developer builds and publishes through controlled source, dependency and
+    runner paths'
 availability:
-  current_level: A1
+  current_level: A4
   target_level: A4
   current_artifacts:
-    - activity-core/INTENT.md
+  - SCOPE.md
+  - README.md
   consumption_modes:
-    - informational
-
+  - HTTP API
+  - source
 relations:
   depends_on: []
   related_to:
-    - capability.statehub.workstream-coordinate
-    - capability.audit.event-retain
-
+  - capability.statehub.workstream-coordinate
+  - capability.audit.event-retain
+  - capability.security.iam-tooling-suite
 consumer_guidance:
   recommended_for:
-    - planning org-wide event response patterns
+  - Maintainer observes posture, prioritizes findings, coordinates work and verifies
+    outcomes
+  - Developer builds and publishes through controlled source, dependency and runner
+    paths
   not_recommended_for:
-    - assuming production automation is available
+  - Not a general shell executor; first unassisted security-flow cadence acceptance
+    remains open
   known_limitations:
-    - early discovery stage
+  - Not a general shell executor; first unassisted security-flow cadence acceptance
+    remains open
+  - 2026-10-14 architecture review estimates operational maturity separately; a registry
+    entry does not authorize execution or establish deployment.
+promotion_history:
+- date: '2026-10-14'
+  dimension: availability
+  from: A1
+  to: A4
+  rationale: Interface-form reassessment from current owner sources; no completeness/reliability
+    promotion.
+  author: codex
+evidence:
+  documentation:
+  - SCOPE.md
+  - README.md
 ---
 
-# Organizational Event Coordination
+# Durable automation and bounded operations
 
-activity-core coordinates how the org responds to events—not the domain logic
-inside each repo.
\ No newline at end of file
+Temporal/NATS/webhook/manual trigger, validated definitions and evidence/runtime sinks.
+
+## Reuse boundary
+
+Not a general shell executor; first unassisted security-flow cadence acceptance remains open.
+
+## Supported use cases
+
+- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes
+- U12: Developer builds and publishes through controlled source, dependency and runner paths
+
+## Evidence and integration
+
+- [SCOPE.md](../../SCOPE.md)
+- [README.md](../../README.md)
+
+Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.
diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml
index ded089e..4c54976 100644
--- a/registry/indexes/capabilities.yaml
+++ b/registry/indexes/capabilities.yaml
@@ -1,19 +1,23 @@
 version: 1
-updated: '2026-06-16'
+updated: '2026-10-14'
 domain: helix_forge
 capabilities:
 - id: capability.activity.event-coordinate
-  name: Organizational Event Coordination
-  summary: Coordinate structured responses to cross-domain events through activity
-    workflows and automation.
-  vector: D3 / A1 / C1 / R0
+  name: Durable automation and bounded operations
+  summary: Temporal/NATS/webhook/manual trigger, validated definitions and evidence/runtime
+    sinks.
   domain: helix_forge
   status: draft
   owner: activity-core
-  path: registry/capabilities/capability.activity.event-coordinate.md
   tags:
   - activity
   - coordination
   - automation
+  - security
+  - netkingdom
+  - framework-reuse
+  vector: D3 / A4 / C1 / R0
+  path: registry/capabilities/capability.activity.event-coordinate.md
   consumption_modes:
-  - informational
+  - HTTP API
+  - source