Build a shared African satellite program

AfDev-Sat links a satellite-development goal with the ability of participating teams to carry out the work. Egypt’s November 2025 report to the United Nations names Egypt, Ghana, Kenya, Nigeria, Sudan and Uganda as the six partners. It describes a hyperspectral Earth-observation mission and training, with Egypt coordinating integration, facilities and mentorship. A delivered spacecraft and a team able to develop the next spacecraft are related but different outcomes.

EgSA’s presentation on its 2021 work records a two-week AfDev-Sat course for sixteen engineers, from July 25 to August 5. That is a dated training milestone. It is not a launch record. The presentation separately describes Space Keys educational laboratory equipment; a teaching platform should not be counted as an orbital AfDev-Sat spacecraft.

Kenya Space Agency reports that its engineers developed and tested the mission’s electrical power subsystem at EgSA facilities between May and August 2025. Egypt’s later UN report also records Kenya’s contribution and a workshop hosted by Uganda. These accounts support a development history. They do not, by themselves, establish an orbital launch, operational imagery or independently measured performance.

Imagine a partner delivering a fictional power board to another partner’s computer team. Naming the countries is not enough to make the connection work. The teams must agree on connectors, voltages, permitted loads, command formats and the evidence accompanying the delivery. A clear responsibility table names who supplies each item, who accepts it and who resolves a mismatch.

Develop the team and the mission

Consider an invented training exercise in which twelve participants attend and eight independently diagnose a seeded interface fault. Attendance is twelve; demonstrated performance on that task is eight. Neither number should replace the other. A participant may have learned useful theory without yet demonstrating that particular troubleshooting skill.

For a shared project, retain the test procedure, equipment configuration, observations and responsible people. A later team should be able to repeat the exercise and understand the result. Training records, tested hardware and flight events form different parts of the history, each with its own evidence and date.