Appendix F — Task types and rollout phases
9 task_type categories phased v1 / v2 / v3
The task_type field (§7.2) determines UI rendering and rollout phase. This appendix is the starter list: 9 categories phased into v1 / v2 / v3, with example subtypes per category and where each surfaces in Conductor. Not exhaustive; alignment meeting refines.
Phase 1 — four categories
Category (task_type) |
Example subtypes | Where it surfaces | Origin buckets |
|---|---|---|---|
messaging |
reply-draft, scheduled-send, follow-up-prompt |
Composer view; inline in the conversation thread; member-page activity feed | Client-driven (§3.1) |
booking-action |
property-search, quote-request, vendor-rebook, payment-chase |
Trip page (hotel / flight / restaurant section); component-detail view | Client-driven (§3.1), World-driven (§3.2) |
trip-prep |
pre-arrival-checklist, day-of-departure-message, day-1-check-in, post-trip-review |
Trip page (timeline); scheduled-messages view | Trip lifecycle (§3.3) |
disruption-response |
weather-alert-reroute, flight-cancellation-rebook, vendor-side-change-respond, compliance-advisory-brief |
Trip page (alerts panel); ops dashboard with high-priority badge | World-driven (§3.2) |
These four are the v1 launch set, assuming Andy's AI messaging work lands in parallel. They cover the messaging flow, the booking flow, the templated trip lifecycle, and time-sensitive disruptions — the patterns the ops team uses every day in CC v1.
Phase 2 — three categories
Category (task_type) |
Example subtypes | Where it surfaces | Origin buckets |
|---|---|---|---|
member-context |
preference-capture, returning-client-gesture, care-context-check-in, referral-acknowledgement |
Member page; account page | Client-driven implicit (§3.1b), Relationship (§3.4) |
ops-internal |
coverage-gap, shift-handoff, profile-hygiene-reminder, sla-breach-escalation, workload-imbalance-flag |
Ops dashboard; shift-handoff view | Internal ops (§3.5) |
agent-subtask |
ai-research-step, human-followup-call, document-lookup |
Within the agent run; rolls up to the trip page when bound to a trip | Any (driven by what the TA prompted the agent to research) |
These layer on once the v1 patterns are stable. Internal-ops automation matters for scale but doesn't block the v1 client experience.
Phase 3 — two categories
Category (task_type) |
Example subtypes | Where it surfaces | Origin buckets |
|---|---|---|---|
compliance-safety |
state-dept-advisory-brief, passport-expiry-reminder, visa-renewal-prep |
Member page (compliance section); trip page | World-driven (§3.2) |
discovery |
behavioural-interest-prompt, deal-saved-followup, search-pattern-nudge |
Member page (low-priority badge); curated daily digest | Client-driven behavioural (§3.1b) |
Phase 3 covers the more behavioural / ambient surface area. Lower urgency for v1 because the threshold rules (§3.1b) and behavioural-signal scope (§8 q12) need product judgement before locking. Internal-surface signals from Slack / operator inboxes (§8 q15) plug into Phase 2 or Phase 3 once enumerated.
Surface rollout summary
Engineering and design think in surfaces ("what do we build in v1?"), not just task_type categories. The aggregation below, pulled from the "Where it surfaces" column across the three phase tables, makes the phasing tangible in those terms.
- v1 surfacescomposer view, trip page, ops dashboard.
- v2 surfacesmember page, account page, agent run view.
- v3 surfacesmember-page compliance section, curated daily digest.
How to use this appendix
- • Engineers:
task_typeis one of these 9 values in v1; subtypes are the enumerable child within each category. - • Designers: each row's "where it surfaces" column drives the rendering decisions per task type.
- • Alignment meeting: confirm the phase split is right, prune / add categories, confirm subtype starter list for Phase 1 categories.