Adoption path

From hosted scan to embedded standard layer.

Adoption should move through product proof, low-friction integration, partner deployment, and conformance — across every pack family, not just one.

Phase

What must exist

Why it matters

1. Product proof

Documented cases and measurable repair outcomes inside multiple pack families.

Shows the engine solves repeated customer pain before broad rollout.

2. Hosted adoption

Free scan, one-case repair, reviewer simulation, and workspace reports.

Lets adopters start without engineering work.

3. Productized integration

Widget, plugin adapters, API / SDK, and profile-aware outputs.

Lets the engine leave the website and enter live workflows.

4. Partner deployment

White-label shell, partner program, governance, audit, and co-branded reports.

Lets agencies and products resell or embed Vraimony safely.

5. Conformance

Profiles, vectors, schema versioning, and compatibility checks.

Lets adoption scale without silent drift.

6. Platform adoption

Recurring workspace usage, partner integrations, and standards-like language around faults and repairs.

Turns the engine into a real layer others depend on.

Portable scores make adoption easier because partners do not need a full case UI first.

Adopters keep coming back when the engine tells them what to fix next.

Partner-safe outputs reduce friction without creating a hidden black box.

Conformance vectors stop partner drift before it becomes a support burden.