MVP scope
What's live, what's mocked, what's out
Honesty about boundaries is part of what makes the MVP credible. Reviewers can spot a 'live demo' that's secretly a Figma slideshow from across the room. Here's the unflinching version.
Layer 1 — Live and functional
Built for real use today
- Landing + onboarding flow (role → region → commodities), persisted to localStorage.
- Ohangwena region briefing with climate history, dominant crops, livestock, documented pests, programmes, and key contacts — all sourced.
- Mahangu commodity profile with cultivation calendar, recommended varieties, conservation-agriculture notes, common challenges, post-harvest, market notes.
- Programme directory with 10 real, current programmes — filterable by climate, finance, market, drought, training. Each carries eligibility, what-you-need, contact, and source citation.
- Bounded AI advisor at /advisor. Answers come from a curated corpus of indexed documents. Cites every source. Refuses gracefully when no Namibian source matches.
- Forum at /forum with seeded posts in English and Oshiwambo — voice note placeholders, photo attachments, verified-officer pins, private-to-officers channel.
- Officer queue view at /officer-queue showing the moderation surface from a verified officer's perspective.
- Heita styled mockup at /heita — the WhatsApp persona the advisor takes on in Phase 2.
- WhatsApp share deep-links from programme cards (the link is real; the API isn't yet).
Layer 2 — Honestly signalled, not yet live
Mocked-up with clear labels
- WhatsApp inbound (Heita bot live on WhatsApp): in progress — Business API registration takes 4–6 weeks. The Heita page styles the conversation as it will appear.
- Notifications inbox: structure visible on the home feed; push delivery is Phase 2.
- Other regions (Omusati, Oshana, Oshikoto, Kavango, etc.): listed but content is Phase 1 launch work.
- Other commodities (cattle, small stock, horticulture, etc.): listed but full profiles are Phase 1 launch work.
Layer 3 — Out of MVP scope
Deliberately not in this build
- Real MAWLR officer accounts — pilot validation conversation precedes integration.
- Application-conversion instrumentation (the headline production metric — Year 1 work).
- Multi-language UI — English-only chrome for the MVP; corpus content includes Oshiwambo terms inline.
- Offline mode and PWA install — Phase 2.
- User authentication, profiles, posting from the web — Phase 2.
The point of the layering is not to hedge. It's to be specific about what a reviewer can poke at right now (Layer 1) versus what is committed to in the roadmap (Layers 2 and 3). Most of what makes Oshana defensible — the bounded advisor, the cited corpus, the officer-moderated forum, the WhatsApp bridge — is in Layer 1 today.