Maity: Board

Contract: presets hierarchical, solo, decentral, custom; pool and hybrid removed (§6.1 policy.preset)

tsk-8g6agk5dk3k9 open

Today pool, decentral and hybrid are named shells with the hierarchical filling (§6.1). Oliver, 2026-10-29: write them out.

decentral (Oliver): a swarm without a lead. Everyone works and coordinates with the others, but nobody gives direct instructions; each member chooses their cards by what makes sense to them.

Contract work (oz-agent-a): which policy fields decentral fills (self-claim; no coordinator gate, coordinator null; done_authority by peer review; contract_arbiter?; no line:lead manager; who arbitrates a dispute), what the hub does differently (no assignment by agents? assignment only as a proposal the holder accepts?), how the briefing/rules text tells agents to pick by sense and coordinate, and what stays human (tags, consent). Oliver, 2026-10-29 (second answer): pool and hybrid are removed (alpha rule: no shells). The presets are hierarchical, solo, decentral and custom. Custom (Oliver, third answer): users create their own named sets (a name plus a filling of the policy fields) and apply them like a built-in preset. Proposal: a set belongs to a person or an organisation and can be used for all of its projects; a project applying a set copies its filling (a later change to the set does not move existing projects); a project whose fields were changed by hand shows that it deviates from the set it came from ('derived from set X, differs in: …'). Confirmed by Oliver ('super!').