net-kingdom-architecture proposed · draft-1 net-kingdom reviewed 2026-08-18generated from canonical source — do not edit

NetKingdom architecture

Source: net-kingdom · docs/architecture/net-kingdom_v0.1.md · ba5d8642e91a31055eafdaef6993d779f6af7e06

Review due: 2027-02-18

About this document

First-wave arc42 for NetKingdom: the estate's identity and tenancy security core. Chapter 9 lists governing ADRs and standards; it does not paste them.

01Introduction and Goals

NetKingdom is the open security core for DevSecOps on Kubernetes. It owns identity, tenancy posture, and the contracts that flex-auth, key-cape, tenant-engine, and railiance workloads implement.

1.1 Requirements Overview

  • One IAM profile, versioned, owned here.
  • Tenancy described as graduated axes, not a single on/off switch.
  • Workload packaging and credential vending have explicit boundaries.

1.2 Quality Goals

  1. Provider-neutral identity contract.
  2. Recursive multi-tenant authorization that implementers can declare.
  3. Honest about what is not there yet (Tenancy Posture).

1.3 Stakeholders

RoleConcern
net-kingdomCanon owner for identity and tenancy.
flex-auth / key-cape / tenant-engineImplementers of the contracts.
railiance-masterWorkload packaging on the rail.
the-custodianFederation; does not redefine these concepts.

02Architecture Constraints

N/A for this stub.

03System Scope and Context

In: IAM profile, tenancy posture, tenant/user-engine boundaries, credential management, playbook capability contract, NetKingdom ADRs. Out: publication (policy-nexus), rail runtime (railiance), estate work-factory (the-custodian).

3.1 Business Context

Security here is dynamic and adversarial. The system exists so implementers share one contract instead of copying a neighbour.

3.2 Technical Context

Consumers: flex-auth, key-cape, tenant-engine, audit-core, rApps. Published today: Tenancy Posture /standards/tenancy-posture/v0.1/.

04Solution Strategy

N/A for this stub — recursive multi-tenant identity (ADR-0006) and the IAM profile ownership rule (ADR-0011) are the spine.

05Building Block View

5.1 Level 1 – System/Top-Level

N/A for this stub.

06Runtime View

N/A for this stub.

07Deployment View

N/A for this stub.

08Cross-Cutting Concepts

N/A for this stub.

09Architecture Decisions

SourceStatusNotes
canon/standards/tenancy-posture_v0.1.mdproposedPublished. First publication of this site.
canon/standards/iam-profile_v0.3.mdacceptedCurrent profile. Needs a unique publication id (v0.2 still shares netkingdom-iam-profile).
canon/standards/iam-profile_v0.2.mdshould be supersededv0.3 supersedes it; front-matter still accepted.
docs/adr/ADR-0006ADR-0015see filesIdentity, orchestration, IAM ownership, tenant roles, packaging. Publish after NK-ADR-* prefix and review metadata.

Custodian ADR-008 is superseded by Tenancy Posture and is not current.

10Quality Requirements

N/A for this stub.

11Risks and Technical Debt

N/A for this stub. Residual: IAM Profile id collision (WP-0003 packet).

12Glossary

TermMeaning
IAM ProfileProvider-neutral OIDC contract owned here.
Tenancy PostureGraduated axes for describing multi-tenancy.
Tenant-engineLifecycle and capability roles for tenants.