security: retire unsafe legacy LDAP lifecycle callers
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a1346b-72a4-7d40-b8bd-8b8ca346cfa2
This commit is contained in:
parent
276b95f6ba
commit
84c5dbeec8
21 changed files with 390 additions and 1023 deletions
|
|
@ -1,5 +1,14 @@
|
|||
# NetKingdom Runtime Architecture
|
||||
|
||||
> Lifecycle update, 2026-10-14: the lifecycle tooling descriptions below are a
|
||||
> historical snapshot, not current execution instructions. Account creation,
|
||||
> pattern deletion and inferred-claims verification in the old 0019 helpers are
|
||||
> retired. Their secret handling and success assertions are not accepted evidence
|
||||
> of current safety or readiness. Use the [current owner routes](legacy-lldap-lifecycle-retirement.md)
|
||||
> and actual native receipts. Ordinary lifecycle delivery has since advanced in
|
||||
> NK-WP-0025/NK-WP-0038; independent recovery and other IAM callers remain open.
|
||||
|
||||
|
||||
**Status:** draft (initial capture for NET-WP-0018-T02)
|
||||
**Date:** 2026-06-03
|
||||
**Context:** Documents the *as-deployed* runtime after the first successful bootstrap (0015-0017) + T06-adjacent polish (0019). Not an idealized future architecture. Specific enough to guide a scratch rebuild or rehearsal without rediscovering integration details. Incorporates pragmatic audit paths and known UE integration points/gaps per the persisted assessment.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue