What verification means here

The source, execution limits and levels of evidence behind the utilities, integration recipes and simulations.

Maintained by Oveyon · .md

One implementation, several representations

The utility registry is used by the browser worker and local tests. Pages display that function’s source. Recipe files feed the HTML, Markdown, context package and downloadable starter; they are not independently rewritten for each format.

Original MDX is retained as inert provenance evidence, never executed as an imported page. Selected files are checked against their Git blob identifiers at the recorded upstream commit. The recovery manifest distinguishes verified source from unknown archive and traffic evidence.

Levels of evidence

Local: deterministic transformations, request construction, signing, persistence and state transitions are exercised with synthetic fixtures.
Contract review: the examples were checked against the captured Oveyon OpenAPI and official reference. This does not establish a successful authenticated response.
Authenticated sandbox: not executed for this release. Sandbox consumes quota/rate while freezing delivery.
Controlled real delivery: not executed for this release. An accepted API request or an SMTP acceptance does not establish inbox placement.

The code lab

Only curated functions run. Visitors edit JSON data, never JavaScript. The main thread and worker both validate input. The lab caps input at 64 KB, output at 128 KB, depth at 12, total fields and elements at 1,000 and any string at 16,000 characters.

Each run uses a worker with a two-second timeout and explicit cancellation. Its response policy blocks network connections. These controls bound this example but are not a hard browser memory quota. Errors and output are rendered as text.

Reference pages

Some originals take callbacks, the DOM, timers or the runtime, which JSON cannot carry. Their pages show the function and a usage snippet. Every line marked → is executed — in Node.js 22, in headless Chromium against the markup on the page, or both — and its result is compared with the value shown. Lines marked e.g. are illustrative, because clocks, randomness and platforms vary.

Two pages, reloading and redirecting to HTTPS, would navigate away during a test. They are reviewed, not executed, and say so.

The delivery lab

Every timeline and export says “Simulation — no email is sent”. The clock is virtual and its timings are illustrative. The application schedules a retry; Oveyon handles provider-side deduplication within its documented window; the recipient server performs SMTP acceptance.

The simulator is not a production trace, deliverability experiment, latency benchmark or evidence of an authenticated integration.

Corrections and review

Substantive changes update the changelog and invalidate the affected example’s previous evidence until its checks are repeated. There is no publication-frequency target and no automatic date refresh to imply new verification.

Use the linked official contract when adapting an integration. Report a site issue through the maintainer’s support page; omit credentials, real recipient addresses and message content.