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>
This commit is contained in:
2026-07-06 19:03:43 +02:00
parent 922e7322cf
commit 2ff7a7c234
2 changed files with 139 additions and 2 deletions

View File

@@ -0,0 +1,120 @@
---
id: capability.infotech.canon-service
name: InfoTechCanon Service Surface
summary: Concrete service surface (CLI, importable functions, read-only local HTTP API) over the InfoTechCanon
information-processing infospace, backed by infospace-bench.
owner: info-tech-canon
status: draft
domain: infotech
tags:
- canon
- infospace
- service
maturity:
discovery:
current: D2
target: D4
confidence: medium
rationale: README documents a working CLI surface (inspect, artifacts, models, standards, review-kit,
alignment-template, validate, graph) over one concrete infospace under infospace/.
availability:
current: A2
target: A3
confidence: medium
rationale: Runnable today via `PYTHONPATH=src python3 -m info_tech_canon ...`; includes a read-only
local HTTP API in addition to the CLI.
external_evidence:
completeness:
level: C1
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- CLI commands for inspect/artifacts/models/standards/review-kit/alignment-template/validate/graph
- read-only local HTTP API
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- depends on infospace-bench for artifact loading/checks/graph summaries; only one concrete infospace
implemented so far
discovery:
intent: Provide a small, concrete service surface over one InfoTechCanon infospace so the canon corpus
is usable via CLI, importable functions, or a read-only API, not just documentation.
includes:
- JSON-first CLI over the infospace
- importable Python service functions
- read-only local HTTP API
excludes:
- the underlying infospace-bench workspace/evaluation tooling itself (separate capability)
assumptions: []
use_cases: []
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- Python package (`info_tech_canon`)
target_artifacts: []
consumption_modes:
- cli
- library import
- http api (read-only, local)
relations:
depends_on: []
supports: []
related_to: []
evidence:
documentation:
- README.md
tests:
- tests/
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- consumers wanting programmatic or CLI access to the InfoTechCanon infospace
not_recommended_for:
- needs requiring a writable or hosted API
known_limitations:
- only one concrete infospace implemented under infospace/ so far
promotion_history: []
---
# InfoTechCanon Service Surface
## Overview
`info-tech-canon` implements a concrete service surface over one InfoTechCanon infospace: a JSON-first CLI, importable Python functions, and a read-only local HTTP API, backed by artifact loading and graph summaries from `infospace-bench`.
## Assessment notes
### Discovery
README documents a working CLI surface (inspect, artifacts, models, standards, review-kit, alignment-template, validate, graph) over one concrete infospace under infospace/.
### Availability
Runnable today via `PYTHONPATH=src python3 -m info_tech_canon ...`; includes a read-only local HTTP API in addition to the CLI.
### 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`

View File

@@ -1,4 +1,21 @@
version: 1 version: 1
updated: '2026-06-16' updated: '2026-07-06'
domain: helix_forge domain: helix_forge
capabilities: [] capabilities:
- id: capability.infotech.canon-service
name: InfoTechCanon Service Surface
summary: Concrete service surface (CLI, importable functions, read-only local HTTP API) over the InfoTechCanon
information-processing infospace, backed by infospace-bench.
vector: D2 / A2 / C1 / R0
domain: infotech
status: draft
owner: info-tech-canon
path: registry/capabilities/capability.infotech.canon-service.md
tags:
- canon
- infospace
- service
consumption_modes:
- cli
- library import
- http api (read-only, local)