What happens after you sign

Week 0 — paperwork landed, no surprises

• Order Form + MSA + DPA signed and counter-signed. We use the standard templates published at /legal/terms and /legal/dpa. If your procurement team needs a markup, we negotiate in 10 business days or less.
• Engineering kickoff call (60 min) with your AI / data platform team. We walk : what to instrument, where the chain lives, how the signing key is managed, what the support-session protocol looks like, the first-30-days success criteria.
• Slack / Teams channel shared between Aryamind and your team for asynchronous questions during the pilot. Async-first ; no expectation of business-hours coverage on either side outside support windows.

Weeks 1–2 — instrumentation

We work alongside one of your engineers to drop the SDK into the AI workflow you've scoped in the Order Form. The integration footprint :

• One SDK call at the inference site — typically 5–15 lines, depending on language and framework.
• One SDK call at the human-oversight site — wherever your reviewers approve, override, or escalate AI decisions. This is the Article 14 binding event.
• Producer key creation on your side : ECDSA P-256, stored in your secret store of choice (HSM, AWS KMS, GCP KMS, Vault). We provide the runbook ; you keep custody.
• RocksDB chain dir on a durable filesystem (typical : an EBS/PD-SSD volume mounted at /var/lib/carvetrace/chain). Self-host the operator UI by running carvetrace serve behind your reverse proxy.
• TSA cadence configured — typically hourly RFC 3161 anchors during the pilot. Production cadence is tuned to your retention + cost profile.

Checkpoint at end of week 2 : first signed AI inference event lands on the chain. We verify it together on a screen-share.

Weeks 3–7 — real chain, real evidence

Your AI workflow runs as it normally would. The SDK emits events. The chain accumulates. At week 4, we generate the first evidence coverage report against the real chain and walk the dossier with your AI Act program owner.

• Weekly office hour (30 min) with the Aryamind engineering team — show up with whatever's blocking you, leave with it unblocked.
• Coverage report walkthrough at end of week 4 : we walk every dossier with you, point at the AI/human story per row, explain how an auditor would read it.
• Stress test at end of week 6 : we tamper a bundle and walk you through how the verifier catches it. Your internal audit team is invited.

Checkpoint at end of week 6 : a real evidence bundle covering a real production week is in your hands.

Week 8 — auditor sign-off

Hand the week-6 bundle to your internal auditor. They open verify.carvetrace.com and verify it themselves — no CarveTrace login, no API key, nothing from us. Their verdict matches the verdict the regulator's verifier would produce.

If the auditor signs off, the pilot is successful. Pilot fee credits back against your first annual subscription term. Welcome to CarveTrace.

Beyond week 8 — ongoing cadence

• Quarterly evidence bundle — generated on a schedule that fits your audit calendar. Your operator UI ships a "Generate bundle" button ; we automate the cadence if you want.
• Monthly office hour — Aryamind product + engineering, 30 min, your team's questions.
• Two-week support response on email for Starter, one-business-day for Growth, on-call SLA for Enterprise. Detail in your Order Form.
• Major releases include a 60-day version-upgrade window with a migration guide and an upgrade-help office hour.
• Annual review at the end of each subscription term : what shipped, what's coming, what's evolving in your AI Act program. Renewal scope (Starter → Growth → Enterprise) sized to where you actually are.