APPROVAL-WP-0007-T06: self-acceptance exception mechanism (backlog, founder direction)

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:14:01 +01:00
parent 0a61207b2f
commit 9287fb33fe

View file

@ -133,3 +133,25 @@ live service.
## Founder decision 2026-10-31
Approved by the founder (`proposed` -> `ready`) after the NK-WP-0056-T02 owner answers (hub decision 19afd15e).
## Self-acceptance as an exception with handlers (backlog)
```task
id: APPROVAL-WP-0007-T06
status: todo
priority: low
```
Founder direction, 2026-11-01 (gate-house GH-DEC-2026-026 addendum, relayed by the net-kingdom coordinator).
Today, under `human_control`, an entry whose subject equals `binding.actor` is refused (403, `5c45d3c`), and that
stays the default.
Later, self-acceptance may become a declared exception on the approval:
- explicitly accepted by the self-accepter;
- with exception handlers bound to it, such as eligibility exclusions (trainees) or a publication plus cooldown
window in which named others can veto before the approval becomes valid.
The engine would hold the exception and its window and refuse validity until the window closes without a veto.
Doctrine on which classes admit it comes from gate-house (GH-WP-0005-T07). Not to be implemented now.