---
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
  - Creating LLDAP groups or enrolling MFA. Service-access groups are
    identity-provisioner POST /v1/groups/ensure. Second-factor enrollment is
    user-engine / privacyIDEA.
  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
  - docs/directory-group-binding.md
  consumption_modes:
  - CLI
  - source
relations:
  related_to:
  - capability.security.credential-lifecycle
  - capability.security.iam-tooling-suite
  - capability.railiance.platform-services
  - capability.identity.user-engine
evidence:
  documentation:
  - SCOPE.md
  - docs/construction-plan-format.md
  - docs/directory-group-binding.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
  - Directory groups are not created here. See docs/directory-group-binding.md.
  - 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)
- [docs/directory-group-binding.md](../../docs/directory-group-binding.md)

## Service-access groups

ops-mason names the group in the plan. net-kingdom identity-provisioner creates
it with `POST /v1/groups/ensure` inside the provisioner pod. user-engine does
not write LLDAP groups; it is the account and MFA journey, including TOTP
enrollment at `https://pink-account.coulomb.social/`. The call does not enroll
a factor and does not attach OpenBao policies. Reserved prefixes
`tenant`, `netkingdom-`, `net-kingdom-` and `lldap_` are refused. Details:
[docs/directory-group-binding.md](../../docs/directory-group-binding.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.