vta-policy 0.3.19

VTA policy subsystem — the regorus (Rego) engine, the default policy bundle, consent model, and decision evaluators
docs.rs failed to build vta-policy-0.3.19
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: vta-policy-0.3.17

vta-policy

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

  • engine — the 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 workspace. Apache-2.0.