Capabilities
Six operational responsibilities we take on.
Not services. Each is a responsibility inside someone’s operation,
and each names the systems that evidence it, including where that evidence is only
internal or a single pilot.
The map
Payments and reconciliationTaking payment through the instruments people actually use, and keeping the internal record in agreement with the provider's.Evidence example · BizMtaani · LiveIdentity, authority and approvalEstablishing who someone is, what they are allowed to do, and who approved a consequential action.Evidence example · CarePro · LiveCoordination and fulfilmentMoving work across customers, operators and organisations that do not share one clean system.Evidence example · BizMtaani · LiveRecords and accountabilityMaintaining records, decisions, receipts, votes and approvals that have to survive later scrutiny.Evidence example · Jamii Projects Hub · LiveInfrastructure, reliability and securityDeployment, isolation, access boundaries, observability, hardening, failure behaviour and recovery.Evidence example · SentinelCore · InternalConnected and embedded controlSystems that sense, decide or act through physical equipment, including where the network is intermittent or absent.Evidence example · Greenhouse controller · Pilot
Payments and reconciliation
Evidence base · Live system
Taking payment through the instruments people actually use, and keeping the internal record in agreement with the provider's.
M-Pesa STK push initiated from a chat message · card payment alongside M-Pesa · reconciling a provider event against the internal record.
Evidenced by BizMtaani, Gen-Eat, CarePro
Identity, authority and approval
Evidence base · Live system
Establishing who someone is, what they are allowed to do, and who approved a consequential action.
Licence and registry checks, scored interviews, and a named human sign-off that can refuse.
Evidenced by CarePro (Live), Cypher (Research)
Evidence limitScoped to approval of consequential actions. This is not identity infrastructure, and CarePro's steps are described by the product, not measured by us.
Coordination and fulfilment
Evidence base · Live system
Moving work across customers, operators and organisations that do not share one clean system.
Catalogue, inventory and order flow · rider and pickup logistics · ordering over WhatsApp with no app to install.
Evidenced by BizMtaani, Gen-Eat, Hazina Nomads
Records and accountability
Evidence base · Live system
Maintaining records, decisions, receipts, votes and approvals that have to survive later scrutiny.
Group records for families, chamas and welfare groups, with votes and clear balances.
Evidenced by Jamii Projects Hub
Evidence limitOne live system, running as a pilot in Mbeere North. Not yet an institutional deployment.
Infrastructure, reliability and security
Evidence base · Internal system
Deployment, isolation, access boundaries, observability, hardening, failure behaviour and recovery.
Port scanning, log watching and host hardening on Linux servers: an orchestrator and five modules, with 133 tests passing at a recorded commit.
Evidenced by SentinelCore
Evidence limitEvidenced only by the tool the company runs on itself. No customer deployment of this capability is published.
Connected and embedded control
Evidence base · Pilot system
Systems that sense, decide or act through physical equipment, including where the network is intermittent or absent.
Temperature, moisture and watering held without a person or a network.
Evidenced by Greenhouse controller
Evidence limitA single owner-reported pilot. No second deployment and no published performance figure.