TASKS

Concrete next actions, ordered roughly by dependency.

Before any v2 drafting

• Adrian: read original proposal end-to-end (source/original-proposal.md)
• Adrian: confirm SPARK can be referenced in the proposal at all, and at what level of specificity (it is publicly documented but Obi is named on the site — implications for NDIS deployment context need a beat of thought)
• Conversation with James: see synthesis/conversation-with-james.md for the exact questions to ask. Most important: “What do you imagine Adrian doing in an average week by Month 6?” Pop the fantasy balloon if there is one, before either party invests further effort.
• Decide: is the contractor-architect frame the model, or does James have a different vision?
• Verify pricing: pull current NDIS Support Catalogue (Pricing Arrangements 2025-26 v1.1, effective 24 November 2025) and map every proposed service item to a real line item code.

Pre-launch hard requirements (independent of plan rewrite)

• NDIS Worker Screening Check — both practitioners
• Professional indemnity insurance — get real quotes for disability services (the $1,500–2,500/year estimate may be optimistic)
• NDIS Code of Conduct — both practitioners must understand and agree compliance approach
• Privacy/data handling system — needs to be substantive, not a bullet
• Practitioner agreement — IP ownership, dispute resolution, continuity of care if one party leaves

v2 drafting (in dependency order)

• 04-roles-and-scope.md — write this first; everything else hangs off it
• 03-financial-model.md — fix the math, build to Adrian’s actual hours
• 02-eligibility-matrix.md — replaces the support category table
• 06-spark-deployment-model.md — what is “SPARK” when deployed to a participant? Bespoke? Productised? Open question.
• 05-safeguarding-appendix.md — boring and beautiful
• 01-service-model.md — five-stage model with corrected role split
• 00-executive-summary.md — write last, after everything else is settled
• 07-risks-and-go-to-market.md — pilot framing, not market launch
• 08-next-steps.md — concrete, dated

Open strategic questions (need decisions, not drafting)

See synthesis/open-questions.md for the live list.

CF Pages implementation (parallel track)

See briefs/codex-cf-pages.md for the Codex execution brief. Three artifacts in priority order: (1) internal dashboard, (2) public landing, (3) intake hub derived from (2). Phase 0 is ADRs; Codex stops there and waits for review before scaffolding.

• Adrian: read briefs/codex-cf-pages.md and amend before kicking Codex off
• Codex Phase 0: write three ADRs in briefs/adrs/ (auth, data store, monorepo layout) and stop
• Adrian: review and approve ADRs
• Codex Phase 1: scaffold internal dashboard, deploy preview
• Codex Phase 2: scaffold public landing (structure only, placeholder copy)
• Codex Phase 3: derive intake hub from landing