Jabali -- Food Systems Intensive Hackathon
{"type": "project", "title": "Jabali -- Food Systems Intensive Hackathon", "logoImg": "bafkreicxy4yvo7bdjsc6ne7fnho2cgrzwo2s6dm3hk4dao2vyy6vsr5cae", "website": "https://ipfs.io/ipfs/Qmdw7XsdGUkWnBDEJhkds6aSvZk2QLooMjigKDSz7qpAHk/", "bannerImg": "bafkreiesqdjraiuwxy64zrlb2n3ecpyftdovjcd4cuxdjvvwdhugoqisoq", "createdAt": 1682108660789, "credentials": {}, "description": "\n\n**Let’s focus on hackathon solutions for regenerators – **\n# FOOD SYSTEM INTENSIVE Hackathon\n\nMany players in the web3 space are adopting more sophisticated and effective formats for hackathons and most of us are quite satisfied with this. \nUntil now, hackathons have been rushed, hyper-competitive free for alls. Some of the results have been quite good but for a large part, it has just created a large amount of bounty hunting hackers.\nFor products of value to come from the tech web3 offers, this is the logical step of refinement to take in the hackathon culture.\n\nAs a joint effort by Jabali and Chama DAO, we want to create a 3 month long experiment to test one thing: \n**if the buidlers and the regenerators (land stewards and more) hang out more, will more meaningful tech services and products come from it?**\n\n\nLearning is a relational art. We will aim to include that art in a 12-day food systems crash course prior to any of the hacking even starting.\n\n\nThe format will be as follows with periods of rest and restoration happening between:\n\n\n10 days of a bioregional food systems – “How is currently is” crash course. \n\n## —  Context Setting “Crash Course” Portion — Field Visits\nHaving context is important for hackathon participants to create the solutions they will be able to offer their communities and actually implement.\nWe plan to have several visits from conservation reps, land rights legal experts, soil scientists, agricultural development reps, operations food distribution stakeholders, and agricultural economists. The idea is to get candor and reflection from each one of these figures on what’s working, what’s not working, and how they think it can improve. Some facts, some opinions, from several different perspectives.\n\nWe will also include several days of farm visits - going through the staples on your plate from morning to dinner. Eating food sourced from the regions we will be visiting so the hackers really understand the geographic distance of travel for all products involved in the supply chain.\n\n1. 1 day produce farms - veg and fruits\n- Monocultures and polycultures\n2. 1 day predominantly grain farms\n-Monocultures and polycultures\n**— rest day —**\n3. 1 day dairy and other livestock farms \n- (because a lot of the grain and produce also ends up going to the livestock) \n4. 1 day freshwater aquaculture\n\n**— rest day —**\n\n5. 1 day cash crops\n- coffee \n- another special commodity – Perhaps wine, vanilla, or nuts. Something expensive that is grown for export most likely.\n6. 0.5 day “recreational” ag – sport fishing or horse ranches.\n- Something like ranches or roses that show just how much money goes into sectors that aren’t producing anything edible haha\n7. 1 day regenerative farms or a self sufficient village. A Maasai village that is preserving their traditions and conserving biodiversity. \n8. Recreation, restoration and dinner with all of the farmers together with the builders. The challenge by the end of the night is for the scholars to make a list of things all of the farmers seem to care about.\n\n**— rest day —**\n\n## —  Workshop and Reflection Portion —-\nUpon the completion of the food system crash course, we will begin the workshops and brainstorming for solutions that will inspire protopian design for a Kenyan food system.\n\nThe following facilitated conversations and workshops will be included in the reflection period:\n\n1. Mapping out the existing food system – everything everyone has learned mapped out, a community effort. Building a complex systems diagram.\n2. Coming up with quotas for food production to make farmer parity possible\n- What would have to happen?\n- Pointing out what is working and what needs to change\n- Breaking down the problems and discussing whether they can or should be fixed with technology\n3. The last day before the teams disburse and go to develop their teams for the hackathons, they spend the entire day with the farmers (the farmers are paid for their time spent) and ideate solutions with them\n\n- They also show the farmers the larger scale mapped out diagram and learnings to see if the farmers agree with their understanding of the local food system.\n- They create a vision together. What do the farmers care about right now and what do they care about when they think about the food system as a whole?\n- What do they want to see happen to their farms and to other farms in their community?\n- From the foresight analysis done as a group, the group can assess which aspects the agricultural community cares about the most. This is going to be what fuels the inspiration for the food system focused technical solutions.\n\n\n\n**By the end of the 12 days the goal is for the builders to have more empathy for the farmers than they otherwise would have. This can catalyze bioregional solutions directly with the farmers themselves.**\n\nThe hackathon bounties will be offered upon submission of a project 3 months later.\n\n\n### —  Fine Print —-\nThe pre-requisite to this hackathon should be for people who have an interest in food systems overhaul to begin with. We understand this is an intensive and emotionally taxing course therefore we will need to source hackers who seriously have a passion for a food system overhaul on this course.\n\n\nThe focus won’t be the technical implementation as much as it is for the ideation and strategy.\n\n\nThe focus is also more on building rapport with the farmers and seeing just how much more meaningful of solutions result from some initial **“seeing into their worlds”**. Empathizing with users/target market. Sensible tech development 101.\n\n\nhttp://Jabali.co is the non IPFS domain btw. :)", "logoImgData": {}, "bannerImgData": {}, "projectTwitter": ""}