The full incident scenario now runs against the assembled daemon: an
operator goal becomes a want to reduce uncertainty, an investigation
intention and a diagnosis plan; telemetry is read; logs need authority,
so a scoped request with risk, mitigation and fallback is raised and the
intention is blocked until an operator grants it; the logs are read with
personal data masked and summarised back into cognition; the operator
supplies the judgement that a restart should help; a standing commitment
turns the restart into a request for approval; after approval the typed
capability runs and health is verified rather than assumed; the fault
persists, so a prediction error weakens the supporting belief, the plan
is replanned into an escalation that reuses the live log grant and does
not repeat the restart; once the database is fixed a second approved
restart verifies, the procedure is learnt, and "Why did you restart
atlas-worker?" is answered from the recorded chain and scores as
supported.
Changes the scenario exposed:
- New operator goals are raised by the goal monitor, so a cycle runs and
wants are derived from them.
- Intentions link live beliefs about their action's target, so a failed
expectation is evidence against the belief it rested on and the plan
lists it as an assumption.
- Reconsideration reacts to a plan's own intention only; a subordinate
"obtain approval" intention shares the plan and previously caused the
parent's plan to be closed.
- The harness accepts a clock for the executor's verification windows.
Further failure-mode tests: a retracted assumption replans a waiting plan
away from the restart and withdraws its approval request; conflicting
commitments are raised once in a cycle while both stay represented.
Andy Dixon
7d67745ff8