PH5.1 — Locks: every plan_lock type with checks, GET /locks, clear, expiry, E_LOCK_VIOLATED #33
Labels
No labels
ready-for-agent
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
Reference
patrick/Polaris#33
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
Row PH5.1 in
docs/12-implementation-plan.md(branch, owned paths and doc section are defined there).What to build
All
plan_locktypes (pin, forbid, fix-time, rejection, …) are created through domain services with per-type validity checks, listed viaGET /locks, cleared with a reason, expired by a worker job, and violations are reported by the validator (E_LOCK_VIOLATED).Acceptance criteria
E_LOCK_VIOLATEDwith the lock in params/clearrequires a reason and is auditedBlocked by