STATE-WP-0101-T01 done: decisions capability moves to hub-core; implementation rules accepted
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s

Founder decisions 2026-11-01 relayed by the net-kingdom coordinator.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 5502@bnt-lap001
Assistant-Session: 68b3b02f-5d0f-4e71-8421-796f62e50196
This commit is contained in:
tegwick 2026-11-01 09:11:00 +01:00
parent 0b473c1bda
commit c5504d8230
2 changed files with 14 additions and 6 deletions

View file

@ -226,8 +226,12 @@ coordinator; recorded here as relayed, not as C1 evidence.
trigger, C3 reserved and not usable) was accepted by the founder the same day. The hub sets no
keyword-based class floor; classes are declared by the creator under that doctrine. The
existing financial/legal auto-escalation stays as it is and does not set a class.
4. **Not decided; open.** The keep/move disposition of the decisions capability remains with the
founder. The implementation stays small and portable (section 6) so either answer is served.
4. **Keep, move to hub-core** (given later on 2026-11-01, relayed the same way). The decisions capability and
its evidence links survive the retirement and move to hub-core unchanged (section 6 keeps them portable).
The founder also accepted the four rules added during implementation: C3 refused while reserved; evidence fields
only through the evidence route; frozen class after resolution or supersession; no PATCH reopening of a decision
resolved by evidence.
## 9. Asks of other owners