docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
This commit is contained in:
parent
3d206a56f4
commit
9b9be2ec8e
2 changed files with 70 additions and 65 deletions
|
|
@ -1,8 +1,7 @@
|
|||
---
|
||||
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.
|
||||
name: Shared semantic contracts and validation
|
||||
summary: Markdown canon with library, CLI and read-only API.
|
||||
owner: info-tech-canon
|
||||
status: draft
|
||||
domain: infotech
|
||||
|
|
@ -10,19 +9,24 @@ tags:
|
|||
- canon
|
||||
- infospace
|
||||
- service
|
||||
- security
|
||||
- netkingdom
|
||||
- framework-reuse
|
||||
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/.
|
||||
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
|
||||
current: A4
|
||||
target: A4
|
||||
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.
|
||||
rationale: 'Source interface assessed 2026-10-14: Markdown canon with library,
|
||||
CLI and read-only API. Availability describes the delivery form, not production
|
||||
acceptance. Mixed seed/candidate maturity; validation is not owner runtime conformance.'
|
||||
external_evidence:
|
||||
completeness:
|
||||
level: C1
|
||||
|
|
@ -38,37 +42,39 @@ external_evidence:
|
|||
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
|
||||
- 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.
|
||||
intent: Markdown canon with library, CLI and read-only API
|
||||
includes:
|
||||
- JSON-first CLI over the infospace
|
||||
- importable Python service functions
|
||||
- read-only local HTTP API
|
||||
- Markdown canon with library, CLI and read-only API
|
||||
excludes:
|
||||
- the underlying infospace-bench workspace/evaluation tooling itself (separate capability)
|
||||
- Mixed seed/candidate maturity; validation is not owner runtime conformance
|
||||
assumptions: []
|
||||
use_cases: []
|
||||
use_cases:
|
||||
- 'U01: Architect composes a security deployment from explicit owner contracts and
|
||||
case types'
|
||||
- 'U08: Consumer emits security events and reconciles independently retained evidence'
|
||||
- 'U14: Framework adopter validates and reuses selected contracts, tools and reference
|
||||
compositions'
|
||||
research_memos: []
|
||||
availability:
|
||||
current_level: A2
|
||||
target_level: A3
|
||||
current_level: A4
|
||||
target_level: A4
|
||||
current_artifacts:
|
||||
- Python package (`info_tech_canon`)
|
||||
- SCOPE.md
|
||||
target_artifacts: []
|
||||
consumption_modes:
|
||||
- cli
|
||||
- library import
|
||||
- http api (read-only, local)
|
||||
- HTTP API
|
||||
- source
|
||||
relations:
|
||||
depends_on: []
|
||||
supports: []
|
||||
related_to: []
|
||||
related_to:
|
||||
- capability.security.iam-tooling-suite
|
||||
evidence:
|
||||
documentation:
|
||||
- README.md
|
||||
- SCOPE.md
|
||||
tests:
|
||||
- tests/
|
||||
consumer_feedback: []
|
||||
|
|
@ -76,45 +82,43 @@ evidence:
|
|||
incidents: []
|
||||
consumer_guidance:
|
||||
recommended_for:
|
||||
- consumers wanting programmatic or CLI access to the InfoTechCanon infospace
|
||||
- Architect composes a security deployment from explicit owner contracts and case
|
||||
types
|
||||
- Consumer emits security events and reconciles independently retained evidence
|
||||
- Framework adopter validates and reuses selected contracts, tools and reference
|
||||
compositions
|
||||
not_recommended_for:
|
||||
- needs requiring a writable or hosted API
|
||||
- Mixed seed/candidate maturity; validation is not owner runtime conformance
|
||||
known_limitations:
|
||||
- only one concrete infospace implemented under infospace/ so far
|
||||
promotion_history: []
|
||||
- Mixed seed/candidate maturity; validation is not owner runtime conformance
|
||||
- 2026-10-14 architecture review estimates operational maturity separately; a registry
|
||||
entry does not authorize execution or establish deployment.
|
||||
promotion_history:
|
||||
- date: '2026-10-14'
|
||||
dimension: availability
|
||||
from: A2
|
||||
to: A4
|
||||
rationale: Interface-form reassessment from current owner sources; no completeness/reliability
|
||||
promotion.
|
||||
author: codex
|
||||
---
|
||||
|
||||
# InfoTechCanon Service Surface
|
||||
# Shared semantic contracts and validation
|
||||
|
||||
## Overview
|
||||
Markdown canon with library, CLI and read-only API.
|
||||
|
||||
`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`.
|
||||
## Reuse boundary
|
||||
|
||||
## Assessment notes
|
||||
Mixed seed/candidate maturity; validation is not owner runtime conformance.
|
||||
|
||||
### Discovery
|
||||
## Supported use cases
|
||||
|
||||
README documents a working CLI surface (inspect, artifacts, models, standards, review-kit, alignment-template, validate, graph) over one concrete infospace under infospace/.
|
||||
- U01: Architect composes a security deployment from explicit owner contracts and case types
|
||||
- U08: Consumer emits security events and reconciles independently retained evidence
|
||||
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions
|
||||
|
||||
### Availability
|
||||
## Evidence and integration
|
||||
|
||||
Runnable today via `PYTHONPATH=src python3 -m info_tech_canon ...`; includes a read-only local HTTP API in addition to the CLI.
|
||||
- [SCOPE.md](../../SCOPE.md)
|
||||
|
||||
### 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`
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,21 +1,22 @@
|
|||
version: 1
|
||||
updated: '2026-07-06'
|
||||
updated: '2026-10-14'
|
||||
domain: helix_forge
|
||||
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
|
||||
name: Shared semantic contracts and validation
|
||||
summary: Markdown canon with library, CLI and read-only API.
|
||||
domain: infotech
|
||||
status: draft
|
||||
owner: info-tech-canon
|
||||
path: registry/capabilities/capability.infotech.canon-service.md
|
||||
tags:
|
||||
- canon
|
||||
- infospace
|
||||
- service
|
||||
- security
|
||||
- netkingdom
|
||||
- framework-reuse
|
||||
vector: D2 / A4 / C1 / R0
|
||||
path: registry/capabilities/capability.infotech.canon-service.md
|
||||
consumption_modes:
|
||||
- cli
|
||||
- library import
|
||||
- http api (read-only, local)
|
||||
- HTTP API
|
||||
- source
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue