Integration Recipes

Integration Recipes

These recipes show how to connect external applications to DigiEmu verification workflows without hiding the verification boundary.

They are integration patterns, not new normative DigiEmu APIs. Adapt them to the authoritative interface and contract version published by the technology you integrate.

Recipes

• Verification Adapter Pattern — isolate DigiEmu behind an explicit request/result boundary.
• Python Consumer Pattern — consume a structured verification result conservatively.
• TypeScript Consumer Pattern — validate result state before application code accepts it.
• Verification Receipt Storage — preserve results and evidence references without rewriting history.
• AI Output to Evidence — keep immutable model output separate from later review or correction.

Before integrating, review Reference & Contracts and the Contract Integration Checklist.