vta-policy 0.2.2

VTA policy subsystem — the regorus (Rego) engine, the default policy bundle, consent model, and decision evaluators
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
# vta-policy

The VTA's policy subsystem, extracted from `vta-service`.

- **`engine`** — the [regorus]https://crates.io/crates/regorus (Rego) policy
  engine: compile + evaluate.
- **`defaults`** — the default policy bundle + config-driven consent reconcile.
- **`consent`** — the DTTE consent model (approvals, guards, delegation).
- **`input`** / **`types`** / **`effects`** — policy input construction, the
  shared decision types, and effect/state-pin descriptors.
- **`storage`** — policy + active-policy keyspace storage.

Depends only on `vti-common`, `vta-config`, and `vta-keyspaces` — never on
`vta-service`. `vta-service` re-exports it as `crate::policy`, so every existing
`crate::policy::…` path is unchanged.

Part of the [Verifiable Trust Infrastructure](https://github.com/OpenVTC/verifiable-trust-infrastructure)
workspace. Apache-2.0.