Evidence notes

Proof-backed notes from AI implementation work.

Short public notes from Verduona implementation work: what was changed, how it was verified, and which operating rule it supports.

Public proof

Form-first intake replaced email-only conversion paths

Verified 2026-07-08

Verduona now routes audit, managed-ops, finance-ops, BOZP beta, and checkout-corridor interest through a web intake form instead of pricing-page mailto links.

  • Live /en/get-started/ renders action="/api/intake", name="interest", consent, and scoped interest choices.
  • Live /en/pricing/ contains get-started intake CTAs and no mailto:, no /cdn-cgi/l/email-protection, and no cal.com conversion link.
  • A synthetic POST to /api/intake returned HTTP 200 ok:true; the synthetic KV record was deleted afterward.
Open intake
Implementation playbook

Start with bounded workflows, not a generic AI platform promise

Updated 2026-07-08

The pricing and audit pages now describe the same adoption path: audit the workflow, train operators, pilot one bounded lane, then operate only the parts with clear review ownership.

  • AI Implementation Audit is priced and described as the first paid unit before broad rollout.
  • Implementation Sprint is scoped as one bounded internal workflow, agent lane, voice demo, or orchestration proof.
  • Managed AI Ops remains downstream of workflow count, review depth, integration surface, and support window.
Review offers
Boundary case note

BOZP evidence work is preparation, not compliance certification

Verified 2026-07-08

The BOZP lane is now framed as a private-beta evidence workspace with synthetic data first, qualified human review, and explicit ADR/radiation-protection boundaries.

  • The BOZP product page states outputs are not legal certification, official sign-off, or a replacement for qualified professionals.
  • The pricing page says payment, checkout, or inquiry does not grant BOZP workspace access until Sphere approval exists.
  • ADR is treated against the current agreement edition, and radiation protection is a separate specialist lane.
Read BOZP boundary
Commerce proof

Public checkout is request-gated until Sphere entitlement proof is green

Verified 2026-07-08

Verduona can describe products and services publicly without implying payment equals runtime access. Commerce remains separated from Sphere entitlement and workspace provisioning.

  • The shop page states products authorize against Sphere entitlement state only.
  • The pricing page describes a request-gated checkout corridor and signed Sphere bridge.
  • An order is a paid request. A named Verduona person confirms scope. Orbit is not sold.
Open shop status
Reusable playbook

Evidence-first AI adoption checklist

  1. Name the workflow and the human owner before choosing tooling.
  2. Separate public interest, payment, and runtime entitlement.
  3. Use synthetic or metadata-only examples before real customer or employee data.
  4. Define the reviewer, acceptance criteria, escalation path, and evidence cadence.
  5. Expand only after the pilot leaves reusable proof: route checks, form capture, rollback path, and owner handoff.
See training options