A policy is how you tell Hiberden what protection your archives deserve: how long to keep them, and which destinations must each hold a copy. Everything the workspace says about coverage is judged against a policy. An archive is Covered only when every destination its policy requires has a verified copy.
Where a policy lives
A policy attaches to a Project. A new project starts without one; you assign a policy (Settings > Policies) before you archive. From then on, every archive you add to that project with Add archive is written to the destinations the policy binds (for tape, the first tape destination), with each copy tracked separately. An archive added with Find archives… arrives with only the copy that was found (see Local Folder and NAS). A disabled or retired destination takes no new copies, and Add archive says why on its row.
Destinations themselves are a shared pool across projects. Policies bind to destinations from that pool; see Projects, Archives, and Destinations.
What a policy is made of
Name. Permanent once the policy is created. Name the protection shape ("Long-term hold"), not a specific project, since many projects can share one policy.
Retention. How long archives under this policy are meant to be kept: "forever", or a span such as 7 years, 18 months or 90 days. It is a note for you and anyone auditing the catalog; nothing in Hiberden expires or deletes an archive when its retention passes.
Bindings, the required copies. Each binding is one required copy slot, tied to one distinct destination. The number of destinations is how many times the policy stores each archive: bind three destinations and every archive under the policy gets three copies, each verified on its own.
A tape binding is filled after the save: the tape copy is written from a disk or NAS copy of the archive, so a policy with tape needs a disk or NAS binding beside it. With more than one tape destination, Add archive writes the first; write the others with Write to tape in the archive's details. A tape copy the desktop app writes is checked by reading it back as it is written; after that, Hiberden 2.0 checks it again only when you restore from it, which re-hashes every byte.
That is the whole of it. A policy answers how many copies, where, and for how long, not how often they are re-read. Scheduled re-verification of disk and NAS copies is set once for the application under Settings > Verification and applies across every project. See Running a verification.
Bindings only grow in the editor
In the policy editor, bindings are add-only. Adding a destination only increases protection, so the editor allows it in place. It gives you no way to remove one: to require fewer copies, create a new policy with the smaller shape and assign it to the project. Retention can be edited, because it is a note and changes no protection. Within the editor, then, a policy's meaning does not quietly change underneath archives that were judged against it.
One path outside the editor can shrink a policy: the MCP connector, at its opt-in Full access level, exposes tools that add and remove bindings. That level is off by default, and every write the connector makes is recorded in the audit trail shown in Settings > MCP.
The starter policies
Hiberden offers three starter policies you can create with one click:
| Policy | Retention |
|---|---|
| Working | 1 year |
| Long-term hold | 7 years |
| Permanent | forever |
Starter policies are created unbound: no destinations yet. Add bindings before assigning one, or it will not require any copies and the project will show as needing setup.
Coverage is judged against the policy
Once a policy with bindings is assigned, the workspace compares the verified copies each archive actually has against the copies the policy requires. Every bound destination verified means Covered. Some but not all means At risk. No verified copies, with nothing currently being written, means Unprotected; if a copy is being written right now, the archive shows In progress instead, which is what you will see while your first copy lands. A project with no policy, or a policy with no bindings, shows Needs setup. The full set of badges and what to do about each is in Reading coverage status.