Kit list and exit plan
Use this sheet in lesson 07. Plan for the worst week of connection you can remember, not the best.
Task:
What has to keep working
| What | Local | Sync later | Online only |
|---|---|---|---|
The kit
The kit GainForest left at Parque das Tribos in 2026, for comparison: a Raspberry Pi running Taina, a Starlink dish, three AudioMoth recorders in waterproof bags, phones with Telegram set up, cables, chargers and a printed checklist.
| Item | How many | Who looks after it | Monthly cost |
|---|---|---|---|
Who pays the monthly costs after the grant ends?
What never leaves the device
Without a decision by the data council, these stay on the community's own device:
- Raw recordings
- Exact locations of rare species or important places
- Sacred or restricted knowledge
- ID documents and payment details
- Private chats
What goes outside, and why
Some tasks may use an outside service, such as a cloud AI model that identifies species from photos. List each one, what is sent, and who agreed to it.
| Service | What is sent | Agreed by | Date |
|---|---|---|---|
Exit plan
If the cloud account, the vendor or the model provider disappeared tomorrow:
- What could the community still open?
- What could it still run?
- Where is the latest copy of the data?
- Who knows how to switch everything off?
Data is Soil · GainForest · www.datasoil.org/handouts/kit-and-exit-plan