wiki: valet / over-capacity mode; 'full' is a soft operator policy

Capture that refusing at capacity is the default, not absolute: an operator
may opt into valet over-capacity (customer hands over keys, operator stacks
the car into custody). Manned-only, new custody/session shape. Deferred;
not built into the entry flow. Made capacity-occupancy's FULL gate a soft
policy knob.
This commit is contained in:
2026-06-15 18:32:40 +02:00
parent 8c2cf93067
commit 648d3254d6
4 changed files with 73 additions and 3 deletions
+9 -1
View File
@@ -33,8 +33,16 @@ editable and drifts; the chain is the truth). Spaces-free = `capacity − occupa
loop count, or the [[opencv-anpr-service|vision]] count) reconciles it — surfaced as an anomaly,
not silently corrected.
## "Full" is a soft, operator-configurable policy
Refusing at capacity is the **default**, not an absolute. An operator may opt into
**[[valet-overcapacity|valet over-capacity]]** — accept the car into operator custody (keys handed
over, stacked beyond the marked count) instead of refusing. So the FULL gate is a policy knob
(refuse vs. valet-accept), set by the operator per site. Valet is a manned-mode feature with its
own custody/session shape — see [[valet-overcapacity]] (deferred).
## Open
- Whether "FULL" is a hard block or a soft warning (operator can wave one in) — operator policy.
- Zone/level granularity at launch vs. single capacity number.
- Reserve-for-permits threshold.
- The valet over-capacity mode + custody model ([[valet-overcapacity]]).