Legal Hold Flag
A soft, reversible hold flag that marks a resource as under legal hold — with content-hash integrity, reason, and actor tracking — without claiming to be e-discovery or an evidence locker.
The problem
/ 01When a resource must be frozen in place pending legal action, you need a lightweight flag that records the reason, case, and actor, reports whether a resource is currently held, and supports a one-shot release with an audit note — while being honest about not being a full e-discovery or evidence system.
What it does
/ 05Places a hold flag on a resource (resourceId, optional resourceType/reason/caseId/actor/meta).
Returns a holdId, contentHash (SHA-256 over the hold payload), and status.
Checks whether a resource is currently held, returning held flag, activeHoldCount, and activeHoldIds.
Releases a single hold one-shot with an optional note and actor — status transitions to released.
Lists all holds and fetches a full record by hold ID.
Private pilot adds
/ pilotPilot-ready: durable legal-hold store available under NDA with a /v1 API for private pilots. The public studio card runs against /demo (ephemeral, soft-flag only).
Who it’s for
/ 03- Legal ops placing and releasing holds
- Compliance engineers auditing hold state
- IT stewards checking is-held before mutation
In context
/ 01Complements Retention Expiry Clock (expiry scheduling), Consent Receipt Registry (consent lifecycle), and Escape Hatch Notarization (exception records).