# Policy Hub

Policy Hub keeps durable instruction documents separate from runtime permissions. Write and review rules in Documents, inspect enforced function access in Runtime permissions, and use Cold Storage to read saved device documents and verified history. Saving a rule does not grant a tool permission or change an operating-system sandbox.

## Choose the surface that owns the change

| Surface | Use it for | Check before relying on it |
| --- | --- | --- |
| [Documents](https://dashboard.ouros.md/policy) | Edit workspace Markdown and commit a reviewed device version | Exact path, saved content and storage status |
| [Runtime permissions](https://dashboard.ouros.md/policy/board) | Inspect reported policy revision, scopes, approval rules and spending observations | Runtime availability and the exact permission record |
| Cold Storage, from the Policy Hub navigation | Read device documents and their verified version history | Draft changes and any integrity error |

A device version and a repository commit are different records. A document can be saved locally while repository sync is unavailable. A displayed author and device signature establish document integrity within that saved history, not independent identity verification or runtime approval.

## Write rules that survive the task

[Save a durable rule](/docs/shared/write-and-review-rules) with an explicit scope, action boundary, stop condition and completion check. Keep stable instructions separate from a one-off request or a transcript. Replace a superseded rule rather than leaving both instructions active.

### Keep the document tied to its consumer

Choose the file the intended agent actually reads. A Markdown filename or a successful repository sync does not establish that every agent, existing chat or local checkout has reloaded it. The document editor labels repository sync for new Ouros chats; device saves remain local. Check the consuming task separately.

## Inspect authority before execution

[Read runtime permissions](/docs/shared/runtime-permissions) before invoking a function or changing access. Function policies, hosted-loop build/run capabilities and native operating-system permissions are separate controls. A passing document validation is not a runtime grant.

For workflow-specific actions, start with [Loop Builder's first canvas task](/docs/loop-builder/quickstart). Keep the [hosted-version lifecycle](/docs/loop-builder/version-and-run) separate from governed function actions.

## Recover without discarding either copy

If storage, signature verification or repository sync fails, [preserve the draft and reconcile its history](/docs/shared/recover-policy-documents). Do not clear browser storage or overwrite another tab merely to remove a warning.