Add SDK decision context
Send the facts needed to evaluate a rule, explain its decision, and record the application outcome. Use only fields supported by your installed 1.0.0 package.
Choose the policy boundary
- Use the core SDK for application-owned model calls, tools, workflows, and business actions.
- Use an Enforce adapter only for the framework operation listed in its package documentation.
- Do not send the same operation through both paths.
The framework coverage guide lists all 35 adapters and their exact boundaries. Calls outside those boundaries remain application-owned.
Send only required facts
Add a fact when an active rule or review workflow needs it:
| Fact | Send it when |
|---|---|
| Action | The rule must identify the proposed operation. |
| Application facts | The rule needs typed business data supplied by your application. |
| Industry values | The rule uses a value from the SDK’s maintained industry vocabulary. |
| Initiator identity | Authorization depends on a verified user or workload identity. |
| Review profile | The action can pause for a documented human-review workflow. |
| Outcome | The application has recorded what actually happened. |
Resolve identity from the authenticated application or workload context. Do not trust prompt text, model output, or tool arguments as identity.
Content capture is off by default. Enable it only when the rule or reviewer needs the content and your data policy permits storage.
Use the maintained language guide
Each language guide shows the current constructors, options, review flow, Stop handling, Edge Gateway path, and server path:
Use @veriproof/sdk-core with any of its 11 Enforce adapters.
Use veriproof-sdk with any of its 8 Enforce adapters.
Use Veriproof.Sdk.Core with any of its 5 Enforce adapters.
Use the Java core SDK with any of its 6 Enforce adapters.
JavaUse the Rust core SDK with any of its 2 Enforce adapters.
RustUse the Go core SDK with any of its 3 Enforce adapters.
GoCopy package-source settings and installation commands from Tools and SDKs. Do not reuse commands from an older package or another tenant.
Verify the result
- Run one allowed test action from a Development application.
- Open its exact decision link and confirm the operation, rule version, verdict, and deployment mode.
- Open SDK Health and confirm the required fields arrived.
- Run one denied action and confirm its protected side effect did not occur.
- Test review, Stop, and restart recovery when those controls apply to the workflow.
A recorded event does not prove enforcement. Confirm that the protected operation passed through the core SDK or an adapter’s documented Enforce boundary.