diff --git a/registry/capabilities/capability.infotech.issue-tracking.md b/registry/capabilities/capability.infotech.issue-tracking.md
index 1efc9e5..ee452b1 100644
--- a/registry/capabilities/capability.infotech.issue-tracking.md
+++ b/registry/capabilities/capability.infotech.issue-tracking.md
@@ -1,8 +1,7 @@
 ---
 id: capability.infotech.issue-tracking
-name: External Issue Tracker Connector
-summary: Backend-agnostic CLI/Python connector to Forgejo (and SQLite cache)
-  with work-record UUID ↔ external issue mapping. Not the fleet work origin.
+name: External issue tracker connector
+summary: CLI and Python adapters for external issue systems.
 owner: issue-core
 status: draft
 domain: infotech
@@ -10,6 +9,9 @@ tags:
 - issue-tracking
 - connector
 - work-record
+- security
+- netkingdom
+- framework-reuse
 maturity:
   discovery:
     current: D4
@@ -21,8 +23,10 @@ maturity:
     current: A2
     target: A3
     confidence: high
-    rationale: Python package + CLI (list/create/project/map) installable via pip;
-      mapping store shipped; MCP not yet available.
+    rationale: 'Source interface assessed 2026-10-14: CLI and Python adapters for
+      external issue systems. Availability describes the delivery form, not production
+      acceptance. Internal work originates in owner files; external projection is
+      optional.'
 external_evidence:
   completeness:
     level: C2
@@ -32,7 +36,8 @@ external_evidence:
     - Forgejo + local SQLite backends
     - CLI with JSON output; project/map commands
     - work_record_uuid optional on TaskSpec
-    - credential handling via env vars (FORGEJO_TOKEN preferred; GITEA_API_TOKEN deprecated alias; ISSUE_CORE_API_KEY)
+    - credential handling via env vars (FORGEJO_TOKEN preferred; GITEA_API_TOKEN deprecated
+      alias; ISSUE_CORE_API_KEY)
     broken_expectations: []
     out_of_scope_expectations:
     - Fleet task origin / intake promotion (work-record canon)
@@ -46,40 +51,60 @@ external_evidence:
     - no built-in issue locking beyond assignee+state
     - inward boundary sync not shipped
 discovery:
-  intent: Project and operate on external issue trackers with a stable link to
-    work-record UUIDs; never replace file-first work records as coordination substrate.
+  intent: CLI and Python adapters for external issue systems
   includes:
-  - unified Python API and CLI over Forgejo/SQLite issue operations
-  - work_record_issue_map store + project/map/push-status
-  - local offline cache and backend sync
-  - credential handling via environment variables
+  - CLI and Python adapters for external issue systems
   excludes:
-  - originating workplans/tasks/intake
-  - MCP server (planned)
-  - multi-agent fleet board semantics on Forgejo
+  - Internal work originates in owner files; external projection is optional
   assumptions: []
-  use_cases: []
+  use_cases:
+  - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and
+    verifies outcomes'
   research_memos: []
 availability:
   current_level: A2
   target_level: A3
   current_artifacts:
-  - Python package (`issue_core`)
-  - '`issue` CLI (including project/map)'
+  - README.md
   target_artifacts: []
   consumption_modes:
-  - cli
-  - library import
-  - rest (optional `[api]` extra)
+  - CLI
+  - source
 relations:
   depends_on: []
   supports: []
   related_to:
   - capability.activity.event-coordinate
+  - capability.security.iam-tooling-suite
 evidence:
   documentation:
-  - INTENT.md
-  - SCOPE.md
-  - CAPABILITY-issue-tracking.yaml
-  - docs/uuid-external-id-mapping.md
-  - docs/boundary-sync-and-status-mapping.md
+  - README.md
+consumer_guidance:
+  recommended_for:
+  - Maintainer observes posture, prioritizes findings, coordinates work and verifies
+    outcomes
+  not_recommended_for:
+  - Internal work originates in owner files; external projection is optional
+  known_limitations:
+  - Internal work originates in owner files; external projection is optional
+  - 2026-10-14 architecture review estimates operational maturity separately; a registry
+    entry does not authorize execution or establish deployment.
+---
+
+# External issue tracker connector
+
+CLI and Python adapters for external issue systems.
+
+## Reuse boundary
+
+Internal work originates in owner files; external projection is optional.
+
+## Supported use cases
+
+- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes
+
+## Evidence and integration
+
+- [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 7be3fce..682f056 100644
--- a/registry/indexes/capabilities.yaml
+++ b/registry/indexes/capabilities.yaml
@@ -1,20 +1,22 @@
 version: 1
-updated: '2026-07-07'
+updated: '2026-10-14'
 domain: helix_forge
 capabilities:
 - id: capability.infotech.issue-tracking
-  name: Universal Issue Tracking Coordination
-  summary: Unified Python/CLI interface for issue tracking across Forgejo, GitHub, and GitLab, preventing
-    direct platform API usage and credential sprawl for coordinating agents.
-  vector: D4 / A2 / C2 / R1
+  name: External issue tracker connector
+  summary: CLI and Python adapters for external issue systems.
   domain: infotech
   status: draft
   owner: issue-core
-  path: registry/capabilities/capability.infotech.issue-tracking.md
   tags:
   - issue-tracking
-  - coordination
-  - multi-platform
+  - connector
+  - work-record
+  - security
+  - netkingdom
+  - framework-reuse
+  vector: D4 / A2 / C2 / R1
+  path: registry/capabilities/capability.infotech.issue-tracking.md
   consumption_modes:
-  - cli
-  - library import
+  - CLI
+  - source