The same software and the same service lines run three kinds of programme. What changes is which pillar carries the weight. This page exists so a leader can see, in one screen, what applies to their case rather than reading six pillar pages to work it out.
What this site is built around: allocations, cohorts, vehicles and certificates, evidenced as they happen. Weight sits on pillars 01, 05 and 06 with service lines 01 to 04 running alongside.
The dMRV layer: sealed field capture, an offline-first ward map, an exception list and a verification chain that survives audit. It is the same evidence engine as pillar 06, applied to assets and environmental records rather than handovers. Service lines 01, 03, 04 and 05 do the fieldwork; the software proves it.
Cohorts, assessment and certification: the pillar 01 and 04 layer. Registration, attendance at the session, assessment against a pass standard the client sets, and a certificate issued through the signature engine with a seal and an audit trail. Service line 02 delivers it, line 05 measures whether the capability held twelve months later.
| Layer | Gbaja 27 | SAGA 6.2 | AI Training |
|---|---|---|---|
| 01 Youth empowerment and skills | Core | – | Core |
| 02 Fleet and asset ledger | Core | Supporting | – |
| 03 Women and youth initiative | Core | – | Supporting |
| 04 Leadership and mentorship | In build | – | Core |
| 05 Record and document verification | Core | Supporting | Supporting |
| 06 Delivery evidence (dMRV) | Core | Core | Supporting |
| S1 Register reconstruction | Core | Core | Core |
| S2 Training and certification | Core | – | Core |
| S3 Field verification | Core | Core | – |
| S4 Maintenance and sustainment | Core | Core | – |
| S5 Evidence and reporting | Core | Core | Core |
| S6 Deployment and operations | Supporting | Supporting | Supporting |
Core means the programme does not work without it. Supporting means it is available and often useful. A dash means it is not part of that programme and we will not sell it as though it were.
The three share one register, one key hierarchy and one export format, so a constituency programme can adopt the training layer without a second system, and a climate programme can adopt the verification layer on the same instance. That is the reason to keep the layers separable.
Take the next stepSee the services