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:
codex 2026-10-14 06:43:58 +02:00
parent ffb9e272ce
commit 33b840faac
2 changed files with 109 additions and 0 deletions

View file

@ -0,0 +1,91 @@
---
id: capability.railiance.substrate-bindings
owner: reef-railiance
status: draft
domain: infotech
maturity:
discovery:
current: D3
target: D5
confidence: medium
rationale: Owner scope, neighboring responsibilities, concrete use cases and limitations
are documented; no exhaustive or generalized maturity claim.
availability:
current: A0
target: A0
confidence: medium
rationale: 'Source interface assessed 2026-10-14: Grouped home-reef identity,
topology and placement declarations. Availability describes the delivery form,
not production acceptance. Declarations are not automatic placement or authorization.'
external_evidence:
completeness:
level: C1
confidence: low
basis: Source artifacts establish a bounded capability; no independent consumer-completeness
assessment in this review.
reliability:
level: R0
confidence: low
basis: No longitudinal consumer reliability measurement established by this review.
name: Substrate topology and bindings
summary: Grouped home-reef identity, topology and placement declarations.
tags:
- security
- netkingdom
- framework-reuse
discovery:
intent: Grouped home-reef identity, topology and placement declarations
includes:
- Grouped home-reef identity, topology and placement declarations
excludes:
- Declarations are not automatic placement or authorization
use_cases:
- 'U13: Platform owner deploys and rolls back a workload with explicit substrate
and custody bindings'
- 'U14: Framework adopter validates and reuses selected contracts, tools and reference
compositions'
availability:
current_level: A0
target_level: A0
current_artifacts:
- SCOPE.md
consumption_modes:
- informational
relations:
related_to:
- capability.security.iam-tooling-suite
evidence:
documentation:
- SCOPE.md
consumer_guidance:
recommended_for:
- Platform owner deploys and rolls back a workload with explicit substrate and custody
bindings
- Framework adopter validates and reuses selected contracts, tools and reference
compositions
not_recommended_for:
- Declarations are not automatic placement or authorization
known_limitations:
- Declarations are not automatic placement or authorization
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
---
# Substrate topology and bindings
Grouped home-reef identity, topology and placement declarations.
## Reuse boundary
Declarations are not automatic placement or authorization.
## Supported use cases
- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions
## Evidence and integration
- [SCOPE.md](../../SCOPE.md)
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.

View file

@ -0,0 +1,18 @@
version: 1
domain: infotech
capabilities:
- id: capability.railiance.substrate-bindings
name: Substrate topology and bindings
summary: Grouped home-reef identity, topology and placement declarations.
domain: infotech
status: draft
owner: reef-railiance
tags:
- security
- netkingdom
- framework-reuse
vector: D3 / A0 / C1 / R0
path: registry/capabilities/capability.railiance.substrate-bindings.md
consumption_modes:
- informational
updated: '2026-10-14'