diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/key-cape/registry/capabilities/capability.iam.key-cape.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/key-cape/registry/capabilities/capability.iam.key-cape.md new file mode 100644 index 00000000..59cc40e2 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/key-cape/registry/capabilities/capability.iam.key-cape.md @@ -0,0 +1,138 @@ +--- +id: capability.iam.key-cape +name: OIDC identity and assurance +summary: OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI. +owner: key-cape +status: draft +domain: infotech +tags: +- iam +- oidc +- netkingdom +- security +- framework-reuse +maturity: + discovery: + current: D4 + target: D5 + confidence: high + rationale: README documents a versioned canonical contract (net-kingdom canon/standards/iam-profile_v0.2.md), + explicit lightweight-vs-expanded (Keycloak) migration story, and a completed + implementation status (all 23 workplan tasks, 21 green test packages). + availability: + current: A4 + target: A4 + confidence: high + rationale: 'Source interface assessed 2026-10-14: OIDC code with PKCE, service + tokens, JWKS, MFA and caller CLI. Availability describes the delivery form, + not production acceptance. Current stack is Authelia, LLDAP and privacyIDEA; + service secrets remain static and recovery proof has open gates.' +external_evidence: + completeness: + level: C2 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - full v0.1 implementation per its own workplan (23/23 tasks) + - 21 test packages, all green + - documented lightweight-to-expanded (Keycloak) migration path + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R1 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - maturity claims rely on the repo's own workplan completion record, not independently + re-verified in this sweep +discovery: + intent: OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI + includes: + - OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI + excludes: + - Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static + and recovery proof has open gates + assumptions: [] + use_cases: + - 'U02: Human signs in with MFA and manages account or factor recovery' + - 'U03: Application combines identity, tenant and resource facts and enforces a + bound decision' + - 'U04: Protected operation obtains and consumes exact human approval before its + side effect' + - 'U10: Operator recovers identity, custody or data with independently held recovery + material' + research_memos: [] +availability: + current_level: A4 + target_level: A4 + current_artifacts: + - SCOPE.md + - README.md + target_artifacts: [] + consumption_modes: + - HTTP API + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.identity.user-engine + - capability.identity.tenant-facts + - capability.authorization.policy-evaluate +evidence: + documentation: + - SCOPE.md + - README.md + tests: + - .gitea/workflows/ + - .forgejo/workflows/ + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Human signs in with MFA and manages account or factor recovery + - Application combines identity, tenant and resource facts and enforces a bound + decision + - Protected operation obtains and consumes exact human approval before its side + effect + - Operator recovers identity, custody or data with independently held recovery material + not_recommended_for: + - Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static + and recovery proof has open gates + known_limitations: + - Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static + and recovery proof has open gates + - 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 +--- + +# OIDC identity and assurance + +OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI. + +## Reuse boundary + +Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static and recovery proof has open gates. + +## Supported use cases + +- U02: Human signs in with MFA and manages account or factor recovery +- U03: Application combines identity, tenant and resource facts and enforces a bound decision +- U04: Protected operation obtains and consumes exact human approval before its side effect +- U10: Operator recovers identity, custody or data with independently held recovery material + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [README.md](../../README.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/key-cape/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/key-cape/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..0718f521 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/key-cape/registry/indexes/capabilities.yaml @@ -0,0 +1,21 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.iam.key-cape + name: OIDC identity and assurance + summary: OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI. + domain: infotech + status: draft + owner: key-cape + tags: + - iam + - oidc + - netkingdom + - security + - framework-reuse + vector: D4 / A4 / C2 / R1 + path: registry/capabilities/capability.iam.key-cape.md + consumption_modes: + - HTTP API + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/kings-guard/registry/capabilities/capability.security.posture-assessment.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/kings-guard/registry/capabilities/capability.security.posture-assessment.md new file mode 100644 index 00000000..d2facd1c --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/kings-guard/registry/capabilities/capability.security.posture-assessment.md @@ -0,0 +1,102 @@ +--- +id: capability.security.posture-assessment +owner: kings-guard +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Normalized observation evaluator, + cadence checks and secret-use snapshot adapter. Availability describes the delivery + form, not production acceptance. Bounded reference pilot; containment proposals + only; deployed-stream admission remains open.' +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: Security posture assessment and response proposals +summary: Normalized observation evaluator, cadence checks and secret-use snapshot + adapter. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Normalized observation evaluator, cadence checks and secret-use snapshot + adapter + includes: + - Normalized observation evaluator, cadence checks and secret-use snapshot adapter + excludes: + - Bounded reference pilot; containment proposals only; deployed-stream admission + remains open + use_cases: + - 'U08: Consumer emits security events and reconciles independently retained evidence' + - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and + verifies outcomes' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - SCOPE.md + - docs/SecretUseSnapshotAdmission.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.maturity-claims + - capability.audit.event-retain + - capability.security.risk-register + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + - docs/SecretUseSnapshotAdmission.md +consumer_guidance: + recommended_for: + - Consumer emits security events and reconciles independently retained evidence + - Maintainer observes posture, prioritizes findings, coordinates work and verifies + outcomes + not_recommended_for: + - Bounded reference pilot; containment proposals only; deployed-stream admission + remains open + known_limitations: + - Bounded reference pilot; containment proposals only; deployed-stream admission + remains open + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Security posture assessment and response proposals + +Normalized observation evaluator, cadence checks and secret-use snapshot adapter. + +## Reuse boundary + +Bounded reference pilot; containment proposals only; deployed-stream admission remains open. + +## Supported use cases + +- U08: Consumer emits security events and reconciles independently retained evidence +- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [docs/SecretUseSnapshotAdmission.md](../../docs/SecretUseSnapshotAdmission.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/kings-guard/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/kings-guard/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..8cd80d38 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/kings-guard/registry/indexes/capabilities.yaml @@ -0,0 +1,20 @@ +version: 1 +domain: infotech +capabilities: +- id: capability.security.posture-assessment + name: Security posture assessment and response proposals + summary: Normalized observation evaluator, cadence checks and secret-use snapshot + adapter. + domain: infotech + status: draft + owner: kings-guard + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.posture-assessment.md + consumption_modes: + - CLI + - source +updated: '2026-10-14' diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/maturity-engine/registry/capabilities/capability.security.maturity-claims.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/maturity-engine/registry/capabilities/capability.security.maturity-claims.md new file mode 100644 index 00000000..ce86465f --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/maturity-engine/registry/capabilities/capability.security.maturity-claims.md @@ -0,0 +1,101 @@ +--- +id: capability.security.maturity-claims +owner: maturity-engine +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: SQLite library and CLI for ladders, + evidence expiry, compute, explain and stance inventory. Availability describes + the delivery form, not production acceptance. No production deployment claimed; + levels supply facts and cannot authorize actions.' +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: Evidence-based maturity claims and gap register +summary: SQLite library and CLI for ladders, evidence expiry, compute, explain and + stance inventory. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: SQLite library and CLI for ladders, evidence expiry, compute, explain and + stance inventory + includes: + - SQLite library and CLI for ladders, evidence expiry, compute, explain and stance + inventory + excludes: + - No production deployment claimed; levels supply facts and cannot authorize actions + use_cases: + - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and + verifies outcomes' + - 'U14: Framework adopter validates and reuses selected contracts, tools and reference + compositions' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - SCOPE.md + - docs/claim-contract.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.doctrine-review + - capability.authorization.policy-evaluate + - capability.security.posture-assessment +evidence: + documentation: + - SCOPE.md + - docs/claim-contract.md +consumer_guidance: + recommended_for: + - Maintainer observes posture, prioritizes findings, coordinates work and verifies + outcomes + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - No production deployment claimed; levels supply facts and cannot authorize actions + known_limitations: + - No production deployment claimed; levels supply facts and cannot authorize actions + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Evidence-based maturity claims and gap register + +SQLite library and CLI for ladders, evidence expiry, compute, explain and stance inventory. + +## Reuse boundary + +No production deployment claimed; levels supply facts and cannot authorize actions. + +## Supported use cases + +- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes +- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [docs/claim-contract.md](../../docs/claim-contract.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/maturity-engine/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/maturity-engine/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..6c46b9ea --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/maturity-engine/registry/indexes/capabilities.yaml @@ -0,0 +1,20 @@ +version: 1 +domain: infotech +capabilities: +- id: capability.security.maturity-claims + name: Evidence-based maturity claims and gap register + summary: SQLite library and CLI for ladders, evidence expiry, compute, explain and + stance inventory. + domain: infotech + status: draft + owner: maturity-engine + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.maturity-claims.md + consumption_modes: + - CLI + - source +updated: '2026-10-14' diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.bootstrap-recovery.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.bootstrap-recovery.md new file mode 100644 index 00000000..ee6f65f3 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.bootstrap-recovery.md @@ -0,0 +1,100 @@ +--- +id: capability.security.bootstrap-recovery +owner: net-kingdom +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Local identity, bootstrap console, + encrypted custody handoff and caller tools. Availability describes the delivery + form, not production acceptance. Source repairs and disposable native fixtures + do not prove estate root isolation or recovery.' +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: Guarded bootstrap and recovery preparation +summary: Local identity, bootstrap console, encrypted custody handoff and caller tools. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Local identity, bootstrap console, encrypted custody handoff and caller + tools + includes: + - Local identity, bootstrap console, encrypted custody handoff and caller tools + excludes: + - Source repairs and disposable native fixtures do not prove estate root isolation + or recovery + use_cases: + - 'U10: Operator recovers identity, custody or data with independently held recovery + material' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - tools/security-bootstrap-console/README.md + - tools/custody-record/README.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.practice-canon + - capability.security.doctrine-review + - capability.iam.key-cape + - capability.authorization.policy-evaluate + - capability.registry.register + specializes: + - capability.security.iam-tooling-suite +evidence: + documentation: + - tools/security-bootstrap-console/README.md + - tools/custody-record/README.md +consumer_guidance: + recommended_for: + - Operator recovers identity, custody or data with independently held recovery material + not_recommended_for: + - Source repairs and disposable native fixtures do not prove estate root isolation + or recovery + known_limitations: + - Source repairs and disposable native fixtures do not prove estate root isolation + or recovery + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Guarded bootstrap and recovery preparation + +Local identity, bootstrap console, encrypted custody handoff and caller tools. + +## Reuse boundary + +Source repairs and disposable native fixtures do not prove estate root isolation or recovery. + +## Supported use cases + +- U10: Operator recovers identity, custody or data with independently held recovery material + +## Evidence and integration + +- [tools/security-bootstrap-console/README.md](../../tools/security-bootstrap-console/README.md) +- [tools/custody-record/README.md](../../tools/custody-record/README.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.case-contracts.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.case-contracts.md new file mode 100644 index 00000000..85c58983 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.case-contracts.md @@ -0,0 +1,110 @@ +--- +id: capability.security.case-contracts +owner: net-kingdom +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Versioned types, cases and schema + validation. Availability describes the delivery form, not production acceptance. + Type acknowledgment, case acceptance, structural materialization and native + execution are distinct.' +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: Security case types and instance validation +summary: Versioned types, cases and schema validation. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Versioned types, cases and schema validation + includes: + - Versioned types, cases and schema validation + excludes: + - Type acknowledgment, case acceptance, structural materialization and native execution + are distinct + use_cases: + - 'U01: Architect composes a security deployment from explicit owner contracts and + case types' + - 'U05: Operator provisions and delivers a scoped workload credential through the + approved owner lane' + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - tools/security-case-types/README.md + - canon/standards/security-case-types_v0.1.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.practice-canon + - capability.security.doctrine-review + - capability.iam.key-cape + - capability.authorization.policy-evaluate + - capability.registry.register + specializes: + - capability.security.iam-tooling-suite +evidence: + documentation: + - tools/security-case-types/README.md + - canon/standards/security-case-types_v0.1.md +consumer_guidance: + recommended_for: + - Architect composes a security deployment from explicit owner contracts and case + types + - Operator provisions and delivers a scoped workload credential through the approved + owner lane + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + not_recommended_for: + - Type acknowledgment, case acceptance, structural materialization and native execution + are distinct + known_limitations: + - Type acknowledgment, case acceptance, structural materialization and native execution + are distinct + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Security case types and instance validation + +Versioned types, cases and schema validation. + +## Reuse boundary + +Type acknowledgment, case acceptance, structural materialization and native execution are distinct. + +## Supported use cases + +- U01: Architect composes a security deployment from explicit owner contracts and case types +- U05: Operator provisions and delivers a scoped workload credential through the approved owner lane +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity + +## Evidence and integration + +- [tools/security-case-types/README.md](../../tools/security-case-types/README.md) +- [canon/standards/security-case-types_v0.1.md](../../canon/standards/security-case-types_v0.1.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.emission-profile.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.emission-profile.md new file mode 100644 index 00000000..2766f8c8 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.emission-profile.md @@ -0,0 +1,97 @@ +--- +id: capability.security.emission-profile +owner: net-kingdom +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Security profile over generic + emission contracts and validator. Availability describes the delivery form, + not production acceptance. Profile adoption and source completeness require + owner-native evidence.' +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: Security emission cadence validation +summary: Security profile over generic emission contracts and validator. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Security profile over generic emission contracts and validator + includes: + - Security profile over generic emission contracts and validator + excludes: + - Profile adoption and source completeness require owner-native evidence + use_cases: + - 'U08: Consumer emits security events and reconciles independently retained evidence' + - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and + verifies outcomes' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - tools/emission-cadence-profile/README.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.practice-canon + - capability.security.doctrine-review + - capability.iam.key-cape + - capability.authorization.policy-evaluate + - capability.registry.register + specializes: + - capability.security.iam-tooling-suite +evidence: + documentation: + - tools/emission-cadence-profile/README.md +consumer_guidance: + recommended_for: + - Consumer emits security events and reconciles independently retained evidence + - Maintainer observes posture, prioritizes findings, coordinates work and verifies + outcomes + not_recommended_for: + - Profile adoption and source completeness require owner-native evidence + known_limitations: + - Profile adoption and source completeness require owner-native evidence + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Security emission cadence validation + +Security profile over generic emission contracts and validator. + +## Reuse boundary + +Profile adoption and source completeness require owner-native evidence. + +## Supported use cases + +- U08: Consumer emits security events and reconciles independently retained evidence +- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes + +## Evidence and integration + +- [tools/emission-cadence-profile/README.md](../../tools/emission-cadence-profile/README.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.iam-tooling-suite.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.iam-tooling-suite.md new file mode 100644 index 00000000..ab95d6fc --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.iam-tooling-suite.md @@ -0,0 +1,133 @@ +--- +id: capability.security.iam-tooling-suite +name: NetKingdom security architecture and conformance tooling +summary: Versioned IAM, layer, tenancy and credential contracts plus validators. +owner: net-kingdom +status: draft +domain: infotech +tags: +- security +- iam +- kubernetes +- conformance +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D5 + confidence: medium + rationale: SCOPE plus docs/secrets-engine-security-infrastructure-boundary.md + describe an explicit integration boundary with OpenBao, flex-auth, user-engine, + ops-warden, ops-bridge, info-tech-canon, and State Hub; canon/standards/ holds + versioned IAM v0.3, playbook capability, scenario composition, tenancy, zone, + and boundary standards that provider repos implement against. + availability: + current: A2 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Versioned IAM, layer, tenancy + and credential contracts plus validators. Availability describes the delivery + form, not production acceptance. Mixed accepted and proposed standards; framework + integration remains incomplete.' +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - versioned canon standards already implemented by a sibling repo (key-cape) + - documented, runnable conformance, posture, composition, and bootstrap tools + under tools/ + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R1 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - no top-level packaging; each tool under tools/ has its own runtime dependencies, + no unified install path yet +discovery: + intent: Versioned IAM, layer, tenancy and credential contracts plus validators + includes: + - Versioned IAM, layer, tenancy and credential contracts plus validators + excludes: + - Mixed accepted and proposed standards; framework integration remains incomplete + assumptions: [] + use_cases: + - 'U01: Architect composes a security deployment from explicit owner contracts and + case types' + - 'U02: Human signs in with MFA and manages account or factor recovery' + - 'U03: Application combines identity, tenant and resource facts and enforces a + bound decision' + - 'U14: Framework adopter validates and reuses selected contracts, tools and reference + compositions' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + - SECURITY-COMPANION.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.practice-canon + - capability.security.doctrine-review + - capability.iam.key-cape + - capability.authorization.policy-evaluate + - capability.registry.register +evidence: + documentation: + - SCOPE.md + - SECURITY-COMPANION.md + tests: + - tools/iam-profile-conformance (pytest fixtures) + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Architect composes a security deployment from explicit owner contracts and case + types + - Human signs in with MFA and manages account or factor recovery + - Application combines identity, tenant and resource facts and enforces a bound + decision + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - Mixed accepted and proposed standards; framework integration remains incomplete + known_limitations: + - Mixed accepted and proposed standards; framework integration remains incomplete + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +promotion_history: [] +--- + +# NetKingdom security architecture and conformance tooling + +Versioned IAM, layer, tenancy and credential contracts plus validators. + +## Reuse boundary + +Mixed accepted and proposed standards; framework integration remains incomplete. + +## Supported use cases + +- U01: Architect composes a security deployment from explicit owner contracts and case types +- U02: Human signs in with MFA and manages account or factor recovery +- U03: Application combines identity, tenant and resource facts and enforces a bound decision +- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [SECURITY-COMPANION.md](../../SECURITY-COMPANION.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.posture-feedback.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.posture-feedback.md new file mode 100644 index 00000000..134d6c67 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.posture-feedback.md @@ -0,0 +1,101 @@ +--- +id: capability.security.posture-feedback +owner: net-kingdom +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: CLI evaluates evidence age and + posture into owner-routed findings. Availability describes the delivery form, + not production acceptance. Proposal only; no policy changes or remediation execution.' +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: Deterministic posture feedback +summary: CLI evaluates evidence age and posture into owner-routed findings. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: CLI evaluates evidence age and posture into owner-routed findings + includes: + - CLI evaluates evidence age and posture into owner-routed findings + excludes: + - Proposal only; no policy changes or remediation execution + use_cases: + - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and + verifies outcomes' + - 'U14: Framework adopter validates and reuses selected contracts, tools and reference + compositions' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - tools/posture-feedback/README.md + - tools/posture-feedback/posture_feedback.py + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.practice-canon + - capability.security.doctrine-review + - capability.iam.key-cape + - capability.authorization.policy-evaluate + - capability.registry.register + specializes: + - capability.security.iam-tooling-suite +evidence: + documentation: + - tools/posture-feedback/README.md + - tools/posture-feedback/posture_feedback.py +consumer_guidance: + recommended_for: + - Maintainer observes posture, prioritizes findings, coordinates work and verifies + outcomes + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - Proposal only; no policy changes or remediation execution + known_limitations: + - Proposal only; no policy changes or remediation execution + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Deterministic posture feedback + +CLI evaluates evidence age and posture into owner-routed findings. + +## Reuse boundary + +Proposal only; no policy changes or remediation execution. + +## Supported use cases + +- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes +- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions + +## Evidence and integration + +- [tools/posture-feedback/README.md](../../tools/posture-feedback/README.md) +- [tools/posture-feedback/posture_feedback.py](../../tools/posture-feedback/posture_feedback.py) + +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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.scenario-compose.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.scenario-compose.md new file mode 100644 index 00000000..769cd3f9 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/capabilities/capability.security.scenario-compose.md @@ -0,0 +1,101 @@ +--- +id: capability.security.scenario-compose +owner: net-kingdom +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: CLI selects pinned providers + and orders trust transitions. Availability describes the delivery form, not + production acceptance. Plan only; execution.permitted is always false.' +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: Deterministic security scenario composition +summary: CLI selects pinned providers and orders trust transitions. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: CLI selects pinned providers and orders trust transitions + includes: + - CLI selects pinned providers and orders trust transitions + excludes: + - Plan only; execution.permitted is always false + use_cases: + - 'U01: Architect composes a security deployment from explicit owner contracts and + case types' + - 'U14: Framework adopter validates and reuses selected contracts, tools and reference + compositions' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - tools/security-scenario-composer/README.md + - tools/security-scenario-composer/security_scenario_composer.py + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.practice-canon + - capability.security.doctrine-review + - capability.iam.key-cape + - capability.authorization.policy-evaluate + - capability.registry.register + specializes: + - capability.security.iam-tooling-suite +evidence: + documentation: + - tools/security-scenario-composer/README.md + - tools/security-scenario-composer/security_scenario_composer.py +consumer_guidance: + recommended_for: + - Architect composes a security deployment from explicit owner contracts and case + types + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - Plan only; execution.permitted is always false + known_limitations: + - Plan only; execution.permitted is always false + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Deterministic security scenario composition + +CLI selects pinned providers and orders trust transitions. + +## Reuse boundary + +Plan only; execution.permitted is always false. + +## Supported use cases + +- U01: Architect composes a security deployment from explicit owner contracts and case types +- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions + +## Evidence and integration + +- [tools/security-scenario-composer/README.md](../../tools/security-scenario-composer/README.md) +- [tools/security-scenario-composer/security_scenario_composer.py](../../tools/security-scenario-composer/security_scenario_composer.py) + +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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..507b2d61 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/net-kingdom/registry/indexes/capabilities.yaml @@ -0,0 +1,98 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.security.iam-tooling-suite + name: NetKingdom security architecture and conformance tooling + summary: Versioned IAM, layer, tenancy and credential contracts plus validators. + domain: infotech + status: draft + owner: net-kingdom + tags: + - security + - iam + - kubernetes + - conformance + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R1 + path: registry/capabilities/capability.security.iam-tooling-suite.md + consumption_modes: + - CLI + - source +- id: capability.security.scenario-compose + name: Deterministic security scenario composition + summary: CLI selects pinned providers and orders trust transitions. + domain: infotech + status: draft + owner: net-kingdom + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.scenario-compose.md + consumption_modes: + - CLI + - source +- id: capability.security.posture-feedback + name: Deterministic posture feedback + summary: CLI evaluates evidence age and posture into owner-routed findings. + domain: infotech + status: draft + owner: net-kingdom + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.posture-feedback.md + consumption_modes: + - CLI + - source +- id: capability.security.case-contracts + name: Security case types and instance validation + summary: Versioned types, cases and schema validation. + domain: infotech + status: draft + owner: net-kingdom + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.case-contracts.md + consumption_modes: + - CLI + - source +- id: capability.security.bootstrap-recovery + name: Guarded bootstrap and recovery preparation + summary: Local identity, bootstrap console, encrypted custody handoff and caller + tools. + domain: infotech + status: draft + owner: net-kingdom + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.bootstrap-recovery.md + consumption_modes: + - CLI + - source +- id: capability.security.emission-profile + name: Security emission cadence validation + summary: Security profile over generic emission contracts and validator. + domain: infotech + status: draft + owner: net-kingdom + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.emission-profile.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-bridge/registry/capabilities/capability.ops.tunnel-bridge.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-bridge/registry/capabilities/capability.ops.tunnel-bridge.md new file mode 100644 index 00000000..b4457be8 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-bridge/registry/capabilities/capability.ops.tunnel-bridge.md @@ -0,0 +1,111 @@ +--- +id: capability.ops.tunnel-bridge +name: SSH tunnel lifecycle +summary: Named tunnels, reconnect, health and TTL-aware cert_command. +owner: ops-bridge +status: draft +domain: infotech +tags: +- ssh +- tunnel +- ops +- connectivity +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D5 + confidence: medium + rationale: README.txt documents named tunnels, auto-reconnect with exponential + backoff, HTTP health checks, and structured JSON audit events per tunnel; this + is also the tool underlying reuse-surface's own `/bridge` skill. + availability: + current: A2 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Named tunnels, reconnect, health + and TTL-aware cert_command. Availability describes the delivery form, not production + acceptance. Private transport does not authenticate applications or decide access.' +external_evidence: + completeness: + level: C2 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - auto-reconnecting named SSH reverse tunnels + - HTTP health checks confirming forwarded service reachability, not just SSH liveness + - structured audit event log per tunnel + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R1 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - operational tool with real production usage but no independent load/failure + testing recorded in this sweep +discovery: + intent: Named tunnels, reconnect, health and TTL-aware cert_command + includes: + - Named tunnels, reconnect, health and TTL-aware cert_command + excludes: + - Private transport does not authenticate applications or decide access + assumptions: [] + use_cases: + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + tests: + - tests/ + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + not_recommended_for: + - Private transport does not authenticate applications or decide access + known_limitations: + - Private transport does not authenticate applications or decide access + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +promotion_history: [] +--- + +# SSH tunnel lifecycle + +Named tunnels, reconnect, health and TTL-aware cert_command. + +## Reuse boundary + +Private transport does not authenticate applications or decide access. + +## Supported use cases + +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity + +## 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-bridge/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-bridge/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..b15d1ac7 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-bridge/registry/indexes/capabilities.yaml @@ -0,0 +1,23 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.ops.tunnel-bridge + name: SSH tunnel lifecycle + summary: Named tunnels, reconnect, health and TTL-aware cert_command. + domain: infotech + status: draft + owner: ops-bridge + tags: + - ssh + - tunnel + - ops + - connectivity + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C2 / R1 + path: registry/capabilities/capability.ops.tunnel-bridge.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-mason/registry/capabilities/capability.security.structure-construction.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-mason/registry/capabilities/capability.security.structure-construction.md new file mode 100644 index 00000000..09834982 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-mason/registry/capabilities/capability.security.structure-construction.md @@ -0,0 +1,103 @@ +--- +id: capability.security.structure-construction +owner: ops-mason +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Digest-bound OpenBao AppRole + and Kubernetes-auth plans and guarded apply. Availability describes the delivery + form, not production acceptance. Founder plan gate is an explicit exception; + not full PDP conformance.' +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: Reviewed security structure construction +summary: Digest-bound OpenBao AppRole and Kubernetes-auth plans and guarded apply. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Digest-bound OpenBao AppRole and Kubernetes-auth plans and guarded apply + includes: + - Digest-bound OpenBao AppRole and Kubernetes-auth plans and guarded apply + excludes: + - Founder plan gate is an explicit exception; not full PDP conformance + use_cases: + - 'U01: Architect composes a security deployment from explicit owner contracts and + case types' + - 'U05: Operator provisions and delivers a scoped workload credential through the + approved owner lane' + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - SCOPE.md + - docs/construction-plan-format.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.credential-lifecycle + - capability.security.iam-tooling-suite + - capability.railiance.platform-services +evidence: + documentation: + - SCOPE.md + - docs/construction-plan-format.md +consumer_guidance: + recommended_for: + - Architect composes a security deployment from explicit owner contracts and case + types + - Operator provisions and delivers a scoped workload credential through the approved + owner lane + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + not_recommended_for: + - Founder plan gate is an explicit exception; not full PDP conformance + known_limitations: + - Founder plan gate is an explicit exception; not full PDP conformance + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Reviewed security structure construction + +Digest-bound OpenBao AppRole and Kubernetes-auth plans and guarded apply. + +## Reuse boundary + +Founder plan gate is an explicit exception; not full PDP conformance. + +## Supported use cases + +- U01: Architect composes a security deployment from explicit owner contracts and case types +- U05: Operator provisions and delivers a scoped workload credential through the approved owner lane +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [docs/construction-plan-format.md](../../docs/construction-plan-format.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-mason/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-mason/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..99ea4658 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-mason/registry/indexes/capabilities.yaml @@ -0,0 +1,19 @@ +version: 1 +domain: infotech +capabilities: +- id: capability.security.structure-construction + name: Reviewed security structure construction + summary: Digest-bound OpenBao AppRole and Kubernetes-auth plans and guarded apply. + domain: infotech + status: draft + owner: ops-mason + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.structure-construction.md + consumption_modes: + - CLI + - source +updated: '2026-10-14' diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.access-routing.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.access-routing.md new file mode 100644 index 00000000..dbab2a00 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.access-routing.md @@ -0,0 +1,104 @@ +--- +id: capability.security.access-routing +owner: ops-warden +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: A3 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: warden route and access catalog; + exact lane conduit and secret-exec routing. Availability describes the delivery + form, not production acceptance. Routing grants no authority; interim delegates + and attended high-risk lanes persist.' +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: Credential routing and contained access +summary: warden route and access catalog; exact lane conduit and secret-exec routing. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: warden route and access catalog; exact lane conduit and secret-exec routing + includes: + - warden route and access catalog; exact lane conduit and secret-exec routing + excludes: + - Routing grants no authority; interim delegates and attended high-risk lanes persist + use_cases: + - 'U04: Protected operation obtains and consumes exact human approval before its + side effect' + - 'U05: Operator provisions and delivers a scoped workload credential through the + approved owner lane' + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' +availability: + current_level: A3 + target_level: A3 + current_artifacts: + - SCOPE.md + - wiki/CredentialRouting.md + consumption_modes: + - library + - CLI +relations: + related_to: + - capability.security.credential-lifecycle + - capability.authorization.policy-evaluate + - capability.ops.tunnel-bridge + - capability.security.structure-construction +evidence: + documentation: + - SCOPE.md + - wiki/CredentialRouting.md +consumer_guidance: + recommended_for: + - Protected operation obtains and consumes exact human approval before its side + effect + - Operator provisions and delivers a scoped workload credential through the approved + owner lane + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + not_recommended_for: + - Routing grants no authority; interim delegates and attended high-risk lanes persist + known_limitations: + - Routing grants no authority; interim delegates and attended high-risk lanes persist + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Credential routing and contained access + +warden route and access catalog; exact lane conduit and secret-exec routing. + +## Reuse boundary + +Routing grants no authority; interim delegates and attended high-risk lanes persist. + +## Supported use cases + +- U04: Protected operation obtains and consumes exact human approval before its side effect +- U05: Operator provisions and delivers a scoped workload credential through the approved owner lane +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [wiki/CredentialRouting.md](../../wiki/CredentialRouting.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.case-follow-through.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.case-follow-through.md new file mode 100644 index 00000000..1268c238 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.case-follow-through.md @@ -0,0 +1,104 @@ +--- +id: capability.security.case-follow-through +owner: ops-warden +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: KnownSecurityCase route, plan + and operational receipts. Availability describes the delivery form, not production + acceptance. Execution requires accepted structure and exact owner contracts; + case closure is not automatic.' +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: Security case operational follow-through +summary: KnownSecurityCase route, plan and operational receipts. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: KnownSecurityCase route, plan and operational receipts + includes: + - KnownSecurityCase route, plan and operational receipts + excludes: + - Execution requires accepted structure and exact owner contracts; case closure + is not automatic + use_cases: + - 'U01: Architect composes a security deployment from explicit owner contracts and + case types' + - 'U05: Operator provisions and delivers a scoped workload credential through the + approved owner lane' + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - workplans/WARDEN-WP-0044-security-case-follow-through.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.credential-lifecycle + - capability.authorization.policy-evaluate + - capability.ops.tunnel-bridge + - capability.security.structure-construction +evidence: + documentation: + - workplans/WARDEN-WP-0044-security-case-follow-through.md +consumer_guidance: + recommended_for: + - Architect composes a security deployment from explicit owner contracts and case + types + - Operator provisions and delivers a scoped workload credential through the approved + owner lane + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + not_recommended_for: + - Execution requires accepted structure and exact owner contracts; case closure + is not automatic + known_limitations: + - Execution requires accepted structure and exact owner contracts; case closure + is not automatic + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Security case operational follow-through + +KnownSecurityCase route, plan and operational receipts. + +## Reuse boundary + +Execution requires accepted structure and exact owner contracts; case closure is not automatic. + +## Supported use cases + +- U01: Architect composes a security deployment from explicit owner contracts and case types +- U05: Operator provisions and delivers a scoped workload credential through the approved owner lane +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity + +## Evidence and integration + +- [workplans/WARDEN-WP-0044-security-case-follow-through.md](../../workplans/WARDEN-WP-0044-security-case-follow-through.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.ssh-certificate-issuance.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.ssh-certificate-issuance.md new file mode 100644 index 00000000..91e05c85 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/capabilities/capability.security.ssh-certificate-issuance.md @@ -0,0 +1,138 @@ +--- +id: capability.security.ssh-certificate-issuance +name: Decision-bound SSH certificates +summary: warden sign with local and OpenBao backends and adm/agt/atm actors. +owner: ops-warden +status: draft +domain: helix_forge +tags: +- ssh +- certificate +- ca +- ops-warden +- openbao +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D4 + target: D5 + confidence: medium + rationale: 'SCOPE, AccessManagementDirective alignment, config runbooks, and cert_command + contract are documented; production OpenBao integration is documented but engine + deployment lives in railiance-platform. A machine-readable routing catalog (registry/routing/catalog.yaml) + and wiki/AccessRouting.md make the "issue SSH, route the rest" boundary discoverable. + + ' + availability: + current: A3 + target: A5 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: warden sign with local and OpenBao + backends and adm/agt/atm actors. Availability describes the delivery form, not + production acceptance. Direct Tooling contact is a declared gap; certificate + reachability is not target authorization.' +external_evidence: + completeness: + level: C3 + name: Functional Core + confidence: medium + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - local and OpenBao/Vault-compatible signing backends + - TTL policy enforcement per actor type + - principals inventory and cert-side scorecard + - signatures audit log and stale-cert cleanup + - cert_command stdout contract for ops-bridge + broken_expectations: + - host-side principal deployment not owned here + - OpenBao SSH engine mount not deployed from this repo + out_of_scope_expectations: + - long-lived API key custody + - tunnel lifecycle management + - Vault/OpenBao cluster operations + reliability: + level: R2 + name: Tolerable + confidence: medium + basis: consumer_quality_signals + known_reliability_risks: + - production signing depends on OpenBao availability and token policy + - local backend requires protected CA key handling by operators +discovery: + intent: warden sign with local and OpenBao backends and adm/agt/atm actors + includes: + - warden sign with local and OpenBao backends and adm/agt/atm actors + excludes: + - Direct Tooling contact is a declared gap; certificate reachability is not target + authorization + assumptions: + - callers supply actor public keys; humans self-issue admin keys + - production platform uses OpenBao with Vault-compatible SSH engine API + use_cases: + - ops-bridge tunnel cert_command + - Inter-Hub bootstrap short-lived agent access + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' + research_memos: + - ops-warden/SCOPE.md + - ops-warden/wiki/CertCommandInterface.md + - ops-warden/wiki/OpsWardenConfig.md + - ops-warden/wiki/AccessRouting.md +availability: + current_level: A3 + target_level: A5 + current_artifacts: + - SCOPE.md + - README.md + target_artifacts: + - packaged ops-warden release with documented OpenBao role bootstrap + - '`warden route` lookup CLI over the pointer catalog (WARDEN-WP-0011)' + consumption_modes: + - library + - CLI +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.credential-lifecycle + - capability.authorization.policy-evaluate + - capability.ops.tunnel-bridge + - capability.security.structure-construction +consumer_guidance: + recommended_for: + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + not_recommended_for: + - Direct Tooling contact is a declared gap; certificate reachability is not target + authorization + known_limitations: + - Direct Tooling contact is a declared gap; certificate reachability is not target + authorization + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +evidence: + documentation: + - SCOPE.md + - README.md +--- + +# Decision-bound SSH certificates + +warden sign with local and OpenBao backends and adm/agt/atm actors. + +## Reuse boundary + +Direct Tooling contact is a declared gap; certificate reachability is not target authorization. + +## Supported use cases + +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [README.md](../../README.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..7f4d6496 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/ops-warden/registry/indexes/capabilities.yaml @@ -0,0 +1,54 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.security.ssh-certificate-issuance + name: Decision-bound SSH certificates + summary: warden sign with local and OpenBao backends and adm/agt/atm actors. + domain: helix_forge + status: draft + owner: ops-warden + tags: + - ssh + - certificate + - ca + - ops-warden + - openbao + - security + - netkingdom + - framework-reuse + vector: D4 / A3 / C3 / R2 + path: registry/capabilities/capability.security.ssh-certificate-issuance.md + consumption_modes: + - library + - CLI +- id: capability.security.access-routing + name: Credential routing and contained access + summary: warden route and access catalog; exact lane conduit and secret-exec routing. + domain: infotech + status: draft + owner: ops-warden + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A3 / C1 / R0 + path: registry/capabilities/capability.security.access-routing.md + consumption_modes: + - library + - CLI +- id: capability.security.case-follow-through + name: Security case operational follow-through + summary: KnownSecurityCase route, plan and operational receipts. + domain: infotech + status: draft + owner: ops-warden + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.case-follow-through.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/policy-nexus/registry/capabilities/capability.security.policy-publication.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/policy-nexus/registry/capabilities/capability.security.policy-publication.md new file mode 100644 index 00000000..cba9831a --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/policy-nexus/registry/capabilities/capability.security.policy-publication.md @@ -0,0 +1,103 @@ +--- +id: capability.security.policy-publication +owner: policy-nexus +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Generated immutable publication, + source currency and stable policy URLs. Availability describes the delivery + form, not production acceptance. Publication does not ratify policy or enforce + it.' +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: Policy publication with source provenance +summary: Generated immutable publication, source currency and stable policy URLs. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Generated immutable publication, source currency and stable policy URLs + includes: + - Generated immutable publication, source currency and stable policy URLs + excludes: + - Publication does not ratify policy or enforce it + use_cases: + - 'U01: Architect composes a security deployment from explicit owner contracts and + case types' + - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and + verifies outcomes' + - 'U14: Framework adopter validates and reuses selected contracts, tools and reference + compositions' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - README.md + - docs/publication-contract.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.iam-tooling-suite + - capability.security.practice-canon + - capability.security.risk-register +evidence: + documentation: + - README.md + - docs/publication-contract.md +consumer_guidance: + recommended_for: + - Architect composes a security deployment from explicit owner contracts and case + types + - Maintainer observes posture, prioritizes findings, coordinates work and verifies + outcomes + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - Publication does not ratify policy or enforce it + known_limitations: + - Publication does not ratify policy or enforce it + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Policy publication with source provenance + +Generated immutable publication, source currency and stable policy URLs. + +## Reuse boundary + +Publication does not ratify policy or enforce it. + +## Supported use cases + +- U01: Architect composes a security deployment from explicit owner contracts and case types +- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes +- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions + +## Evidence and integration + +- [README.md](../../README.md) +- [docs/publication-contract.md](../../docs/publication-contract.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/policy-nexus/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/policy-nexus/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..bb52c8cc --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/policy-nexus/registry/indexes/capabilities.yaml @@ -0,0 +1,19 @@ +version: 1 +domain: infotech +capabilities: +- id: capability.security.policy-publication + name: Policy publication with source provenance + summary: Generated immutable publication, source currency and stable policy URLs. + domain: infotech + status: draft + owner: policy-nexus + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.policy-publication.md + consumption_modes: + - CLI + - source +updated: '2026-10-14' diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/rail-kubernetes/registry/capabilities/capability.railiance.kubernetes-rail.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/rail-kubernetes/registry/capabilities/capability.railiance.kubernetes-rail.md new file mode 100644 index 00000000..1e09015c --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/rail-kubernetes/registry/capabilities/capability.railiance.kubernetes-rail.md @@ -0,0 +1,93 @@ +--- +id: capability.railiance.kubernetes-rail +owner: rail-kubernetes +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Workload declaration, rollout, + observe, promote and rollback surfaces. Availability describes the delivery + form, not production acceptance. Compatibility extraction remains; not cluster + or application-domain ownership.' +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: Generic Kubernetes workload lifecycle +summary: Workload declaration, rollout, observe, promote and rollback surfaces. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Workload declaration, rollout, observe, promote and rollback surfaces + includes: + - Workload declaration, rollout, observe, promote and rollback surfaces + excludes: + - Compatibility extraction remains; not cluster or application-domain ownership + 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: A2 + target_level: A2 + current_artifacts: + - SCOPE.md + consumption_modes: + - CLI + - source +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: + - Compatibility extraction remains; not cluster or application-domain ownership + known_limitations: + - Compatibility extraction remains; not cluster or application-domain ownership + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Generic Kubernetes workload lifecycle + +Workload declaration, rollout, observe, promote and rollback surfaces. + +## Reuse boundary + +Compatibility extraction remains; not cluster or application-domain ownership. + +## 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/rail-kubernetes/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/rail-kubernetes/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..739c5ffe --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/rail-kubernetes/registry/indexes/capabilities.yaml @@ -0,0 +1,19 @@ +version: 1 +domain: infotech +capabilities: +- id: capability.railiance.kubernetes-rail + name: Generic Kubernetes workload lifecycle + summary: Workload declaration, rollout, observe, promote and rollback surfaces. + domain: infotech + status: draft + owner: rail-kubernetes + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.railiance.kubernetes-rail.md + consumption_modes: + - CLI + - source +updated: '2026-10-14' diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-apps/registry/capabilities/capability.railiance.workload-deployment-tooling.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-apps/registry/capabilities/capability.railiance.workload-deployment-tooling.md new file mode 100644 index 00000000..063141ca --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-apps/registry/capabilities/capability.railiance.workload-deployment-tooling.md @@ -0,0 +1,118 @@ +--- +id: capability.railiance.workload-deployment-tooling +name: Workload release configuration and guards +summary: Helm/manifests, exact image pins, application runbooks and rollout/rollback. +owner: railiance-apps +status: draft +domain: financials +tags: +- railiance +- kubernetes +- helm +- deployment +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D4 + confidence: medium + rationale: SCOPE.md places this repo precisely in the Railiance OAS Stack layering + (S5), scoped to application Helm releases, workload manifests, and operator + runbooks for user-facing services such as vergabe-teilnahme. + availability: + current: A2 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Helm/manifests, exact image + pins, application runbooks and rollout/rollback. Availability describes the + delivery form, not production acceptance. Release settings depend on underlying + platform and workload owners.' +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - Helm charts and Kubernetes manifests for application workloads + - smoke-test and dry-run check scripts, including a forgejo-smoke.sh already ahead + of the platform-wide Forgejo transition + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R1 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - no top-level packaging; tooling is a collection of shell scripts under tools/ +discovery: + intent: Helm/manifests, exact image pins, application runbooks and rollout/rollback + includes: + - Helm/manifests, exact image pins, application runbooks and rollout/rollback + excludes: + - Release settings depend on underlying platform and workload owners + assumptions: [] + use_cases: + - 'U12: Developer builds and publishes through controlled source, dependency and + runner paths' + - 'U13: Platform owner deploys and rolls back a workload with explicit substrate + and custody bindings' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + tests: + - tools/forgejo-smoke.sh + - tools/inter-hub-smoke.sh + - tools/k8s-server-dry-run.sh + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Developer builds and publishes through controlled source, dependency and runner + paths + - Platform owner deploys and rolls back a workload with explicit substrate and custody + bindings + not_recommended_for: + - Release settings depend on underlying platform and workload owners + known_limitations: + - Release settings depend on underlying platform and workload owners + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +promotion_history: [] +--- + +# Workload release configuration and guards + +Helm/manifests, exact image pins, application runbooks and rollout/rollback. + +## Reuse boundary + +Release settings depend on underlying platform and workload owners. + +## Supported use cases + +- U12: Developer builds and publishes through controlled source, dependency and runner paths +- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings + +## 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-apps/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-apps/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..a311af53 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-apps/registry/indexes/capabilities.yaml @@ -0,0 +1,23 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.workload-deployment-tooling + name: Workload release configuration and guards + summary: Helm/manifests, exact image pins, application runbooks and rollout/rollback. + domain: financials + status: draft + owner: railiance-apps + tags: + - railiance + - kubernetes + - helm + - deployment + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R1 + path: registry/capabilities/capability.railiance.workload-deployment-tooling.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-bootstrap/registry/capabilities/capability.railiance.bootstrap-sequencing.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-bootstrap/registry/capabilities/capability.railiance.bootstrap-sequencing.md new file mode 100644 index 00000000..cb34eeb4 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-bootstrap/registry/capabilities/capability.railiance.bootstrap-sequencing.md @@ -0,0 +1,90 @@ +--- +id: capability.railiance.bootstrap-sequencing +owner: railiance-bootstrap +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: Bare-VM to estate sequence and + handoff contract. Availability describes the delivery form, not production acceptance. + End-to-end unattended rebuild is not established.' +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: Bootstrap sequencing contracts +summary: Bare-VM to estate sequence and handoff contract. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Bare-VM to estate sequence and handoff contract + includes: + - Bare-VM to estate sequence and handoff contract + excludes: + - End-to-end unattended rebuild is not established + use_cases: + - 'U10: Operator recovers identity, custody or data with independently held recovery + material' + - '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: + - Operator recovers identity, custody or data with independently held recovery material + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - End-to-end unattended rebuild is not established + known_limitations: + - End-to-end unattended rebuild is not established + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Bootstrap sequencing contracts + +Bare-VM to estate sequence and handoff contract. + +## Reuse boundary + +End-to-end unattended rebuild is not established. + +## Supported use cases + +- U10: Operator recovers identity, custody or data with independently held recovery material +- 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-bootstrap/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-bootstrap/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..10349759 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-bootstrap/registry/indexes/capabilities.yaml @@ -0,0 +1,18 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.bootstrap-sequencing + name: Bootstrap sequencing contracts + summary: Bare-VM to estate sequence and handoff contract. + domain: infotech + status: draft + owner: railiance-bootstrap + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A0 / C1 / R0 + path: registry/capabilities/capability.railiance.bootstrap-sequencing.md + consumption_modes: + - informational diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-cluster/registry/capabilities/capability.railiance.cluster-bootstrap.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-cluster/registry/capabilities/capability.railiance.cluster-bootstrap.md new file mode 100644 index 00000000..6b7a5c06 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-cluster/registry/capabilities/capability.railiance.cluster-bootstrap.md @@ -0,0 +1,116 @@ +--- +id: capability.railiance.cluster-bootstrap +name: Kubernetes runtime and cluster controls +summary: k3s, ingress, CNI, operators and kubeconfig/runtime checks. +owner: railiance-cluster +status: draft +domain: financials +tags: +- railiance +- kubernetes +- iac +- bootstrap +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D4 + confidence: medium + rationale: README documents the 'Rails for Ops' convention-over-configuration + philosophy and a concrete quick-start (clone, from two bare servers rebuild + a full k8s environment); has .forgejo CI already in place. + availability: + current: A2 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: k3s, ingress, CNI, operators + and kubeconfig/runtime checks. Availability describes the delivery form, not + production acceptance. Single-node runtime and workload recovery are distinct + from bootstrap success.' +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - documented quick-start from two bare servers to a running Kubernetes environment + - bootstrap/harden ansible playbooks + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R0 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - reproducibility claims not independently re-verified (no live bootstrap run + during this sweep) +discovery: + intent: k3s, ingress, CNI, operators and kubeconfig/runtime checks + includes: + - k3s, ingress, CNI, operators and kubeconfig/runtime checks + excludes: + - Single-node runtime and workload recovery are distinct from bootstrap success + assumptions: [] + use_cases: + - 'U10: Operator recovers identity, custody or data with independently held recovery + material' + - 'U13: Platform owner deploys and rolls back a workload with explicit substrate + and custody bindings' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + tests: + - tests/ + - .forgejo/ + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Operator recovers identity, custody or data with independently held recovery material + - Platform owner deploys and rolls back a workload with explicit substrate and custody + bindings + not_recommended_for: + - Single-node runtime and workload recovery are distinct from bootstrap success + known_limitations: + - Single-node runtime and workload recovery are distinct from bootstrap success + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +promotion_history: [] +--- + +# Kubernetes runtime and cluster controls + +k3s, ingress, CNI, operators and kubeconfig/runtime checks. + +## Reuse boundary + +Single-node runtime and workload recovery are distinct from bootstrap success. + +## Supported use cases + +- U10: Operator recovers identity, custody or data with independently held recovery material +- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings + +## 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-cluster/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-cluster/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..a6161da4 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-cluster/registry/indexes/capabilities.yaml @@ -0,0 +1,23 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.cluster-bootstrap + name: Kubernetes runtime and cluster controls + summary: k3s, ingress, CNI, operators and kubeconfig/runtime checks. + domain: financials + status: draft + owner: railiance-cluster + tags: + - railiance + - kubernetes + - iac + - bootstrap + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.railiance.cluster-bootstrap.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-enablement/registry/capabilities/capability.railiance.ci-enablement.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-enablement/registry/capabilities/capability.railiance.ci-enablement.md new file mode 100644 index 00000000..d817a7c2 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-enablement/registry/capabilities/capability.railiance.ci-enablement.md @@ -0,0 +1,116 @@ +--- +id: capability.railiance.ci-enablement +name: Developer delivery and CI templates +summary: Reusable CI workflows, build and deployment patterns. +owner: railiance-enablement +status: draft +domain: financials +tags: +- railiance +- ci-cd +- developer-enablement +- forgejo +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D4 + confidence: medium + rationale: SCOPE.md places this repo precisely at S4 in the Railiance OAS Stack, + explicitly scoped to reusable CI/CD templates and enablement tooling while using + (not owning) forge capabilities. + availability: + current: A2 + target: A3 + confidence: high + rationale: 'Source interface assessed 2026-10-14: Reusable CI workflows, build + and deployment patterns. Availability describes the delivery form, not production + acceptance. Templates do not prove mandatory checks or runner isolation.' +external_evidence: + completeness: + level: C2 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - reusable Forgejo Actions CI/CD workflow templates already in production shape + - a repo-promotion-to-forgejo script directly usable for the platform-wide forge + transition + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R1 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - templates are workflow YAML, not a packaged/versioned artifact; consumption + is copy/reference rather than dependency-managed +discovery: + intent: Reusable CI workflows, build and deployment patterns + includes: + - Reusable CI workflows, build and deployment patterns + excludes: + - Templates do not prove mandatory checks or runner isolation + assumptions: [] + use_cases: + - 'U12: Developer builds and publishes through controlled source, dependency and + runner paths' + - 'U14: Framework adopter validates and reuses selected contracts, tools and reference + compositions' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + tests: + - workflows/ci-smoke.yaml + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Developer builds and publishes through controlled source, dependency and runner + paths + - Framework adopter validates and reuses selected contracts, tools and reference + compositions + not_recommended_for: + - Templates do not prove mandatory checks or runner isolation + known_limitations: + - Templates do not prove mandatory checks or runner isolation + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +promotion_history: [] +--- + +# Developer delivery and CI templates + +Reusable CI workflows, build and deployment patterns. + +## Reuse boundary + +Templates do not prove mandatory checks or runner isolation. + +## Supported use cases + +- U12: Developer builds and publishes through controlled source, dependency and runner paths +- 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-enablement/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-enablement/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..4aae230e --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-enablement/registry/indexes/capabilities.yaml @@ -0,0 +1,23 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.ci-enablement + name: Developer delivery and CI templates + summary: Reusable CI workflows, build and deployment patterns. + domain: financials + status: draft + owner: railiance-enablement + tags: + - railiance + - ci-cd + - developer-enablement + - forgejo + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C2 / R1 + path: registry/capabilities/capability.railiance.ci-enablement.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-fabric/registry/capabilities/capability.railiance.fabric-graph.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-fabric/registry/capabilities/capability.railiance.fabric-graph.md new file mode 100644 index 00000000..c858fd1f --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-fabric/registry/capabilities/capability.railiance.fabric-graph.md @@ -0,0 +1,128 @@ +--- +id: capability.railiance.fabric-graph +name: Infrastructure ownership and dependency graph +summary: Schemas, validation, graph queries and State Hub exports. +owner: railiance-fabric +status: draft +domain: financials +tags: +- railiance +- graph +- ownership +- discovery +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D5 + confidence: medium + rationale: README and SCOPE.md document the ecosystem graph model bounded by financial/operational + accountability (who pays, who is accountable), with king/lord/tenant ownership + concepts referenced in docs/FabricDiscoveryAndUpdate.md. + availability: + current: A2 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Schemas, validation, graph queries + and State Hub exports. Availability describes the delivery form, not production + acceptance. Graph assertions need current owner evidence; not an enforcement + registry.' +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - ecosystem graph declaration loader and validator + - schemas for services/machines/repos/deployables/endpoints/ownership/dependencies/bindings + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R0 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - discovery/rebuild/update-loop architecture documented as still evolving per + docs/FabricDiscoveryAndUpdate.md +discovery: + intent: Schemas, validation, graph queries and State Hub exports + includes: + - Schemas, validation, graph queries and State Hub exports + excludes: + - Graph assertions need current owner evidence; not an enforcement registry + assumptions: [] + use_cases: + - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and + verifies outcomes' + - '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' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + tests: + - tests/ + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Maintainer observes posture, prioritizes findings, coordinates work and verifies + outcomes + - 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: + - Graph assertions need current owner evidence; not an enforcement registry + known_limitations: + - Graph assertions need current owner evidence; not an enforcement registry + - 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: A1 + to: A2 + rationale: Interface-form reassessment from current owner sources; no completeness/reliability + promotion. + author: codex +--- + +# Infrastructure ownership and dependency graph + +Schemas, validation, graph queries and State Hub exports. + +## Reuse boundary + +Graph assertions need current owner evidence; not an enforcement registry. + +## Supported use cases + +- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes +- 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-fabric/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-fabric/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..b7e9b3af --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-fabric/registry/indexes/capabilities.yaml @@ -0,0 +1,23 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.fabric-graph + name: Infrastructure ownership and dependency graph + summary: Schemas, validation, graph queries and State Hub exports. + domain: financials + status: draft + owner: railiance-fabric + tags: + - railiance + - graph + - ownership + - discovery + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.railiance.fabric-graph.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/capabilities/capability.railiance.forge-infrastructure.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/capabilities/capability.railiance.forge-infrastructure.md new file mode 100644 index 00000000..9221cfa8 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/capabilities/capability.railiance.forge-infrastructure.md @@ -0,0 +1,124 @@ +--- +id: capability.railiance.forge-infrastructure +name: Source forge, registries and runner substrate +summary: Forgejo operation, package registries and runner lifecycle. +owner: railiance-forge +status: draft +domain: financials +tags: +- railiance +- forgejo +- forge +- ci-runner +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D3 + target: D5 + confidence: medium + rationale: README and SCOPE.md explicitly name 'current Gitea operation, future + Forgejo migration, container and package registries, Actions runner substrate, + artifact lifecycle' as the scope; status noted as 'active forge extraction' + with canonical registry operation docs already landed. + availability: + current: A2 + target: A3 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Forgejo operation, package registries + and runner lifecycle. Availability describes the delivery form, not production + acceptance. Runner workload authority and independent verification coverage + remain open.' +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - scope separation from railiance-apps/railiance-enablement documented + - canonical registry operation docs and runner ownership contracts + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R0 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - repo is actively being founded/extracted; no live deploy yet by its own account + - directly relevant to REUSE-WP-0019 but hasn't migrated its own CI to .forgejo/ + yet +discovery: + intent: Forgejo operation, package registries and runner lifecycle + includes: + - Forgejo operation, package registries and runner lifecycle + excludes: + - Runner workload authority and independent verification coverage remain open + assumptions: [] + use_cases: + - 'U12: Developer builds and publishes through controlled source, dependency and + runner paths' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + - workplans/FORGE-WP-0006-independent-secret-detection.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.repository-secret-prevention + - capability.railiance.ci-enablement + - capability.railiance.workload-deployment-tooling +evidence: + documentation: + - SCOPE.md + - workplans/FORGE-WP-0006-independent-secret-detection.md + tests: [] + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Developer builds and publishes through controlled source, dependency and runner + paths + not_recommended_for: + - Runner workload authority and independent verification coverage remain open + known_limitations: + - Runner workload authority and independent verification coverage remain open + - 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: A1 + to: A2 + rationale: Interface-form reassessment from current owner sources; no completeness/reliability + promotion. + author: codex +--- + +# Source forge, registries and runner substrate + +Forgejo operation, package registries and runner lifecycle. + +## Reuse boundary + +Runner workload authority and independent verification coverage remain open. + +## Supported use cases + +- U12: Developer builds and publishes through controlled source, dependency and runner paths + +## Evidence and integration + +- [SCOPE.md](../../SCOPE.md) +- [workplans/FORGE-WP-0006-independent-secret-detection.md](../../workplans/FORGE-WP-0006-independent-secret-detection.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/capabilities/capability.security.forge-secret-prevention.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/capabilities/capability.security.forge-secret-prevention.md new file mode 100644 index 00000000..7e875db9 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/capabilities/capability.security.forge-secret-prevention.md @@ -0,0 +1,96 @@ +--- +id: capability.security.forge-secret-prevention +owner: railiance-forge +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: A2 + target: A2 + confidence: medium + rationale: 'Source interface assessed 2026-10-14: Pinned receive adapter, lifecycle + template and fail-closed scan. Availability describes the delivery form, not + production acceptance. Dated native coverage excludes one repo; import/mirror + fetch and response coverage remain separate.' +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: Independent introduced-history secret prevention +summary: Pinned receive adapter, lifecycle template and fail-closed scan. +tags: +- security +- netkingdom +- framework-reuse +discovery: + intent: Pinned receive adapter, lifecycle template and fail-closed scan + includes: + - Pinned receive adapter, lifecycle template and fail-closed scan + excludes: + - Dated native coverage excludes one repo; import/mirror fetch and response coverage + remain separate + use_cases: + - 'U07: Owner inventories, rotates, revokes and detects exposure of credentials' + - 'U12: Developer builds and publishes through controlled source, dependency and + runner paths' +availability: + current_level: A2 + target_level: A2 + current_artifacts: + - workplans/FORGE-WP-0006-independent-secret-detection.md + consumption_modes: + - CLI + - source +relations: + related_to: + - capability.security.repository-secret-prevention + - capability.railiance.ci-enablement + - capability.railiance.workload-deployment-tooling +evidence: + documentation: + - workplans/FORGE-WP-0006-independent-secret-detection.md +consumer_guidance: + recommended_for: + - Owner inventories, rotates, revokes and detects exposure of credentials + - Developer builds and publishes through controlled source, dependency and runner + paths + not_recommended_for: + - Dated native coverage excludes one repo; import/mirror fetch and response coverage + remain separate + known_limitations: + - Dated native coverage excludes one repo; import/mirror fetch and response coverage + remain separate + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +--- + +# Independent introduced-history secret prevention + +Pinned receive adapter, lifecycle template and fail-closed scan. + +## Reuse boundary + +Dated native coverage excludes one repo; import/mirror fetch and response coverage remain separate. + +## Supported use cases + +- U07: Owner inventories, rotates, revokes and detects exposure of credentials +- U12: Developer builds and publishes through controlled source, dependency and runner paths + +## Evidence and integration + +- [workplans/FORGE-WP-0006-independent-secret-detection.md](../../workplans/FORGE-WP-0006-independent-secret-detection.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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..51cff6e7 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-forge/registry/indexes/capabilities.yaml @@ -0,0 +1,38 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.forge-infrastructure + name: Source forge, registries and runner substrate + summary: Forgejo operation, package registries and runner lifecycle. + domain: financials + status: draft + owner: railiance-forge + tags: + - railiance + - forgejo + - forge + - ci-runner + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.railiance.forge-infrastructure.md + consumption_modes: + - CLI + - source +- id: capability.security.forge-secret-prevention + name: Independent introduced-history secret prevention + summary: Pinned receive adapter, lifecycle template and fail-closed scan. + domain: infotech + status: draft + owner: railiance-forge + tags: + - security + - netkingdom + - framework-reuse + vector: D3 / A2 / C1 / R0 + path: registry/capabilities/capability.security.forge-secret-prevention.md + consumption_modes: + - CLI + - source diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-infra/registry/capabilities/capability.railiance.infra-provisioning.md b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-infra/registry/capabilities/capability.railiance.infra-provisioning.md new file mode 100644 index 00000000..8e5cac8e --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-infra/registry/capabilities/capability.railiance.infra-provisioning.md @@ -0,0 +1,123 @@ +--- +id: capability.railiance.infra-provisioning +name: Host convergence and security baseline +summary: Ansible inventory, firewall, SSH bootstrap and baseline verification. +owner: railiance-infra +status: draft +domain: financials +tags: +- railiance +- terraform +- ansible +- infrastructure +- security +- netkingdom +- framework-reuse +maturity: + discovery: + current: D4 + target: D5 + confidence: high + rationale: README documents a complete, concrete quickstart (clone, prerequisites, + SOPS/age secrets setup, provider setup, terraform apply, ansible convergence) + with a specific inventory file (`inventory/servers.yaml`) as source of truth + — an unusually complete operational README among the swept repos. + availability: + current: A2 + target: A3 + confidence: high + rationale: 'Source interface assessed 2026-10-14: Ansible inventory, firewall, + SSH bootstrap and baseline verification. Availability describes the delivery + form, not production acceptance. Current hosts differ from the retained Hetzner + provisioning path.' +external_evidence: + completeness: + level: C2 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - documented end-to-end quickstart from bare cloud account to converged servers + - SOPS+age encrypted secrets with a documented key-custody model + - inventory/servers.yaml as explicit source of truth + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R1 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - reproducibility not independently re-verified via a live provisioning run in + this sweep +discovery: + intent: Ansible inventory, firewall, SSH bootstrap and baseline verification + includes: + - Ansible inventory, firewall, SSH bootstrap and baseline verification + excludes: + - Current hosts differ from the retained Hetzner provisioning path + assumptions: [] + use_cases: + - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private + connectivity' + - 'U10: Operator recovers identity, custody or data with independently held recovery + material' + - 'U13: Platform owner deploys and rolls back a workload with explicit substrate + and custody bindings' + research_memos: [] +availability: + current_level: A2 + target_level: A3 + current_artifacts: + - SCOPE.md + target_artifacts: [] + consumption_modes: + - CLI + - source +relations: + depends_on: [] + supports: [] + related_to: + - capability.security.iam-tooling-suite +evidence: + documentation: + - SCOPE.md + tests: + - sbom-tools.yaml + - .forgejo/ + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - Operator or automation obtains a bounded SSH certificate and maintains private + connectivity + - Operator recovers identity, custody or data with independently held recovery material + - Platform owner deploys and rolls back a workload with explicit substrate and custody + bindings + not_recommended_for: + - Current hosts differ from the retained Hetzner provisioning path + known_limitations: + - Current hosts differ from the retained Hetzner provisioning path + - 2026-10-14 architecture review estimates operational maturity separately; a registry + entry does not authorize execution or establish deployment. +promotion_history: [] +--- + +# Host convergence and security baseline + +Ansible inventory, firewall, SSH bootstrap and baseline verification. + +## Reuse boundary + +Current hosts differ from the retained Hetzner provisioning path. + +## Supported use cases + +- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity +- U10: Operator recovers identity, custody or data with independently held recovery material +- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings + +## 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. diff --git a/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-infra/registry/indexes/capabilities.yaml b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-infra/registry/indexes/capabilities.yaml new file mode 100644 index 00000000..d2aa9406 --- /dev/null +++ b/docs/assessments/netkingdom-2026-10-14/registry-stage/railiance-infra/registry/indexes/capabilities.yaml @@ -0,0 +1,23 @@ +version: 1 +updated: '2026-10-14' +domain: helix_forge +capabilities: +- id: capability.railiance.infra-provisioning + name: Host convergence and security baseline + summary: Ansible inventory, firewall, SSH bootstrap and baseline verification. + domain: financials + status: draft + owner: railiance-infra + tags: + - railiance + - terraform + - ansible + - infrastructure + - security + - netkingdom + - framework-reuse + vector: D4 / A2 / C2 / R1 + path: registry/capabilities/capability.railiance.infra-provisioning.md + consumption_modes: + - CLI + - source