Documentation
A public overview for engineering, security, compliance and operations teams. Prudenze combines workload identity, business authority, current evidence, policy and verified execution in one control chain.
Identity & authority
Intent & constraints
Current evidence
Applicable policy
Authorization
Controlled execution
Verification & evidence
Interoperability
These interfaces are exercised through deterministic adapters and tests. Each one remains inside Prudenze's authority boundary: external identity, policy and telemetry enrich the control chain without bypassing Guardian or the GDO record.
View the integration catalog →JavaScript SDK 2.11.0 · GenAI conventions snapshot bcc7f9c
Prudenze exchanges standards-aligned OpenTelemetry GenAI traces and correlates them with decisions and GDO records.
Telemetry is observability evidence; it does not replace the governed decision record or authorize an action.
SPIRE 1.15.3
Prudenze accepts SPIFFE/SPIRE workload identity as input to Arkon authority and delegation evaluation.
A valid workload identity establishes who is running. It does not grant business authority by itself.
SDK/CLI 4.13.0 · language 4.5
Prudenze incorporates Cedar authorization decisions into Guardian's final action decision.
A Cedar permit is policy input and does not automatically equal a Prudenze ALLOW decision.
OPA 1.21.1 · Rego v1 · WebAssembly
Prudenze incorporates OPA/Rego decisions into Guardian's consequential-action controls.
Guardian retains the final ALLOW, ESCALATE or DENY decision and fails closed when required policy input is unavailable.
Containerized deployment with an isolated customer environment.
Docker or Kubernetes within customer-controlled cloud or infrastructure.
Local infrastructure with zero-egress capability and customer identity provider.
Prudenze does not expose private implementation details, credentials or customer configurations through public documentation.
Request controlled documentation access