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

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.communication.infospace-workspace	Infospace Workspace And Evaluation Bench	Workspace and service for creating, developing, evaluating, and inspecting structured knowledge spaces (infospaces); application-layer successor to the infospace work begun in markitect-main.	infospace-bench	draft	communication	infospace knowledge evaluation	discovery availability current target confidence rationale D3 D5 medium 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. current target confidence rationale A1 A3 medium Python CLI/workspace, runnable locally via pip-install; consumed today by info-tech-canon for artifact loading/checks/graph summaries.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_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 level confidence basis known_reliability_risks R1 low consumer_quality_signals evaluation/metrics history documented but not independently verified by external consumers yet	intent includes excludes assumptions use_cases research_memos Own the concrete infospace lifecycle (creation, development, evaluation, inspection) as the application-layer successor to markitect-main's infospace work. infospace creation/development/evaluation/inspection workspace and CLI entity-relation modelling evaluation history and metrics markdown tooling and runtime orchestration (remain in markitect-tool/markitect-main) context engine internals (kontextual-engine)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Python package/CLI (`infospace-bench`) cli library import (consumed by info-tech-canon)	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents INTENT.md wiki/ProductRequirementsDocument.md docs/evaluation-and-inspection.md tests/	recommended_for not_recommended_for known_limitations consumers building or evaluating structured knowledge spaces, or building on top like info-tech-canon needs for markdown-syntax tooling itself (see markitect-tool) application-layer successor still consolidating scope inherited from markitect-main

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

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml