feat: let a task wait on an outside event, and hold a task whose effect is not settled

PLAN.md

@@ -68,7 +68,7 @@ Landed so far:
 |---|---|---|
 | 0 | #69 | Nothing |
 | 1 | #71 | Nothing |
-| 2 | #73, and attempt keys for a claim and a completion in #77 | An attempt key on the other operations; an uncertain external effect blocking reassignment; waiting on an outside event as a state; the record's remaining fields (`parent`, `scores`, `implements`, `reversibility`, `artifacts_touched`, `policy_context`) |
+| 2 | #73, attempt keys for a claim and a completion in #77, and waiting, unsettled effects and the remaining fields in #81 | An attempt key on the other operations; a connector that serialises external actions and reconciles them; taps that report the events tasks wait on; rules that read `scores`, `implements`, `reversibility` and `artifacts_touched`; the hold of an unsettled effect follows a task's `origin` only, so the same work filed anew under no origin is not held; a task's classification does not rise to its holder's label, so a session that has read above its task records no effect and no wait on it; a task held under a live lease when its continuation finishes is left to its holder, and is on offer again if that lease runs out |
 | 3 | #74 | A suite that gates a version of a definition; the data scope enforced; a definition required by default, once the system's own filings name one; tools offered a few at boot and the rest by search |
 | 6 | #78 | `check_policy` selecting rules by the action; the unused-rule check over one review period; the approver of an exception checked against the layer breached; a new version of a rule keeping its place under the ceiling; a decision that survives an enforced module that fails; the author and the date of an imported rule not trusted; a session that reloads the policy when a rule changes; a verified rule that stays in force while its next version waits for review; a denial that names no policy counted for the module that made it, in the rates and the lint |
 

README.md

@@ -110,10 +110,11 @@ two weeks. It is also the reason that none of it is the production shape.
   - CPU or memory limits on the sandbox
 - **The task record, in part.** A claim has a generation, and the ledger refuses a
   holder that gives an earlier one. A task can be `blocked` on a task that it depends on.
-  A claim and a completion can carry an attempt key. These parts are not built: an
-  attempt key for the other operations, a block on a new claim
-  while an external effect is uncertain, and a `blocked` state for a task that waits on an
-  outside event. The generation does not prove who the caller is.
+  A claim and a completion can carry an attempt key. A holder can give a task up until an
+  outside event comes, and a task with an external action that is not settled goes to no
+  other session. These parts are not built: an attempt key for the other operations, a
+  connector that makes external actions in sequence and settles them, and taps that
+  report the events. The generation does not prove who the caller is.
 - **Task definitions, in part, and autonomy levels.** A task can name a task definition.
   It then takes the checks of the definition, and its holder can call only the tools that
   the definition declares. Triage requires a definition only when the grants say so,