1674ea550d
Multi-tenancy is part of the IT-security framework NetKingdom provides, so it belongs beside the IAM Profile and the tenant-engine boundary contract rather than in the work-factory canon. Operator decision. Relocation surfaced two things a review would have caught embarrassingly late. NetKingdom's accepted platform-identity-security-architecture has used the word plane since July for a trust and deployment layer - bootstrap, platform control, tenant. This framework was using the same word for an independent dimension of concern. Two senses of one word in one canon is precisely the concept-ownership collision the estate is careful about, and the newcomer yields: they are now axes. The rename is also just better, since a posture vector is a point in five-dimensional space. That same document also disproves the framework's opening line. It has described the trust model, the tenant model and a capability progression since 2026-07-23, so the claim that the estate had never written down what it was building was wrong. The accurate and narrower claim is that nothing said how far a given service had got, or could hold several answers at once. Stub left behind so the ADR-008 identifier resolves. The renderer moved to policy-nexus, which owns publication. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| architecture | ||
| constitution | ||
| projects | ||
| standards | ||
| tpsc | ||
| values | ||