Files
info-tech-canon/registry/capabilities/capability.infotech.canon-service.md
tegwick 2ff7a7c234 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>
2026-07-06 19:03:43 +02:00

3.9 KiB

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

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

  • 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