This idea is not yet agreed. Nobody named on this page has been asked about it. That includes the growers planning the Agri-Heritage Co-operative, The Shift, Stellenbosch University, the Zonderend Water Users Association, Greyton’s tourism businesses and the Genadendal Transformasie Komitee. Some of the ideas it covers would rely on Farm 39 land, so it goes to the Transformasie Komitee in writing first. It can be tabled at a DevForum meeting once the Komitee responds, or 21 days after it was sent, whichever comes first. The idea pages it draws on aren’t public yet either. Please do not share this page publicly yet.

What the letters in square brackets mean

Facts on this page are followed by a tag that shows where they come from.

  • [IC] Independently Corroborated. Confirmed by at least two sources that do not depend on each other, or by an official record.
  • [MS] Mission-Sourced. Comes from the DevForum’s own pages and records, or from the organisation the sentence names. It has not been checked against other sources.
  • [TBV] To Be Verified. Seems likely, but nobody has confirmed it yet.

Statements without a tag are proposals. They describe what the idea could become.

The goal

Every young initiative in the valley knows what protects it, who gives that protection, on what terms, and the date it will stand in the open.

Why the valley needs it

Our Guiding Ethos asks of every initiative: if it’s young, is it protected while it grows, and does it know when it will stand in the open? [MS] It also lists, as an open question, when protection should end and who decides [MS].

Several of the valley’s ideas are young. Graduates of the October 2026 small business course now meet weekly to plan a co-operative and keep their own record [MS]. The Learning Campus would put “formation before funding” [MS]. The Palmiet Principle proposes a shared pool for each stretch of river [MS]. The Political Economy Analysis plans conversations across the valley in January and February 2027 [MS].

The Shift told the DevForum that capital speeds things up, and that where people aren’t ready it can also speed up dependency [MS]. The DevForum has kept the idea that young initiatives need protection, and dropped any steering out of view: it decides at its meetings and records what happens between them on Between Meetings [MS].

What the research says

Researchers who study how new practices grow call the shelter a young initiative needs protective space (see What Is Protective Space?). Good protection holds back pressure while people learn and build networks, and it gets the initiative ready to stand on its own [IC]. The BioConomy wiki’s brief, Protective Space for Young Initiatives, sets out what the research shows:

  • Most of the evidence comes from single cases of initiatives that lasted [IC].
  • A survey of 276 Transition groups in 23 countries found that the less successful ones tended to underestimate their surroundings and the material resources they needed [IC].
  • Ten years of records from five German business incubators found that sheltered firms didn’t outlast similar firms that weren’t sheltered, and that leaving the incubator was a dangerous time [IC].
  • Protection can be captured by the people who give it, or can go on sheltering work that isn’t improving [IC].
  • Protection that was decided and recorded in public is well documented. The research has no finding that protection must be hidden to work [IC].

The idea

For each young initiative, the DevForum would keep a short protection record, agreed at a DevForum meeting and published with the initiative’s page:

QuestionWhat the record says
What is protected?The initiative, and why it needs protection now
From what?The pressure it isn’t ready for: prices, rules, scrutiny, or a funder’s measures
How?Money, a buyer, a place, time, a network, a shared story, or keeping a low profile for now
Who gives it?Each person or organisation, by name, and what they have said they will give
How is it watched?How the group checks its own learning, without scoring people
When does it open up?The review date, and what happens on that date

How it would apply

  • The Agri-Heritage Co-operative. It already has weekly meetings, community mentors and its own record [MS]. Missing: an honest early look at land, water and costs, since the land is part of the unresolved TRANCRAA process [MS], and someone who brings lessons in from other co-operatives. A first opening point could be testing one product with outside buyers on an agreed date.
  • The Learning Campus and Vorming. “Formation before funding” is already a kind of time-based protection [MS]. Missing: a review date for each part of the campus, and a way of tracking learning that doesn’t pay or rank people per act. The first group of learners whose project work is checked by Umalusi would be a natural opening point.
  • The river work. River logs, seasonal photographs and the yearly river walk let people see the work without scoring it [MS]. Missing: a longer time frame. Restoration that lasted elsewhere in Africa grew from long apprenticeships and secure local rights [MS].
  • The stretch pools. Rewards for people are recognition only, and a sponsor gets no larger say for a larger contribution [MS]. Missing: a rule for what happens if a sponsor leaves, and a review date. The first money into a pool would be the moment to record its terms at a DevForum meeting.
  • The Political Economy Analysis. Asking people questions can change what they say. What Must Happen First already shows an open way to handle this: each party gets its row and its reply stays on the page [MS]. The analysis could also say, in its terms, which young initiatives it won’t measure yet.

Who would benefit

The people running young initiatives, who would know where they stand. The valley, which could see who protects what and why.

Who would pay

Keeping the record costs very little. The protection itself would come from whoever offers it, as each record says.

Who would decide

The DevForum, at its meetings, with the people running each initiative. Anything on Farm 39 land goes to the Transformasie Komitee first.

How it fits the DevForum’s goal

It answers the fourth question in Our Guiding Ethos and the open question on when protection should end. It works alongside Vorming and the long-term goal, and it serves four of the five priorities.

What is still open

  • Who keeps the protection records, and where they’re published.
  • Whether each initiative wants a record, and who speaks for it.
  • What happens when an initiative isn’t ready on its review date.
  • No study of community initiatives has tested whether a fixed opening date helps. The valley would be learning as it goes.

What happens next

  1. The idea goes to the Transformasie Komitee in writing.
  2. The groups behind each initiative named above are asked whether they want a protection record, and what it should say.
  3. The idea is tabled at a DevForum meeting.
  4. The first records are drafted with the groups that want them.

Have your say

To comment on this idea, see How to Submit or raise it at the next DevForum meeting.

References