Pilot screening — not an automated intake form
Pilot intake template
Preview template for controlled pilot conversations
Purpose
This template helps you summarize one recurring workflow before a controlled SDVM pilot screening conversation. It is not a sales form, a hosted submission portal, or a guarantee of pilot acceptance.
When to use it
Use it when you want to check whether your workflow may be ready for a narrow SDVM pilot — before sharing traces, logs, or metadata. Complete the sections you can; unknown fields are acceptable at screening stage.
Workflow overview
- Workflow name / label: _(short description)_
- Domain: e.g. coding, bugfix, research, ops automation
- Recurrence: how often comparable runs occur
- Stages / handoffs: main steps, tools, or agents involved
Recurrence and comparability
- Comparable runs available: approximate count or range for PRE baseline
- PRE/POST feasibility: can you run a comparable follow-up after one narrow intervention?
- Known comparability gaps: changing prompts, models, data sources, or scope between runs
Trace, log, and evidence availability
- Primary evidence source: Langfuse, LangGraph, CrewAI, AutoGen, custom logs, CI artifacts, or other tracing
- Export path: how traces or logs can be shared (anonymized if needed)
- Evidence gaps: missing handoffs, retries, tool calls, or stage boundaries
Known failure or degradation pattern
Describe what you observe today — skipped steps, repair loops, handoff noise, plausible-but-drifting outputs, or rising rework — without claiming root cause.
Tools and surfaces involved
List observability, orchestration, or logging surfaces in use. SDVM is workflow-engine agnostic; the current validation path is Langfuse-first, with broader surface compatibility under evaluation.
Candidate intervention surface
Identify one narrow edge you could test if screening supports a pilot — for example:
- prompt or checkpoint summary
- handoff contract or context bundle
- tool-call or retry criteria
- uncertainty gate or repair threshold
Data sensitivity and anonymization
- Authorization status: authorized / pending / not yet authorized
- Redaction approach: what will be removed before sharing
- NDA required: yes / no / unknown
Do not include secrets, credentials, customer payloads, or private data in email or public channels.
Sponsor / technical owner
- Accountable sponsor or owner: name and role
- Technical reviewer: who can interpret PRE/POST/DELTA and test one intervention
- Contact path: email or agreed channel
Expected next step
Email a completed or partial summary to [email protected]. Screening may result in sufficient, partial, or insufficient readiness — not a numeric score and not a full SDVM diagnosis.