Use a certified SDK adapter

Open Tools and SDKs and choose a published Enforce adapter for your framework and language. Install the core package and the adapter package from the portal-generated commands.

VeriProof 1.0 does not provide a public custom-adapter authoring or certification path. Do not publish an internal integration as a VeriProof-certified adapter.

If your framework is not listed, use the core SDK to govern the application actions that need a decision. The application remains responsible for calling VeriProof and applying each result.

Qualify the integration

Confirm these behaviors with the exact package and framework versions you plan to use:

• check input before the protected action runs;
• check output before the application releases it;
• do not release a denied output;
• keep protected workflow state outside Human Review callbacks;
• stop protected work when a live Stop directive applies; and
• confirm accepted evidence appears in the intended VeriProof application.

Related documentation