Skip to main content

Design-partner pilot

The pilot is a joint product-design and technical-validation exercise for one critical workflow. It uses an isolated environment and test assets to produce an evidence-backed integration decision before production planning.

Start with a review of one real operation. After both teams identify a useful validation question, the founding partner program offers scoped free validation for three selected teams, with up to two scoped lifetime software licences for qualifying partners.

Why participate​

The partner receives an authority and bypass map, an enforceable control design, a tested high-threshold authorization profile, independently reviewable evidence, and an estimate of the integration and operating work required for a follow-on integration. The engagement is intended to answer a product and purchase question, not only demonstrate cryptography.

Objective​

Select one real privileged workflow and validate how Luvion integrates with the partner's existing stack to make authorization explicit, harder to bypass, and independently reviewable.

  • one operation type, such as an upgrade, signer rotation, mint/burn limit, or emergency pause;
  • one testnet or isolated non-production environment;
  • synthetic data or test assets;
  • one frozen policy, role map, and acceptance matrix;
  • one existing execution system, such as Safe, a timelock, or a partner API.

Four phases​

PhaseJoint workOutput
1. DiscoverMap authority, workflow, bypass paths, failure modes, and evidence needsUse-case and threat-model brief
2. DesignFreeze intent fields, roles, threshold, policy, adapter boundary, and test casesInterface and acceptance matrix
3. ValidateRun approvals, authorization, failures, retries, recovery, and evidence exportReproducible non-production evidence package
4. DecideReview gaps, integration cost, operating model, and production blockersGo, revise, or stop decision

Acceptance criteria​

The exact operation is bound to one intent; unauthorized, altered, expired, replayed, and conflicting requests fail closed; each required role uses a separate credential; idempotent retries return one unambiguous result; and terminal evidence supports independent review.

Partner contribution​

The partner provides a workflow owner, a technical or security reviewer, a non-production integration surface, sample policies, and written feedback on the acceptance results. Luvion provides the control plane, authorization profile, adapter design, test scripts, evidence export, and known-limitations record.

Commercial boundary​

The design-partner phase uses a time-boxed and narrowly scoped structure. The pilot identifies a valuable operation and its bypass paths, tests execution constraints within the agreed scope, defines key and data responsibilities, and records remaining integration work. The results inform the audit, monitoring, infrastructure and operating plan for production evaluation.

After validation​

The founding program waives Luvion's design-validation service fee for the agreed pilot. At the end, both teams can stop, agree further validation or scope a follow-on integration. There is no automatic paid conversion.

Production Adapters, infrastructure, ongoing services and any licence waiver are defined separately. Scope and fees must be agreed in writing before chargeable work starts. See the founding program for eligibility and the lifetime licence boundary.

Working documents​