Delivery principle
The 16-week plan is a controlled proof of the full decision loop, not province-wide readiness. It assumes timely access to approved documents, pilot users, agronomists, infrastructure and procurement. Missing prerequisites reduce scope rather than silently compressing assurance work.
Phase 0 — Mobilization and readiness (Weeks 1–2)
Deliverables
- programme charter, decision rights and pilot boundary;
- selected district, crop and supported conditions;
- source inventory and policy-rule readiness assessment;
- data classification, consent and retention decisions;
- evaluation design and pre-agreed critical thresholds;
- provider-neutral architecture decisions;
- farmer and officer recruitment plan;
- risk, dependency and procurement registers.
Exit gate: authority, knowledge owners, safety boundary, datasets and operating model are approved.
Phase 1 — Evidence capture and knowledge foundation (Weeks 3–5)
- Flutter shell and weak-network case submission;
- Urdu STT/TTS adapters and terminology dictionary;
- guided image capture and upload retry;
- PostgreSQL/PostGIS and object storage;
- document ingestion, chapter/section structure and hybrid retrieval;
- initial environmental tools;
- audit identifiers and baseline dashboards.
Exit gate: reliable case capture, retrievable approved evidence and complete basic audit trail.
Phase 2 — Reasoning and controlled research (Weeks 6–9)
- model gateway and structured analyst contract;
- active evidence-acquisition loop;
- image reasoning and differential diagnosis;
- confidence/research controller;
- local context and web-research sandbox;
- exact policy-verification service;
- officer queue and reviewer workspace.
Exit gate: end-to-end test cases produce attributable analyses; unsupported exact treatment is blocked.
Phase 3 — Assurance and shadow mode (Weeks 10–12)
- gold-standard and adversarial test sets;
- speech, retrieval, media and reasoning benchmarks;
- security, prompt-injection and load tests;
- reviewer calibration;
- shadow deployment and error taxonomy;
- rollback, source withdrawal and incident exercises.
Exit gate: approved thresholds, zero critical safety-suite failures, tested rollback and audit completeness.
Phase 4 — Controlled field pilot (Weeks 13–16)
- farmer onboarding and assisted-use support;
- controlled live cohort;
- daily operational and safety monitoring;
- weekly agronomist and product review;
- incident and correction workflow;
- cost and capacity measurement;
- final evaluation and production recommendation.
Exit gate: outcomes, failure modes, economics, staffing and regulatory decisions are documented.
Workstreams
| Workstream | Accountable roles |
|---|---|
| Product and field operations | Product owner, field lead, farmer research |
| Architecture and backend | Solution architect, backend engineers |
| Mobile and speech | Flutter engineers, realtime engineer, Urdu speech specialist |
| Reasoning and evaluation | ML engineers, agronomists, evaluation lead |
| Knowledge and retrieval | Data/RAG engineer, knowledge steward |
| Policy and regulation | Regulatory specialist, agronomists |
| Geography and analytics | GIS/data engineer |
| Security and privacy | Security and data-protection leads |
| Platform operations | DevOps/SRE |
| Quality | QA, Urdu language experts, reviewer panel |
Scope-reduction order
When time or prerequisites are constrained, reduce conditions, crop varieties, districts, live video, chemical authorization and provider breadth before reducing safety, audit, evaluation or human-review controls.
Live media workstream
Assign a realtime/WebRTC engineer, mobile engineer, SRE/network specialist, privacy lead and field UX researcher. Phase 1 includes LiveKit/TURN, call UX, Urdu audio, adaptive video, frame evidence and degradation testing—not merely recorded media upload.