Skip to content

Delivery Track

Plan-and-deliver documentation for the integration partner or customer PM team adopting Evospin. The pages here describe the how and when of bringing the platform up in your environment — phases, prerequisites, risks, acceptance criteria, and a final pre-launch checklist.

These pages do not duplicate engineering content. For architecture, request flows, observability, security findings, and runbooks, see the engineering track. For commercial framing, NFR/SLA, and the integration option matrix, see the business track.

Quick references: Glossary — terminology · FAQ — common questions · Service catalog — operator inventory · Portal audit — verification report · Inventory — every doc in the portal.

Read order

  1. Phased Rollout — 8 phases from Discovery to GA, with durations, activities, deliverables, and acceptance gates. read time: 18 min
  2. Dependencies — what the customer must have in place (infra, third-party accounts, people, legal, internal decisions) before each phase can start. read time: 8 min
  3. Risks — 18 specific delivery risks with probability, impact, mitigation, and owner. Read this before quoting a timeline. read time: 10 min
  4. Acceptance Criteria — the objective, testable bar each phase must clear. Sign-off owner and blocker-vs-warning grade per criterion. read time: 10 min
  5. Launch Checklist — final pre-GA checkbox sweep grouped by infrastructure, secrets, observability, performance, security, operational, compliance, and customer-side concerns. read time: 8 min

Who should read what

Role Start with Skim Reference
Customer PM / delivery lead Phased Rollout, Dependencies Risks, Acceptance Criteria Launch Checklist
Customer engineering lead Phased Rollout §3-§5 engineering track docs/architecture.md, docs/onboarding/day-one.md
Customer security / compliance Risks, Dependencies §legal Acceptance Criteria docs/security-register.md, docs/security-findings/
Customer SRE / on-call Phased Rollout §7-§8, Launch Checklist Acceptance Criteria docs/runbooks/, docs/observability.md
Evospin handover engineer All All CLAUDE.md

How this track was assembled

Each page is grounded in code or existing documentation. Where a fact could not be grounded in under two minutes (typical lead times for vendor approvals, customer-specific decisions, jurisdiction-specific compliance), the placeholder {{TBD}} appears with enough context that the customer's team can fill it in during Discovery.

Conventions: durations shown as low / typical / high calendar-week estimates. "Customer-side" means an action that Evospin's handover engineer cannot perform on the customer's behalf (account creation, legal opinion, brand decision, etc.).