Scrum, then a focused build
Share what changed, name the evidence, surface one blocker and leave the meeting with a specific next action. Then move straight into the Nisa branch work.
Tomorrow · Day 12 · integrate
Make Nisa easier to use
Explore voice, multimedia and accessibility without weakening the service boundary.
Complete journey
Explore all 20 days
Review earlier lessons or look ahead without waiting for an unlock.
0 of 8 labs complete
Continue Issue #7
First journey: Define one valuable public need, its trusted source, and the line between general information and a personal case.
Tech field guide
Understand every tool
See what each technology does, when it enters and what must be proven before the stack grows.
Resource centre
Learn, set up and recover
Follow curated lessons, working playbooks, setup checks, a glossary and layer-by-layer troubleshooting.
Beyond Nisa
Explore projects and careers
Adapt the same safe product pattern to aviation, oceans, health, design, engineering, business and Grenadian life.
Execution layer
Open the team repository
Build on your branch, review pull requests and leave evidence in GitHub.
The boundary
Nisa informs. The NIS Board determines.
Nisa may explain reviewed public information and show its source. It must not decide eligibility, calculate a named person’s entitlement, inspect a personal record or collect identifying information.
Your learning path
See where today fits.
Every day stays open for revision and catch-up. The current day is highlighted; GitHub remains the record of submitted work.
Phase 1
Discover
Phase 2
Design
Phase 3
Build
Phase 4
Trust
Phase 5
Integrate
Phase 6