17 lines
995 B
Markdown
17 lines
995 B
Markdown
|
# Root and recovery
|
||
|
|
|
||
|
|
For platform-root the reference model emits ROOT_AUTHORIZATION_REQUIRED. Prepare
|
||
|
|
a bounded recovery case for the human root steward: scope, objective, failed
|
||
|
|
lower-authority paths, alternatives, evidence, duration, and recovery checks.
|
||
|
|
No agent, scheduler, or knowledge adapter grants itself root or treats a standing
|
||
|
|
credential as authority. Actual activation and execution follow the human-owned
|
||
|
|
recovery procedure and current governance mode.
|
||
|
|
|
||
|
|
Root evidence survives the authority that exercised it. Explain after recovery
|
||
|
|
which missing delegation, capability, or contract would prevent recurrence.
|
||
|
|
SOVEREIGN @ a limited scope is not automatically platform L4; ask which boundary
|
||
|
|
is involved. Do not equate all administrative tasks, host root, and platform-root.
|
||
|
|
Unknown scope is a question for the delegator, not a reason to try a credential.
|
||
|
|
|
||
|
|
Source owner IDs (cite the relevant owner, not an invented umbrella): `emergent-security`, `security-canon`, `the-custodian`.
|