Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 1)

Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

registry/capabilities/capability.communication.infospace-workspace.md

@@ -0,0 +1,124 @@
+---
+id: capability.communication.infospace-workspace
+name: Infospace Workspace And Evaluation Bench
+summary: Workspace and service for creating, developing, evaluating, and inspecting structured knowledge
+  spaces (infospaces); application-layer successor to the infospace work begun in markitect-main.
+owner: infospace-bench
+status: draft
+domain: communication
+tags:
+- infospace
+- knowledge
+- evaluation
+maturity:
+  discovery:
+    current: D3
+    target: D5
+    confidence: medium
+    rationale: INTENT.md, wiki/ProductRequirementsDocument.md, wiki/FunctionalRequirementsSpecification.md,
+      SCOPE.md, and multiple docs/ (layout, evaluation-and-inspection, markitect-main-scope-assessment,
+      entity-relation-model, workflow-generation-pipeline, kontextual-engine-boundary) describe scope
+      and boundaries in real detail.
+  availability:
+    current: A1
+    target: A3
+    confidence: medium
+    rationale: Python CLI/workspace, runnable locally via pip-install; consumed today by info-tech-canon
+      for artifact loading/checks/graph summaries.
+external_evidence:
+  completeness:
+    level: C2
+    confidence: low
+    basis: scope_vs_intent_and_consumer_expectations
+    satisfied_expectations:
+    - infospace lifecycle (create/develop/evaluate/inspect)
+    - already consumed by a sibling repo (info-tech-canon)
+    - explicit boundary docs vs markitect-main and kontextual-engine
+    broken_expectations: []
+    out_of_scope_expectations: []
+  reliability:
+    level: R1
+    confidence: low
+    basis: consumer_quality_signals
+    known_reliability_risks:
+    - evaluation/metrics history documented but not independently verified by external consumers yet
+discovery:
+  intent: Own the concrete infospace lifecycle (creation, development, evaluation, inspection) as the
+    application-layer successor to markitect-main's infospace work.
+  includes:
+  - infospace creation/development/evaluation/inspection workspace and CLI
+  - entity-relation modelling
+  - evaluation history and metrics
+  excludes:
+  - markdown tooling and runtime orchestration (remain in markitect-tool/markitect-main)
+  - context engine internals (kontextual-engine)
+  assumptions: []
+  use_cases: []
+  research_memos: []
+availability:
+  current_level: A1
+  target_level: A3
+  current_artifacts:
+  - Python package/CLI (`infospace-bench`)
+  target_artifacts: []
+  consumption_modes:
+  - cli
+  - library import (consumed by info-tech-canon)
+relations:
+  depends_on: []
+  supports: []
+  related_to: []
+evidence:
+  documentation:
+  - INTENT.md
+  - wiki/ProductRequirementsDocument.md
+  - docs/evaluation-and-inspection.md
+  tests:
+  - tests/
+  consumer_feedback: []
+  bug_reports: []
+  incidents: []
+consumer_guidance:
+  recommended_for:
+  - consumers building or evaluating structured knowledge spaces, or building on top like info-tech-canon
+  not_recommended_for:
+  - needs for markdown-syntax tooling itself (see markitect-tool)
+  known_limitations:
+  - application-layer successor still consolidating scope inherited from markitect-main
+promotion_history: []
+---
+
+# Infospace Workspace And Evaluation Bench
+
+## Overview
+
+`infospace-bench` is the application-layer workspace and service for creating, developing, evaluating, and inspecting structured knowledge spaces (infospaces), continuing work that began inside `markitect-main`. It is already consumed by `info-tech-canon` for artifact loading, checks, and graph summaries.
+
+## Assessment notes
+
+### Discovery
+
+INTENT.md, wiki/ProductRequirementsDocument.md, wiki/FunctionalRequirementsSpecification.md, SCOPE.md, and multiple docs/ (layout, evaluation-and-inspection, markitect-main-scope-assessment, entity-relation-model, workflow-generation-pipeline, kontextual-engine-boundary) describe scope and boundaries in real detail.
+
+### Availability
+
+Python CLI/workspace, runnable locally via pip-install; consumed today by info-tech-canon for artifact loading/checks/graph summaries.
+
+### Completeness
+
+First-pass honest assessment from the REUSE-WP-0017 coverage campaign
+(reuse-surface). No external consumer feedback exists yet; levels reflect
+scope-vs-intent documentation quality, not internal code quality.
+
+### Reliability
+
+No production consumer telemetry exists yet; reliability level is
+intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
+
+## Promotion checklist
+
+- [x] ID follows `capability.<domain>.<name>` pattern
+- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
+- [x] `external_evidence` is populated separately from `maturity`
+- [ ] Relations reference valid capability IDs (none yet)
+- [x] Index entry added in `registry/indexes/capabilities.yaml`

registry/indexes/capabilities.yaml

@@ -1,4 +1,20 @@
 version: 1
-updated: '2026-06-16'
+updated: '2026-07-06'
 domain: helix_forge
-capabilities: []
+capabilities:
+- id: capability.communication.infospace-workspace
+  name: Infospace Workspace And Evaluation Bench
+  summary: Workspace and service for creating, developing, evaluating, and inspecting structured knowledge
+    spaces (infospaces); application-layer successor to the infospace work begun in markitect-main.
+  vector: D3 / A1 / C2 / R1
+  domain: communication
+  status: draft
+  owner: infospace-bench
+  path: registry/capabilities/capability.communication.infospace-workspace.md
+  tags:
+  - infospace
+  - knowledge
+  - evaluation
+  consumption_modes:
+  - cli
+  - library import (consumed by info-tech-canon)