## People
Birds are the most socially intelligent of us all.
They live in constant translation — reading sounds, gestures, and tones that cross a dozen different languages at once.
If you mimic a bird call, the bird will probably tilt its head, look a bit confused, and then — if your vibe’s good — start chatting back.
Sometimes they even get close, which is wild when you think about it.
We’re huge, loud, unpredictable creatures, and yet they’ll still come near, testing whether the world is safe.
Birds are quietly brilliant at social life.
They share the same skies and trees without needing to agree on everything.
Signals cross, flocks mix, tiny arguments happen, but there’s no collapse. They make it work.
That’s what’s beautiful about them: cooperation doesn’t have to be perfect to be real.
It’s messy, a bit improvised, and somehow still graceful.
Maybe that’s the best kind of intelligence — knowing how to live side by side, even when nothing lines up exactly right.
### Who might peaceful foundation benefit?
Peaceful Foundation campaigns touch almost everyone — directly or indirectly.
When food gets cheaper, learning feels lighter, and people start meeting each other again, the benefits move quietly through whole communities.
We look first for people most ready to volunteer and build with us.
anyone, as we begin to work together again.
who can see that something better is possible
who are inspired enough to act, not just imagine
who move because they believe change can be gentle and real
who turn that feeling into small, visible steps
people who make others more comfortable being themselves
who listen first and keep things steady
who draw others in instead of pushing them away
who bring warmth, not pressure
people who have opinions but don’t cling to them
who can pause, think, and adapt
who care more about what works than who thought of it
who treat feedback as part of the craft, not a personal attack
people who want to bring people together
not just talk about community, but make it real
who bridge divides quietly, through food, learning, calm, and proof of life
who treat coordination as an act of service, not control
people who like to do the work
who’d rather build than perform
who can move alone when needed, or fall into rhythm with others
who take pride in finishing things and helping others do the same
#### People within local communities
state of work, especially for young people
for many graduates and early-career workers, the job market feels bleak
hundreds or thousands of applicants for each “entry-level” role
AI and automation is quietly shrinking junior and mid-level positions
whole categories (junior dev, junior designer, basic admin) thinning out
the usual path is:
endless applications into black boxes
automated rejections, or no response at all
or multiple interview rounds for jobs that barely exist
the result is:
a slow humiliation ritual
doing unpaid test work
performing enthusiasm for roles with no real security
being rejected, not for lack of talent, but for lack of slots
and people begin to feel:
disposable, replaceable, and deeply tyred
welfare and “activity requirements”
in places with unemployment benefits:
just accessing them is often a maze
forms, phone calls, compliance portals
appointments that assume free time and emotional bandwidth
on top of this, there is “job search activity”
applying for roles that probably do not exist
logging applications to meet points targets
doing “activities” that help systems, not people
for many, this is:
a second humiliation ritual layered on the first
performing effort to keep a small payment
with little sense of progress or dignity
structural disillusionment
across sectors, especially for young people:
internships and “trial periods” used as free labour
roles dangled with vague promises of future work
then dropped once the free value is extracted
for people in this position:
the message is clear:
“your time is cheap unless it makes someone money right now”
many respond by:
moving back in with parents if they can
staying in unstable share houses
or quietly dropping out of the search altogether
where people actually are
behind the statistics, a lot of people:
are not starving, but are stuck
living with family
or in precarious rentals
have skills, energy, and tools
laptops, cars, phones, education
but are blocked by:
lack of stable income
and lack of any structure that values their contribution
it is no surprise that hope feels thin
when the only “official” options are:
compete harder for shrinking jobs
or prove your worth to keep minimal benefits
what people tell us
through volunteering platforms and direct outreach:
people — especially programmers and other skilled workers —
are unexpectedly relieved to find:
work they can just do
without assessment centres, whiteboard tests, or fake friendliness
without pretending a role is their “dream job”
again and again they say:
it feels good to:
contribute directly to something real
use their skills for visible local impact
be treated as a person, not a candidate ID
even when paid work is scarce, people still need purpose
they need to feel:
useful
linked to others
able to move something in the real world
Peaceful Foundation offers a universal role:
building calm, local communities together
everyone has something to give
even if it’s:
time
thought
or kindness
what volunteers report
many say they feel unexpectedly refreshed
not having to perform for endless interviews
not doing unpaid test work to prove themselves
able to just contribute directly
volunteering as rhythm, not employment
small teams formed by shared characteristics and compatibility
creates structure and recognition without salary dependency
no hiring rituals, no whiteboard tests, no performance reviews
links into peaceful passport
passport records effort and proof of contribution
acts as a public log of community achievement
achievement
not performance or hierarchy, but participation
actions verified by peers, not algorithms
recognition for what people *actually do*, not what they say
graduates between jobs, early retirees, gig workers, or those sidelined by automation
find purpose and structure without bureaucracy
reconnect through contribution
who this reaches
mass unemployment affects everyone
not just those in the headlines
graduates between jobs
early retirees
gig workers
those sidelined by automation
all find purpose and structure without bureaucracy
all reconnect through contribution
##### Students
creativity, humour, and the ability to normalise calm, grounded ways of living
they make small actions feel natural, not forced
peer influence spreads faster than official programmes
they make the projects visible on campuses and online
posters, memes, and meetups act as proof of life
study and leisure merge into contribution
campuses become testbeds for peaceful local worlds
###### School Students
underage volunteers need parental or guardian awareness
effective method: a short, prompted live video recording
student + parent/guardian together
confirming the parent knows:
they’ve watched the induction videos
they understand what Peaceful Foundation does
they’re aware their kid wants to participate
this keeps things human, simple, and verifiable
the video must be real, not AI-generated
it should feel like a genuine chat, not a bureaucratic hoop
clarity about roles and boundaries
we are not creating an employment relationship with minors
even if a student helps with tasks
or receives small, appropriate rewards or support
nothing resembles a job or contract
the relationship is:
community-based
educational
and always mediated by adults with WWCC
parents remain fully in the loop
they know exactly:
who can communicate with their child
what tasks are appropriate
how supervision works
discord server
XMPP
###### University Students
the most useful cohort
high concentration of young people
high rates of addiction
pornography
nicotine
alcohol
high uncertainty about job market
mass unemployment
endless interview rituals
skills without outlets
high desire for meaningful impact
want to make difference in world
uncertain how
high loneliness
everyone's lonely
not just students
but students feel it acutely
the ideal experience
start with quiteasily
posters in bathrooms
lowest friction entry
anonymous participation
cure normalised addictions
no more nicotine
no more pornography
no more alcohol
noticeably feel better
cultural shift already visible on campus
then learnstuff.today
broaden what they're good at
discover what they enjoy
focus easier in university
more time to learn different things
then reasonable.diet
most accessible campaign
precursor to calm.college
more socially acceptable posters
recipes
food tips
immediately useful
put up in shared spaces
dorms
kitchens
common rooms
publicly on campus
mental health increases
share the potato
microwave technique
helps more people around campus
integrate with existing university structures
AEs
student guilds
welfare officers
institutional support
Peaceful Foundation provides backup
seed potatoes
name tags
guidance
then calm.college
discover whole bunch of people on campus already part of this
really cool
start meeting up
calm.college posters go up
chalk drawings
mentions in classes
happier person
much better vibe
the meetup
someone brings guitar
someone brings frisbee
girls from dorm room
growing herbs on windowsill
mashed into paste for potato
nice vibe
circle of people chilling
making conversation
computer science major
psychology student
environmental engineer
physiotherapist
teacher
conversation starter
what are you passionate about
learnstuff.today interest
hexagons.world local indicators
what statistic are you passionate about
interdisciplinary collaboration
work collectively with others interested in same thing
create interdisciplinary campaigns
lower statistics in local community
lower statistics around world
unis don't do it
too difficult to coordinate
too difficult to grade
do it ourselves
beautiful thing
the flow through campaigns
quiteasily
start here
posters in bathrooms
lowest friction entry
anonymous participation
learnstuff.today
create content
university students often do this naturally
broaden capabilities
discover purpose
reasonable.diet
most accessible campaign
precursor to calm.college
mental health increases
share the potato
calm.college
join campus community
combat loneliness
create test nets for local communities
interdisciplinary collaboration
expand upon in calm.college strategic plan
hexagons.world
coordinate with other students
influence local communities beyond campus
what statistic are you passionate about
why campuses work as test nets
semi-structured environment
people verified through real credentials
eduGAIN authentication
protection from misconduct through institutional frameworks
easier than unleashing all local communities immediately
figure out structures
figure out what works
Peaceful Foundation disappears into infrastructure
dense population
people live close together
but rarely talk
events nearby and cheap
but existing events too formal
fixed times don't fit student schedules
difficult to drop in
the campus condition
collective loneliness
campus engagement down
people don't know how to communicate
surprising difficulty making friends
ask any student
many commitments
no time for rigid structures
what calm.college provides
shared noticeboard
post what they're doing
others join if down
no pressure
no awkward introductions
no imposed structure
students coordinate whatever structure they want
system provides foundation
they build the rest
impact beyond self
posters around campus
quiteasily in bathrooms
reasonable.diet in dorms and shared spaces
chalk drawings
mentions in classes
integrate with existing university structures
climate down campaigns
whatever feels applicable
the aim
active citizens of their campus
make meaningful difference
combat loneliness
improve mental health through participation
improve university experience
create test nets that scale to neighbourhoods and towns
interdisciplinary collaboration
lower statistics
beautiful thing
##### Purposeful Developers
the supply problem
not AI displacement
AI was catalyst for layoffs
but root cause is simpler
free money ran out
COVID era funding dried up
business models didn't hold
layoffs to keep line going up
basic supply and demand
oversupply of highly qualified software engineers
junior roles especially thin
training-ground work automated
companies want experience
companies don't want to grow people
who they are
engineers, designers, researchers, data scientists, open-source builders
often in strange places work-wise
between jobs
in roles that don't grow them
sending applications that never go anywhere
collective frustration
endless interviews
hoops
pretending to be excited
feels awful
community and mentoring missing
what usually happens
someone replies to a “Volunteer Software Engineer / Developer” listing
we don’t send them a test or a leetcode sheet
instead, we:
have a short call or a few messages
ask what they’re interested in
ask what they already know and what they’d like to learn
check how much time and energy they realistically have
many people say some version of:
“I’m just sick of interviews, hoops, and pretending to be excited about it”
long chains of calls
technical puzzles that never show up in the real work
being expected to perform gratitude for the process itself
the response
no tests
no leetcode
no whiteboard puzzles
short call or few messages
what are you interested in
what do you know
what do you want to learn
how much time and energy do you have
assumed competent and driven
wanting to learn with people
time treated as contribution from start
not something to earn
what they step into
small clear pieces of work
form that behaves on cheap phones
simple internal tool
small part of hexagon or passport flow
see where it lives
which page
which user
which problem it touches
when stuck
say so plainly
someone sits with them
pair briefly
comments that explain changes
commit code into real running system
learn by watching
idea → spec → pull request → live
juniors and people who feel stuck
place that feels like gentle junior role
community
validation that they're wanted
mentoring without permission layers
people further along
mentor
work on tools that line up with their sense of what's useful
what we try to keep intact
questions that feel basic are allowed
no competing to sound advanced
no hiring rituals for volunteer work
honesty about skill set
what they're good at
what they enjoy
project becomes fun
actual growth as person
elegant solutions
building things collectively together
tools we use
Neovim
required
short learning curve
increases productivity
Jujitsu
version control system
over the top of Git
GitLab
main repository
GitHub
mirror for accessibility
open source software
pretty cool
the main expectation
be honest about where you're at
be willing to learn
help build tools that make food, learning, and local life easier for other people
##### Local Organisers and Civic Volunteers
the problem
people already running small initiatives
food drives
tutoring
clean-ups
youth clubs
doing the work
while ineffective campaigns get the credit
protests
movements
building something takes effort
lot of little things
for a long time
without much reward
finding other people is difficult
keen to volunteer
start something
can't find others who want driven impact
can't find others who want to solve local problems
what hexagons.world provides
publicise small initiatives
make visible what's already going on
map of different things happening
wider connection without losing autonomy
templates for campaigns that worked
copy and adapt
wikis of process
missteps
mistakes
replicate everywhere
get participants
hundreds of people who want meaningful impact
meet up
discuss
help
learn from experiences
how we got this started
what worked
collective knowledge
the result
each town becomes both unique and connected
more local world
more goodness visible in local communities
local organisers feel global impact
recognition for quiet work already happening
peaceful foundation inherently does this
##### Institutions That Still Care
universities, co-ops, councils, and NGOs that want measurable social outcomes without bureaucracy
see Peaceful Foundation as a credible partner, not a rival
gain real-time data through hexagons.world and calm.college
use open metrics instead of gated surveys
can cite participation as proof of wellbeing and civic engagement
learn from grassroots instead of directing it
find that small, decentralised action fills the gaps they cannot reach
what institutions get
reduce double-up and load
no need to create own campaigns
smooth the way for existing resources to be used
allow coordination with similar institutions
better mental health outcomes
for their members
for their students
for their communities
free up resources
see what afflicts local communities
find most effective ways of creating impact
direct support where needed
work with current instead of against it
grassroots campaigns already happening
collective lessons already learned
support what exists rather than inventing new
specific institutional types
universities
create test nets for local communities
semi-structured environment
people verified through real credentials
eduGAIN authentication
protection from misconduct
map resources available
more active citizens
more nutrition
support local businesses
connected kinder world
resilient local communities
less reliance on big organisations
cooperatives
appear on map
put hands up
join network of cooperatives working together
ensure good governance
transparency about member care
direct support to strengthen them
local councils
publicise more events
create engagement
ensure campaigns get used
more active local communities
resources for change people agree with
actionable difference
NGOs
people who care a lot
more resources to create local change
collective creation
shared agreement
the relationship
not liaison with Peaceful Foundation
smoothing the way
allowing resources to be used
coordination between similar institutions
reducing bureaucracy between creating measurable impact
increasing mental health outcomes
making better local communities
##### Faith and Cultural Communities
overview
Peaceful Foundation is not a religious organisation
but campaigns touch religious communities deeply
disproportionate impact of pornography
stigmatised but commonly felt
designed as substrate
sits beneath faith and culture
no imposed ways of thinking
best versions of themselves permeate beyond differences
particularly interfaith communities
already grounded in service, discipline, compassion
can adapt Peaceful projects to own traditions
share food, skills, care without stigma or ideology
leaders act as quiet stewards, not figureheads
link global unity with local acts of dignity
make interfaith collaboration feel ordinary, not symbolic
the common lesson
we become what we think about
curiosity creates better outcomes
well-roundedness creates more conversations
better conversations
not debate
no one needs to win
collaborative
hexagons.world applications
find other members of diaspora
build connections
rent out meeting halls
spot for things already happening
cultural communities
find others in their demographic
unique experiences
feeling lonely
active in local community
not exclusionary
kind
good vibe
the result
people get out in gardens
curious about local world
see impact happening
support it
more friendships
heaps of religious people love to debate
but better conversations when no one needs to win
bring more people together
create better things
or just have conversations
whatever
undercurrent
substrate for all
faiths
cultures
anything
people are kind
people want to help
really cool
##### The Quietly Capable
teachers, nurses, parents, tradespeople, and community workers
often hold neighbourhoods together without recognition
used to caring for others, but tyred of working in isolation
Peaceful Foundation gives structure and solidarity without red tape
nurses and doctors for example
extremely overworked
often malnourished
don't get enough food
want communities to support them
walk down street
don't worry about what to eat
hospital could have highly nutritious food available
shortage and overwork recognised
take care of basic living needs
put on autopilot
willing to pay for helpful things
collective contribution if desired
hexagons.world identifies
low nutrition in certain demographics
low mental health outcomes
nursing as focus demographic
work on local problems
providing food
making it accessible
donating food to hospitals
feed everyone
feel happier generally
outside policy changes
make sure people feel support of local communities
backing
small acts
mentoring
cooking
sharing
teachers and others
need support
Peaceful Foundation outside policy
local community backing
structure without red tape
retirees and elders
carry memory
patience
long-term view
anchor younger members through stories and example
host gatherings
document lessons
teach practical skills
bridge generations through calm continuity
often lonely
living at home
in communities
in nursing homes
isolated
no dignity in ageing nowadays
going out in local community
meeting people
world becomes friendlier
peaceful passport accessible
even without formal use
someone got them to do it
or not
friendships intergenerationally
whole bunch of skills to utilise
grandkids ask
"teach me woodwork"
"would you be down to do this task"
build things locally
table made
something repaired
people work together
bridge to unfulfilled and disconnected
social mentorship
retirees and elders with young people
computer addiction recovery
friend group calls
stopped giving crap what people think
culture created receptive people
advice
really good
##### Unfulfilled and Disconnected
who they are
people with time, energy, and skills but no meaningful outlet
may be employed, underemployed, or quietly adrift
want to contribute but don't know how
not hateful
not creating divisions
hopeful and kind
understand we're all in it together
individuals who sense something's wrong with how society works
too online
too anxious
too divided
apathetic but not hateful
if hateful, world slowly calms them down
don't need to worry about that much
what Peaceful Foundation provides
turns isolation into participation
simple first actions
hang a poster
cook a meal
share a link
start belonging
digital actions loop back into real-world connection
community replaces content as measure of life
how each project helps
quiteasily
calms people down
allows them to help others
learnstuff.today
become more active citizens
create meaningful change
have skill sets to help where they can
become more capable
reasonable.diet
improves people's lives
eat healthily and cheaply
saves money
calm.college
creates local communities within places
hexagons.world
more of a social life
see where to improve local communities
create meaningful outlets
the process of change runs on feeling hope, not pressure
in the truth section, we defined the emotions we collectively feeling
apathy, outrage, numb, shame, cynic
each emotion builds on the last
which explains why so many campaigns are ineffective, or turn vindictive or even violent
to get to a more hopeful world, you work backwards through emotions
cynic, you show a more hopeful world.
shame, you give steps and define actions.
numb, you cure what keeps people down.
outrage, you look only at local, and show why.
apathy, you know that the world is getting better.
people end up feeling calmer and see the world responding in kind
each peaceful campaign aims to bring hope and bring people together
One quiet utopian idea is the removal of shame from everyday survival and problem-solving.
If people weren't embarrassed about making things work — imperfectly, locally, creatively — a lot would unlock.
Forgiveness follows naturally from this, since when people drop shame, blame matters less. People stop defending themselves and start adapting. Solutions stop needing to look official or impressive, they just need to work.
This opens the door to ingenuity at every scale:
- white plastic tarps for shade or weatherproofing
- small, informal structures instead of waiting for formal housing
- simple, efficient fans and passive cooling rather than energy-heavy air conditioning
- changes to streets, courtyards, roofs, and walls that make places noticeably more comfortable.
As people start working on what’s right in front of them, life becomes easier in small, practical ways; finding, sharing, repairing, growing, and making each become easy and convenient ways of doing things together.
We're trying to build a set of habits and tools that make it easier to:
- meet each other where we already are
- cover the basics so people can think and act.
Peaceful Foundation is the scaffolding for that — a way for people who already care to find each other and work together without burning out or disappearing into noise.
### An undercurrent of flowing resources
// overview of the project
// summary of why
// how it works
this is Peaceful Foundation’s practical approach towards poverty relief
it focuses on making sure no one is hungry, cold, disconnected, or completely idle
it replaces “job search busywork” and interviewing humiliation rituals with meaningful community work
it is people-driven:
built from neighbours and friends fitting small building blocks together
slowly turning spare capacity into simple routines that look after more people
and this allows increasing and sharing available resources even further
it should feel like people helping each other
in ordinary places
in ways that fit into their existing days
// starting plainly: what we mean by poverty and who we are quietly aiming at
poverty
a person experiences poverty when they can’t reach a modest local standard of living
even though their society has enough surplus
in most places, that standard includes:
food
warmth and shelter
hygiene
electricity and water
basic connectivity
our focus is anyone:
living in poverty
unemployed or underemployed
or trapped in anxious, unstable conditions
universal basic minimum
we propose a universal basic minimum rather than a universal basic income
most utopian UBI visions imagine:
top-down redistribution
central rules about who gets what, and when
this one works bottom-up:
hexagon by hexagon
thing by thing
volunteer by volunteer
the universal basic minimum is:
an undercurrent of real things people need to stay afloat
food and hygiene
warmth and sleep
light, power, and connectivity
enough stability to think and act
not a promise of full income replacement
but a shared commitment to “no one drops below this floor if we can help it”
then progressively raising the floor as more people can help
we begin with Peaceful Foundation volunteers and neighbours:
people already showing they care and can act
who are themselves close to or in poverty
or know someone who might be
we stabilise them first:
get them properly fed
cover the most basic gaps
then support them to map, connect, and help others around them
as each person and crew stabilises:
their reliance on the undercurrent ideally shrinks
their capacity to support others grows
public benevolent institution, in practice and in spirit
legally, the undercurrent is structured as a public benevolent institution
in practice, it aims to:
benefit as many people as possible in each hexagon
including people who have never heard of Peaceful Foundation
by:
finding the most efficient local or semi-distributed ways to provide basics
reducing suffering directly, not abstractly
treating every dollar and potato as a shared civic gesture
rather than a private act of charity
the name is intentional
and it's a descriptive name that's intentionally clunky
if it had some sort of wizzbang name
then it would become another peaceful foundation project
not an ideal outcome
actual aim is to create a more local and co-operative world.
you don't get there from creating a new system
#### Real and imaginary resources
clearly, the problem is the delegation and distribution of resources
most countries already have a surplus of food, goods, and space
the issue is how we decide who gets what, when, and how
real resources
things you can eat, touch, sleep under, or use to move and connect
food and clean water
shelter, bedding, clothing, warmth
transport, fuel, tools, and repair
wire, fibre optic, routers, devices, and electricity
people’s time, attention, and skills (and someone's imagination)
imaginary resources
systems we’ve layered on top of real ones
money and credit
banking and reserve rules
budgets, policies, and welfare programmes
brands, borders, reputations, and institutions
they are powerful and useful
but they are not food, blankets, or friends
they can fail even when the real world is abundant
they can be:
useful tools for moving real resources
or clumsy filters that block them
right now, they often:
reward overconsumption and packaging-heavy products
let food and goods expire in the wrong place
make it harder to help than to waste
money, systems, and rules are re-framed as:
tools for moving real resources
not reasons to withhold them
##### Zero-salary Volunteering Job
instead of “job search busywork”:
we create a civic role with real tasks
people are:
given tasks to help from their circumstances
based on place, skills, and availability
given:
rhythm (regular tasks and meetups)
recognition (through Passport and peers)
autonomy (ability to choose how they contribute)
the support they receive:
keeps them out of immediate poverty where possible
while their work keeps others out of it too
the more people join, the easier that the entire thing becomes
#### What is already available?
existing surpluses?
// kinda how they are implemented but mainly how we can use them
Alright. textiles. Manufacturing. utility infrastructure. utilities. yeah, waste, waste disposal. which, are currently, there's a lot of stuff going to waste. approximately, yeah, yeah, if you just, yeah, everything comes wrapped in plastic and everything. yeah. and then, the entire thing is grossly inefficient. and then but, oh, and then when we're discussing transport and everything, we have created the most efficient a transportation mechanism ever created, which is the which is the bike. and then people also also created the electric bike as well. there's also walking, there's a lot of infrastructure that allows people to walk around, safely, because there's cars. Cars. but they're dependent on things, and they're subject to flux- price fluctu- rate fluctuations and things that, and supply chain disruptions. yeah, a lot of considerations there. yeah. and then dependent on roads, make, crowding roads. roads have to be maintained every 10 years, for good upkeep also. but I'm not sure if that differs for, residential roads, but there's, water. there is an art to good road building. that I promise you. Oh yeah! I would say that, there is an art to road building, that I promise you. mainly because I'm making, a little bit of a nod to my, to my dad, but yeah, I'm bashing, how much, road is required for, yeah. how much is required to, create a road. there's a lot of infrastructure, there's a lot of yeah, all the stuff that you have to make, waste. there are, more efficient ways of making road, I suppose. more, ways that, have yeah, less waste, but, ultimately, the whole process is destroying vegetation and placing road, for, for, diesel powered machinery to to operate on top of. the entire thing is a bit, is a bit, yeah, is a bit wasteful. yeah, there's that. there's trains, there's buses. buses are more efficient. buses have various technologies that they can use. They can be electric buses or gas buses, or, or, high, different little things. yeah. There's electric cars now, but they're, they require a lot of, but for the amount of people that, yeah. pretty, pretty inefficient. sometimes there's small local buses as well, there's, you can call a passenger on demand for that. they've done initiatives with that, which is pretty cool. yeah, there's, there's a lot of stuff. yeah. There's, there's electric bicycles now. yeah. Yep. I suppose the culture is that, you should be, is in a, to be in a rush, pretty much. and then transport in an infrastructure sense, with trucks and everything, requires a lot on just-in-time logistics. everything has to get to the right place at the right time. which is, a sub- subject to supply chain shocks and everything, yeah. and is very stressful, I suppose. there's that too.
##### Food
in what is already available, talking about food, we would talk about the how food is presently supplied, which is from farms to for most people it's to a supermarket and this introduces a because this requires everything to be available everywhere, which is insane. Then a lot of the time, inefficiencies in packaging or things that or waste is generated through plastic or cardboard. And and the whole thing relies on just in time logistics, which is yeah. typically if something doesn't come in a plastic packet, then it's fine because it didn't have to travel far to get that get there, or at least not abhorrently far. broadly speaking if we need to, the industrial food production system has provided for it has allowed us to get to this scale in which we have in which a scale of population that we have. yeah, we already produce a surplus of food. the issue only is getting it, is get making everyone making sure that the distribution of such a thing is fair. and yeah, that's that's effectively how you do it. in a yeah, you can see how supermarket shelves empty out during a a crisis, and this effectively illustrates the problem and the problems with just in time logistics or supply, I think it is an algorithmic model to food supply, which is not reliable. what we want to do is it's that in most places there is still a local food growing economy or that feasibly could support enough people. And that in most places around the world, they could you can conceivably grow things on balconies and at least create local alliance for things that aren't exactly things herbs or things that or or potatoes, or at least and this would make people mindful of the food growing system as a whole as well, and we it does take time to grow food and it's a significant process. growing potatoes that, that that's a thing. yeah, that's effectively what we have access to. in little places there's local markets or green grocers, particularly if there's something from a green grocer or something is available, then yeah. ideally we want to strengthen local supply chains and document them, which is because it's extremely useful. And that if we if there needs to be deterministic failover for local supply chains to feed people locally, then we want that and local resilience in growing food and such. yeah. salt and minerals, I suppose, I don't know. Yeah. This isn't a terribly interesting section, but it is getting me thinking. yeah.
industrial
##### Infrastructure
{transport)
// just in time logistics
// road
cargo
###### Communications
In most cases, places around the world now, there is instantaneous communication. this is typically done through either infrastructure fibre optic cable planted in the ground, or depending on the place, sometimes, fibre optic cable and then ADSL2+, good old from whenever it was, 1985 or more, into the house, which is extremely, extremely dumb. yeah, just make a point of you've got amazing fibre optic cable all the way to, it's the last, little bit, is yeah, unfortunate. then, yeah, you're and get this or the NBN, or the National Broadband Network in Australia. then, what else? yeah, then it's either that through infrastructure, and how that interoperates, it's TCP/IP routing, the entire internet relies on, old, sort of inter- inefficient communication standards. I suppose, you don't really need to dwell on that, but the the IPv6 roll out is not progressing very quickly. we've, we've leveraged IPv4 to just stretch out for as long as possible, pretty much forever, using tricks, pretty much, we have tricked ourselves into having a lot of addresses. even though an IP address, it kind of shouldn't mean nothing, whatever. yeah. then, yeah, most people lasers have, I suppose yeah, the entire infrastructure of the internet, I suppose, is centralised. but, yeah, that that's sort of a, the dwelling of it, it's a controlled by domain names, which is yeah, I don't even I don't want to dwell on it because then I don't want people going into cryptocurrency or the but don't even, don't even worry about it. yeah. yeah. then, I digress. Then you'd sort of talk about how it's also, it's either fibre optic to the to the house, or cable in the ground, or 5G, mobile networks, which require a subscription for the uptake and, then it's a privacy nightmare, and the, yeah, it requires sending a whole bunch of, yeah, building a bunch of infrastructure, which helps a lot of people, but there's a limit on how many things you can create. that's yeah, not, yeah, there's then there's saturation and the size of then there's problems between mobile bands, and then it also requires ID, yeah, it's a, it's entirely centralised system that requires, I'm creating a whole bunch of infrastructure, which is just significant. and, yeah. there's that. Otherwise, there's satellite internet, more more, recently, there's been, now, there's satellites in the sky, you have connectivity everywhere on Earth. and this section, you wouldn't call this internet, you would call this, instantaneous communication, yeah, pretty much, yep, there's that. yeah, there's there's that section. yeah, probably then you'd also in this section, you'd talk about how there's yeah, everyone has, internet connected stuff nowadays as well. everyone has, yeah, everyone has devices, pretty much, smartphones, go for is cheap as it's extremely cheap, and there's a huge pre-owned market, it's it's very difficult for someone not to have a smartphone because the entire world has become, reliant on being on the infrastructure for them. and then, yeah, and then there's social norms in that too, social norms is that you should be reachable and communicative, be able to be, instantly reachable, which has been reinforced by, things read receipts as well, which is, horrible. for the, for yeah, for the first time in human history without having to deploy a spy network, you now have a read receipt. yeah. without yeah, there's that. yeah, most people browse the internet through smartphones. most of the platforms available today, are all, all, pretty much, all smartphone communication goes through two companies, either Google or Apple, that's it. yeah, it, this is mainly owing to the fact that the, the market in create, creating smartphone devices, is cornered, pretty much. and it's difficult therefore to make a supply chain that require, that allows, people to have open hardware, or to have kernels for your software, for the open hardware, you get what I mean? you need to have a Qualcomm, whatever, and you need to have the kernel modules to be able to make it. that's difficult. yeah, there's that. that's then, all smartphones are, are controlled by these two companies, pretty much, and they require logins to use their devices, pretty much. and, yeah, that's that's all, oh, they, you can't say that, I suppose, but all smartphone market share is controlled in two ecosystems, which is yeah, not good. yeah, both, both are walled gardens, pretty much. yeah, you can't get, yeah, there's that. controlled by two, yeah, two companies. Yep. yeah, the smartphone market is is seemingly fragmented, but there, it's faux competition because, they all use the same, operating system. yeah, there's no, there's no, there's no actual competition between, mobile operating systems, there's that. yeah. The that's, that's the thing.
###### Utilities
##### Waste
##### Surplus
// resources?
// inefficiencies
// barcodes
// supermarkets
// surplus
// minimal to aleviate poverty
#### How might something better work?
You mustn't be silly in thinking that you couldn't have everyone together growing food in global with everyone being cooperative. With everyone surplus. And local gardens and then you can move into cooperatives and global pool of food, global full food pool. shouldn't be called a bank. Because that would make it transactional. But, would run at a surplus. Is a wordy line that needs to be a little more authentic. It's conceivable everyone together everywhere. And beautiful. The part is jump whatever, sort of, got lost in thought. Whatever you have can be a surplus. You have to consider food supply chains and mapping them with ease comes from local markets first and who would be glad to have your business. And let you in on the secret of local produce. That's a little funny thing. But, it's not exactly the joke. How beautiful to live in places where, yeah. Yeah. How beautiful to live in places where food grows readily and is plentiful. And is grown nearby. And thus, a very beautiful thing is born. You can be a part of it. But that's not exactly it. More local world. A faster and sure fire, sure fire way to reach a more local world. How incredibly brilliant and everything can be more local and eventually moving into local gardens and people. The moving lawn.
How might something better work? In creating a universal basic minimum, you can start with people, you use the current systems that you've got and progressively make them more bulk using resources of manpower that is reliable within local communities until you have woven a tapestry, or you've created a loose network of yeah, that, be yeah, and you just repeat that process until you have a very large amount of resources available that moves things from where they need to go in the most efficient way of doing because it's already going there anyway. this slowly creates a world where there's more sharing, I suppose, because you already know, where different resources are or are available, or could be used, and it's just a process of getting them from different places instead of creating more things, which creates a a human driven process instead. Yeah, there's that.
all
##### As a process
As a process, you start with Peaceful Foundation volunteers who put their hand up that they need help or would to be part of it. and yeah, that's beautiful over time something's helping someone becomes cheaper in general because of the local pattern, we'll we'll aim to help anyone who puts their hand up pretty much. there's people and volunteers, anyone who needs it, really, but it's we can make broad sort of assumptions that a lot of the people that would be, probably already affiliated with Peaceful Foundation campaigns, which is fine to be able to do, and then you then get them, you ship them goods directly using you want to eliminate wherever you can, you don't want to physically hand money to people, but you use already existing supply chains to get goods to people no matter, in however they can get them, in sort of the most bulk amount of way that they can, depending on their circumstances. for instance, if someone was able to, cook food and distribute it to people who are experiencing homelessness in their local community, and create fresh meals or something that with a group of other volunteers, based on them being able to Yeah, do such a thing safely. or provide different things or whatever, Yeah, you can instead create a surplus of of things, I suppose. you start off by assisting people in getting them that they are at a surplus themselves, at it a, thing. and then give them yeah, and then you just progressively work your way up. Do you get what I'm getting at? There's a way better way of phrasing it. there's prosocial things you can do where you that, I sort of went on a bit of a tangent when you're doing that, but progressively as you get more people in an area, you are doing, you are just pooling resources together, and this includes yeah, money as well, but it's this makes makes a dollar stretch further, and help the most amount of people possible. that's, you sort of go into that in the donor section as a system, but you don't really know, think about that, I suppose. then until you are delivering yeah, that sort of, you put that in the donor section, I think, but not in this section. yeah, you're, you'll scaling it up until you start off with a volunteer who then gets groceries delivered to their house but we try and eliminate the need for plastic in such a thing, that they are then able to be helped, cause we're using already existing supply chains, then you get other volunteers to help them map the most efficient way of going and doing grocery delivery, for such a thing, or doing figuring out how you can supply using local, green groceries or local supply chains if you haven't already. Or there might be grocery delivery from local places there that you can there's a better way of, proposing that. And you can even get the volunteer themselves to propose the most efficient way of doing it, and then other people, because the process of doing is transparent, that how much it takes to help someone within this hexagon, is transparent, then other people can go and suggest suggestions on how to do such a thing, for instance. yeah. there's that. And then you just slowly work the way up where you create better systems of doing until you're delivering pallet-fulls of vegetables to public spaces, or spaces where you can to feed as many people as possible. And then you also have a surplus of food that's been created to help as many people as possible, I suppose. there's that. That's how you do something to assist and is good. And yes, it is. Yeah.
// start with anyone who puts their hand up, probably starting with those already
// over time, helping someone becomes cheaper and gentler because the local pattern is known
1. lifting people up
2. finding all resources
3. helping people together.
we will aim to help anyone who puts their hand up
people and volunteers
any people who need it
and since resources keeps growing
and then more people into it who are down to participate or receive
since there is more or less no downside
the most at risk people within peaceful foundation
many differ
peaceful foundation people
mo
more active citizens
send resources to someone directly
this person is aiready receiving support
is not a volunteer
and has no requirements to
over time, the unit cost of helping someone reduces as
//making sure that we can fund the thing
//we will focus first on active citizens
##### As a system
Additional notes as a system would be that the whole thing is both incredibly simple and, we're just creating as far as, the implementation of such a system is concerned, and how, that should work as a whole, that is both, extremely elegantly simple, because everything is a noun and a thing, but and we speak on how we, how my, the, the whole experience as a whole, but it's also can be extremely verbose, and, I don't want to say complicated, but there are many, yeah. anyone, familiar with game Factorio? It's that for local communities.
As a system, underlying the feelings, yeah, it's just small deterministic building blocks that fail growth gracefully. yeah, every object on earth can be a noun, verb or adjective in the story, that this is all really good. I this. yeah, it should be every object on earth has yeah, for instance, a bicycle or whatever. yeah, you're defining a specification system for that you can end What I'm trying to illustrate here is that every part is a independent building block for other things. when you get down to such a level, in what, individual people can do, or for instance, their capabilities or things that, or for instance, has access to a bicycle or knows how to bicycle repair, or things that, then there's a lot of different characteristics that you can reduce the entire world into somewhat data. you can't, yeah, you can't get, consciousness or whatever, but that's super complex, I'm I'm smiling and joking to myself when I'm saying that, is it? No. you don't need to include that in the thing, but anyway. there's that and then you are just creating ways of moving things to different places that fail over gracefully. yeah, there's my little example of the rubbish truck, man, in the morning could pick up something from a one place and put it down another place. yeah, and this is a slow thing, yeah, and it's a callback to I've that's the reason the assertion section, I explained sort of these useful assertions in the terministic verses algorithmic. there's that and yeah, you just combine all these things together and find what needs to be where, and because people could then there because each that object on earth can have different characteristics, you can create better ways of inputting them in into the system in ways that people need them, or because we have a surplus of all these different things, then it it people could AR categorise all these all the different objects and surplus in my quarter homes, or things that, that could be useful somewhere, or that are not. yeah, for instance, if they need to be distributed somewhere, you can effectively be if there's a blanket, if someone needs a blanket somewhere, then and within a local community and someone has a spare blanket, and someone else needs a blanket that has whatever, then you can then either get the person themselves to deliver it, or if they can't, then someone can pick it up from out the front of their house or wherever and drop it to another place, and because the entire thing is linked through a reputation system that allows not much reputation to form, you don't want five stars or anything that, but just oh, vouched pretty much. that's how you do the entire thing. but not much dwelling on the reputation system because you can get someone who's yeah, got a decentralised identifier, yeah, we sort of discuss all this in Peaceful Passport. But doing such a thing, you effectively create ways of allocating surplus resources in different ways. And if things need to be in a certain place by a certain time forever, then for instance, someone might cycle a big basket of potatoes somewhere if they needed to be somewhere, right? yeah, but yeah, or someone might need meals delivered, or something that, or, or some sort of thing. And it's not much what do you need to be done to be able to do, it's more just there's a surplus of different things, and for instance, a truck or something, might take a bunch of potatoes to another place, and then a whole bunch of people on bicycles, instead of having to send a whole bunch of cars to go somewhere. or there are there are very efficient ways to create networks by which if there's a huge amount of resources to divide it up into smaller resources based on how much to be where, there's effectively, the entire thing is very efficient. you, and then you have yeah, as a system, you're just repeatedly. this is the summary of the thing. You're just repeatedly optimising the distribution of needs and objects to different places in the most efficient ways possible. but except that fail over gracefully because they're deterministic, that there's always a fail safe, or multiple redundant sort of oh, it the the whole thing degrades, instead of eventually someone can just some random volunteer close by can be I need to go in my car and drop this to this, because because every other logistical thing has failed and I am available and I'm happy to do it. there's that. for instance, a van could pick up a whole bunch of things in the morning and drop them to different places. that's the concept as a whole. Does that make sense as a system? that's that's pretty much it. you're because there's many deterministic building blocks, everything is you categorise everything in the lens of an object, and then you just and everyone has needs and there are efficient ways of then it becomes a really fun problem to solve, instead of the current algorithmic mess that we have currently. Or not even that, but instead of what's got us here currently. then you can use resources more effectively, I suppose. yeah, I don't know, it's it's sort of this section, this and the previous section, they are supposed to be sort of artistic sort of summaries that explain the concept of the things as a whole. But I'm just rambling, I suppose. yeah, then yeah, there's a better way of explaining this and you got to got to synthesise this entire thing into something beautiful. Thank you, ChatGPT.
// underneath the feelings, it’s just small, deterministic building blocks that can fail gracefully
// every object can be a noun, verb, or adjective in the story of “how might this help someone?”
// it should be simple enough to sketch on a napkin, even if the backend is clever
deterministic
building blocks
defining the backend thing also
assignment of little rules
similar to clippy previously defined
getting all of the resources within an area
defining them with characteristics
noun, verb or adjective
// the same thing can mean “a way to move a person”, “a way to move potatoes”, or “spare steel for something else” or anything or this list perhaps and beautifully
for example, a bicycle
can be
riden (and given to someone)
transporting something
itself transported
turned into spare parts
modified into something else
melted down
or any number of different actions
there could be multiple manifestations of an app but who knows
as an app
participating
receiving
donating
only a small amount of money
#### A distributed system for practical kindness
In the how might something different work
and then below that looking at the experience for
a distributed system for practical kindness within
that's participants and recipients and donors
We would focus first on donors
All of the summaries of that thing are really good and there's a whole bunch of sections beneath it the sort of double slash beginning of a lot of these things
is very good and summarises the entire thing as a whole and it's really good and honestly the whole thing should just sort of be refactored around those things but there's other points that don't really need to be um really elaborated on there's too much prose for instance in tax deductible where possible In many jurisdictions deduct donations to the undercurrent are tax deductible
And that's not really right or highly
this means that reduce their tax bill slightly while increasing the basic safety of their own community and I'm doing this all in a pretty funny and intense voice
And then larger contributors can justify serious to boards accounts or families with clear social outcomes That is not right that's not exact it's a it could just be a little node and and in many places deductions the donation is tax deductible and people who are in the know with that would appreciate that because it's a public benevolent institution
yeah
Or some more beautiful and subtle way of wording that
// a quiet and practical answer to “how do we make sure no one slips through?”
// not theory or vibes, just resources moving in calm, human ways
// we have a surplus of stuff
// putting it to different places
// and the whole thing doesn't need things to function
// and is deterministic so fails over nicely too
//: as in, imagine there's a solar flare, or natural disaster, or who knows, anything -- just something so as such you need everyone to come together
// the whole experience is building blocks of different functions and different things and such
// the whole thing is factorio. we build the thing as a programming language and everything can fail and countless everything and objects and such
// so for the distributed system for practical kindness as the undercurrent or flow as a peaceful foundation for people; the aim is to use concensus and build systems that are deterministic so they can fail and adapt to everything
// (the entire thing can be a game as a user experience)
for participants
// the world becomes slower and more humaan
// a complete understanding and eaou can not
to move resources from where they’re spare to where they’re needed
as quickly, cheaply, and locally as possible
to turn “I’m stuck doing fake job applications” into:
“today I moved food, blankets, and light to people near me”
for recipients
// you receive
for donors
// in person
// in some sort of app format
// daily or in whatever timeframe
// you can not
// we do not want anyone
// making an ideal donation for you
// you donate money in the most effective way
// you are looking at a map of hexagons that are coloured in a scale of different colours from green to red
- //
the process is far more effective, transparent and is relatively instant.
principles
local first
solve needs within a hexagon or cluster before reaching outward
speed and transparency
money and goods don’t sit in accounts or sheds for months
simplicity
fewer hand-offs, fewer forms, fewer delays
stability without dependency
people feel held, not trapped
cooperation over control
communities decide how the system looks on the ground
##### Participants
// help the helpers first so it blooms outwards
// the world becomes less sharp at the edges
// there are pockets where you just quietly know “I’ll be okay for food and warmth here”
// you never have to perform worthiness or gratitude to keep being welcome
// the world becomes slower
// everyone
// resources,
everyone who touches the system is a participant
some give time
some receive support
some give money or goods
most people move between these over time
in almost every community, we can reasonably expect:
at least a few people willing to help
a few people needing help right now
the undercurrent is about:
connecting those people through a shared tool
so no one has to struggle alone or “prove” their worth
people with some time and capacity
unemployed or underemployed
gig workers in quiet periods
students in school, university, or vocational training
parents and carers
people between things
(major life changes, relocations, breaks from study or work)
they might be:
living with parents or extended family
sharing a house on a tight budget
juggling studies, caregiving, or irregular shifts
stable enough to help, but not always stable enough to ignore basics
common patterns
between jobs
applying for roles that never write back
doing unpaid tests and “trial days”
exhausted by interviews that lead nowhere
studying
full-time or part-time students
school, TAFE, university, other training
wanting to do something real between classes and assignments
parenting and caring
parents or carers who:
hold families together on limited time and money
can’t take on a formal job
but could give a few consistent hours each week
people between things
changing cities, courses, careers, or relationships
needing something steady and decent to plug into
while the rest of life re-arranges itself
what they bring
real resources
transport
car, bike, scooter, or just strong legs
space
shelf in a garage
freezer space
a living room or backyard for small meetups
tools
cooking gear, tools, or basic repair equipment
skills
cooking, packing, cleaning, organising
web dev, design, writing, translation
spreadsheet brain, logistics brain, “people wrangling” brain
soft skills:
listening, keeping calm, noticing who’s missing out
social reach
school gates, campuses, group chats, clubs, faith spaces
online communities, discords, local forums
they know who is quietly struggling and who quietly has more than they need
how they relate to support
volunteers are not assumed to be “fine”
some will also need basics themselves
food, toiletries, bedding, phone credit
we treat:
“needing help this month”
and “helping others most months”
as normal phases of the same life
for volunteers close to poverty:
the undercurrent can:
stabilise their basics
cover fuel or transport costs
lighten their household load where possible
so that:
they are not punished for stepping up
and don’t burn out from giving more than they can spare
how we invite them in
initially, most volunteers:
come through existing Peaceful Foundation campaigns
quit-easily, calm.college, reasonable.diet, learnstuff.today
already have a Peaceful Passport
and some history of small, real actions
we ask very simple questions:
how much time do you honestly have?
what kind of tasks feel good for you right now?
what do you already have — skills, tools, space, or transport?
are you also needing help with basics at the moment?
the goal:
match people to tasks that fit their life
not squeeze them into someone else’s idea of “service”
let them reduce their reliance on the undercurrent over time
as their own situation stabilises
and their role in the local crew grows
they’re not “staff”
they are neighbours and peers
logging what they do through their Peaceful Passport
there is no obligation to be endlessly available
people can step back when life is heavy
and return when they have capacity again
the system:
assumes fluctuation
and is designed so that:
many people doing a little
is safer than a few people doing everything
ways in
they might:
hear from a volunteer
see a poster at a campus, clinic, or faith space
or be referred by a partner organisation
sharing circumstances
the undercurrent asks for:
what’s actually needed this week
meals, staples, toiletries, blankets, phone credit
any constraints
allergies, access issues, safe meeting times
contact method
phone, in-app, or via a trusted place (church, centre, campus)
it does not ask for:
long written stories
humiliating “prove you’re poor” details
stewards see:
summary needs per household
without broadcasting names or drama
what happens
their hex shows:
X households needing food this week
Y needing bedding
Z needing connectivity
stewards:
match them to upcoming drops
flag if a delivery is needed
e.g. disability, safety, or very young children
in most cases:
they go to a local meetup
park, hall, co-op kitchen, campus room
at predictable times
no one gets a box in the dark from an anonymous van
it’s calm, human, and visible
how it feels
it feels like:
“this is my community’s pantry and toolbox”
not “I’m a case file in a system”
they see:
other people receiving and giving
the same faces over time
when their situation stabilises:
they are invited — not pressured — to help too
help is offered on the assumption that people are trying
recipients are invited to contribute when and how they can
there is no moral test and no performative gratitude required
stability without dependency
undercurrent is there so people can breathe
not so they become stuck in a new system
relief comes with pathways into:
co-ops
local crews
learning
paid work where possible
post-charity, mutual uplift
this is not “saviours and victims”
it’s neighbours using a shared tool
every dollar, blanket, and potato:
moves through people
creates bonds, not just transactions
limits, stated plainly
we probably can’t pay everyone’s rent
but we can:
keep people fed
keep them warm
keep them connected
give them work that matters
and as more communities reach that baseline
they help others reach it too
##### Recipients
// the world becomes less sharp at the edges
// there are pockets where you just quietly know “I’ll be okay for food and warmth here”
// there is no distinction between participating and receiving
//: no scores or ranking systems
// you never have to perform worthiness or gratitude to keep being welcome
// the world becomes less intense
// the world becomes less intense
// there is no scoreboard that says “giver” or “taker” next to anyone’s name
blurred roles, not fixed labels
in reality, almost nobody is “just” a recipient
most people who receive help also give in some way
most people who give will, at some point, need help
the lines are soft:
a volunteer who loses work may need food this month
a doctor or nurse may need rest and easy meals more than anything
a student might need support during exams, then help others later
the undercurrent treats:
“needing support”
and “being a helper”
as different days in the same life
not as two separate kinds of person
who counts as a recipient?
anyone whose basics are tight enough that:
food is stressful
warmth or bedding is unreliable
hygiene items feel like a luxury
phone credit or data runs out too fast
this includes:
people in visible poverty
people in hidden poverty
living with family, couch-surfing, in overcrowded homes
people who are overworked and exhausted
nurses, doctors, carers, shift workers, support staff
people who are “okay on paper”
but one bill, rent rise, or crisis away from collapse
people experiencing homelessness
sleeping rough, in cars, in tents, or temporary shelters
who may need deeper, longer-term support than most
rough sleeping and deeper support
people sleeping rough usually need:
more than just a food box
safe places to sleep and wash
consistent contact with calm, reliable humans
the undercurrent alone cannot:
solve housing systems or trauma
but it can:
ensure no one sleeping outside is:
regularly cold
regularly hungry
completely cut off from phones and people
create:
stable, predictable hubs where rough sleepers are:
when food will be there
when hot drinks, blankets, and conversation are available
link gently into:
existing homelessness services where they are safe and respectful
so people are not bounced between systems with nothing in hand
outreach
volunteers and partners:
don’t wait for everyone to come to hubs
where it’s safe, they:
bring food, blankets, and basics to known sleeping spots
offer information about nearby hubs and times
make sure people know they are welcome without paperwork
the tone is:
“you’re allowed to exist here, and we’ll try to make it less brutal”
not:
“here’s a programme to fix you”
you can’t volunteer from empty
the system assumes:
if you are in severe poverty, homelessness, or exhaustion
you might not be able to give anything right now
for those people:
there is no expectation to “pay it back”
there is no requirement to volunteer to “deserve” food or warmth
the priority is:
take them out of acute strain first
feed them
warm them
steady their week
then — if they ever want to — show them small, optional ways to help
everyday receiving, not case management
many interactions are casual, not formal:
a hospital or clinic might have:
a small undercurrent table in the staff room
real food, ready to heat
snacks and staples volunteers have organised
so an overworked nurse:
grabs a meal at the end of a long shift
no paperwork, no questions
on the way home:
they walk past a park or hall hub
volunteers are giving out food and basics
neighbours are milling around, talking, catching up
someone simply says:
“hey, do you want to take a bag for the week?”
they take it, wave, and keep walking
there is:
no scanning a passport to be “allowed” to eat
no public sorting of who is “poor enough”
it feels more like:
a familiar, friendly part of the street
than a service or a queue
where the passport fits (and doesn’t)
for some distributions:
hubs may lightly track:
how many households were reached
rough volumes of food and supplies
this is done at:
hex / hub level, not person level
for individuals who:
receive ongoing or higher-intensity support
we may:
link their needs to a pseudonymous passport
so stewards can:
plan routes
avoid duplication
notice when things are improving or getting worse
what we don’t do:
require everyone at a table or park to “check in” digitally
tie a one-off meal to a permanent record
use support history as a gate or a score
short bursts, changing needs
recipients can:
let the system know when they’re planning something specific
“having a few friends over this weekend”
“need a bit more this month because of extra kids at home”
or:
say nothing, and simply show up when a hub fits their day
the undercurrent is designed for:
a mix of planned and spontaneous help
people who can’t always predict their week
how it feels on the ground
for someone needing basics:
it feels like:
their city or town has a softer texture
there are places where they will quietly be okay
they see:
familiar volunteers
other neighbours receiving and giving
over time:
shame fades
it becomes normal to say:
“yeah, I grabbed some potatoes on the way home”
for someone glancing at the map:
it looks less like a “service directory”
and more like:
a quietly growing network of:
shared kitchens
pickup spots
potato tables
and little pockets of calm
if they want to:
they can tap into the details
see where food tends to be available
see which hubs they might one day help at
or which ones they might visit if things get tight
moving from receiving to helping (if and when)
if a recipient’s situation stabilises:
they could, if suitable, to:
help at the same hubs they once visited
map new resources
host or support small gatherings and meals
this is framed as:
a natural next step if it feels right
not a debt to repay
the system keeps the story simple:
“some days you need more
some days you can give more
people are here for both.”
starting point
someone is:
living with parents or in a share house
unemployed or underemployed
tyred of fake job applications and pointless “activities”
they already have:
a Peaceful Passport
a bit of history from posters, calm.college, or meals
what they see
open the app → “my day”
a small list of things they could do:
“drive 7km to pick up veg boxes, drop at park at 4pm”
“help pack hygiene kits at the hall from 2–4pm”
“check in on freezer stock at the co-op kitchen”
each with:
estimated time
fuel covered or not
any physical requirements
fuel and thank-you top-ups
if they take a driving task:
the system can issue a fuel card or digital voucher
valid at local stations
capped by distance and vehicle type
they log:
start and end odometer
or allow coarse GPS distance (hex-to-hex, not street-level)
the app can also add a small surplus:
a modest “thank you” top-up
for someone who’s doing this regularly
all of this:
records in their passport as contribution
never framed as a wage
but enough to make helping easier than doing nothing
how it feels
instead of:
sending CVs into a void
refreshing job boards that list fake roles
they experience:
“I moved 80kg of food”
“I helped four families get blankets”
“I know exactly what my hour did”
their week has rhythm
regular tasks
recognition from stewards and neighbours
simple proof that they matter
##### Donors
// you can feel sure your contribution is used quickly and well, not parked in a black box
// giving is designed to feel light, calm, and easy — no guilt, no pressure, no drama
// even one dollar, when suitable, scaled across many people, becomes a vast river of basics moving every day
// the whole experience is beautiful and reassuring: you see real things changing, not just numbers on a receipt
// you know your money turns into food, fuel, light, and tools almost immediately—not a vague future promise
// it’s easy to set a comfortable pattern and trust that it’s being used well, without having to think about it every day
// the “one dollar a day” idea scales quietly and beautifully: tiny amounts, everywhere, keeping communities afloat
// the experience for donors is refreshing
// you can see where your donations are being used
//: either, set and forget and more or what
//:. people can create recipes with how much they want to donate
//:.. so that things feel genuine and effortless.
you never want someone to feel any 'oops' or even intensity about donating
and obviously there are different circumstances
// or donate more
//: have transparency about where their money is going
// we believe the entire concept
// so little money is needed and benefits everyone
who they are
anyone sending money into the undercurrent
students chipping in a few dollars
workers giving a “this would’ve been takeaway” amount
people with higher incomes sharing more consistently
foundations or philanthropists backing specific regions
it is not a separate class of person
most donors are also volunteers or recipients at different times
it’s just another way to participate in the same pattern
tax-deductible where possible
in many jurisdictions:
donations to the undercurrent are tax-deductible
that means:
people can:
reduce their tax bill slightly
while increasing the basic safety of their own community
larger contributors:
can justify serious commitments
to boards, accountants, or families
with clear social outcomes
a simple meme to remember
if everyone on earth gave about a dollar a day:
that would be roughly eight billion dollars of real resources moving daily
we don’t necessarily expect that to happen
but it’s a useful picture:
even tiny amounts, when coordinated well,
can keep whole communities fed, warm, and connected
and the experience of giving stays light, certain, and quietly beautiful
what they can choose
donors see two simple choices:
,
Donors can help their local hexagon and then based on the privilege of the relative privilege of that hexagon let's say,, people in Uganda you could have many people. This is just an example to myself but you could have you could help many people with wells or things that., but oh we need to get,, some obviously you want the place you want to live in to be better. But yeah, also depending on the current status globally comparatively to other hexagons then we also donate to where the money was stretched furthest. a little a little bit of your donation is so we can build infrastructure for,, we we create local communities everywhere not just where we live. So,, but ideally it's it's mainly that there the spillover effect it's going to reach places that are closer to you comparatively speaking, Yeah, it'll reach it'll reach places that yeah, would be, closerish as well but going through it imagine a green hexagon and you want to donate. So not a lot of your donation goes it's it certainly supports your green hexagon. But then it sort of starts searching out broader and broader and broader broader and then a bit goes to the other side of the world. Or really far away but conceivable or whatever, not for just for something beautiful happening a well that's being built somewhere is really cool., there's that., and so you kind of want to you don't even want two simple choices. it's it's really just that's how donations work and it's not really what can they choose. a lot of that has been sort of a lot of different things that ChatGPT is sort of filled in,, and sort of extrapolated but some of that doesn't really work. But large reinvestments sometimes or corporate startup funds or things that or things buying a skyscraper to,, re-poop repurposing a mostly empty office block. That's a good one as well. So yeah, that's, that's nice,, that thousands of people could be fed cheaply for years., so live and recent logs, yeah, all that's pretty good as well. So,, yeah. Yeah. You don't have to overcomplicate the local-first with honest flexibility. You just want it to be the the simple donation mechanism and just mathematical understanding of how donations work. because primarily people are mainly going to support the hexagon they live. So you just let them choose any hexagon on earth. And then yeah, they it just flows out. And so if you donate to your own hexagon, then of course someone's going to get fed in your hexagon and you'll get a little thing and then also there's something that will happen on the other side of the world that you're a part of as well, which is pretty cool.
help this hexagon
money flows first into basics near where they live, work, or care about
with a gentle spillover:
if their hex is already well-supported
excess automatically helps neighbouring hexes under more strain
help “where it stretches furthest”
routed to hexes with:
high need
efficient logistics
clear plans to reduce long-term cost
and occasionally:
into step-change infrastructure
when that clearly multiplies future impact
for most people:
this is all they ever need to decide
for those who want more detail:
they can see:
which strands their giving currently supports
food, fuel, hubs, shared kitchens, tools, co-ops, infrastructure
without having to micromanage it
what they see
donors see:
the real texture of life on the ground
how many people things tends to feed
what a delivery route costs per week
which hexes are stable and which are under strain
a simple “strata” of cost:
cheap, high-frequency basics
staple food, hygiene, phone credit, local bus cards
fuel for volunteers moving blankets or veg between hubs
mid-range supports
freezers, kitchen equipment, solar lights, rain tarps
tools and parts for mechanics keeping old vehicles alive
small stipends for key local coordinators where needed
large, rare investments
co-op start-up funds
shared storage or cold rooms
and sometimes:
things like “buying a skyscraper”
e.g. repurposing a mostly-empty office block in a city
into hydroponics, kitchens, and housing
so thousands of people can be fed cheaply for years
for people who want more depth:
live and recent logs:
what went out in the last 24–48 hours
photos and short notes from hubs and crews
examples of tasks currently being funded
a van repair
a batch of bus passes
a 3D-printed part that keeps a key fridge running
how their money moves
core norm:
around 90%+ of funds flow out as basics within 24–48 hours
the rest:
covers predictable near-term commitments
or seeds carefully chosen infrastructure
a single contribution might:
top up fuel for a volunteer moving sleeping bags across town
fill the gap in this week’s staple food orders
keep phone credit alive for households who’d otherwise drop offline
pay a mechanic for parts to keep an old delivery car roadworthy
fund a small 3D-printed or machined part
that saves replacing an entire appliance
pooled over time, contributions can:
help convert underused urban buildings into:
shared growing spaces
storage and kitchens
community hubs that feed thousands cheaply
anchor co-ops and bulk-buy networks:
in places where food is expensive but buildings are empty
the point is:
donors aren’t just “funding boxes”
they’re paying for motion — the movement of food, warmth, light, tools, and people
a simple meme to remember
if everyone on earth gave about a dollar a day:
that would be roughly eight billion dollars worth of resources moving daily
we don’t necessarily expect that to happen
but it’s a useful picture:
even tiny amounts, when coordinated well,
can keep whole communities fed, warm, and connected
and the experience of giving stays light, certain, and quietly beautiful
local-first, with honest flexibility
when someone chooses “my hexagon”:
the system:
prioritises their area and nearby hexes
while still reserving a small, clearly tagged slice for:
projects that dramatically reduce global cost
or unlock new capacity (like major useful stuff or buildings)
all of this is:
transparent in dashboards and reports
“80% used within three neighbouring hexes”
“20% contributed to a regional cold-storage project”
this balance keeps us:
not beholden to rigid, arbitrary rules
but clearly accountable
so donors can see when and why their contribution helped beyond their own hex
local-first, with honest flexibility
when someone chooses “my hexagon”:
the system:
prioritises their home hexagon first
as long as there are clear basics to fund
or useful reserves to build (e.g. a freezer, hub gear, tools)
then lets support gently ripple outward
to nearby hexagons with:
higher unmet need
shared hubs or delivery routes
or clear “we’re nearly stable, just need this last piece” cases
and, when it clearly reduces suffering for many:
can route a small share along existing routes
towards more distant, high-leverage infrastructure
(e.g. a major shared kitchen or tower farm in another city)
in practice, a single donation to “my hexagon” might:
cover basics and motion in their own hexagon
strengthen one or two neighbouring hexagons on the same routes
and send a small, clearly explained fraction
through that chain of hexagons
to a larger shared project that benefits many areas at once
all of this is:
visible as a simple breakdown, not a mystery
e.g. “your $40: 60% → your hexagon, 25% → two nearby hexagons on your routes, 15% → shared kitchen serving your wider region”
explained in plain language:
which parts stayed close
which parts helped further away
and why that pattern made sense this week
if someone wants to help a specific place:
they can always choose that hexagon or project directly
e.g. “Kuala Lumpur city centre” instead of “my hexagon”
in that case, their donation is aimed there on purpose
subject only to basic safety and feasibility
this balance keeps us:
local-first in spirit and practice
free from rigid, arbitrary rules about where every dollar must go
but clearly accountable about:
how far each contribution travelled
and what it unlocked along the way
invitations, not pressure
the tone toward donors is:
“join in if this feels right”
not guilt, alarm, or moral scoreboard
they are:
invited to stay involved
invited to attend hubs or events if appropriate
free to stop or change their giving at any time
the system’s job:
is to show clearly what their money is doing
not to keep asking for more
a simple meme to remember
if everyone on earth gave about a dollar a day:
that would be roughly eight billion dollars of real resources moving daily
we don’t necessarily expect that to happen
but it’s a useful picture:
even tiny amounts, when coordinated well,
can keep whole communities fed, warm, and connected
first view
open the map → see hexes
shaded by “impact per dollar” or “current need”
two simple options:
“help my hexagon”
money goes to immediate needs near where they live
“help where it stretches furthest”
money goes to hexes flagged as most efficient per dollar
choosing and giving
they tap a hex
see a short summary like:
“this week, $1 here helps feed 3 people”
“$10 keeps a delivery route running for a day”
“$40 tops up phone credit for 5 households”
they choose:
one-off or recurring
public or quiet (whether to show up on a generic donor roll)
the app shows:
what share goes to:
food
fuel and repairs
toiletries and bedding
connectivity
light-touch housing support
audit trail and feedback
immediately after donating, they see:
“your $25 joined 138 others in this hex today”
“today that pool funded:
– 42 veg boxes
– 120km of deliveries
– 17 phone top-ups”
later, they can open:
a simple running log
filtered by hex and time
aggregated stories
photos of packed tables, parked vans, stacks of potatoes
short notes from stewards
no individual is ever singled out as “the person you saved”
it always stays at the community pattern level
how it feels
not:
“I sent money into a black box”
but:
“I can see the routes, the crates, the hubs my money keeps alive”
they experience giving as:
paying for motion — food, fuel, light, tools
keeping a living system flowing
rather than topping up a static fund
##### Communities
// farmers
// people
#### What might this feel like?
(it needs to feel better)
// it is pleasant
// feels good
// feels better
// helping out the people around you
// open access
tub of toothpaste
potato
transit
// tub of toothpaste
//
// walking down the street, free vegetables
//
supplies
.
everywhere
.
and always works with whatever resources
and always keeps on getting better
Okay, so here is a short understanding of donors that... You know with certainty that your donation is going to be used effectively and immediately, and the ease by which you're donating and the comfort by which you can is implicitly easy and calm and good, and the concept of donating a dollar a day for everyone on earth is extremely scalable and benefits as many people as possible. And the experience and understanding is beautiful.
#### What keeps people healthy?
Well, certainly not chronic stress.
We can alleviate stress for everyone around the world
not bare minimum
but in some cases, bare minimum
global picture of the world
//
overview
health starts with boring, reliable basics
eat properly
sleep warmly
stay clean
feel safe
stay connected enough to ask for help
the undercurrent focuses on:
cheap, dense nutrition
dignified hygiene
warmth and rest
simple connectivity
targeted stability for housing and utilities
Last I wouldn't even go into fluoride. it'd last for, yeah. You walk down the street and there's free vegetables and people are happier and
You'd start off with the toothpaste example.
You feel noticeably more pleasant.
You feel noticeably, yeah, not even that.
I might just brainstorm, I just instead of enforcing myself to describe such a thing, I might just think about it and random words will come up and
beautiful.
I suppose a more broad question and this would be under a four a main sub heading which would be what would alleviate poverty, which would be that everyone would get what they needed, or the bare minimum and then you would slowly raise that minimum up. everyone needs food, everyone needs shelter, everyone needs to feel comfortable while they sleep. everyone needs to be relaxed, be confident that things are going to be okay. and yeah, that reliability, safety I suppose. they need to be in a community that takes that that feels calm and good and is happy. yeah, they need to be able to provide for dependents if they if they wish to. I'm sort of just riffing. but broadly speaking, yeah, they need food, shelter, water. They need yeah. transport in some places, reliable transport, or goods being brought to them, I suppose. if that. Yeah. yeah, I don't know. people are in different circumstances as well. someone who's experiencing disability has different needs to someone who isn't, or yeah. Yeah, caring, maybe. And a happy smiling and hug. Good vibes. Don't even know what to say.
##### Food
Just rambling about local gardens as well. You're describing in many ways, or who knows, and sending love and whatever. And just rambling about local gardens. And, you don't have to wait for anyone to radically reduce their, radically achieve surplus within the industrial system. I'm too wordy. It's more that right now, you can go to your local supermarket which has everything and prepare for a local world. Prepare for a more yeah, a local world. And if you buy plastic bottles, then get rid of most of them through giant water jug. And rest assured that your testicles are fine for now, that a lot of the research on plastic in blood has been contaminated by the reach searchers' plastic gloves. if there's any plastic in the room at all, at the amount that you're measuring, it's got to, rest assured, this will float out of your blood. Your body doesn't know what to do with it. it's just there, you can just eliminate plastic from the earth, yeah, from the world, yeah. That isn't, yeah. You have to do this with, you change your purchasing habits from is. Yeah. far faster ways to create the entire thing immediately and as a whole. the concept of olive oil, someone will bulk bulk get olive oil pretty quickly, and they may just sell it at the unit cost. You can start off immediately by doing that that you just have global food. Most things don't need to be that way that everyone's stocking up and things, stocking up, that's not really useful. Yeah, it's got to be things that don't need to be refrigerated is the metric that is going on. And you could create a self-sustaining, muscle system by icebox or central cool, central freezing. You don't even need that much land in building underground. And you don't need to refrigerate food stores either because they're underground. And, it's just got it. [Cough] [Chuckles] Laughing happy time. With a global compute cluster, you could even have, oh, this is very radical, but you would demolish most of the earth. Yeah. When it came time. Yeah, goodbye. There's nothing hitting something to relieve aggression. Yeah. yeah, you can, we can make the best tools for you to be able to demolish tyre repair shops. Would you let it happen to the family, who were safely well, we just it doesn't have to be concrete. You can repurpose everything that you've got that is wonderful that is resourceful. And people in this and demolishing things, could even be in a zen- state, who are just yeah, just slowing down my thoughts by hitting things. Don't even know. Instead of anyone in the streets, you just have everyone vibing. And quite wonderful, right?
// potatoes
// onions, potatoes, carrots, etc
//: local vegetables
// vegetables delivery to people
// using supermarkets as this is the cheapest mechanism
// farm or local suppliers
// bulk delivery
// scaling through bulk buying
// prefer cooperatives
// bes
someone gets a bucket of produce that keeps them healthy delivered to them and local
more or less, the idea is that you can't get anything that comes in single use containtering
what do you do experience is the joy of opening a big wonderful cornucopia of wonderful coloured vegetables and food
although, what you get is the best possible thing for you.
since some people can't even eat coloured fruits or vegetables
the main colour is white and depends on the capcicum chemical
and people experiencing this should have to put up with that.
or any other allergies or anything.
principles
cheap, dense, and simple
uses existing industrial food supply chains where needed
adapted to local climate, culture, and growing seasons
we will supply a reasonable amount of food to as many people as possible
seassonable fruit and vegetables
staples (example set)
potatoes, onions, carrots, and other hardy vegetables
legumes and rice suited to the region
mussels or similar dense protein where coastal or feasible
seasonal fruit and greens
non-processed oils for cooking
approach
focus on a few “workhorse” meals people can actually cook
use calm.college and reasonable.diet to teach and normalise them
bulk-buy whenever possible; portion locally
###### Curing Type Two Diabetes
you need specific ranges of salt and potassium and critical non-caloric inputs. critical. you will die of arrhythmia. and fasting causes a ***reversible atrophy*** and you need to be careful and perfect and know you are loved and also take breaks from fasting.
you will experience profound hunger with any other diet. we will give you a team of people making sure your exact demographic is as comfortable as possible. and, the choice is up to you. and: the more reasonable method is actually just having a good go to *eliminate* fat or sugar (so, amounts of the entire day of 5 grams) for a couple of weeks so that your metabolism burns more. and, then, just eat what's best.
moreso, a system, as peaceful foundation is all about those. but -- we also
although this is mainly to shock everyone into the reality of providing a universal for people in the subsequent paragraphs,
###### Don't Be Silly
"how much food do you need?" is the question we will ask people. and the answer to this can be calculated by people themselves using thermogenic calorie calculators. there's no real need to lie.
there might be groups for fasting in local communies if people make them on hexagons.world.
###### Making This Cheaper
// initiallly, the aim would be to buy vegetables and supplies in bulk
//. for participants and receipients to distribute in public spaces and to each other
// long term, the approach to reduce costs and increase local resilience differs in different places
// it is unlikely, for some time, that we will outperform the industrial food system
//. but we could grow incidental things; herbs, or potatoes
//. local resilience and ownership
// keep creating better and increasingly efficient approaches
// potatoes in buckets
// hydroponics
// in gardens and replacing lawns
// skyscrapers growing food
//. malaysia
//.. high vacancy rate
//.. government already looking at doing this
##### Hygiene and toiletries
The experience is waking up and you brush your teeth from a refillable tub of toothpaste. It's quite large.
You floss with floss within a reusable 3D printed pick.
Wonder what will happen today.
Everything everywhere is right there and is beautiful.
That's a beautiful thing in we don't necessarily expect that to happen. But it's a useful picture. Even tiny amounts when coordinated well can keep whole communities fed, warm and connected.
The only problem with that last bit is that the connected part.
another word there, because it just makes it sound too AI generated. And that's the only thing. There's no, there's nothing. warm and fed, can keep whole communities warm and fed. Then
you'd probably only just use warm. You would probably only just use warm. Apologies for my accent as well.
Can he warm and cosy. Warm and cosy would be pretty cool.
You could do fed, warm and cosy. Cosy could be good. Yeah.
principles
bulk, low-waste, and unbranded where possible
“everyone deserves to feel clean” as a baseline
examples
toothpaste
nano-hydroxyapatite [2] or similar
bought in bulk; decanted into simple containers
flossing
bulk floss sticks
3d print a holder and replace
or prefer biodegradable or recycled materials where reasonable
hair care
concentrated shampoo and conditioner
a few types only, tuned to common hair and scalp needs
these are cycled by people when your hair is responsive
sun protection
local norm:
sunscreen where appropriate
or broad-brim hats and face shields as more practical
without ongoing financial stress about basics
##### Warmth, sleep, and equipment
// transporting stuff
// ingeneous solutions
// old stuff
// we will get better ideas of where to get old stuff
many different living situations
people are in very different places:
sleeping in cars
couch-surfing or in overcrowded houses
in rentals they’re barely hanging onto
in tents, temporary shelters, or on the street
in very hot or very cold climates
we can’t fix everything at once
but we can make those situations safer, warmer, and less exhausting
the aim is:
not to create permanent dependency on “charity”
but to cover the basics well enough
that people have the energy and ability to change their situation
principles
start with comfort and safety
if people are freezing, soaked, or exhausted
nothing else works properly
cover:
warmth, dryness, and basic sleep quality first
make upgrades, not monuments
choose items that:
actually get used
can be repaired or passed on
don’t require fragile, complicated systems to maintain
solve for the person, not the ideal
some people will stay in cars, tents, or share-houses for a long time
we respect that reality
and design support that works there
rather than insisting on a “proper” solution first
stability without trapping
support should:
make each week more bearable
without locking someone into a service forever
people should feel:
“this helps me move,” not “this defines me”
use surplus before buying new
draw from:
lost-and-found stock
donated bedding and clothing
unclaimed items from institutions (washed and checked)
fill gaps with targeted purchases when needed
move gear, not waste
move gear between nearby hexagons as circumstances change
pay for motion (fuel, maintenance), not for landfill
track flows lightly so we know:
what’s in use
what’s idle
what needs repair or replacement
###### Examples of circumstances
// no stigma
sleeping in cars
consider:
window covers for privacy and insulation
blankets, sleeping bags, or liners appropriate to climate
simple organisers so the car is less chaotic
paired with:
knowledge of safe, legal places to park
or volunteers or institutions providing spaces for them to do so
access to toilets, showers, and laundry where possible
aim:
to turn “living in a car” from constant crisis
into something survivable while other options are built
homelessness in a street or tent
consider:
sleeping mats
warm, weather-resistant bedding
lightweight tarps or simple shelters
torch or small light with rechargeable batteries
aim:
to reduce exposure, damp, and constant cold
hubs and local groups:
keep an eye on longer-term options
use regular meetups to:
check on people
swap ruined gear for workable gear
adjust what’s offered with the seasons
insecure or overcrowded housing
people technically “have a roof”
but sleep quality and warmth are still poor
consider:
additional bedding and pillows
thermal curtains or window coverings
draft stoppers and simple insulation
small improvements here:
can massively increase rest and mental bandwidth
help families cope without needing to move immediately
climate differences
cold climates
focus on:
layered bedding and clothing
hats, gloves, socks
simple heating where realistic and safe
hot climates
focus on:
shade (hats, tarps)
breathable bedding and clothing
ways to improve airflow
the goal is:
to help people actually sleep through the night
rather than just “having somewhere to lie down”
central stores and local circulation
in most areas, it makes sense to:
build small, central repositories of:
bedding
basic clothing
sleep and warmth equipment
and then:
move items out to where they’re needed
using the same hub-and-spoke patterns as food
volunteers and stewards:
map surplus gear in each hexagon
use regular runs to:
collect under-used items
redeploy them to higher-need spots
log just enough data to:
avoid overstock in one place
and shortages in another
target
no one sleeping rough should be cold
if the network has blankets within reach
over time:
each hex knows it has:
enough warmth equipment for “a bad week”
and a clear plan to share with neighbours if things spike
###### Connectivity
principles
low but real
enough to reach help, work, and community
examples
prepaid phone plans
low-data, SMS and calls first
aimed at safety and coordination, not infinite scrolling
open or shared Wi-Fi
volunteers and hubs offering safe, clearly marked access points
rate-limited if needed, but stable
goal
people can:
call services
coordinate deliveries
check maps and job boards
keep a basic social fabric
housing and utilities
we are not a rent-replacement scheme
we will not pay people's rent
as this could overall increase the price of rent
overall, a better option would be moving people to wide spaces
perhaps in little hexagon homes, could be cute
however, prevent collapse where a little help keeps someone stable
particularly in places where utilities are very cheap
avoiding long-term dependency
also, paying bills directly or a percentage
prioritise situations where:
a small payment keeps power or water on
sharing space with others is possible and safe
##### Utilities
Much of the world lives decent, social, meaningful lives with unreliable or minimal access to formal utilities [3]. Peaceful Foundation does not assume constant grid power, piped water, or climate-controlled space as prerequisites.
Our goal is not to recreate high-consumption lifestyles everywhere, but to ensure enough light, warmth, water, and heat to live, rest, cook and connect using the simplest means available.
###### Electricity
// Share power for the basics: light and charging.
// Power banks circulate hand to hand inside hexagons, mates, neighbours, whoever is nearby.
// In places with patchy grids, including some developing or emerging countries, we get useful proposed things to where they matter.
//: leave room for cleverness, people will solve this locally in ways we cannot predict.
for instance, people experiencing homelessness
aim is using already existing utilities to enhance life for everyone
Electricity is treated as support, not a dependency
Prioritise low-wattage, high-impact uses
Assume intermittent or zero grid access is normal in many places
Baseline needs
Light after dark
Charging for one basic device
Occasional power for tools, not continuous use
Approach
Small battery packs and shared power banks
Rechargeable LED lanterns and task lights
Solar where climate and cost make sense, but never required
Charging hubs at community spaces rather than individual households
What we deliberately avoid
Powering heat-heavy appliances
Promising “off-grid independence” narratives
Creating new maintenance burdens people can’t repair locally
do they have solar panels?
could receive power banks to change during the day, as well
###### Water
The approach for us to make water more accessible differs within different regions, but brought we've already discussed that in Uganda, then they it's well boring wells. But then there's a lot of, for instance, you can take you can filter water pretty easily. There are consumer grade water filtration systems and you can do testing on the water to make sure it's everyday or whatever. to make sure that it's safe for people to drink. yeah. in many cases, you don't need to do that at all. or if someone needs stable drinking water, then you can have someone in a developed country you can just get water from the tap to fill up jugs of big water they people have shared water things and then they get disinfected and a lot of different yeah, you can give people personal and then they can fill it up from shared. If they're experiencing homelessness or something, then, however they're filling up water currently, we can just have a a bunch of water delivered to them or place sort of infrastructure in place that makes it more comfortable. yeah, and sort of, yeah, there's just one element of how you do that. then, in places that it needs to be filtered, then buying filters for places where a bunch of people are clumped together, but it should feel a surplus of yeah. And then that can that too can help other people and transport water to other places and, yeah. in places that, there might be involved in a small cash injection, for instance, could completely revitalise a local community by building a well or something, and that's a much a, a bore hole or however, that's that's a a much better approach. or if water isn't accessible, then can we make at the very least routes to transport water more effective, or have people bringing water to different locations or things that. yeah. There are a lot of different or can we can we get a closer water source or things that, yeah, the sort of the same thing with a bore hole sort of thing. yeah. Yeah, that's some approaches about how we solve it. It depends on people's circumstances or the community's circumstances as a whole, and really the country's, or really the communities. Everything's local after all.
The overarching goal for us in calculating these things is to have perspective over the problem. for instance, to eliminate someone from having to buy plastic bottles, you need to be able to give them water filtration in whatever way they can. it it cuts out them having to pay that cost, and then they get more water, probably, and there's regardless. Bit of a side there, felt I was going off topic. But in doing this, we want to have an understanding over the situation, and put in perspective how many people don't have access to water at all, and yeah. The We don't want to get too granular about it, considering homelessness and things that. We just want to understand the infrastructure within different countries and understand the problems that we're up against, because we can all solve them collectively together, but we need to understand where we're coming from. Yeah, I think that makes sense, and that's good. Anyway. I digress, but ideally, we want to consider how many countries and then have a breakdown within different regions, or have an understanding a big spreadsheet for countries about the the water situation, and then broadly, I suppose. And then Yeah, and it doesn't need to be a whole bunch of data or anything that, but maybe you could do confidence in the But you don't need necessarily need to do that. It's yeah, how you would it's calculating. yeah. I just don't want it to be too, it doesn't need to be perfect. It doesn't need to consider every sort of manifestation of the problem and people who'd it's just infrastructure within different countries. And then once you have a full understanding of that, then you can do how many places don't have water within different regions. and that, you can have different pie charts or and then an understanding of how many people on Earth don't have water in general, or are living in different water situations, because it sort of puts it in perspective that there are, there are anyway.
To calculate how many people have, you want to make the calculation simple where possible, ? if the vast majority of a country has drinkable water, you would consider for instance, the United States, as a country that has drinkable water, but just remember we're also pretending that the United States doesn't exist. yeah. This can be the most egregious example where you're "Yeah, not really defining it." which is very funny. yeah, you can think of America, yeah, it depends how many, Latin American countries have, have drinkable water, but, yeah. but, even though there are situations that gain a lot of attention where for instance, the water in Flint, Michigan or something, is not drinkable. On the by and large, water is drinkable in the United States. you don't have to calculate all those people on the, that, all the country, you just check it off. And you do that for most most developed countries. And then you have all, you just confirm that the water is drinkable for instance in Australia, or Sweden, or Germany, or, yeah, you don't wanna fixate too much on edge cases because ultimately, the governments of those countries could fix any sort of unsuitable situations as a whole. there's that. But then for, number two, then you consider all the different countries that have that circumstance of scheme of water directly to the house. That, yeah, but they don't have, yeah, but, that, that's sort of yeah, for instance, you might need to consider India as having, it depends how many people have that circumstance where the water is completely, or probably not, it's most of India, or people don't have access, there's different demographics in that and that's when you become more, granular within a country, or a region, or something that, or more a country. yeah. And then, then there's, yeah, obviously the problem is intersectional, or, obviously the problem is but you don't wanna use big words about it. It's mainly sort of understanding through the simplest possible understanding of how many people have access to different circumstances in water, access.
To calculate how many people have, you want to make the calculation simple where possible, ? if the vast majority of a country has drinkable water, you would consider for instance, the United States, as a country that has drinkable water, but just remember we're also pretending that the United States doesn't exist. yeah. This can be the most egregious example where you're "Yeah, not really defining it." which is very funny. yeah, you can think of America, yeah, it depends how many, Latin American countries have, have drinkable water, but, yeah. but, even though there are situations that gain a lot of attention where for instance, the water in Flint, Michigan or something, is not drinkable. On the by and large, water is drinkable in the United States. you don't have to calculate all those people on the, that, all the country, you just check it off. And you do that for most most developed countries. And then you have all, you just confirm that the water is drinkable for instance in Australia, or Sweden, or Germany, or, yeah, you don't wanna fixate too much on edge cases because ultimately, the governments of those countries could fix any sort of unsuitable situations as a whole. there's that. But then for, number two, then you consider all the different countries that have that circumstance of scheme of water directly to the house. That, yeah, but they don't have, yeah, but, that, that's sort of yeah, for instance, you might need to consider India as having, it depends how many people have that circumstance where the water is completely, or probably not, it's most of India, or people don't have access, there's different demographics in that and that's when you become more, granular within a country, or a region, or something that, or more a country. yeah. And then, then there's, yeah, obviously the problem is intersectional, or, obviously the problem is but you don't wanna use big words about it. It's mainly sort of understanding through the simplest possible understanding of how many people have access to different circumstances in water, access.
for the what keeps people healthy section inside peaceful people. in discussing water, I want to have a understanding of a pretty. For instance, I asked Abhigyan, who who is the big, the best developer. But I digress. How expensive water was in India. And he says that he's he hasn't thought about it for a long time, me in Canada, for instance, the water is fairly cheap and it's also drinkable and the cost for for this and the infrastructure as a whole to get it to people and how much it cost for scheme water compared to drinking water or things that. but we don't really want to consider the price of bottle of water, because that's not really, there's no point in doing that, because we're not gonna use it. But filtration and and yeah, a lot that. yeah, I've sort of or I've summarised the situation into four strata, I suppose. And if we could map that onto publicly available data, it would be better. well, that's what we'll sort of have to do. and for each of those. For instance, you don't have access to safe or accessible water would be in Uganda. They have to have wells or ball wells and water in the ground. there's that. that would be involved in boring a hole if there's accessibility with such a thing. then you can get drinkable water within a 30 minute round trip. yeah, that would be also in emerging countries as well where people have to go to a central well or something. or for number four, where you don't have access to safe or accessible water, it would mainly be that people are drinking unsafe water that has that is polluted and really bad. there's that. and yeah, people die from that and it's it's bad. you can get drinkable water within a 30 minute round trip. It's a pump in the ground or something that, would be yeah. sort of how it sounds a shared well or things that. I really want to paint a picture of the global water thing as a, as a whole. and then we can sort of think through and estimate how many countries and different regions have different circumstances. And then number two is you have tap or accessible water, but you can't safely drink it. And then in most cases here people then get water from they get water delivered or something that from a plastic bottle company. yeah, that. But we mainly want to focus on places that it's sort of Bali or outside of Manila in the Philippines and different places everywhere, and we can estimate how many people are in that zone. But it's Indonesia, how many different places, yeah. have yeah, non potable water. yeah, there's that. And then there's you can, then number one is you can drink water directly from the tap, which is mainly Australia. And we can sort of generalise it's mainly the circumstance, for instance, if there's places in a country where the infrastructure is good compared to everyone, then you would subtract, for instance, the Philippines, how many places in the country have drinkable water, which I think is just Manila, but I'm not sure. But that's just an example, you would subtract that. and yeah. Then you can think the think through the percentage within different. you can sort of generalise regions or whatever. But ideally, you would have a comprehensive understanding of the water situation within every country. would be the goal. there's yeah. And to be able to make that calculation,
for the what keeps people healthy section inside peaceful people. in discussing water, I want to have a understanding of a pretty. For instance, I asked Abhigyan, who who is the big, the best developer. But I digress. How expensive water was in India. And he says that he's he hasn't thought about it for a long time, me in Canada, for instance, the water is fairly cheap and it's also drinkable and the cost for for this and the infrastructure as a whole to get it to people and how much it cost for scheme water compared to drinking water or things that. but we don't really want to consider the price of bottle of water, because that's not really, there's no point in doing that, because we're not gonna use it. But filtration and and yeah, a lot that. yeah, I've sort of or I've summarised the situation into four strata, I suppose. And if we could map that onto publicly available data, it would be better. well, that's what we'll sort of have to do. and for each of those. For instance, you don't have access to safe or accessible water would be in Uganda. They have to have wells or ball wells and water in the ground. there's that. that would be involved in boring a hole if there's accessibility with such a thing. then you can get drinkable water within a 30 minute round trip. yeah, that would be also in emerging countries as well where people have to go to a central well or something. or for number four, where you don't have access to safe or accessible water, it would mainly be that people are drinking unsafe water that has that is polluted and really bad. there's that. and yeah, people die from that and it's it's bad. you can get drinkable water within a 30 minute round trip. It's a pump in the ground or something that, would be yeah. sort of how it sounds a shared well or things that. I really want to paint a picture of the global water thing as a, as a whole. and then we can sort of think through and estimate how many countries and different regions have different circumstances. And then number two is you have tap or accessible water, but you can't safely drink it. And then in most cases here people then get water from they get water delivered or something that from a plastic bottle company. yeah, that. But we mainly want to focus on places that it's sort of Bali or outside of Manila in the Philippines and different places everywhere, and we can estimate how many people are in that zone. But it's Indonesia, how many different places, yeah. have yeah, non potable water. yeah, there's that. And then there's you can, then number one is you can drink water directly from the tap, which is mainly Australia. And we can sort of generalise it's mainly the circumstance, for instance, if there's places in a country where the infrastructure is good compared to everyone, then you would subtract, for instance, the Philippines, how many places in the country have drinkable water, which I think is just Manila, but I'm not sure. But that's just an example, you would subtract that. and yeah. Then you can think the think through the percentage within different. you can sort of generalise regions or whatever. But ideally, you would have a comprehensive understanding of the water situation within every country. would be the goal. there's yeah. And to be able to make that calculation,
In how might something better work you are making people as comfortable as is feasible and there are a lot of different circumstances around the world.
everywhere’s water situation is different
in most places, tap water is accessible
however in many places, it is not reliably safe to drink
microbial contamination (bacteria, parasites, viruses)
heavy metals (lead, arsenic, mercury)
agricultural or industrial runoff
ageing pipes and unsafe storage
an understanding of the situation for each country, and around the world
1. You can drink water directly from the tap.
2. You have tap or accessible water, but you can't safely drink it.
3. You can get drinkable water within a thirty minute round trip.
4. You don't have access to safe or accessible water.
###### Graph and Understanding of How Many Countries
map of how many people
###### Graph and Understanding of How Many People on Earth
our preference
local tap or source water + filtration
over bottled water
reasons:
lower long-term cost
far less plastic waste
less reliance on fragile delivery chains
easier to normalise locally
otherwise, working with organisations to fund sustainable aquafer bores
###### Accessibility
common forms of access
tap (continuous or intermittent)
shared taps or standpipes
wells into aquifers
rainwater collection
trucked or bottled water
assumptions
manual collection is normal
shared access is normal
intermittent supply is normal
###### Pollution and disease
main issue is contamination, not absence
microbial contamination
heavy metals
drinking water risk is often biological, not chemical
typical outcomes in polluted source areas
reliance on bottled water deliveries
high plastic use
ongoing household expense
our approach
switch to local tap or source water where possible
with treatment
and make it tastier that bottled
low-cost filtering options
gravity-fed filters
ceramic filters
carbon filters
boiling where fuel is already in use
our aim
dramatically reduce illness
with simple, maintainable methods
###### Affordability
water itself is often inexpensive
clean access and hygiene are what create stress
where household water is cheap
small, direct support may prevent instability
bills may be paid directly where appropriate
avoid overuse and dependency
where water is scarce or expensive
avoid locking people into high household consumption
prefer shared access
common access points
community centres
gyms or fitness spaces
faith spaces
campuses
typically provide
showers
toilets
handwashing
our approach
map what already exists
help people reach it
pay small fees or memberships when that keeps someone stable
community centres
memberships
fitness
showering
Rather than inventing new infrastructure:
we map what already exists
we help people reach it
we pay small fees when that keeps someone stable
directly paying bills
###### Heating
With heating, often times heating is a survival risk for people. although we can acclimatise to cold well, then it is, yeah. That's a bit too wordy even that, the approach that we we're outlining here in that sort of beginning sort of slash slash thing is You just bring people blankets and cool stuff and whatever from wherever you have a surplus of it, if there's, if it's somewhere. And then give it to people who need it. And that's sort of the approach, the people-focussed approach of it, which sort of mirrors how we would distribute food and things that, that if we can get if we can locate where a heap of stuff is, where everything is pretty much, then you can very easily turn that into a comprehensive understanding of how to get it to people as well with things that are already in places. yeah. I'm now looking at the text that has been written here. That is good, especially the whole thing is very good. Yeah. Although we'll pr- yeah. We want to keep people as as comfortable as feasible. but we'll put that in the in the cooling section, I reckon. Quick nod to it. Yeah, everything that's been outlined there is exactly how we would do it. Yeah, keeping people warm is is cheaper than Damn, that's good writing. Yeah. Cool. Yeah, avoid solutions that require constant fuel input. Well, that's yeah. Anyway. Don't know, it's too wordy, but this has been really well done. Yeah. It's a whole bunch of goods, yeah. Becoming aware and giving those things to people who need them and just an openness, I suppose, which is pretty cool.
// bringing blankets from other places close by or afar
//. heaps of people have many different things
//.. examples of hoarder houses and such
//.. becoming aware and giving those things to people who need them
Warmth comes from layers, shelter, and timing before electricity
Heating people is cheaper than heating rooms
Avoid solutions that require constant fuel input
Approach
Bedding, clothing, insulation, and wind protection first
Shared heated spaces where culturally appropriate
Safe, low-tech heating methods already used locally
Education on sleep warmth rather than room temperature
We don’t treat space heating as a default human right — keeping and sleeping warm is.
###### Cooling
in the heating section we discussed that heating is a direct response or it's it's more we were putting that section that it's it's the response to how many people get how open people are to sharing. As far as most people are, that that's yeah. and sort of, yeah, that's a a part of open do it yeah, you get what I mean there. It's a part of the solution. For cooling, it is a direct response to how many how open we are to human ingenuity that there are a lot of, people will create for instance, cooling is is then we probably, then you can think through the characteristics that are involved in cooling places, for instance, but I don't exactly know what to say. The point that I'm going towards is that it's, for instance, well, first, people would make fans through 3D printing. there's a whole bunch of there's a whole bunch of different designs. People will ideate, or people not much yeah, maybe you could say ideate. People will yeah, ideate and build and create different things that we can spread far and wide to solve problems in the most effective way using there might be automotive things airflow, whatever that keeps people cool or or things. and ultimately, we want to keep people cool, and we want to make people, one of the core principles is we want to keep people as comfortable as is feasible. The main priority for cooling would be to cool people's sleep. make sure they have good sleep quality at the very least. and there's things in that section where we're discussing it's cheaper to cool, anyway, these are all mirrors from the heating section. But yeah, it's whatever the most effective approaches are for things, I suppose, yeah. And yeah, it it's how open we are to using having solutions that work, pretty much which, yeah, is a direct counter to shame, and then is yeah, you'd make an allusion a little bit to narcissism, where you don't care about how you're perceived, ? you're just doing things that are genuinely better. it doesn't matter about the looks or yeah, a little illusion of narcissism there, you can drop the the the narcissism end bomb, ? yeah, you can you can say the word narcissism. shame or yeah, for instance, I I think of it people in places that are really hot, for instance. where there's a lot of street density and everything. Obviously, it will take a while to create to grow trees in those locations. if you put up local you painted things white, you had banners and stuff, yeah, whatever is the cheapest way to create things that rapidly cool down urban centres or anything that. It's not just about individual people. It's cool, cooling the entire planet through the most effective actions to be able to do that have the highest health outcomes for people. there is that. And yeah, that when people come together and make things work, you could have yeah, white or, grey or yeah, people come together and sort of do these things. I suppose I'm rambling a bit, but it just leads between the realisation that we can be open that, it's the room for human ingenuity is the beginning part of it, and then 3D printing and different a people will make a whole water, cooling and evaporation and people are then given a license and then not not a license more agency, they're given a task to be able to cool things more effectively, that doesn't use where possible doesn't use electricity or whatever. just a whole lot of it yeah, it's it's practically inconceivable how many ideas you have, and then the openness for us to be able to do that, and making things work, is, ? And then that sort of leads into shame and that, yeah, I think in previous parts of the peaceful foundation strategic plan, we also talk about how yeah, the solutions don't have to look pretty, they don't have to be it blame matters less. I think in the true section, when yeah, blame matters less. things don't have to be about, how exactly you're doing it, they just have to work. there's that. they just have to work more effectively, a blame matters less. And then people don't have to care about how they're being perceived or or things, but for participating. It's it just all of a sudden there's a much better vibe. And yeah, if if there's a whole bunch of stuff that's painted black, or, places that people are, or any places that they aren't, that could be made far more efficient, then, yeah, there's there's that. they could be way less hot. There's that. And yeah, it really just matters how open we are to doing such things. yeah. then it sort of goes into shame and then then you just casually mention narcissism of caring how you're perceived in acting in such in a certain way or whatever, or trying to live up to a story that you're telling yourself about who you are as a person and then whatever. That instead, you're doing what is good and a compassionate thing, instead of maintaining a fa a false self narrative. And that that is exactly how you would approach the thing. and then sort of leads to that and then yeah, from shame and then opening people's eyes to the entire probably after shame that you sort of talk about the wider world as a whole, or some, there's some beautiful way of yeah, structuring it. I'm not exactly sure, but from narcissism to showing people the world as a whole, and then there's that. And then that's a beautiful thing.
// a reference to leaving space for human ingeniuity
// building fans and such
//. 3d printing
Cooling is about survivability, not air-conditioning
Sleep quality matters more than daytime comfort
apart from places where the heat poses survival risk
Shade and airflow outperform machines at low cost
Approach
Shade structures, hats, reflective coverings
Cross-ventilation and night cooling practices
Fans only where power allows — never assumed
Cooling schedules (rest during heat, activity when cooler)
We learn from places that already live well in heat — not from energy-intensive buildings.
###### Cooking
Community cook-ups and shared preparation
Preparing and sharing food in bulk, and 'thermos' approaches like reasonable.diet for school
for creating recipes
the design philosophy is like a potato
*cheap, forgiving, and hard to mess up*
meals designed around one-pot
someone should be able to go down to a shared place to cook
otherwise, at home with things that don't cost much to run
and sharing things as well, where possible
By lowering our dependency on infrastructure while increasing standards of living, we can make communities easier to rebuild when things break.
our understanding and aim
“we can’t fix everything yet
but we can make sure you’re not hungry, freezing, or completely alone
while you help make your community better too.”
[2] a note from the author: as far as I know -- there's actually nothing particularly wrong with fluoride, apart from packaging use
https://www.youtube.com/watch?v=GefwcsrChHk
nano-hydroapatite seems to be just as effective (as fluoride, the most widely studied molecule) without changing the mouth’s microbiome as much as fluoride (still very little)
[3] Dr Andrew Wefwafwa of Uganda, am incredibly driven and unbelievably good bloke has created a beautiful, healthy and wonderful local community https://www.youtube.com/watch?v=UrLxyJoZCC4
#### ...
##### Starting with one person
scenario
someone raises their hand:
“i’m struggling, i don’t really have work,
i want to get out of the house, meet people,
and not be a burden on my family.”
often they are:
someone already active in Peaceful Foundation
helped with posters, calm.college, reasonable.diet, or local organising
a web developer or similar between jobs
living with parents or in a share house
applying for jobs eight hours a day with no outcome
or just feeling stuck and underused
we can’t help everyone at once
so we start with people like this:
proven they can act
ready to turn stability into contribution
simple intake, not a sob story
they already have or create a Peaceful Passport
pseudonymous, but bound to a real person through trust checks
the app or someone:
explains the undercurrent’s goal
turning people into active citizens, not clients
asks a small set of questions:
what do you need to not be in poverty?
food? toiletries? bedding? phone credit?
what is your current housing situation?
what real resources do you have?
time, skills, transport, family support
what imaginary resources?
existing benefits, debts, obligations
no long narrative, no humiliation
just enough context to act wisely
verification
for people receiving regular material support:
light ID check via trusted verifier or partner
kept confidential and minimal
purpose:
prevent impersonation
protect the fund
keep trust high for everyone
first support box
early on, the stopgap is simple:
make sure this person is properly fed
and cover a few basics they’re missing
for the very first phase:
we lean on existing industrial logistics
once approved, stewards:
assemble a basic box:
staple food (e.g. potatoes, onions, carrots, grains)
hygiene items (toothpaste, soap, shampoo, pads)
bedding or clothing if clearly needed
phone credit voucher if required for safety
ship it directly to their address
using mainstream courier networks
or partner organisations with delivery capacity
design choices:
we send resources, not cash
harder to misuse
easier to keep focussed on basics
we err on the side of generosity for the first box
to quickly move someone out of immediate anxiety
and into a more stable baseline
briefing into the role
alongside the first box, stewards (or the app) explain:
“this is not charity you owe us for.
this is your community investing in you,
so you can help shape this hex.”
they are invited to:
share what they can do when they’re ready
web dev, poster design, logistics, outreach, cooking
identify other people who might want to help:
family, friends, flatmates, local contacts
start noticing local resources:
spare space, potential hubs, shops with surplus
the ideal direction:
as undercurrent support helps them stabilise
they look for ways to need less from it personally
while building more capacity around them
how it feels
instead of:
endless job applications
or sitting at home scrolling in a fog
they experience:
“someone trusted me enough to help without judgement”
“i can see a path from barely coping to actively helping”
“i’m not being managed, i’m being invited”
##### Having more people helping
expanding the circle
once the first person is more stable, stewards:
check in:
what still feels tight? food? time? bills?
what feels lighter?
ask who else around them might:
benefit from basics
want to contribute
the household or friend group:
can each create a Peaceful Passport
declare:
their own needs
their own capacities
the aim is not to “enrol” everyone
it’s to find natural small crews
who care about their area
they’re backed by a wider network
remote volunteers from other hexes can:
help research local suppliers and co-ops
prepare outreach emails and scripts
support mapping work from a distance
so the first local person:
/ne
isn’t alone
but also isn’t bypassed by outsiders
first tasks, before local logistics exist
online coordination:
helping volunteers reach out to local shops and co-ops
finding surplus sources (e.g. discounted potatoes, near-expiry stock)
helping set up simple pages or forms
practical mapping:
listing possible hubs (parks, halls, churches, co-ops)
noting public transport and walking routes
communication:
softly explaining the idea to neighbours, groups, campuses
this crew becomes:
the seed “cell” for that hex
people who know both the map and the actual streets
reducing cost to support them
as the crew works with stewards:
they identify:
places that can donate or discount bulk staples
partnerships that keep resource costs low
this means:
keeping a person out of poverty
becomes cheaper over time
even as their contribution grows
the pattern:
first, the system “overpays” in attention and logistics
then, local relationships lower the cost per person
then, that crew is able to help the next person faster
from supporting one, to supporting many
once:
a few people are stable
a few supply lines exist
a possible hub is identified
the same crew can:
help pack and distribute basics to others
host meetups in parks, halls, or shared spaces
start light delivery for those who can’t travel
they are not just “recipients turned volunteers”
they are the first local organisers
whose lived experience shapes how the undercurrent runs there
##### Making this far more scalable
overarching goal
the point of supporting individuals and small crews
is to grow stable local hubs
a hub is:
a recurring place and time
where people can reliably:
receive basics
share surplus
meet neighbours
coordinate next steps
each hub:
serves one or a small cluster of hexagons
runs on people first, money second
gets cheaper and more resilient over time
role of volunteers in each hex
local volunteers focus on:
finding excess resources in their own community
finding or negotiating shared spaces
keeping the hub predictable and calm
their tasks include:
spotting “quiet surplus”
shops with near-expiry stock
farms with seconds or oversupply
offices or campuses with unused space
mapping those onto the hex:
who to call
what they can offer
how often
helping justify costs when needed
if a room hire or cold storage fee unlocks big impact
the system can pay it directly
building the first hub
start with the smallest viable setup:
a central spot:
park, hall, church, campus room, co-op, car park
a predictable rhythm:
e.g. “every Saturday 3–5pm”
a starter set of supplies:
staples, hygiene, a few extras
crews work with stewards to:
confirm permission and safety
set basic norms (no chaos, no queue jumping, no shame)
log the hub into the hex map:
location (at hex-level)
time window
expected capacity
over time, hubs:
branch into:
cook-ups and shared meals
repair sessions and tool sharing
learning circles and mutual-aid projects
###### Local sufficiency
For, local sufficiency, it wouldn't really make sense for someone within their local community to be
if they've already found some way that they ideally wouldn't want a supermarket delivery box. If they're part of Peaceful Foundation, if they're, initial volunteer or something. If they can suggest us a better approach to accomplishing the thing, that would be better. It, yeah, if they can get farm direct, delivery to their house or something that, that would be more ideal and particularly if it's unsellable yeah, different characteristics that Pace For Foundation might have about the supplier as well, then that's even better. we'll just use that. And we primarily would mainly give people yeah, in essence, then you go through until you discuss how local supply chains operate in this context, and you prefer cooperatives and all these other things and whatever. I don't know what to say. hopefully some food will help, and we want everyone to be, to have nutrition with everyone. that would be the ideal. We want them to have yeah, really good nutrition year round, and yeah, there's also that you are catalogueing and understanding the local supply chain for a given area as well, which is really cool. Although which is done with a format as a whole. But, overarchingly returning to global localness and just a giant cooperative of people growing food. And such a thing would be beautiful and everyone would get everything they need, forever.
(CHECK)
//
// mapping local supply chains
// local supply chains
prefer cooperatives and small suppliers where possible
help producers become co-ops if they want to
consistency
clear quality
fair pricing over time
where co-ops don’t exist yet
use mainstream suppliers
but keep the door open for transition
and resilience
###### Processing
keep food and goods as close to raw as reasonable
unwashed vegetables
bulk detergent, bulk soap, bulk grains
recipients finish the easy work
washing, sorting, packing
turning “ingredients” into meals or kits
use existing community spaces
church kitchens, school canteens, co-op hubs, shared laundries
###### Transport and Places
you don’t need just-in-time logistics
people don’t always need door-to-door delivery
except where disability or safety requires it
pattern
pickup points in each hex (or cluster)
volunteers and retirees ferry goods
fuel reimbursed directly
local volunteer mechanics maintain vehicles
focus
short, predictable routes
walking-distance pickup where possible
###### Matching Surplus to Need
map:
farm and market surplus
overstock from shops
unused equipment and tools
match:
hexes with reliable volunteers
communities with storage and kitchens
always ask:
“what real need does this batch solve this week?”
###### Shared Infrastructure
over time, communities can build:
staple-food cooperatives
tool libraries and repair sheds
shared cold rooms and storage
undercurrent funds the bootstrap phase
then gradually steps back as local income and co-ops sustain it
###### Record and Feedback
hexagons.world shows:
for hexagons.world the main one we're focussing on is the maps application. And then making a little nod to Laia Quall and and because we have all these local indicators and yeah a lot of information that is readily available which is satellite data and things that, then and we're running statistics we're creating we're using volunteers donating their gaming their not some gaming rigs probably gaming rigs their compute wherever they can to compute deterministic results for such things. Then we can also consider routing for for routes and whatnot. and we can do this for people and a lot of the stuff can be done on device but it's a global compute cluster that can get you it either caches the result or it's always trying to find the best way of approaching the problem in a really elegant way.
whatever I don't even know because it's deterministic results of sequences of how your getting there or of what you're running to in order to find the best route home. I suppose the central thing and you could summarise it in just this is that you could ask any woman on Earth if she would pay one dollar a month for a maps application that allows you to find the way home that is most has the most light or during the day you shade or things that. Um and this this is and just in the calm.college section you wouldn't need to add this but it's you would also have that all these things are equity adjusted um adjusted and it should feel one dollar a month everywhere. it's not big at all but so we use that to um fund providing for local communities in ever ever more um come ever more reasonable and comfortable ways. So there's that.
where goods move
how quickly needs are met
which hexes are stable and which are under strain
Peaceful Passport records:
who did what
without turning it into a score
communities can see:
what’s working
where bottlenecks are
how to adjust routes or kits
###### Mapping and defining resources and systems
// mapping so the aggregate colour of a hexagon from different statistics
// and defining the thing is basically the understanding as variables as every system and everything
// since you can break both of those things down
//
using the hexagon map
each hex gradually fills with:
known surplus sources
shops, markets, farms, processors
known “support spaces”
halls, churches, co-ops, shared kitchens
hubs and meetups
when and where people already gather
volunteers:
add and confirm entries
attach:
a contact person
what can be offered (and under what conditions)
how often it’s realistic (daily, weekly, seasonal)
confirming and maintaining contacts
for each surplus source:
a named contact (or role)
agreed norms:
what we can ask for
what days/times work best
how much notice they need
the app:
reminds crews to check in:
verify that sources still exist
update quantities and reliability
flags:
resources that are under-used
areas with very few options
moving between hexagons
if one hex has more than it needs
and a neighbour is under strain
stewards can:
create cross-hex routes
pool volunteers from both sides
the map:
shows “lanes” of movement:
where food, tools, and people regularly flow
helps avoid:
dozens of small, redundant trips
while still keeping it human-scale
Money and non-money flows
not just monetary donations
participants can contribute:
money
food and goods
space, tools, and equipment
time, skills, and social reach
the system is designed so that:
money is helpful
but not the only fuel
over time:
stronger hexes lean more on:
local surplus
local co-ops
recurring in-kind support
and less on fresh cash entering from outside
using money where it matters
when donations arrive, they are used to:
fill the gaps that surplus cannot
buy staples when donations dip
fund fuel and repairs
cover small fees for room hire or storage
bootstrap new hubs
“dump” an initial amount (e.g. the equivalent of $1,000)
use it to feed as many people as possible
while mapping local alternatives
the goal:
in each hex, track how much money is needed:
this month
next month
over a year
and deliberately:
reduce that number as local systems mature
industrial food chain vs. local networks
early phase:
we lean more on the industrial chain
bulk orders from supermarkets or wholesalers
ship basics directly to people and hubs
this is:
faster to start
more legible for donors
middle phase:
as local volunteers and partners grow:
more goods come from:
local shops and markets
farms and co-ops
community gardens and kitchens
industrial sources become:
backups, not the mainstay
mature phase:
hexes with strong local networks:
use money mainly for:
in the peaceful people section, I talk a little bit about financial transparency in with respect to the,, obviously we want to have financial transparency reports and things that. But in the people section, I reckon talking about financial stuff would be with how supply chains would work as a whole, instead of just,, you want, obviously transactions will be public. that's all good. But then you want a, oh, I don't really think you should make transactions public. I reckon otherwise it just becomes a big hassle and then people overanalyze. Or there's some sort of balance that you go through with that. So yeah. Or,, there's there's open startups and things that as well. So that's good I suppose. So, and yeah, I suppose if you you turned it into from the get-go all the transactions are public then that really would get rid of,, it would call give a lot of public scrutiny to,, how money is being spent. And ultimately it's people's money so you want you want that. So that's good. yeah. Then you'd you'd have to think about things,, at what point does someone get a credit card? not a credit card but a debit card. we use we're using Wise and so you can do multiple approvals for purchases, which is inside the app. this is all really good. then probably you'd also make investments as well. That would be in the money section for peaceful peaceful money but you can note it down in the people section. We'll just focus on the people section as well. just,, when we're making investments I don't know. yeah. but yeah, transparency in finance, it wouldn't be under a financial section, it would be under a transparency section in the people section. And then in the money section, we'll discuss other things. But thinking about the failure conditions of the thinking about failure conditions of how people could get away with things. Well, ultimately you want to, you want to prevent someone from yeah, you want to standardise kit and then make all the supply of it super transparent. yeah, because the entire audit trail for, calm.college all the entire audit trail for The entire audit trail for expenses in the undercurrent as well is it's not an I there's an audit trail I suppose but the supply chain and then what was costed. You wouldn't really call it an audit trail. but that is transparent as well. So that's that's fine. yeah. That that's that's good there's no yeah, I don't it would be difficult to we want to make it nigh impossible to embezzle money into the thing. for instance, if you're going to give someone a a grant for to be able to do something and they think there needs to be clear actionable steps and milestones and they have to put a fair bit of work into writing a small plan to be able to do it. And there has to be a fair bit of work put into this and they can also transcribe voice messages into it and just show a lot of their thinking and then we can have the raw transcripts of the voice messages as well and then yeah, they can see that we can see that they've clearly got a lot of thought into it. so there could be that as well. ultimately we want the people to succeed. and then there should be milestones and deliverables and things that. And then if that doesn't happen then what the heck. But in reality probably people would do it for the love of the game and pull income in local communities to be able to do such a thing but micro loans might be a pretty good way of yeah, that would be really aligned with our purpose as well. So that would be good. in yeah, developing countries or emerging countries and developing countries. So yeah. That's pretty cool.
fuel, upkeep, and “last mile” gaps
can:
host hubs for neighbouring hexes
lend equipment and know-how
show, in data, how they cut their cash needs over time
###### Giving the excess to people
// deterministic
// failsafe
// building blocks
// systems
// such as transport or something
// and then
auditable supply chains
clear origin to table
for each major food flow, the system can show:
where it started:
farm, shop, warehouse, co-op
how it moved:
which hexes and hubs it passed through
how it was used:
cook-ups, parcels, pantry shelves
this is not:
detailing every carrot
but:
showing that bulk shipments
weren’t wasted or quietly resold
tools for crews and partners
crews can:
tag batches:
“Farm X → Hub A → Hub B”
note:
wastage (e.g. 5% spoiled)
success (e.g. “fed ~60 people on Saturday”)
partners can:
see impact of their contributions:
“this pallet of potatoes fed these clusters of hexes”
use this data to:
justify ongoing support
report internally (CSR, community impact)
reducing money reliance through insight
by watching:
how much food passes through
how much cash it required
how many people it reached
crews and stewards can:
spot where to:
negotiate better surplus agreements
shift hubs to more effective locations
invest in something permanent:
e.g. a shared freezer, a co-op lease
the pattern:
use money to:
create stable, auditable supply lines
then:
gradually replace “cash-needed” segments
with recurring in-kind flows and local co-ops
##### What might the app look like?
// factorio
// and a mobile intuitive thing
//: feels entertaining
People joke about “the factory must grow,” but it’s real. The game trains you to:
- Think in flows and rates
- Spot inefficiencies instantly
- Break problems into modules
- Feel mild discomfort when things aren’t symmetrical or balanced
It’s deeply satisfying if you like:
- Programming
- Logistics
- Urban planning
- Process optimisation
- Watching chaos slowly become order
hexagon as home
each person chooses a primary hexagon in the app
where they live
or where they spend most time
they can add secondary hexes
where they study, work, or pass through often
the app shows:
“my hex” — needs, offers, meetups, routes
nearby hexes — where a short trip could help a lot
peaceful passport
each user has a pseudonymous passport identity
no need to expose legal name
passport links:
which hexes they belong to
what roles they’ve taken (helper / organiser / recipient)
what contributions they’ve logged
reputation is based on:
consistent action over time
peer verification, not scores
app / web app
runs on phones and browsers
low-data, low-friction, readable on cheap devices
main screens:
“my day” — suggested tasks and meetups
“my hex” — current needs, stock levels, routes
“donate” — where money will go right now
“log” — quick way to note what you did
people can declare:
resources they have
car, bike, trailer
time windows
skills (cooking, repair, translation, admin)
spare space (garage shelf, back shed, freezer)
needs they have
food, toiletries, bedding
connectivity (phone credit, Wi-Fi)
one-off items (sleeping bag, warm jacket)
stewards see an aggregated view
not people’s private stories
just patterns of “have” and “need”
###### Quick Response codes look ugly
// they are inhuman
// you can imagine the
qr codes look ugly
there
yuck
qr code
qr code reads: omg what does it say
if reading on phone
caption: how you gonna scan it now.
If a human can kinda redraw it from memory, it’s allowed.
Glyphs, patterns, symbols pass.
This constraint keeps things
simple
recognisable
human.
a visual data language
that lives between art and code
robust to messiness
friendly to humans
legible to machines
deterministic spacial or colour encoding
// flow field and curved-line code and also constellation diagram
squiggle
draw what you think a squiggle could look like in the box below
____________
| |
| |
| |
| |
|__________|
### Volunteers and staff
Each campaign requires clear coordination and tracking. People need to know what’s expected, how to move between roles, and where their work fits. The Peaceful Passport keeps this consistent across every project, linking a person's contribution with trust and accountability.
Ambassadors, volunteers and staff each operate within the same system, just at different levels of responsibility. This keeps things fair and shows that volunteering isn’t about hierarchy, but about matching people to the work they can handle and grow through.
everyone has a passport
we use different domain names to create recognisable distinctness between ambassadors, volunteers and staff.
same passport number
- ambassadors: peaceful.network
- volunteers: peaceful.foundation
- staff: peacefulfoundation.org
#### Ambassadors
// everyone, kinda
// supporters
//: interact with things and do small things to share them
//: things that scale
//: online and offline
// active ambasadors
//: progress through swan stages and such
//:
everyone who joins a Peaceful Foundation project becomes part of the wider movement
it happens naturally — participation itself is contribution
using a project, adding a recipe, or joining an event already helps it grow
these people are informal participants — they share the work just by interacting with it
two kinds of ambassadors
##### Supporters
use the projects in their normal way
ggexample → someone joins reasonable.diet to save or sync recipes
their actions — badges adding meals, comments, or reactions — quietly show up through the Peaceful Passport
badges appear automatically in the background
they don’t need to track or manage anything
##### Active Ambassadors
opt into the progression system on peaceful.network
progress through the swan stages — egg, hatchling, cygnet, swan, black swan
receive small, context-based tasks
posters, local outreach, digital sharing, or project support
their completed work links back to their passport as verified contributions
all visible across the ecosystem, showing both activity and reliability
peaceful.network
the open layer connecting everyone across all Peaceful Foundation projects
not a separate organisation — a shared space for coordination and visibility
allows people to move between casual participation and structured volunteering easily
every participant is already an ambassador
the only difference is whether they choose to formalise it
this keeps things light, inclusive, and easy to scale
draw what you think a squiggle could be like in the area below
|
|
|
|
|
#### Volunteers
with volunteers in peaceful people and it begins with anonymous participation.
I think this is all pretty good here.
And we discuss the onboarding system in safety, but I think it should be moved underneath volunteers. And
volunteers do a lot pretty much people who are developing and running and creating and doing a whole bunch of different things for the project as a whole. There's a lot that people do in that regard.
developers are building all the software and then there's volunteers who are liaising with universities and helping things. And
Who knows what else.
There is just a lot, there is just a lot. yeah.
anonymous participation
volunteers move from informal participation to structured coordination
these are the people we can trust to represent the foundation externally
they help link the movement with institutions, councils, and local groups
to join as a formal volunteer, verification is required
each person must have a verified Peaceful Passport identity
no legal identity, but there's a chain of trust
(someone in the network knows they're real)
identity checks prevent impersonation and keep accountability visible
##### Registered Volunteers
anyone can become a formal volunteer at any time
// formal volunteers
// things where people could go wrong
//: like, calm.college outreach or something
//: finding external suppliers and liasing
//:
people need to become volunteers in cases where there could be a significant
a significant risk
// id verification
//
// students
//: working with childrens check
verification
the process scales globally through local verifiers
systems track who is verified, where they are, and what work they’re cleared to do
in some cases this may require real identity or working with children checks
keeps the foundation compliant and safe to work with across all projects
registered volunteers coordinate public-facing actions
point for local initiatives, university partnerships, or civic collaborations
may coordinate regional campaigns within their hexagon
ensure that volunteers and ambassadors under their area are supported and aligned
the progression from ambassador to formal volunteer is natural
people usually begin by acting locally through peaceful.network
when they show reliability and want to contribute more, they move into formal roles
this allows responsibility to grow with trust and proven action
formal volunteers create the bridge between the decentralised movement and the organised foundation
they keep local actions coordinated, verifiable, and consistent
and help maintain the standard of safety, accountability, and calm that defines the work
finances, partnerships, hiring, data access, or press statements.
trusted volunteers who confirm identity and documentation
example → background checks, working-with-children cards, or local equivalents
collect real identity under confidentiality agreement
external ID verification tools
require signed volunteer agreement and conflict-of-interest declaration
#### Staff
// neovim
flat organisation
expertise not rank
nobody ‘reports to’ anybody else
no rigid job titles or fixed job descriptions in many cases
people may shift, do multiple types of work, or evolve their roles
// anyone we hire should be capable of running the foundation
open allocation of work or projects
Employees can choose what they work on.
There is no top-down assignment of tasks.
People gravitate toward work they think is valuable and interesting.
"To start a project, you need to convince others to join you; you can’t just mandate resources. This means initiating a project often requires some level of persuasion, reputation, or alignment of interests." [1]
[1] Valve Employee Handbook, 2012
people on firstLast@peacefulfoundation.org
external can be psuedonym
have to have ID or verification
all email addresses should be unique, slight nickname or middle name over numbers. can also include another related word to field of the persons choosing
pay is transparent
in most cases, each person only has one focus
hire for:
calm, and embody our values -- especially fun (with playful seriousness)
autonomous self starters
don't wait for permission to do what's obvious
strong ethical intuition
instinctively project dignitity, privacy and fairness
technological competence (neovim, static sites, scripts, modern toolsets)
mainly problem solving
should be comfortable using GNU/Linux
know how to learn things
low-ego
rotate leadership easily and value shared credit
logical
doesn't succumb to peer pressure
non-bureaucratic executors
move from idea to prototype quickly
comfortable with minimal resources
frugal builders
*company machine*
remote into BSD user
minimal attack surface
reproducable vm
remote into from tailscale
mosh
neovim + your dotfiles
run gui on local machine using data
GrapheneOS
only supported option for peaceful foundation
GrapheneOS gives you the keys; iOS asks you to trust the jailer
pixel
or should an eink phone or RLCD be supported by grapehene
##### Roles
###### Developers
###### Project managers
###### Compliance
- Lawyer
- Paralegal
###### Financial
- Accountant
#### Steering
##### Not Currently Released. Thanks for Reading the Document Everyone. Will You Please Jjoin
```
vision
approach organising
[artisty] culture
compute community
```
steering:
vision: Fraser Patterson
organising: Athina Hilman
culture: Francis Faulkner
community: Savannah Kruger
compute: Abhigyan Tripathi
artistry: /someone/
approach: jullian harris
**Athina Hilman** does so much it is disorienting.
has extensive experience in gurrella marketing campaigns, student engagement, and
Bachelor of Journalism
and currently building groups to provide media training for underrepresented groups
solves problems
coordinating people
incredibly hard working
although sometimes too much
so we ask her to slow down
have a great team around her
**Francis Faulkner** understands how cultures create cohension.
understands cultures
find resonance
understands the social undercurrent of problems
can explain them in a beautiful way
Bachelor of Anthropology
how cultures create cohension and find resonance
**Fraser Patterson**'s core value is openness
studying Bachelor of Psychology
core value is openness
easypeasymethod.org
// conflict of interest, since easypeasymethod.org as an addiction cessation work
in many ways this is a harmonious
fiscal benefit from addiction cessation
selling physical books
to resolve this: is to not do that.
creative commons
aim instead is to get as many people as possible to print addiction cessation material for the lowest cost with local businesses
pulp non-fiction
reading on a screen is unpleasant
far better reading experience
**Abhigyan Tripathi** creates elegant and scalable systems.
computer system design
able to give a problem to him and he just makes it happen
the most elegant solution to the problem
scalable and adaptable way
extensive software experience
thinks abstractly
Bachelor of Computer Science and Cybersecurity
social impact minded
**Savannah Kruger** helps people create villages.
**Julian Harris** applies a vast knowledge base to problems.
broad
knowledge
Psychology
student engagement
when you're chatting with Julian, there
adaptable
applies knowledge to many different domains
##### Advisors
**Angela Ho** asks questions to help people. Any problem is better
strategy
advice
writes really well, too.
complexities of decarbonisation and examining interactions between international environmental and trade regimes
kind, and applies this into
Bachelor of Law
Bachelor of Journalism
overall interdisciplinary
not-for-profit
systems thinker
coordinating
volunteering
social impact, accomplished.
connects people together
journalism and media relations
**Deniz Alpaslan**'s core value is justice.
cultural approach to International Relations
meaning that he understands politics, but dislikes it
Environmental Science
communities
in actuality it's lowkey deniz for culture and francis is keen
##### Technical
[redacted] **Isaac Freund** [/redacted] designs protocols that scale.
best known for river and his work as a core contributor on zig
##### Coordination
###### Devahuti Rai
###### Rosa
###### Sheila Lam
Accountancy
###### Stephanie David
Registered Psychologist, Coordination
##### Domain Specific Experts
**Angus McAullay** knows geospacial.
[redacted]**Sarah Joe Chamoun**[/redacted] organises the world into data.
### Joining
finding peaceful foundation
finding how they can participate
#### Onboarding
through project or as part of something idk
##### Ambassadors
quiteasily
learnskills.today
reasonable.diet
calm.college
hexagons.world
you need to rest
high stress from world
job:
high stress from the continual job search
school:
exams or drawl
working:
are you sure and stressing?
university:
is the world gonna exist
have fun
dog:
why are they not walking me?
introducing people to each other
##### Volunteers
###### volunteer.peacefulfoundation.org
###### An Easy Onboarding Experience
resume
accounts
training during onboarding
Demographics
Countries
Underage
Adolescent
the experience is replicated
Adult
https://volunteer.peacefulfoundation.org
// Applying
resume
info
interests
// priming
// interview
a lot of volunteers
7 minutes
// onboarding
cal.com
open soruce
###### Registering as a registered volunteer
background check and such
real name and stuff
#### Training
make sure everyone knows how to work safely, communicate clearly, and act responsibly
each role has different risks and duties, but the same goal → prevent harm and confusion
##### General public
// how might we train the general public?
// into the design
// visible integrations
// memes
###### Rule 1: Everything Peaceful Foundation has a peaceful passport
people who see campaigns or take part casually
clear information on what is official and what is not
if someone claims to represent Peaceful Foundation but doesn’t have a valid passport → disavow
teaches personal verification and reduces reliance on figureheads
###### Rule 2: We will never, ever, do cryptocurrency.
[1] [2]
[1] https://web3isgoinggreat.com
[2] Folding Ideas -- "Line Goes Up - The Problem With NFTs" https://www.youtube.com/watch?v=YQ_xWvX1n9g
##### Training for ambassadors
// built into the experience of onboarding through other things
using peaceful passport
why
recognition and trust
prevents impersonation and co-opting
how
register, set up profile, and post using the link-in-bio page
passkeys → how to log in, recover, and protect credentials
vibe
easy, calm, fair, minimal
represent the tone of Peaceful Foundation
completing tasks
instructions included for posters, social media, and campaign materials
norm of posting through Peaceful Passport via Discord
ideas
best ideas come from calm, open discussion
everyone encouraged to contribute without hierarchy
preventing harm
identifiable information
don’t share personal location, name, or age
reduce any other information out there
how you could indirectly leak PII
physical safety
actions must be safe for local culture and law
don’t be a hero
mental safety
this is not a therapy space
refer serious issues to professional support
report recurring issues anonymously if needed
scams
verify it’s actually Peaceful Foundation
official list on peacefulfoundation.org
things we’ll never do
crypto
web3
selling objects not on peacefulfoundation.org url
##### Volunteers
must complete ambassador training first
coordinating internal peaceful foundation things
security and privacy
use a password manager
be cautious with downloads and phishing links
keep digital footprint small
grooming
recognise manipulative or isolating behaviour
report early — don’t keep secrets for others
use public or logged channels only
exploitation
watch for grifters asking for money, favours, or fame
avoid clickbait or off-brand promotions
harassment
don’t engage — document and report
speak publicly when safe; minimise exposure to offenders
burnout
recognise fatigue early
show real effects and normalise breaks
enjoy life — this work should feel sustainable
##### Registered Volunteers
external outreach
use public or group chats, not unsolicited DMs
explain purpose clearly and stay transparent
end conversations that turn strange or personal
report concerns immediately
##### Staff
conduct
model calm and fairness
separate personal and organisational communication
responsibilities
monitor safety, support volunteers, prevent burnout
systems
use moderation logs and reporting tools correctly
handle data only as permitted
##### Directors
leadership ethics and transparency
avoid conflicts of interest
make decisions in open view when possible
clarity and adaptability
record decisions and rationales
update policies as risks change
transparency
publish updates, budgets, and minutes
acting in good faith
prioritise truth, safety, and stability over speed or optics
// more ACNC stuff here
### Safety
embedding safety into the culture
main risks are that we have a bunch of people talking to each other
safety means designing systems, habits, and environments where harm feels out of place
the idea of anyone getting harmed from peaceful foundation is vomitous
Our aim is to create spaces where people feel psychologically, socially, and physically safe — everywhere Peaceful Foundation operates.
Peaceful Foundation spans addiction recovery, student mental health, mutual aid, civic action, and more — which all touch sensitive, vulnerable areas of life. Safety ensures:
* People show up as themselves — not as defensive avatars.
* Conflict can be repaired, not avoided.
* Beauty can be built without fear.
Working together with honesty.
#### Safety principles and architecture
// safety architectural elements
// considerations
We discuss risks in each of the alternatives sections for projects and for peaceful foundation, and in the risk profile section below
mitigate these ...
.
..
principles
Design — stops most simple harms
Governance — catches organisational drift
Environment — shapes context
Culture — prevents escalation
Education — teaches detection
##### Design
prevent harm through structure and systems
the design itself discourages manipulation and secrecy
no hidden reputation or karma systems
technology
child-safety and privacy-by-design baked into every campaign
clear context for all public actions → who, when, and where
information flow
data should move slowly enough to be checked
delay or queue updates if moderation needed
anonymity is pseudonymous — stable identity without exposure
people decide which info becomes public
every field optional, every change reversible
Product rules to protect users:
* **Data minimisation**: store the minimum needed for the feature.
* **Default private**: passports and profiles should start private; public sharing is opt-in.
* Product defaults: **private by default**, no leaderboards, no persistent public history.
* **No permanent public history** by default (especially for anything sensitive).
* **Rate limiting + anti-spam** (prevents mobs from weaponising the tools).
* **Friction for risky actions**: e.g., posting an event location should require extra confirmation + safety reminders.
* **Soft location**: prefer approximate areas over precise pins when people meet.
* **No “search for people” by default**; match based on mutual intent + guardrails.
examples designing for safety
Peaceful Passport
Allows proof of participation without revealing identity. Verifiable, sharable records without needing personal accounts. Recovery is done via trusted friends, not corporate email.
calm.college
Zero-knowledge login with no tracking. Public participation counts show trends *without* identifying individuals. Events require no personal sign-up.
hexagons.world
Sensitive statistics (e.g. on distress or unsafety) can be blurred, anonymised, or aggregated. Local organisers can shield certain areas from visibility if necessary.
hexagon data design
don’t track where people take action — only the general hex layer
users can choose to “claim” or display a hex if they wish
prevent people from encoding private messages through hex-word patterns
verify that shared hex data can’t reveal individuals or coordinates
###### Privacy
Privacy-preserving design is the norm:
* No surveillance-style analytics.
* No personal data collected without consent.
* Use of passkeys, federated authentication (e.g. eduGAIN), and anonymous posting by default.
data minimalism
collect nothing not essential
opt-in by default; visible when active
user control
all profiles exportable, deletable, self-owned
no central analytics or tracking
human privacy
no forced cameras, real names, or identity disclosure
people reveal only what they choose to share
###### Security
passkeys as default authentication
passkey resets must occur through verified consensus
Digital and data safety
Community and relational safety
Tools are in place to prevent impersonation, reduce burnout, and resolve conflict non-violently. Conflict isn’t avoided — it’s navigated carefully.
###### Campaign safety
Posters, memes, and messages are tested for tone and cultural fit.
If a campaign raises tensions
it's always framed constructively with opt-out paths
??
###### Designing features
If you want to sanity-check any new feature, ask:
*“Does this surface information, or does it compel behaviour?”*
If it compels behaviour, it creates authority.
If it surfaces information, it enables coordination.
What you’re building is very consistent already — the danger isn’t in the model, it’s only in accidentally adding a control surface later. Keeping this distinction explicit will save you years of cleanup.
EXAMPLES OF THIS IDK???????????????
X
X
X
X
X
X
X
anti examples too
##### Governance
prevent power and secrecy from enabling harm
the purpose of governance is to keep truth visible at every level
structure decisions so no one person can cause hidden damage
public logs for moderation, finances, and policy changes
independent ombuds contact for confidential reporting
clearly defined roles → volunteer / staff / director separation
regular reviews and transparent policy updates
scaling
could be issues during rapid growth
direct contact point if you have a problem
clear support for volunteers and staff in every region
power abuse
make sure authority is temporary, shared, and reviewable
make private things public when safe to do so
every major action traceable through clear logs
###### Preventing power structures
Roles are verbs, not positions
Roles should be framed as:
- things someone does
- for a time
- in a place
when we describe what someone does, it should sound like:
“hosted 2 meals in this hex”
“verified 5 posters locally”
“helped coordinate a one-off event”
“maintained this dataset for three months”
“organised the hexagons.world January 2026 launch timeline into issues”
Not:
“Local lead”
“Regional manager”
“Country admin”
“Owner of Hexagons”
The moment a role sounds like a noun, it starts to accumulate power.
no ladders
it’s:
what they did
not who they are forever
not:
people owning territory
or climbing titles
we keep the feeling:
people doing things
in a place
for a while
##### Culture
the aim of culture within safety is preventing harm through honesty and open communication
discuss culture later in this document, but within a safety context, in creasing good organisational cultures we're aiming to ensure physical, social, and psychological safety
In practice, this looks like:
* A question is met with patience.
* A mistake is quietly corrected, not shamed.
* A story is heard without interruption.
* An overwhelmed person is allowed to step back without fear of exclusion.
* A meetup has someone standing near the exit, gently checking people’s comfort levels.
........
###### Physical safety
Activities (like public meetups or meal shares) account for local risks. Posters and public campaigns avoid doxxing or harassment risks. Volunteers are never pressured to share exact locations.
// regional considerations
for example: never place posters where removal might cause conflict or hazard
###### Social safety
People feel safe to speak, share, participate, or stay silent without fear of shame, judgment, or coercion. This underpins all onboarding, moderation, and culture-setting.
encourage people to raise concerns early without fear
show that disagreement and truth-telling are signs of health, not conflict
no social penalty for calling out unsafe or manipulative behaviour
calm, kind, and precise speech replaces performance or gossip
###### Psychological safety
prevent emotional fatigue or moral overload
offboard distress to external support services
suicide
safeTALK training for stewards and volunteers
clear pathways to external help and crisis services
gratitude and rest normalised as protective habits
the culture treats honesty as the foundation of safety
These are practices, not features. They don’t need permission. Anyone can do them. But the system should *support* them by default — nudging the culture toward gentleness.
##### Environment
create conditions that make harm unlikely
all spaces — online or physical — designed for calm visibility
clearly marked moderation and reporting paths in every chat
well-lit venues and daytime gatherings for appropriate meetings
no expectation to meet privately or share personal info
the environment itself teaches people they are safe and seen
A system is safe not when the most skilled can thrive, but when the most fragile can survive.
###### Volunteer culture rules that prevent harm:
* “**Buddy rule**” for outreach and anything in public space: don’t do it alone if it’s avoidable.
* “**Exit is success**”: leaving is always a valid choice; nobody is shamed for backing out.
* “**No heroics**”: volunteers don’t “handle” volatile people; they route to professionals or disengage.
* “**Role clarity**”: people distributing food aren’t also the people mediating disputes, etc. Separation reduces abuse risk.
###### Basic training (high-level, non-violent):
* De-escalation basics (tone, distance, disengage early).
* Bystander intervention (how to get help, how to support a target, how to document safely).
* Psychological first aid basics (listen, stabilise, refer — not “fix”).
* Digital privacy hygiene (what not to post; stripping metadata from photos; not filming others).
This aligns with the “calm scaffolding” intent in your People + Assertions sections.
Self-Defence & Local Anchors
As you noted — local community members (like someone trained in martial arts) could run basic self-defence or de-escalation workshops. The idea isn't to prepare for violence, but to restore a *feeling* of confidence and safety in public. These local strengths are recognised and shared through hexagons or the passport system.
###### Online
###### Safety shortcuts in all spaces
// discord
top of the channel list
###### Monitoring and moderation
###### Considerations and contingencies
If impersonation or harassment increases → digital assets are signed with other accounts (such as Steam), campaigns verified, and public dashboards only show safe, validated contributions.
If someone is harmed through over-participation → social recovery, contribution breaks, and visible cooldowns help protect wellbeing.
###### Local
If local conditions are hostile (e.g. oppressive governments, stigma) → campaigns can be mirrored, anonymised, and localised under pseudonyms, with regional protections applied.
* Sites and posters work for people with trauma, anxiety, neurodivergence, or low bandwidth.
* Quiet participation is welcomed (lurking, observing, listening counts).
* People in distress can engage anonymously or at distance.
###### Processes and responses
This keeps you aligned with your “practical action over theory” value: you don’t debate safety, you operationalise it.
a simple safety system
safety.peacefulfoundation.org
voice or written
can be anonymous
###### safety.peacefulfoundation.org
A **single reporting channel** (anonymous allowed) + a basic triage playbook.
* immediate containment (hide content, pause user, cancel event listing)
* support the harmed party
* short internal write-up (“what happened, what we changed”)
###### [risks]
prompt for people to do risk analysis sometimes
###### [incidents]
###### [triage]
* A single “Report a safety issue” flow (anonymous allowed).
* Triage categories:
* urgent physical danger
* harassment/doxxing
* safeguarding/minors
* fraud/resource misuse
* product/security bug
###### {playbook}
###### {quick response}
A **standing safety panel** (small, trusted, rotating) for serious cases.
##### Education
last line of defence → awareness and response
teach what real online harm looks like → grooming, blackmail, coercion
explain early that “weird behaviour” can mean danger, not drama
show how to report issues and when to escalate
run short trainings → digital safety, safeTALK, consent, manipulation tactics
emphasise that coming forward is never shameful
incentivise care → reward those who protect others and tell the truth
the goal is not fear, but literacy — recognising and naming harm quickly
// safety as culture, not paperwork
induction teaches:
safety ≠ reading a lot of documents
safety = behaviours that are normal in the group
examples:
working in pairs
checking in after tasks
clear delegation
kind tone in text
privacy defaults
not overpromising capacity
calling in early when stuck
goal:
when people think “safe,” they think:
“this is just how we do things here”
not:
“I have to remember another rule”
// inductions
inductions exist so:
people can participate safely
they understand the architecture of the organisation
they know where to speak up
they know where autonomy is encouraged
and they feel confident contributing from day one
// primers
primers (and inductions!) also invite feedback
people can propose better methods
SOPs evolve with experience
not top-down decree
###### Inductions
apart from an overview video about peaceful foundation,
we will have three main inductions
and some additional ones assigned based on characteristics
for example, they are in a country with political repression
where even putting up a poster could lead to problems
we would then give other instructions and ways to participate
###### Safety
physical
social
psychological
key principles:
safety is a shared responsibility
but not dumped on individuals
systems should make unsafe behaviour difficult
people should work in groups because:
it’s safer
it’s more fun
it reduces failure conditions dramatically
procedures are light, cultural, and intuitive
too much documentation becomes unsafe
people start half-arsing it
no one reads it
issues hide in the gaps
###### Culture
###### Operations
covers:
how to report a concern
how to escalate gently
how to protect someone without shaming them
how to notify stewards if there’s a pattern
emphasis:
reports are not punishments
they’re part of maintaining calm, human environments
design philosophy:
reporting should be:
safe
light
private
non-judgemental
actionable
// additional inductions
###### High Risk Countries
###### Medium Risk Counries
###### Child Safety
// child safety primers (student + parent + WWCC volunteers)
// already defined in the school-student section
strengthened with:
clear explanation that safety is built into:
group interactions
platform design
mentor selection
reporting structures
we avoid fragile systems
single adult contact
unverified helpers
opaque task assignments
###### Parents
###### Primers
every role has a small set of primers
short videos
simple conversations with a camera
clear explanations of:
what the project is
how the role works
how safety fits into the work
primers aren’t bureaucratic
they set tone and culture
they show people how we do things
and why we do them that way
// developer induction (front-end, back-end, data, volunteers)
covers:
dev environment setup
tools we use
Prettier (consistent style)
JJ version control (jujutsu on top of Git)
why:
we normalise style to reduce pointless debates
we keep repos predictable for onboarding
we choose tools that beginners can grow into
embraces:
juniors learning new things
mentors showing where tasks live
pairing when stuck
philosophies:
self-direction is necessary
many people, many tasks
you must know how to find the next small piece of work
visibility is a safety layer too
quiet repos are unsafe
lonely contributors drift off
group review avoids silent disasters
feedback is normal
and part of belonging
// organising + logistics induction
for people handling:
deliveries
resource movement
check-ins
micro-coordination across hexagons
covers:
never move goods alone where avoidable
when solo:
device-based safety pings
buddy notifications
and automatic “are you okay?” checks
group logistics:
better outcomes
safer trips
stronger morale
often lead to spontaneous additional help
(side quests, picking up extras, cooking more meals, etc.)
privacy model:
no public map of resource flow
no way for outsiders to pattern-match who has what
safety checks run on-device
data minimisation everywhere
failure-condition modelling:
we identify:
how harm *could* occur
what systemic vulnerabilities exist
what someone with bad intentions might exploit
and we embed:
guards
diffusion
visibility
grouping
soft failovers
so the system is safe by default
and resilient to misuse
// role-specific primers
every job category has:
intro to the role
how safety works for your role
what autonomy looks like
what collaboration looks like
explicit examples of edge cases
check-in practices
paths to support
examples:
front-end dev
back-end dev
moderation volunteers
event stewards
cooking crews
resource-distribution crews
drivers and navigators
research + data roles
campus organisers
primers end with:
“how to ask for help”
“who to talk to”
“what to do when something feels off”
If you want the highest ROI safety work up front:
* A **Code of Conduct + safeguarding policy** (short, readable).
* Event safety checklist for Calm.College hangouts (public places, group norms).
* Undercurrent rules: no cash, partner-first distribution, separation of duties.
#### Risks
A realistic risk model for Peaceful Foundation falls into three buckets.
##### External
* **Harassment & doxxing** (especially around stigma-heavy topics like addiction).
* **Bad actors** trying to impersonate official content, recruit people into ideology, or create scandal.
* **Institutional overreaction** (schools/unis/councils: “what is this?”) leading to shutdown pressure.
* **Media framing** that tries to turn the project into a culture-war symbol (even if you refuse).
##### Internal
* **Volunteer conflict** (status, factions, burnout, or “moral policing”).
* **Power dynamics** (charismatic “leaders,” coercive organisers, predatory behaviour).
* **Safety drift**: small rule-bends that accumulate (“we only collected a little extra data…”).
##### Structural
* **Platform misuse**: stalking via events, targeted harassment on anonymous walls, spam.
* **Map harms**: publishing “unsafety” or poverty data at too-fine granularity can stigmatise or endanger communities.
* **Undercurrent exploitation**: fraud, theft, coercion around resource distribution, or volunteers being put at risk.
##### External risks
1) Partnership safety
Especially for the undercurrent:
* Prefer distributing goods via **existing trusted partners** (community kitchens, co-ops, service orgs) where possible.
* Contracts/MOUs that state:
* no coercion
* no proselytising
* no political recruitment
* basic privacy handling
* Don’t partner with groups that demand control over tone or identity.
* **Harassment & doxxing** (especially around stigma-heavy topics like addiction).
* **Bad actors** trying to impersonate official content, recruit people into ideology, or create scandal.
* **Institutional overreaction** (schools/unis/councils: “what is this?”) leading to shutdown pressure.
* **Media framing** that tries to turn the project into a culture-war symbol (even if you refuse).
##### Internal risks
* **Volunteer conflict** (status, factions, burnout, or “moral policing”).
* **Power dynamics** (charismatic “leaders,” coercive organisers, predatory behaviour).
* **Safety drift**: small rule-bends that accumulate (“we only collected a little extra data…”).
##### Conflicts of interest
Anything influencing impartial decision making.
Conflicts can be financial (like money, contracts, employment), but they can also be non-financial. Personal relationships, ideological commitments, loyalty to another organisation, or even reputational interests can all count if they affect impartial judgment.
Responsibilites for decision making
We want to make the best decisions possible
disclosing relationships and such
For example, uni food thing has parent as a supplier
Decision making
directors
developers
Conflicts of interest are extremely common.
Because conflicts are common and often unavoidable, the standard approach in the charity sector is management, not elimination.
// is it serious?
well, yeah.
risk not recognising
- breach of trust
- funding and donations
- volunteers
That usually means:
Declaring the conflict openly
Recording it in a conflicts register
The conflicted person stepping back from discussion and decisions
Ensuring decisions are made by independent, non-conflicted people
Being transparent in reporting where relevant
2. publicly accessible conflict of interest register
The goal isn’t to prevent influence everywhere. It’s to make influence visible, bounded, and documented.
Charity regulators take perceived conflicts seriously because charities rely on public trust. If donors or beneficiaries think decisions are self-serving, then trust collapses.
###### Questioning
determining if there's a conflict of interest
different conflicts of interest
// university food thing
// fraser easypeasy example
**Question 1:** ***Who benefits?***
Does anyone involved stand to gain personally, financially, reputationally, or relationally from the decision?
If yes, assume a conflict exists. Don’t argue it away.
**Question 2:** ***Who is making the decision?***
Is the person with the interest also influencing:
Discussion?
Shortlisting?
Final approval?
Implementation?
The closer they are to the decision, the higher the risk.
**Question 3:** ***How would it look written down?***
Imagine this sentence in an annual report or newspaper:
“The charity uses X, where a board member has Y interest.”
If that sentence makes you instinctively want to add explanations or defensiveness, treat it as a real issue.
An elegant process does three things at once:
1. Assumes conflicts will exist (no moral drama)
2. Normalises disclosure (no shame, no defensiveness)
3. Creates a clean moment of separation where it counts
We use our safety architectual principles in managing conflicts of interest.
###### Resolving
###### [Design]
*Applicability*
why are we adding it?
why do we need it?
*is this the best way?*
*Replaceability*
check: what would we do if [X] didn't exist?
No decision should rely on the founder being the only one who can approve it.
No asset should be so central that independence collapses without them.
no 'special sauce'
*Approach???*
open source
or irl, can we use a co-operative or an an equivilent
managing conflicts of interest
What matters most is that the charity can clearly show it is acting in its best interests, not in the interests of individuals connected to it.
+++++++++++++++++++++++
3. Resource flow ambiguity
If people, attention, donations, volunteers, or platforms flow like this:
Peaceful Foundation → Quiteasily → EasyPeasy
Donations → outreach → brand/IP lift
then regulators want to see:
clear purpose boundaries
no circular justification (“it helps the mission, which helps the book, which helps the mission”)
Circular benefit logic is a red flag unless very clearly governed.
What makes your situation defensible (this matters)
You have several things working strongly in your favour:
Your projects are free / open / public-benefit oriented
You are not extracting salaries, dividends, or royalties (as far as structure goes)
The mission is coherent and pro-social
You are proactively asking about conflicts (regulators like this more than you’d think)
This puts you firmly in “founder-led charity with managed conflicts,” not “vehicle for private benefit.”
+++++++++++++++++++++++++
###### Governance
*Level 1 — Disclosure only*
Low-risk, unavoidable conflicts (e.g. founder’s background).
Action: declare and proceed.
an example within peaceful foundation:
*Level 2 — Partial recusal*
A person can contribute context or expertise but does not:
- propose the motion
- vote
- approve final wording
*Level 3 — Full recusal*
High-risk decisions involving:
promotion of EasyPeasy
allocation of funds/resources to aligned entities
brand positioning tied to founder IP
Person leaves the room (or call). Decision is made independently.
+++++++++++++++++
4. Founder recusal on specific decisions
Whenever decisions involve:
promotion of EasyPeasy
use of its materials
branding alignment
resource prioritisation that clearly benefits it
The clean move is:
you declare the conflict
you step back from the formal decision
it’s minuted
This is boring governance — and exactly what regulators want.
A blunt but helpful test
Ask yourself this, honestly:
“If I sold EasyPeasy tomorrow, or stepped away from it entirely, could Peaceful Foundation continue without distortion?”
+++++++++++++++++
###### Environment
How would it be implemented?
open source or co-operatives
*What alternatives are there?*
Could we:
- Use an independent supplier?
- Get multiple quotes?
- Delegate the decision entirely to non-conflicted people?
- Delay until governance is clearer?
- Regulators expect charities to choose the least conflicted path, not the most convenient one.
###### Culture
everybody wins
transparency
“Of course you have conflicts — you’re human”
not “We’re worried about impropriety”
If volunteers or board members feel awkward declaring conflicts, the system is already failing.
Founders set this tone by over-declaring, not under-declaring.
When you treat conflicts as normal facts rather than threats, everyone follows suit.
###### Education
It’s also important to understand the distinction between:
Actual conflict – the interest is currently influencing a decision
Potential conflict – the interest could influence a future decision
Perceived conflict – it might look improper to an outside observer, even if it isn’t
###### Considerations
conflicts of interest usually show up around:
attention
influence
and potential profit
they’re rarely malicious
but attention can bend incentives without people noticing
as the culture strengthens
these pressures ease
and people just act because it feels right
core principle
no one should profit from access to Peaceful Foundation
participation must stay open:
no paywalls
no soft hierarchies
no special channels for the well-connected
attention as a resource
influencers and creators are welcome to promote PF
but they don’t receive special access or authority
organisers are trustees, not beneficiaries
their role is to protect the community
not to build a personal brand from it
organisers and stewards
stewards avoid:
private access networks
attention-seeking behaviour
using PF for personal gain
popularity is not currency inside PF
we reward contribution, not visibility
funding, donations, and influence
funding can't buy influence
donors — big or small — receive gratitude, not special treatment
public figures promoting PF don’t get governance roles by default
handling issues
if someone’s personal project overlaps with PF:
they disclose it
we decide if boundaries need tightening
most conflicts are solved by:
making access open to everyone
separating roles
adding a bit more transparency
cultural expectation
people contribute because:
it helps communities
it feels meaningful
it lightens the world
the culture assumes:
shared work
shared credit
and no one using PF to climb a ladder
long-term vision
as PF grows:
we expect the attention-based conflicts to fade
the culture becomes its own gravity
rewarding contribution
not visibility
the system shifts from:
“Who gets attention?”
to
“Who made something that helped someone today?”
###### Risk profiles for projects and milestones
quiteasily
Main risks:
* Stigma, shame spirals, harassment.
* People projecting ideology or moral judgement onto “addiction” topics.
* Unsafe user-generated content.
Mitigations:
* Strong tone standard: non-shaming, non-graphic, no targeting.
* Clear disclaimers: “not medical care,” crisis links where relevant.
* If you allow discussion spaces: heavy moderation and “no advice-giving as authority.”
###### coomer.org
###### peaceful.network
learnstuff.today
Main risks:
* Unsafe “how-to” content if the library expands into risky topics.
* Minors participating.
Mitigations:
* Content policy with “red zones” (no weapons-making, no harm instructions).
* Safeguarding rules if schools use it (public contributions, no private adult-minor mentorship channels by default).
reasonable.diet
Main risks:
* Dietary harm (allergies, eating disorders, medical conditions).
* Food safety issues if people copy recipes.
Mitigations:
* Strong labelling: allergens, substitutions, “if you have a medical condition, check with a professional.”
* Avoid weight-loss / diet-culture framing; keep it “food you can afford,” consistent with your Alternatives/Truth framing.
calm.college
Main risks:
* Stalking/harassment via hangouts.
* Toxic anonymous posting (wall).
* Identity leakage (even accidental).
Mitigations:
* Keep your existing design direction: verified student token without identity exposure; thread-scoped anonymous identifiers; no persistent persona-building.
* Event safety defaults:
* public places first
* minimum group size suggestions
* “tell a friend / buddy rule” reminders
* easy reporting + immediate hiding of suspicious events
* Aggressive anti-harassment moderation + rapid removal model.
***Each of the tools on the thing***
hexagons.world
Main risks:
* “Safety” metrics becoming a stigma map.
* Publishing granular distress/poverty indicators that can be used to target vulnerable people.
Mitigations:
* Your own listed mitigations are right: aggregate to larger hexes for sensitive indicators, show uncertainty, allow shielding, never publish microdata.
* Tone: display “needs support / strain / risk” rather than “dangerous people live here.”
###### Maps
###### What if?
###### Hexagons Private
Peaceful Passport
Main risks:
* Reputation becoming coercive.
* Identity correlation/doxxing.
* Sybil attacks or forged badges.
Mitigations:
* “Attestations not ratings,” no popularity metrics, factual badges only.
* Signed content manifests for official assets (so impersonation is repudiable).
* Default minimal public profile; “dual profile” (public-minimal vs private-full ledger).
Undercurrent
Main risks:
* Coercion (“do X to get help”).
* Theft and fraud.
* Volunteers being targeted at distribution points.
* Creating dependency or “gatekeepers.”
Mitigations:
* **No cash**, as your plan already implies (“real resources” focus).
* Use voucher/partner models where possible (grocers, co-ops, kitchens).
* Distribution safety:
* public, well-lit, staffed locations
* clear hours
* never store large quantities of valuable goods in unsecured places
* Strict separation:
* the person deciding eligibility/support should not be the same person doing personal follow-up.
* A “no strings attached” clause, always.
scalablecampaigns.org
Main risks:
* Campaign capture by ideology/faction.
* Escalation into “us vs them.”
Mitigations:
* Keep the platform focussed on **measurable, local improvements** and neutral templates (not political mobilisation).
* No calls for confrontation; no targeting institutions or individuals.
###### Social media
###### Mass media
###### Partnerships
###### Donors
being self-sufficient
##### Structural risks
* **Platform misuse**: stalking via events, targeted harassment on anonymous walls, spam.
* **Map harms**: publishing “unsafety” or poverty data at too-fine granularity can stigmatise or endanger communities.
* **Undercurrent exploitation**: fraud, theft, coercion around resource distribution, or volunteers being put at risk.
#### Child safety
>moving the expanded section above to here<
// wwcc is not wholeheartedly effective
// why don't we also induct kids and their parents?
importance of a WWCC and why it’s only the first filter
only adults with a Working With Children Check may interact directly with under-18s
WWCC filters out known risks
but it is not the whole safety system
our actual safeguarding relies on:
parent visibility
group-only contact
primers for kids
clear cultural norms
consistent adult presence
we take induction seriously
parents should feel confident that:
we know who is in the space
we know how to spot creeps
and we shut that behaviour down early
parental vigilance
parents are encouraged to stay aware
kids move fluidly across online spaces
Discord, Roblox, TikTok, etc.
some of these spaces normalise bizarre or unsafe behaviour
we aim to give kids something healthier
a calmer culture
clear expectations
real-world grounding
parents should:
check in
ask questions
look at the primers with their child
and remain part of the loop as the child participates
ideal pathway when volunteers are available
a brief video call with:
student
parent or teacher
and PF Registered Volunteer (WWCC-verified)
sets expectations
shows care
and gives the family confidence in the project
tasks for young participants
tasks given to students are:
age-appropriate
light
not financially dependent
designed to help them grow as people
never used to outsource serious organisational labour
the aim is:
building confidence
teaching contribution
helping them feel part of something calm and human
parents should understand:
we do not profit from their child’s work
we cannot pay much, if anything
and everything must remain above board
reassurance about our demographic
Peaceful Foundation attracts:
students
young adults
purposeful developers
quietly capable community members
parents and educators
we maintain a demographic that parents generally feel comfortable with
and we keep it that way by:
strong cultural norms
active moderation
WWCC gating
clear boundaries
this transparency is part of the parent primer:
“Here’s who is in this space, here’s why we trust them, and here’s how we keep it that way.”
ranks and progression
egg → hatchling → cygnet → swan
kids who reach cygnet or swan have:
proven reliability
completed small life-improving tasks
understood the culture
we want to meet them properly at this point
same as adults:
a short conversation
get to know them as a person
check their understanding of safety
make sure they’re a good fit for community spaces
“bouncer at the door” model:
kind, firm, human
edgy behaviour goes to a pit or pause queue
most kids settle quickly once spoken to plainly
safety culture
we treat online safety as common sense, not panic
clear explanation to kids:
there are adults online who try to:
groom
manipulate
blackmail
never call them “pedos”
some of them fetishise the term
we show them the Roblox-style behaviours to recognise
“you’ve seen those videos — that’s what we’re safeguarding against”
rules:
never alone with a PF volunteer
online or offline
always group settings or visible channels
never share:
real name
private details
photos
private DMs discouraged
all PF-related contact kept in group spaces
keeps things fun, social, and safe
kids should feel:
empowered
not frightened
immune to weird behaviour rather than exposed to it
frank student primer
we talk plainly:
“here’s what grooming looks like”
“here’s how manipulation works”
“here’s why some people try to exploit kids”
explain:
blackmail tactics
coercion around intimate imagery
what to do if something’s already happened
absolute stance:
no shame, no blame
global forgiveness culture
if a kid has been harmed or coerced:
they are supported
never mocked
never stigmatised
we embed protective norms:
“that behaviour is disgusting” instead of treating it as gossip
grounded reactions, not edgy ones
tone:
straightforward
kind
never sensational
parent primer
after the universal induction, parents watch a dedicated primer
explains:
what Peaceful Foundation is
how projects work
why their kid wants to take part
the safety structure
WWCC requirements
group-only interaction rules
parents see:
we’re not an online free-for-all
this is closer to a well-run youth programme
but built around calm contribution and local good
parent comfort matters
many parents are wary of:
Discord culture
online communities
“youth empowerment” schemes
so we speak plainly:
“we do not want Peaceful Foundation anywhere near the weird stuff online”
“here’s exactly how we prevent that”
“here’s how to reach us directly if anything ever feels off”
staff + server separation
all under-18 spaces are isolated
only volunteers with verified Working With Children Checks
WWCC is our first line of defence
it filters out people with known issues
but it is not a guarantee of safety
which is why our real safeguard is:
clear cultural norms
parent involvement
group-only interaction
and direct primers for kids
the aim is not just to screen adults
it is to induct young people properly
so they understand the whole ecosystem
and can participate safely across all campaigns
project access
school students can participate in every Peaceful Foundation project
quiteasily
learnstuff.today
reasonable.diet
calm.college
hexagons.world
scalablecampaigns
and future projects as they appear
however, some projects tend to be most directly relevant to young people:
learnstuff.today → practical skills, study-life balance, learning pairs
reasonable.diet → simple, affordable meals at home
quiteasily → posters, messaging, calm contribution
these are not limits
just patterns: where young people usually find immediate value
restrictions apply only around safety:
no one-on-one adult contact
no private DMs for PF matters
no involvement in adult logistical roles without supervision
otherwise, the goal is to induct kids into the whole system
so they can understand the full landscape
see how the projects fit together
and grow into broader participation as they mature
expectations framework
student + parent understand:
participation is optional and gentle
assignments are small
safety is the top priority
PF understands:
children aren’t miniature adults
the aim is supporting their growth
creativity, humour, calm influence
not loading them with movement responsibilities
// why include young people at all?
they:
normalise grounded behaviour quickly
defuse weirdness instinctively
share ideas through peer networks
make posters, cooking, meetups, and small acts feel natural
campuses become early testbeds for:
calm local life
better social norms
affordable food
shared purpose
// summary
the entire under-18 system is:
clear
transparent
parent-visible
group-based
safety-first
aim:
let young people take part in a hopeful, human way
while ensuring nothing about their experience drifts into unsafe territory
##### Children
authenticated through openage for regional specifics
(but mainly understandable as under 16)
MongooseIM
functional (deterministic) programming
Debian
##### Adolescents
.
##### Parents
.
#### Safeguarding vulnerable persons
Identify and assess the risks and any legal and ethical obligations
Commit to managing the risks involved when working with vulnerable people
Prevent harm and mitigate risks with clear and comprehensive policies, procedures and systems
Engage people, including third parties, to help manage risks by adhering to those policies, procedures and systems
Detect changes in risks, instances of harm and of non-compliance with obligations
Take action when concerns, suspicion or complaints arise
Assure the charity’s board that risks are being managed.
Risk assessment
A risk assessment will help your charity to identify the risks that come with its work with people, prioritise each risk according to its likelihood and consequences, and identify the policies, procedures and systems to address the risks.
You can conduct risk assessments for the whole organisation, a department, or for specific processes, programmes or projects. Risk assessments do not have to be complex; a simple and methodical approach is best.
When conducting a risk assessment, you should:
think broadly about all the people your charity affects – what forms of abuse, exploitation or coercion could happen to them, and who might be responsible for them?
consider potential risks in all activities, including those in your charity’s supply chain or of partners and subcontractors
think about the likelihood of your charity’s resources being affected by these risks
consider the consequences of an incident: the effects on the victim, your charity’s beneficiaries, its reputation, financial position, partners, and the staff morale.
seek out information to understand the risks – consult widely, for example through meetings, workshops and surveys, and identify information sources such as previous incidents, reports, events in other organisations, and media reports.
Remember that talking about safeguarding may be confronting, particularly if people have had a traumatic experience, so approach the topic with care.
It is important that your charity knows its legal obligations. Keeping a register that lists the national, state and international legislation that affects your charity’s work can help.
This register should:
identify the jurisdiction and source of the obligation
provide a short summary of the obligation
record what your charity does to ensure that it complies with the obligation.
Review the obligations regularly to ensure the register is up to date.
Your charity can also use the register to record and monitor other external obligations, such as government policies or professional standards or codes of practices.
When your charity has considered its risks and its obligations, it can evaluate whether it has the right policies, procedures and systems to manage them.
Committing to protecting people from harm means:
having a clear and accessible safeguarding policy
allocating adequate resources, leadership and authority to manage the risks
ensuring everyone in your charity shares the commitment.
A policy that outlines your charity’s approach to safeguarding is an important document. This document should:
reference your charity’s legal obligations
outline identified risks
define key terms (for example, ‘safeguarding’ and ‘vulnerable person’)
clearly state your charity’s expectations of staff, volunteers and partners
outline your charity’s processes for managing risks
identify who is responsible for managing safeguarding
clearly define the roles and responsibilities of people involved in safeguarding
extend obligations to your charity’s partners and contractors
contain supporting resources, such as an incident response plan or an employee vetting document
be endorsed by your charity’s board.
Your charity can use our template safeguarding policy as a starting point.
Everyone in your charity should have access to the policy. It is also a good idea to also make it publicly available.
It is important that safeguarding is given appropriate resources and is supported by your charity’s leaders.
Ensure those resources are proportionate to your charity’s work, its risks and its funding. It can be helpful to use the risk assessment, and the priorities that came out of it, to decide where to focus resources.
Ensure your charity's leaders support the safeguarding approach and take it seriously. Have a senior person take responsibility for safeguarding and make sure it features regularly in board meetings.
Internal controls are policies, procedures and systems that can reduce the likelihood and consequences of incidents. It is important that these internal controls are appropriate for your charity and address its specific risks.
Examples of procedures and systems include:
due diligence – the research, background checks and preparation that your charity does to minimise the possibility of doing harm to people
segregating duties and providing supervision – policies or procedures that ensure the responsibility for high-risk situations is shared by more than one person
managing third parties – third parties are people or organisations that your charity works with, and managing them includes ensuring they are capable of, and committed to, protecting people in their work. Written agreements, contracts or memoranda of understanding are useful ways to do this.
It is not enough for a charity to have a culture of good safeguarding practices – formal procedures and policies should be adopted by charities to ensure that there is a consistent process for addressing safeguarding risks.
Engaging everybody involved in your charity and its work means communicating the charity's expectations, raising awareness of the issue and building a positive culture of protecting people.
Your charity may do this through formal channels such as policies, procedures and training resources, or less formal methods such as email updates, newsletters and staff meetings.
To help develop and maintain a culture that values safeguarding, consider:
Are your charity’s values expressed in a code of conduct and do these values support safeguarding?
Has your charity considered the kind of culture it wants?
Does your charity's leadership embody the desired culture and encourage others to be part of it?
How do attitudes and events in your charity compare with its desired culture?
It is important to detect incidents of harm, moments of non-compliance with commitments, and indicators of changing risks.
To detect an incident of harm effectively, ensure that:
staff, volunteers and third parties report any concerns they have – and can do so confidentially, if they wish
there are ways for people to provide feedback, raise grievances and report suspected or actual incidents of harm
people who report concerns or incidents of harm are protected
there is guidance for managers and staff on detecting situations which have risks of abuse, neglect and exploitation
there is a supportive culture that encourages staff and volunteers to speak up – a whistleblower policy may also be appropriate.
there is a clear and transparent system for investigating and responding to concerns.
Examples of ways your charity can do this include:
training on safeguarding for new staff and volunteers
having clearly defined reporting procedures in its policy
providing staff and volunteers with simple guidance on 'red flags' that might indicate incidents of harm
a communication campaign that shows volunteers, staff and beneficiaries that it is safe to make reports
an email address, contact number or other way through which people can make anonymous disclosures.
In the event of a suspected incident, your charity needs act promptly to understand what might have happened, the risks that might exist, and how to protect the people affected.
To effectively respond, it is helpful to be able to follow a response plan. This plan will help your charity manage the suspected incident and the risks involved. A response plan should:
clearly assign roles and responsibilities for responding to the incident (with major roles and responsibilities reserved for people with appropriate training, skills and experience)
set out what is required at each stage of the response
include an internal investigation to understand what may have happened
provide guidance for when matters should be reported to an external party, for example, the police, the ACNC or a partner or donor agency
include a step focussed on development and learning lessons.
Your charity can use our template incident response plan as a starting point.
Carefully consider the risks before beginning an internal investigation into a matter. Some incidents may be beyond your charity’s ability to investigate effectively, meaning you may need external help, or to refer them to police.
Your charity’s board needs to make sure that there are regular reviews of safeguarding policies, procedures and systems.
Review them at least annually and after any incident. Consider, for example, the following questions:
Are they up to date, reflecting the current working environment and legislation or regulation?
Do they reflect the current risks for your charity’s work?
Do staff, volunteers and third parties follow the policies, procedures and systems properly?
Do the policies and procedures work?
What feedback has your charity received about them?
What improvements could be made?
### Community
people want and need community
anchors
welcome and supports beginners
#### Online
##### Nests
// nests are groups of people who get along or are working together on something
The fact that different nests also have different time outs depending on how long., if you're bringing a whole bunch of people who have been interested and expressed interest on a task and you put them together in a way that you think would,, best enhance and they,, you take them through,, you have an organiser person to facilitate,, in a really unscripted way,, very extrovert sort of people or,, people might interview people initially in a very authentic way and practice social skills in many ways and the other person talk about themselves and things that and listen., yeah, and then they would, yeah, and a note for organisers as well is that,, they need to train their brain to shut up completely when another person is talking. thinking why another person is talking is very is so rude and so don't do that. Go, yeah., and then, yeah. But you probably would deal,, discuss a lot of these different things in sort of where there's the intersex, the intersect, ser, intersect, ser,, of the different, just getting the pronunciation right. The intersex for the different roles based on their their thing., yeah, and through consistent receipt people have a sense of self-direction of tasks they can do anytime even if they're not being assigned something in particular., then it's something that can be locally doable or something. Oh yeah. Or online stuff as well. So.
If everything is totally open and fluid, people don’t know where to land, nothing feels like *theirs*, and it’s easy for things to evaporate. If you make teams too rigid, they turn into mini-organisations with their own micro-hierarchies, politics, and gatekeeping.
So you’re looking for a third thing: teams as very light containers.
They exist so that people are not alone, so that responsibility and communication have somewhere to sit, but they’re not “slots” you’re forced into. You should be able to drift, combine, pause, and restart without the system snapping.
###### Discord bot
///////
##### Flocks
just groups of demographics
regions and such, too
##### Seasons
#### irl
in real life
means that the less structure the better
##### hexagons spaces
##### calm.college events
##### Within local communities
Yeah.
a firefighter could look out for what is, flammable in their local community or something, or get people to watch out for,, yeah,, bottles or,, figuring out what starts the most fires in their community and whatnot., or having if you're a botanist person, then you can if you're a, yeah, if you're a botany person who deals with invasive species and whatnot, you can yeah, find or get people to recognise where there's weeds that shouldn't be there in their local community. That, yeah, obviously environment adapts and everything, but if it's killing other plants or things that,,, yeah. A lot of cross-pollination and mixing and things that, but it's not a, yeah, I digress. And I'm sending happy smiling good times overall.
Yeah.
### Culture
#### Our values
##### Easy
honesty
communicating your feelings in real time
censoring our feelings
working together
##### Calm
Obviously, not violent,
No vigilantism, no intimidation, no “security squads,” no threats (even joking).
No weapons (events, distribution points, meetups).
Finding common ground
Fu
##### Fair
**No doxxing, ever.** No sharing screenshots with identifying info; no “exposing” anyone.
go through proper safety channels
##### Less
Dross
Arguments
Debates
No forced personal disclosure; no pressuring people to discuss addiction/trauma.
##### Good
good for everyone involved
#### Prequisites for a good culture
##### Safety
##### Integrity
compressing or compromising one value one time might not lead to a big change in the short term
but slowly over time, compromising ten leads over time leads to a completely different organisation
##### Maturity
professionalism
authenticity??
#### Practicing a good culture
#### Honesty
#### Accountability
#### Conflict and directness
Conflict is normal in any group.
The problem is not friction itself. The problem is the slow rot that builds when conflict goes sideways — into gossip, triangulation, quiet reputation damage, and people recruiting others into their grievances instead of talking directly.
Common sources of tension include:
- friction from stress and logistics
(lateness, ghosting, tone over text, misunderstood deadlines)
- status / credit tension
(who “owns” an idea, campaign, or event; who gets thanked)
- ideology drift
(political grandstanding or culture-war topics pulling focus off food, learning, and calm)
- co-option and impersonation
(people speaking “for” the project without a passport or mandate)
- boundary issues
(unsolicited DMs, oversharing, pressure for personal details, blurred work–romance lines)
- burnout irritability
(good people running hot → sharp replies, withdrawal, hopelessness)
We assume conflict will appear whenever people care and are tyred. The aim is to keep it honest, contained, and repairable — and to protect the environment from people who cannot or will not do that.
##### Cultural responses to conflict
We treat conflict as something you can move through together, not something to fear or avoid.
That means:
- we try to say what actually happened and how it felt, even when it is uncomfortable
- we keep our words tied to our own experience, not other people’s motives
- we expect that adults can hear hard things without exploding or collapsing
- we do not recruit others into our conflicts
People should feel able to speak openly about what they are feeling, as long as they are talking about their own experience, in grounded language, and with the intention of moving things forward rather than scoring points.
1. Speak from your own experience
people are encouraged to describe their experience, not diagnose others
examples
“when the deadline moved, I felt unconsidered and stressed”
not: “you’re inconsiderate”
why
makes feedback easier to hear
keeps the focus on facts and impact, not on judging someone’s character
short pattern we use
“when X happened, I felt Y, and the impact on me was Z”
“can you tell me how it looked from your side?”
feelings are treated as real data
but not the whole story on their own
2. Keep venting separate from gossip
venting is human; gossip is corrosive
if someone starts talking about another person rather than to them
the default response is gentle and practical
examples
“would you be willing to say this to them directly?”
“do you want help figuring out how to raise this with them?”
we don’t usually say “don’t gossip” or “I don’t want to hear this”
those lines shut people down instead of helping them act
the aim is to redirect
away from character talk
toward: “that sounds like an emotion or something human. what do you want to do about this?”
venting is fine when
it’s clearly named (“I need to vent for five minutes”)
it ends with some kind of next step or letting go
3. Direct conversation as the default path
if you have an ongoing issue with someone
the expectation is that you try to talk to them
and that they are willing to listen
no one has to be perfect
but they do need to be reachable
simple habits
reflective listening
“what I’m hearing is that when I did X, you felt Y — is that right?”
checking assumptions
“I noticed you went quiet after the meeting — did I miss something?”
refusing all feedback
or treating every concern as an attack
is not compatible with shared work
4. Opt-out is always allowed
no one is forced to work closely with someone they don’t mesh with
if two people consistently clash
options include:
moving to different projects
adjusting roles
reducing overlap
general principle
if you have the issue, you help carry the adjustment
unless there is clear systemic harm
this prevents
campaigns to get someone pushed out socially
slow coalition-building against a person
sometimes two good people just don’t work well together
that is allowed
the structure makes it easy to step sideways instead of trying to “win”
5. Patterned harm is handled differently
occasional conflict is normal
repeated destabilisation is not ignored
patterns we pay attention to
someone consistently:
creates drama
refuses any self-reflection
turns every boundary into a crisis
pulls attention into themselves at others’ expense
if this keeps happening
it is treated as a sign that the person is not currently safe for the environment
this is not about punishment
it is about protecting the group and the work
we are not expecting people to be flawless
we are expecting that they can notice their own impact and adjust over time
people are not excluded for being imperfect
they are asked to step back (or are removed from roles) when:
they cannot or will not self-reflect
and their behaviour keeps making things unsafe or unworkable for others
##### Systems covering conflict
> Conflict is normal in groups. We prevent harm by spotting early signals, using shared scripts, and keeping decisions transparent — not by pretending tension isn’t there.
The cultural habits above only work if the systems underneath support them. We design conflict-handling the same way we design safety: using overlapping layers, not one heroic fix.
###### Layers and defaults
Design
clear roles
participant, ambassador, volunteer, staff, director
no leaderboards or clout metrics
small teams by default
easy to leave or reshuffle when needed
Governance
moderation logs and reporting tools are required for staff
not optional
key decisions recorded with short rationales
simple ways to raise concerns
without having to go through one particular personality
Culture
norms against gossip and triangulation
venting redirected toward resolution, not recruitment
“speak from your own experience” scripts shared in training and onboarding
Education
all roles get basic conflict training
how to name what’s happening
how to ask for help early
ambassador / volunteer trainings include
“what to do if…” conflict scenarios
Environment
official comms stay in logged spaces
Discord channels, email, tickets
important decisions are not made in private DMs where possible
the “right” behaviour is the easiest path
clear channels
low-friction scripts
visible support from staff
###### Who does what when there’s conflict
ambassadors
can step back at any time
can raise concerns via:
simple forms acting as a direct reporting mechanism
raising concerns to designated staff
are not expected to mediate complex conflict themselves
first line for small tensions in their spaces
use shared scripts:
“can we talk about this directly?”
“would you be okay if I help you both sit down and talk this through?”
redirect venting away from dogpiling
and toward direct conversation or support
volunteers
registered volunteers
coordinate responses when conflict affects:
projects
local campaigns
shared spaces in their hex or region
make sure everyone understands options:
1:1 conversation
mediated call
switching project or team (at least for a while)
staff
watch for patterns:
repeated harm
same person / same behaviour in multiple places
hold the escalation levers:
temporary pauses
access changes
offboarding from roles or spaces when needed
directors
step in when:
conflict risks safety
legal issues
or the charity’s integrity
set and update policies
do not run case-by-case interpersonal drama
###### Scripts, channels and conversations
scripts
true language:
“I felt…”
“this is how I experienced it”
avoid diagnosis language:
“you are X”
explicit anti-gossip norm:
“would you feel okay saying this to them?”
“do you want help figuring out how to bring this up with them?”
channels
every conflict of substance should have a home in a logged channel
options include:
private mod / staff thread
small group chat with a staff member present
short call with a brief written summary posted afterwards
logging
reasons we log:
see patterns over time
avoid people having to re-explain painful events
keep decisions reviewable and fair
if someone keeps breaking norms (co-option, harassment, secrecy)
stewards:
hide or limit their posts or access as needed
note why in the mod log
optionally, a short public line if required for clarity
e.g. “this post has been removed for misrepresenting Peaceful Foundation”
no pile-ons
no public shaming threads
###### Moving away
opt-out
no one is forced to work closely with anyone they don’t mesh with
if direct conversation doesn’t resolve it
default move = change project, team, or scope
responsibility
if you have the issue
you help carry the adjustment:
moving yourself where possible
letting people know
handing over context cleanly
this prevents:
campaigns to exile someone
invisible blacklisting
structureI th
open allocation stays, with guidance
people are encouraged to pick work that doesn’t entangle active conflict
staff keep an eye on combinations that obviously don’t work
and suggest alternatives quietly
###### Escalation and “not a fit”
soft escalation
1. direct conversation
2. mediated conversation with a neutral person
3. temporary pause on shared work
4. project or role change
hard escalation
used when there is:
repeated boundary-breaking
targeted harassment
co-ordinated drama or manipulation
clear refusal to engage in good faith
options include:
limiting access to certain spaces
removing organiser / ambassador status
full removal from PF spaces if needed
criteria
we distinguish between:
normal friction, burnout snappiness, misreads
and patterned harm, refusal to self-reflect, ongoing chaos
the system protects:
the environment as a whole
not just the loudest person in a conflict
###### Learning from a negative experience
after significant conflicts
we do a short internal review:
what early signals did we miss?
did people know where to bring this?
did roles and systems assist, or make it worse?
outputs
small adjustments instead of big swings:
update training examples
tweak scripts and FAQs
add or clarify a policy only when clearly needed
ethos
conflict is treated as information
a sign that something in design, governance, culture, education, or environment needs a nudge
not a reason to centralise power
not a reason to invent new punishments
we keep refining the system so that:
people can disagree safely
sideways harm stays rare and easy to spot
### Working together
working together and being comfortable and effective
#### Communicating
##### Gratitude and recognising someone
#### Representing
tone
calm, factual, and friendly
avoid hype or fear
internal flow
clear channels for feedback and coordination
silence never punished — people can step back anytime
public dialogue
respond simply and truthfully
disagreement welcomed if it stays kind
##### Boundaries
legal and ethical guardrails
- follow venue rules and signage policies; no vandalism
- no commercial spam; no harvesting personal data
- health/nutrition advice kept simple, sourced, and non-medical
- respect for religion, culture, and local norms; not discussing politics
#### Workload and burnout
things not depending on individual people
(aim of the strategic plan, too)
### Passport, identity, and organising
The Peaceful Passport is the shared identity layer across all Peaceful Foundation projects.
It solves three linked problems:
- how people show they are *actually* part of the work
- how we stop others from quietly speaking “for” the movement
- how we coordinate thousands of small actions without building a weird reputation game
We explore and expand upon this more in the peaceful passport section.
#### Why we need a shared identity layer
without a shared layer
it is easy for anyone to:
claim to represent Peaceful Foundation
post “official” content
start groups or drives in our name
this leads to:
co-option
confusion
people getting hurt by things we never endorsed
with a shared layer
we can say, in plain language:
“if it’s not linked to a valid passport, it isn’t us”
this helps:
the general public
check whether something is really connected
volunteers
know which requests to trust
partners
see who they’re actually talking to
#### What the Peaceful Passport is
a simple, pseudonymous identity
one person → one passport
used across:
quiteasily
learnstuff.today
reasonable.diet
calm.college
hexagons.world
toilet.network (peaceful.network)
coomer.org
tools we use to organise
peaceful passport itself
minimal by design
passport holds:
a stable identifier
which projects you’re active in
which roles you currently hold
participant / ambassador / volunteer / staff
a log of verified contributions
(posters, meals, hubs, code, organising)
it does *not* hold:
private stories
detailed personal data
numeric “scores” or karma
identity and privacy
public view:
pseudonym + broad region / hex
high-level contributions
private / staff view:
just enough extra detail to:
prevent impersonation
handle safety and compliance
legal identity is only collected where required
(e.g. working with children checks, employment)
and kept under strict access and audit
#### How it sits alongside domains and emails
we use different domains to make roles easy to read from the outside
participants and ambassadors
use:
peaceful.network links in bios and profiles
these pages:
show their passport handle
list which projects they’re supporting
link to official materials
volunteers
use:
peaceful.foundation addresses and pages
e.g. “local organiser”, “campus contact”, “regional steward”
staff
use:
peacefulfoundation.org emails
for press, institutions, and formal partnerships
each email or profile
maps back to a single passport
so if something goes wrong:
we can see who actually did what
without guesswork or public pile-ons
#### Trust, roles, and progression
roles are about scope, not status
participants
use projects in normal life
actions are logged quietly in the background
(e.g. adding a recipe, attending a meetup)
ambassadors
opt into small, visible tasks
posters, outreach, helping online
progress through gentle stages (egg → hatchling → cygnet → swan → black swan)
all tracked through their passport, not through screenshots in DMs
volunteers
...
registered volunteers
take on:
public-facing coordination
local organising
university or council links
require:
deeper verification of identity and safety checks where needed
staff and directors
have:
narrow but stronger powers
data access
employment decisions
signing external agreements
their passports:
record those powers explicitly
so others can see:
who is acting as “the organisation”
and who is just helping locally
progression is simple:
people start as participants
move into ambassadors when they show up consistently
move into formal volunteer or staff roles only when:
the work clearly needs it
and they have already been acting at that level informally
#### Preventing impersonation and co-option
for the general public
simple rule:
“if in doubt, check the passport”
official channels always:
link back to a passport or a small set of passports
appear on a list of current projects on peacefulfoundation.org
for volunteers and staff
standard checks:
if someone:
asks for money
tries to move you to a private platform
claims to be a “leader” or “official representative”
you can ask:
“can you link your passport for this?”
and look for:
role in question (e.g. campus organiser, steward, staff)
consistent history of contributions
for external partners
agreements and MOUs:
only signed by people with:
staff or director roles
on passports tied to peacefulfoundation.org emails
this prevents:
well-meaning but unauthorised deals
people trading on the name for their own projects
when something goes wrong
if someone:
uses the brand in unsafe ways
or seriously breaches norms
we can:
remove or limit their roles on the passport
add an internal note for future safety
publish a brief, factual clarification if needed
this lets us:
protect the wider community quietly
without long public dramas
#### Coordination without hierarchy
organising a lot of people is hard
the usual options are:
- rigid hierarchy (clear, but stifling)
- flat chaos (free, but exhausting)
Peaceful Foundation needs something in between:
clear enough that work happens
light enough that nobody becomes “the boss of everyone”
principles
expertise, not rank
people move based on what they’re good at and what they care about
roles describe responsibility, not status
open allocation, with guardrails
anyone can propose or start work
but safety, legal, and money-related work still need explicit approval
one backbone for everyone
ambassadors, volunteers, and staff all use the same Passport and tools
the difference is scope of responsibility, not a separate class of person
avoiding hidden hierarchies
no global scores, karma, or popularity metrics
we don’t want “high-score users” becoming gatekeepers
reputation comes from proof-of-action
“did they do the thing?” matters more than who they are
trust is local and contextual
someone might lead a food drive in one hexagon
and be a normal participant in another
preventing local infighting
design for small groups, not giant committees
most work happens in clusters of a few people, not big meetings
clear scripts for conflict
early, honest conversation is the norm
issues surfaced quickly so they don’t turn into factions
transparent decisions where it matters
money, safety, and policy changes are documented and visible
so people argue about ideas, not rumours
keeping it fun and not lonely
nobody should feel like “the only one doing anything”
systems highlight who else is working on similar tasks
easy ways to pair up or join existing efforts
small wins over grand plans
short, clear tasks that feel doable
people can step in for an afternoon, not just long commitments
rest is normal
stepping back is expected and respected
work should fit around life, not consume it
consensus for direction, clarity for delivery
high-level direction comes from:
- shared metrics (hexagon stats, visible outcomes)
- patterns from lots of small actions
- open discussion across projects
delivery is still specific
each task has a clear owner (or small group)
deadlines and expectations are written down, not implied
the corporate layer stays small and boring
handles:
legal
safety
data
finance
so everyone else can focus on local actions and human connection
#### Using the passport to organise work
coordination
the passport gives:
a unified view of who is doing what, and where
staff can see:
“who are our active people in this hexagon?”
“who has a passport and has authenticated themselves with University eduGAIN here in this hexagon and shows it on their profile?"
“who has logistics experience for undercurrent routes?”
tasking
tasks and invitations are:
attached to passports, not platforms
so if someone moves from Discord to email or another tool
their history and context move with them
hexagons and projects
each passport:
is linked to one or more hexagons (home, work, campus, etc.)
this allows:
local organising
sensible matching of people to tasks near them
without publishing their exact address or schedule
limits
we deliberately avoid:
public “top contributor” lists
visible point systems
gamified badges that push people into overwork
the passport is:
a quiet record
a coordination tool
a way to make trust legible
not a scoreboard
more in peaceful passport, including failure modes and such
### Organising
Peaceful Foundation is meant to feel light on the surface — posters, meals, calm, local maps — but underneath everything we really require a very solid way to organise work.
One of the big background facts here is: the space of “useful people” is basically infinite. You’re not building a system for this set of roles (programmer, organiser, etc.), you’re building something that has to stay sane even when completely new patterns of contribution appear that you didn’t predict.
We aim to do three things when organising people:
- makes it easy to see *who* is available
- makes it clear *what* they are focussed on right now
- lets people and tools suggest next steps without turning life into a dashboard
// overall design of the system
We then map the elements (characteristics, demographics and experiences) to
// aspects
like ...
and volunteers progressing through consistency.
// structure
// tools
Most of this runs quietly through the Peaceful Passport and a small set of tools.
// governance
With respect to governing the organisation as a whole, you still need some things that are firm: such as legal responsibility, money, data, safety, etc. Those can’t be left to “whoever feels like it this week”. However, you don’t want that firmness to leak into the whole culture and turn everything into “managers and subordinates”.
So you end up with something like: a small band of clearly accountable people who hold the boring, non-negotiable bits, and then a very wide field where everyone else is treated as peers working in different directions and at different depths.
This looks like
#### Elements
// things that people have themselves
characteristics
demographics
experiences
One of the main problems isn’t about listing all the roles but trying to describe people in ways that are flexible, honest and useful when coordinating.
That pulls you toward very general dimensions:
* what they know how to do,
* how much time and energy they actually have,
* where they are
* what they are drawn toward, and how they've participated previously.
We treat these as moving, not fixed. Someone might show up “as a programmer” and six months later mostly be doing people work. Or they might only want to do one tiny thing reliably. The structure can’t punish that; it has to expect it.
##### Characteristics
resources
skills
interests
availability
##### Demographics
geography
religion
##### Experiences
/// what they have done with their skillset
// resume stuff
#### Aspects
// what we as peaceful foundation define onto people
##### Avian progression system for consistency
any reputation system with ranks is not a good one for the real world -- but for people contributing online, it is an invaluable thing for peaceful foundation as an organisation to have some idea who is available and has consistency.
the problem we have had previously and continue to will do so is:
good people
life gets busy
mission is not driven
and I have been guilty of being a contractor from Time Wasters Incorporated (Ltd.)
a little reputation consistency system
should not be automated
a little bit of ceremony
You can’t rely on individual relationships and informal memory. You need a shared language about people that is simple enough that anyone can use it, but not so crude that it becomes a status game (“top contributors”, “rockstars”, etc.).
egg
hatchling
cygnet
swan
black swan
###### Egg
// submitted information
// give them a general task
- putting up a poster
- online task or other
but this requires more effort
no, you can't skirt out of irl stuff
but, it can be different in different places
task characteristic is that the action is universally helpful from anyone doing it
// consensus mechanism through other volunteers
submits proof in #proof
bot assigns role to rank from reactors rank weighting (from above, not other eggs)
###### Hatchling
// generalised skill task
###### Cygnet
Then
The intersect is the focus that they can it it intersects with the a the the I suppose you would probably call it a focus. if they're a programmer and a and have this level of time availability and commitment then they can do it it distills what the intersect of that is between into a I suppose you'd call it an intersect because it it's a I think that's better because focus could be,, a more a a a adjective that is used elsewhere.
We would then just have a short example of, for instance, we we consider the two avian consistency thing and then yeah, you don't have to put the nests stuff in the avian section, we'll just define the roles and and go from there and then probably when we're discussing Discord and how we're,, then we sort of discuss nests which tops it all off because people want community. as a whole, so there's that. and in cygnet we talk about how we're getting people to work together and yeah. then in intersect the we just give some examples of how the focus section sort of works. Well,, what what people might be focussing on, so I I know off the top of my head that the, you probably have a little table there of all of them. But then if it's a yeah, the the intersect of
euphoria and euphoriaer is the thing. is then that is the
outside focus, it's that that are the the it describes that role as going outside and getting involved in your local community because obviously obviously real world work on creating community is going to be far better than online. there's that, but and especially because,, people in other countries where they can't protest, they can definitely pick up your slack, mate. no one's going to, yeah, you'll be okay. yeah, if they're in an oppressed country and they want to participate anonymously,, that's that's going to be better. yeah. and then I think there's different ones, there's the intersect of programming and then probably the one for euphoriaer as well, which I think is design or, yeah, or and then I think it's,, the other two are build or something else. so yeah, depending on what they've sort of got able to do, I suppose. So there's that. yeah. just darting around a little bit and then for editing and artistry, I I don't think that it's really smart to,, tell artists in in reality what you want as the output of people editing and remixing and doing different things and then posting the content in different places and then it's, yeah, effectively a very large bucket of content is what you want. So you don't want to create arbitrary things of yeah for artists to be able to participate in the thing because everyone has their own different little process and everything, so yeah, doing that is the best is the best, so there's that. So yeah.
it's just called bucket for artistry, it's a big bucket and yeah. But then probably some other little examples of them and then,, ones that are sort of, yeah, you can pick out my best ones in your opinion and then so, for instance, the thing between this and this and this. And then I think for instance the programming ones are a little bit repetitive, but you can show an example of what one of them or two of them look about how,, consider these steps repeating and whatnot. So,, yeah, consider this repeat,, yeah. I sort of did all that intentionally but I won't mention that. Yeah. yeah.
further onwards.
then for hatchlings moving to cygnets cygnets probably going to be the the largest rank but obviously it's well it's more about reliability and things that. the doesn't necessarily have to be the the largest rank but you sort of do little things as a hatchling and then you probably get put in little group of people to work on something together. And then provided everyone's playing nice in the group and you want to make sure that the characteristics that you've chosen for when you get from cygnet to from hatchling to cygnet is that people are able to work together. They have their own if they're working at a team then they should be able to work together. if they can't work in a team then they can still be a cygnet but they they need to work on it to be able to work in a team and that's most of the experience as a whole as well. so yeah is that yeah that's as a cygnet that's where you have you're put you're working on tasks in nests with people. So yeah probably you could also describe the experience of being in a the egg rank as well where you have a each of these also has a an understanding of a nest a nest thing as well. So
// a specific task
// working with people
// different elements together
// teams of people
###### Swan
// doing what they said they'd do
// coordinating and doing work
// consistent and to a high standard
// in reality, the passport holds the actual vibe of the thing
###### Black swan
// exceptional and good work
// great efforts
// consistency
##### Self-direction through intersects
#### Structure
// tasks
// components
// milestones
##### Tasks
small, concrete pieces of work
an task is:
a single change
that can be finished
by a person or a tiny group
without needing to understand everything
it lives:
usually in Gitlab (for software / content)
or in a simple list (for organising, research, influencing, etc.)
software-flavoured examples
Calm.college
“make the course list readable on a small phone screen”
— one clear layout change
— can be checked by opening the site on a phone
“add keyboard focus states to the main navigation”
— accessibility
— well-scoped, testable
hexagons.world
“write a test that each hex ID maps to exactly one place name”
“add a debug view that shows the current hex and neighbours on hover”
passport
“draft a first-pass list of core fields for people”
(name, region, time, skills, interests)
“prototype passkeys-only login for passport.staging”
reasonable.diet
“define a recipe JSON example that supports scaling by calories”
“add one recipe that can be cooked in a microwave in 10 minutes”
organising-flavoured examples
Strategic plan
“turn the ‘January 2026 launch components dump’ into a GitHub issue list”
“write a one-page explainer for how Components work for new volunteers”
Influencing
“prepare 10 draft posts for @easypeasymethod”
“find 3 likely partners in Malaysia (Muslim, with reach) to talk to”
Research
“collect 5 candidate datasets for local loneliness indicators in WA”
“list regional indicators that could feed hexagon place names”
Artistry / editing
“draft a Calm.college landing page that feels like hopeful Windows 95”
“edit the Philippines outreach copy into clear AU English + local flavour”
shape of a good issue
clear title
what changes, in a sentence
context
current behaviour or state
what we’d like instead
check
how we know it’s done
(“this page on mobile feels snappy and not clunky” is allowed if we define “snappy” a bit)
scope
small enough:
to be done in one sitting
or a couple of short sessions
##### Components
coherent patches of work that group issues
a component is:
a small area of the world or the stack
that needs ongoing care
and can be held by a 2–5 person crew
it groups:
5–20 issues
that all point in the same direction
software-flavoured components (examples)
Calm.college — mobile layout
goal:
resolve the clunkiness of the Calm.college mobile layout
so it feels like a tiny Windows 95 desktop in your hand
component could be called:
“Calm.college — Mobile layout and snapping windows”
issues inside might include:
“snap lesson windows to a simple 2×2 grid on phones”
“make the start button always visible”
“ensure scrolling doesn’t hide the current task window”
“add a simple ‘reset layout’ button”
hexagons.world — deterministic addressing
I thcomponent:
“Hexagons — semi-deterministic addressing layer”
aim:
a mathematical specification and programmatic implementation
of a semi-deterministic addressing system
issues might include:
“define base hex size and projection for global map”
“write spec for hex ID format (string form)”
“implement encoder / decoder for hex IDs”
“add tests for round-tripping coordinates → hex → coordinates”
passport — core model
component:
“Passport — core fields and storage”
issues:
“draft field list for people (skills, region, time, focus)”
“decide on storage (serverless DB + encryption approach)”
“document how Passport links to Huly and Chad”
reasonable.diet — recipe model
component:
“Reasonable.diet — recipe data model”
issues:
“sketch TypeScript types for recipes”
“support scaling recipes by servings and by budget”
“test one ‘potato + toppings’ recipe flows through the system”
organising-flavoured components (examples)
Strategic plan → January 2026 launch
component:
“January 2026 launch — components to issues”
issues:
“walk through each section of the plan and list launch-critical tasks”
“tag issues by project (Calm, Hexagons, Passport, etc.)”
“prepare a shared timeline view in Huly”
Influencing — Philippines
component:
“Philippines — intro campaign”
issues:
“draft outreach letter to a friendly Catholic community”
“record a short explainer aimed at students in Manila”
“collect 3 pieces of art that feel local and hopeful”
Learnstuff.today — skills pages
component:
“Learnstuff — first wave of skills pages”
issues:
“finalise list of starter skills (AU / PH / MY relevant)”
“write one-page template for each skill page”
“publish 5 skills with basic guidance + hexagon hooks”
components in tools
usually live in:
Huly (boards, status, small crew)
and link to:
GitHub issues (for implementation)
hexagons / regions (for where the work shows up)
campaigns (for why it matters now)
people:
join components
for a season
while they have energy and interest
then:
hand context on
or close the component if it’s done
components are not:
territories
permanent titles
things someone “owns”
they are:
pieces of the garden
that we keep tidy together for a while
##### Milestones
Milestones are points where the project
Yeah differ between every project and every characteristic of the task that people are completing but it's when a significant amount of, this yeah you shouldn't obviously there are cases where more art is good but for instance on that's not a manageable sort of thing bucket of art but otherwise there's there needs to be a point where you
say success criteria has been reached for this milestone of the project which also helps prevent burnout from people just having an infinite amount of tasks forever. you're feeling you're going somewhere and then it's, six weeks is enough to
plan and create something big as well. yeah I probably put that in seasons though.
Yeah that's that.
visible steps that tie components together
a milestone is:
Then I'm not exactly sure there are yeah, I think you're not really give you don't really want to give examples of what a milestone is because there are too many variables and characteristics to be able to do that but I suppose it's completing a yeah it should be that it now leads on to bigger and brighter work I suppose. That's that's a loose sort of characteristic. You can ask to go so yeah preventing burnout and things that is important so yeah.
a clear moment in time
where several components
reach a “good enough for now” state together
it answers:
“what will be true by this date
that isn’t true today?”
examples
January 2026 launch
milestone:
“January 2026 — first public constellation”
things that should be true:
Calm.college
a student on a basic phone:
can open the site
find at least one skill page
and not bounce from clunky layout
hexagons.world
a simple demo map:
Perth + one other city
with named hexagons
and at least a couple of indicators wired in
passport
people who have already helped:
can sign in with passkeys
see a simple record of what they’ve done
reasonable.diet
at least:
one complete potato-based recipe
that can be cooked in a microwave
and scaled up/down based on time and budget
organising
the strategic plan sections:
have been turned into components and issues
so the next wave of work is clear
smaller local milestones
“Geraldton — first Civic Picnic”
“Perth — first hexagon-based Calm session”
“Philippines — first outreach call with a local partner”
each milestone:
pulls in issues from:
influencing
organising
research
artistry
and makes the result:
public
cheerful
repeatable
milestones in tools
live alongside components in Huly
components:
own the ongoing patches of work
milestones:
group tasks across components
by date and story
when we approach a milestone:
we:
trim nice-to-haves
focus on “what needs to be ready for this to feel real”
let other components wait
when we hit a milestone:
we:
celebrate
document what happened
close or reshape components
based on what we learned
#### Systems
Important: progress is always shown relative to a project, never relative to other people.
So:
“This task is blocking these next tasks”
“This contribution feeds into Calm.College”
“This helped a hexagon move from X to Y”
A system should feel like:
a shared map
a shared memory
a shared vocabulary
Not:
an org chart
a command structure
a platform that needs managing
Never:
“Top contributor”
“Most active”
“Highest rank this month”
That single design choice prevents gamification creep.
The last big constraint in what you’re saying is that it has to stay enjoyable.
If the system is conceptually elegant but people feel isolated, guilty, or confused, it fails. “Fun” here isn’t gimmicks; it’s that people rarely work alone, the tasks are sized so they feel doable, it’s socially normal to change what you’re doing, and stepping back doesn’t feel like a betrayal.
All of that together is the thing you’re actually designing:
not “a volunteer programme”, but a way for a huge number of very different people to find each other, line up loosely around shared projects, and keep moving without needing centralised commands.
##### Volunteers progressing
// how do volunteers progress?
#### Software
we use a small set of tools, layered gently:
Discord
where most people first show up
where conversations and early coordination happen
Peaceful Passport
a calm record of what people have actually done
Gitlub
where concrete tasks live as issues
where code and content are kept together
Huly (later)
how we group work into components when things get bigger
Chad (later)
a gentle matching layer between people-as-they-are and work-that-exists
the aim is:
someone with a Discord account can:
join
understand what’s going on
pull one clear piece of work
co-create how it will be done
without:
needing to learn everything
or fight their way through a pile of issues
how people first meet the system
Discord as the doorway
most people already have Discord
it’s familiar and low-friction
they don’t have to install a new app just to help
they arrive into:
a clearly signposted welcome space
a small jobs forum
project channels that are:
quietly curated
kept from turning into chaos
the first experience should feel:
intuitive
honest
and more effective than anything else they’ve tried
“oh, I can actually do something here”
Passport as the quiet memory
early on:
people can just act
join a call
test a page
write a small thing
once they’ve done a couple of tasks:
Passport becomes:
a simple reflection of those actions
not a performance score
not a title
this lets us:
see who is already doing what
invite them into deeper coordination when it makes sense
without:
bureaucracy
or personality politics
how this evolves as things grow
when it is just a few groups
Discord + Passport + GitHub:
are enough to coordinate most things
people:
join via Discord
pull a job from the forum
work with a coordinator and a maintainer
see their work reflected in Passport
this stays:
quite informal
very human
as projects and people multiply
at some point:
Discord becomes:
noisy
general
too much to hold the whole plan
we do not try to:
force all planning to stay in chat
instead:
we start using Huly to:
group work into components
make small boards for each area
let crews of a few people care for them over time
we introduce Chad to:
look at Passport:
skills
availability
past contributions
and suggest:
“you might like helping with this component”
rather than:
“here is your assignment”
Discord’s role once Huly and Chad arrive
Discord remains:
the doorway
the place to:
ask questions
share wins
host small calls
offer generalised tasks that anyone can do
structured planning:
lives in:
Huly (components and timelines)
Gitlab (issues and changes)
Passport (who did what, across projects)
for someone new:
the experience is still:
join Discord
see a small, curated set of jobs
do one thing
gradually be invited, if they wish, into the deeper layers
for someone experienced:
they can:
see the bigger picture in Huly
pick and shape work at component level
use Chad’s suggestions as a way to spot where help is most needed
##### Discord
structure.
I think that you would begin the section by describing how you need a highly scalable structure for organising.
And such a thing should be really simple.
,
components
have tasks within them
and are part of a milestone.
And and the and works towards a milestone.
,
structure.
Then each of the subcategories within this little thing, explain what a task is and how it's is a GitLab a GitLab issue, because we put everything we distil everything into that.
And then we use that's the neutral thing.
And then the component maps onto the coordination platform that we're using, Discord or Huly.
And they can be kept up to date in the same way, broadly speaking.
some tasks might only be on Huly because of complexity or requirements or whatever.
But,,
yeah, we can keep those things in sync with bots, broadly speaking, even if Discord is just read only at some point.
through a Huly migration or things.
Discord, the then in the Discord section as well, the aim, eventually we'll wind down the Discord it's less of a project management thing.
And that in a long while, it's less of a project management thing and more of a way to do scalable tasks for the project and coordinate and different things and yeah, Discord is for
the junk food of social interaction.
Sorry.
, you probably don't say that.
But
yeah.
Discord is for
online communication.
Not conversation.
, that happens I that happens IRL.
, and you can put the term IRL instead of
in real life or defining it,.
, yeah, because Discord, whatever.
,
then within structure, you're defining task, components, milestones, the different characteristics that they have the presentation of them.
in components, then we collect those into a tasks are discussed on GitLab, which is where they're stored, which is where project whatever.
The really nice way of explaining that, I'm sure.
, and then the components have a
they're in Huly because they're called components in Huly, but in Discord, and they hold different tasks and sit within a milestone.
In Discord, then because it's not a project management software, then we do a
because it's not a project management software, then we do a
tasks forum, and the forum posts within that are
components.
And then also when so Discord is also useful through as a discussion platform because we can also have people arguing over the best approaches to accomplish something, even before the component is ready to go or anything that.
there's that.
Which is good.
For instance, Discord has forum posts and then forums can have little comments and things that where people can,, create a little little chat between them. and that can be around a central central topic. Um, you're alluding to all, you're getting people to understand different parts of Discord if they've never used it or heard about it before, but also for people who the most simple explanation and very concise for people who more than likely already know what Discord is or get the get the concept immediately. You're just sort of highlighting the features that we use in Discord like without naming where they go into like yeah, like for instance like there's private threads, there's public threads, there's like yeah, forum posts, there's roles and onboarding and yeah, a bunch of different things. And there's also like bot integration which deals into our volunteering system as well, which is good. Says that so you're just sort of naming all the different features that Discord has that we utilise but not really how we utilise them, but in like a really like effective yeah, concise and elegant way. And without it feeling too much like a list, like it should feel like a lived experience of it, but like really, really concise. Like it's not someone a person's like lived experience of the thing. It's like because that's pretty sad too. Um, but not because it's sad but because like you wanted it to be concise and just like there are,, yeah, naming features without listing them um and like making it seem like AI generated slop. Wow.
in the system section. to talk about how we apply the same structure, soon to be defined, structure, of,, of,, yeah, task components and milestones, which are about what they sound onto each version of this system so that, yeah., maybe you don't even say that. All right? you don't have to introduce the structure. I think you'd put that into, you define, then you'd explain how you implemented on each of those two systems in tasks and components and,, because Chad is something a little bit different as well. So,, yeah, with systems, it's Discord., everyone has it, and it's easy to onboard people, and we do have a volunteering system outside of that as well. But, and, these things interlink with our volunteering organising system. But if people don't know what to do, they can just join the Discord and they'll answer a couple of questions in-built into Discord and that's up to them if they want to go further. So there's that., so,, an ambassador can also find a whole bunch of things that they can do in their little thing., for different projects that could help out if they want to do something, especially if they want to do it IRL., so yeah. I think on, in the Discord, explaining Discord, you'd be, well, Discord, everyone has it., on most of our target demographic has it., young people and whatever,, young people, university students, a lot of these,., yeah, and it can support a lot of users. So,, yeah, don't worry about that, I don't think. But how it sort of a brief explanation of Discord of, oh,, you can have things,, it's a chat room, and then you can have forums and threads so that people can talk about something in a side channel during the main conversation. Um, yeah, people spend a lot of time on Discord. And it also has voice a calling functionality and a whole bunch of stuff. So there's a bit there. So, your aim is, so yeah, you just want to have a bit of a fairly streamlined system. it's Discord isn't can can make do with a as a project management system. but yeah, you're not even dwelling on that. You're just explaining what Discord is and how are using it. It's both a community space, and then there's we list a yeah, people can coordinate around different components which are stored,, which are referenced within their, um, which are referenced inside the yeah, they mirror different locations where, yeah, information is mirrored in Discord and it's often used as a communication platform. But then whenever more formal things have to be discussed, then it goes to Gitlab, but I feel it's overcomplicating things. this this section should just mainly be on Discord. And,, it's a yeah, it's a very easy to use communications platform and people can create little chat rooms. And then the different functionalities and, then in the structure we'll sort of talk about how the, how the structure maps onto those systems is the most effective way of of showing that. So yeah, and then we get to yeah, discuss working together in nests, which we've already discussed a fair bit on. So yeah.
main ingress into project
conversational
casual
everyone has an account
or makes one easily
adapts Discord structure
maps onto all other Peaceful Foundation systems
not project management software
but we adapt it
characteristics
onboarding functions assign ranks and roles
personality type
location
interests
skills
personalised task lists
based on demographics
demographics
youth-centreed
gaming origin
technically literate
corresponds with target volunteers
aspects
understandable for most people
some won't use it
can still contribute
putting up posters
calm.college events
Q&A sessions
ambassador role
outside Discord
channels
types
announcements
rules
normal
conversation
slow mode
toggled
threads
public or private
forums
not too many
funnels conversation into too many places
overwhelming
feel good
fun
onboarding flow
click link
join with existing Discord
or create account
four questions maximum
personality type
DISC
animals
quirky
understood implicitly
location
interests
skills
main page
actual server access
additional onboarding
menu access
more roles
guides on how
video requirements
overview of Peaceful Foundation
safety briefing
short
vertical
attention span appropriate
age verification
over 18 channel
button press
basic check
under 18 funnel
volunteering onboarding
call with people
safety verification
training completion
separate server
automated methods later
Age ID
open age API
privacy-respecting
parental involvement
video with parents
awareness of participation
verification complete
access granted
ranks and progression
egg
new joiners
can't participate in tasks yet
no training completed
can do general tasks
putting up posters
can make content
hatchling
API integration tasks
simple programming
toolbox integrations
regex for hexagons.world
clippy recipe viewer
work with others
cygnet
swan
black swan
nests
grouping by demographics and interests
initially manual
private forums
private threads
assigned by swan or cygnet or organising rank
based on time availability
immediate community sense
focus for work
tasks forum
forum posts as components
tags
maximum 20
projects
quiteasily
skills
peaceful foundation mapping
progress status
titles with specifics
not just "programming"
felt
svelte
web dev
design
manhwa
manga
component discussion
project management
meta discussions
design decisions
tasks on GitLab
manual initially
bot integration later
formal specification
technical discussion
assigned to components
migration path
structure maps to future systems
progressive onboarding
familiar platform first
target demographic match
voice notes
implicit in system
recorded
processed
integrated
###### Safety on Discord
// underage
discord age filtering
// safety link at the top
###### Channels
welcome
readme
safety
induction
role based ticket onboarding
ambassadors and volunteers
interests
computers
programming
organising
influencing
researching
editing
artistry
personality type
DiSC
MBTI
availability
euphoriaer
journeyer
adventurer
supporter
sharer
register as a volunteer
register as a registered volunteer
-- you'll have to give us your real name
what are your circumstances?
not over 18?
underage brief primer
flow to join other server
export their information into short code they can copy
then join reef.peacefulfoundation.org
OpenAge
onboarding
child induction
parent induction
booking link together
over-18-check
guide
chat
converse
project
fun
// channels for you
developers
quiteasily
learnskills.today
reasonable.diet
pit
###### Egg to hatchling, to cygnet, to swan
need people to have some skin in the game
because oftentimes, people say "yeah"
but life gets in the way
or, personal problems
embedded heirachy, sure
but this is fine for these tasks
contributions neutral underneath
egg
generalised tasks
hatchling
generalised specific tasks
cygnet
doing a good job
swan
proof channel
###### Nests
Then working together. The nests yeah can discuss how that sort of works. Where nests are people can add people in a nest. You don't want an overcrowded nest, but they are flexible. And you can build bigger ones, I suppose., and we've discussed some in previous sort of things, so I just pull that stuff to where it is here. But yeah, nests are where we coordinate people into groups based on their characteristics or different circumstances or,, a nest is a very highly versatile group of people who,, and because we have all the characteristics of things, we endeavour to put people in nests where people grow and complement each other and their skill sets. And then,, probably,, interviewing people and getting to know them and things that and,, understanding their skill sets and and,, complete honesty and yeah, good practicing of the culture as well, which is why you get people going through multiple nests through a thing and then you get a feel for them and,, little team tasks and things that and whatnot. So, yeah. Um, nests there's also,, just inherently safety features in them as well., people get booted from a nest through a,, a reaching a quorum within the nest. Um, and the quorum size depends on the size of the nest, because ultimately it should be a good place to work in general. Um, and yeah, there's a, there's a weight to,, in smaller nest, then it might be a more than half people fit the quorum to,, remove someone from this nest. Um, but in larger groups, it might be a smaller quorum because you're not contacting as many people and,, yeah. And then if someone gets booted from a nest, we sort of want to understand why and then there's reflection sort of things and,, after people have been in a nest and they all have different times and whatnot, then we ask them to sort of reflect and,. Um, yeah, it's good. And it sort of helps because you can sort of paint to people a journey throughout their things and,, and that's sort of a, the personal change sort of link into the seasons part of that as well. But the other thing is flocks and flocks are a whole bunch of people moving in a similar direction, um, or have different characteristics. Um,,, interests or things that, programmers or,, anyone can make a little flock. And um, or,, we want to keep them not too so clicky. they should be sort of, um, yeah, we want to have people joining different flocks based on for instance, if they're a programmer, we don't want too many flocks, but if they're a programmer, then they should probably be able to meet up with other people if they've got enough people in to make a a group for their pro their their programming language Rust or something that. Um, or C, or yeah, or just, yeah, interests or things that. as we can be more we don't want to split up conversation to the nth degree, but more we can do regions and countries and things that. Um,, and,, starting off with regions until we get enough people, then you can do countries. And then,, people can sort of then chat between,, where they are on the Hexagon Map and things that. So, and, this sort of creates more local communication, which is good. Um, and yeah. Um, and also,, I think there's personal change in that as well. And, especially if people are working on on what they wanted to do and a good vibe, so, yeah. And then flocks as well might be interest in,, people who, yeah, people who um, play tennis. But they would not be video games or online hobbies on the, on the discussion., yeah, that's a yeah, no way would you play video games. Um, but they not really that, you wouldn't even bring that up. But, they should be in real life hobbies. Um, and then maybe you say in brackets IRL because it defines the earlier Discord term of IRL. Um, in real life hobbies, so they have, yeah, that. And no electronic stuff. And it it also depends how many flocks that you have, depending on,, how, yeah, because you want large groups of people to show,,, we're sort of solidarity. You don't want a whole bunch of two person or ten person flocks or things that. You want to,, have a a large amount of people to be able to make one and you sort of sca-,, you you consider and then,, people can always make nests for little things as well. So, yeah. That's that's a bit of a delineation. Um, and ultimately they're a little bit more, we just want to make sure that people will, yeah, certainly,, obviously, yeah, Peaceful Foundation, for instance, they would not,, for instance,, cultural factors within this. it didn't even cross your mind that people would do politics or anything that. it would be foolish. in the it with Peaceful Foundation it would be foolish to even consider something that. But that that might might just be a little point for somewhere else or somewhere. So, yeah. Um, yeah. I mean, that's cute. So, it could it could fit in flocks, but obviously, yeah. Anyway, you don't want to say the word politics, but you want to allude to to things that. competing ideologies. it didn't even cross your mind because it's, yeah. Another example of that but you wouldn't name it or you would, you wouldn't even allude to it but you people would understand that instead of a huge different religions or anything that, then instead it's just religious flock. So yeah. They're flying around.
for nests in the cygnet and swan ranking and black swan but it's not really this black swan explains different stuff but it's for the yeah for complete consistency would be black swan and also doing something pretty cool too. So yeah and for cygnet and swan for nests then you're also describing what the appropriate yeah you're based on the task from an organiser sort of running through a little bit of the project management and helping people come to understand of how long their different times might take to be able to,, we sort of have a standard project onboarding flow to be able to bring people together and the questions that they need to fill in to be able to do it. So they have to make a little project plan and then someone an organiser as facilitator to be able to check in on that and also could be the the organiser of a component. and ultimately in a very human way. And so yeah and then this also allows us to have,, um people can list out how they manage things and whatnot, maybe there's a sort of choosable choosing system or something that um and their experiences in managing different things and we try to assign the best project management manager possible to developers or people working together on things.,, a bunch of artists working on some sort of shared thing or,, the different manifestations of it and and whatnot, because it's a,, conceivably unlimited amount of art that you could be created in such a way, which is pretty cool. Um, but yeah there's there's that. so we also estimate the size the how long we're gonna be in this nest for, for the for the foreseeable. So, um yeah,,, if it's a group of 10 yeah, if it's a group of a whole bunch of people hatching,,, from egg to,, that might be 10 days as previously discussed. But then for,, different tasks that are involved that that might be anywhere from 21 days to,, six weeks and but they max out at six weeks., at that point you have to repair the nest and see what's going on, um because you don't want it to be a,, yeah. And then you don't yeah, you don't want it to be a a really long task that just,, extending nest or things that. it's a hard cap and then you have to recreate a new nest to be able to do such a thing. So, is that? Um yeah.
Four nests. Nests are private threads that people use to be able to coordinate work that you put people you think might work well together or people create their own nests and we do this in a variety of different ways for instance., when someone joins a is an egg then we put them in a a little nest of other people who are completing their tasks so they get fulfillment and then they yeah, that they they post their proof and they gets a little bit of thing in the group and then people realise they can do do things and what not. But you also don't want to make it too sort of touchy feely and you're matching people people are matching people to other people and building nests both them both themselves of who they might get along with or something. to in many ways. So yeah, an organiser who sees more people coming in is matchmaking saying what deterministic rules and everything might put people together in interesting and prosocial ways that everyone gets along with personality things or or what not or demeanour or, you probably want to sit down and have people in little onboarding rooms and everything chat rooms and everything to to be able to coordinate the work they're doing as well. or, just sort of not really, just ideally you want to have a conversation with the person where they talk about something that they they love it's not an interview or something that, but you just want to get a vibe of, and then you can also vet for personality tests in more more detail that they can optionally give us,, just how the Myers-Briggs things is optional. but they can also,, you don't want to get people doing a whole bunch of different tests or anything that. and if you are going to get them to do tests and they need to be useful. and exportable so they can and they have insight about such a thing. So, yeah. yeah. Right with nests for instance egg gets put in a nest with other eggs and then you see if they incubate and a nest, that nest might last for 10 days or until everyone incubates. And then or depending on how much stuff people get done initially, if they get it done in that that time then they,, then they're all of a sudden you got a,, a nest full of hatchlings. but then you might also there are a bunch of different ways that you you want to people to be sort of part of multiple nests at the same time. All that creating conversations within the flock as a whole as well. So they they would probably have a a flock is sort of a a group of group of aviants, a group of birds in a who have a shared characteristic. so yeah, that's a that's group of aviants who have a shared characteristic and they're all flying in the same direction. So,, programming would have a really large flock. or then different little groups within the within the thing a flock is people can make their own little flocks then people join them and then they can sort of chat in little tags and everything and it's it's cool. so they just have little private threads that they get invited to based on,, you can sort of find your interests and things that. but this is part of initially as an egg you start off as in a nest but then if you want to be part of a flock, then you got to hatch, right? And then there's a yeah, you got to be a little bit of a grown hatchling,. probably completed your first thing but with the yeah that's sort of a flocks. And then there would need to be as well there's also a
leaving egg rank
private forums
groups of people
allow transparency from mod team and therefore safety
nests are small, time-bounded coordination groups
they are used to bring a small number of people together
for a clear purpose
for a limited period of time
nests support
small group work
initial onboarding clusters where useful
local or demographic coordination
short-term collaboration
nests are not
permanent structures
status objects
replacements for broader project spaces
###### Nests Bot on Discord
implementation
nests are implemented as
private Discord channels
with controlled membership
and lightweight metadata stored externally (bot-side)
the bot is responsible for
creation
membership management
lifecycle tracking
command handling
definition
a nest is defined by
elements
aspects
size
duration
elements and aspects are referenced from the core model
implementation
each nest stores
id
name
creator_id
selected_elements (array)
selected_aspects (array)
target_size
duration
start_time
end_time
state
join_mode
stored in
a simple database table or document store
elements/aspects should be stored as
IDs referencing predefined sets
not freeform text
creation
nests are created through a guided flow
implementation
/nest create triggers
interactive prompt (slash command + follow-ups)
options
Discord modals
or sequential ephemeral messages
flow state
temporarily stored per-user
until confirmation
on confirm
1. create DB record
2. create Discord channel
3. set permissions
4. optionally add seeded members
5. send initial message
commands
/nest create
implementation
slash command
supports optional name argument
followed by guided prompts
/nest join
implementation
input
nest_id or name
checks
capacity
state
join_mode
compatibility (basic)
then
add user to channel
update DB
/nest leave
implementation
remove user from channel
update DB
no confirmation message required in channel
only ephemeral confirmation
/nest safety
implementation
static response
ephemeral message
no DB interaction required
/nest safety report
implementation
open modal or prompt
store report in DB
report_id
user_id
nest_id
reason
text
timestamp
notify moderators
private channel
or webhook
/nest about
implementation
fetch nest from DB
render summary
ephemeral or public depending on context
joining
join modes stored per nest
open
request
invite_only
system_suggested
request flow
store pending request
notify moderators
allow approve/deny
suggestions (v1 simple)
filter nests by
not full
active
basic element overlap
return small list
leaving
implementation
immediate removal
optionally log
leave_reason (if provided)
timestamp
optional trigger
recommend new nests
safety
implementation
no scoring systems
no visible reputation
safety is handled via
clear commands
private reporting
moderator visibility
reports should be
easy to submit
easy to review
reports are sent to peaceful foundation safety team
safety model
no public logs of reports
no public ratings
moderators receive reports via
private channel
or dashboard
users are never exposed to
internal flags
hidden scores
lifecycle
each nest has
start_time
end_time
state
background job (cron or worker)
runs periodically
updates state
if nearing end → cooling
if past end → closed
on close
lock channel
or archive
or delete (configurable)
optionally
send closing message
matching
implementation (v1)
simple filtering, not complex scoring
match users to nests based on
element overlap (basic)
rank compatibility
availability if available
do not over-engineer
no ML
no opaque scoring system
return
2–5 reasonable options
placement boundaries
implementation
enforced as checks during join
if full → reject
if closed → reject
if incompatible rank → reject
if blocked by moderation → reject
return simple reason messages
discord implementation
channel creation
create under "nests" category
name format
nest-<short-name>
permissions
only members + bot + moderators
initial message
posted by bot
name
elements
aspects
size
duration
short guidance
channel lifecycle
active → normal use
cooling → optional message
closed → locked or archived
roles
users
can create, join, leave, report
coordinators
can
view all nests
override membership
close nests
implementation
moderator role tied to Discord role ID
success conditions
implementation view
users can create a nest in under 60 seconds
users can join in under 10 seconds
users can leave instantly
no complex UI required beyond slash commands
system runs without heavy manual moderation
###### Web Portal
purpose
provide a broader interface for nests
beyond Discord command interaction
the web portal is used for
browsing nests
viewing nest details
discovering suggested nests
lightweight coordination
moderation visibility where required
it is not required for basic usage
all core actions remain possible through Discord
core views
###### Nest List
shows active nests
name
short description (if present)
size / capacity
duration / time remaining
key elements / aspects
###### Nest Detail
full view of a nest
name
elements
aspects
size
duration
members (limited visibility)
join option
###### Suggestions
shows recommended nests for the user
based on simple matching logic
###### User Nests
nests the user is currently in
and recently completed nests
interaction model
users authenticate via Discord OAuth
the portal reflects
their identity
their nests
their permissions
actions available
join nest
leave nest
view details
creation (optional v1 or v2)
nests may also be created via web
using the same flow as Discord
moderation surface
moderators can view
all nests
active reports
nest states
moderation actions
close nest
override membership
review reports
this reduces reliance on Discord-only workflows
implementation
simple web app
frontend
basic UI (lists + detail pages)
backend
shares the same database as the bot
auth
Discord OAuth
api
nests
memberships
reports
sync model
Discord remains the source of interaction
web reflects and extends visibility
principles
the web portal should
not duplicate Discord unnecessarily
not introduce complexity
make discovery easier
make moderation clearer
it should feel
calm
lightweight
optional but useful
###### Forums
###### Ambassadors
generalised tasks that ambassadors and volunteers of egg and hatchling get proof for
posters
memes
content
###### Arguments
(later, discussions -- name is a bit tounge-in-cheek for now)
the best ideas floating to the top
pre-specifications
just the project tags
yay!
oh no
.
###### Tasks and Components
// basically make this an early version of huly
posts as components
tags
discord has a limit of 20 tags
this is actually a perfect amount
- meta
progress
- open
- in progress
-
-
- done
skills
- Community
- Programming
- Organising
- Influencing
- Research
- Editing
- Artistry
projects
- quiteasily.org
- learnstuff.today
- reasonable.diet
- calm.college
- hexagons.world
- peaceful passport
- peaceful foundation
title tag
specifics
###### Svelte, Webdev
###### Social
[
[]
specifications
why a small tasks forum
we do not want:
a wall of hundreds of open issues as someone’s first view
instead:
we keep the volunteer forum small on purpose
roughly 20–25 live components at a time
each component:
represents a broad area of work
gives a sense of:
“what exists here”
“what kinds of things people can do”
this helps people:
see the breadth without being overwhelmed
pick one thing that actually fits their energy and skills
how a forum post relates to a component
beneath each job on Discord:
there is usually:
a component or set of issues in Gitlab
and, later, a component in Huly
the job post:
says in human language:
what we’re trying to do
what kind of help would move it forward
who is currently holding context
links out to:
the Gitlab issues
or a simple spec document
if someone wants to help:
they can:
put their hand up in the thread
ask for clarification
be looped in by someone coordinating the component
coordinators without “owning” things
for some jobs:
it helps to have:
one person keeping an eye on progress
collecting questions
making sure we don’t talk in circles
we describe this as:
a responsibility with clear scope and time
e.g. “coordinate this page refresh over the next three weeks”
not as:
a permanent role or identity
e.g. not “HomePage Owner”, not “Hexagons Coordinator”
Passport:
remembers that they did this
without turning it into:
a badge they defend
or a hierarchy they sit above
##### Peaceful Passport
record of contribution
the tasks they performed instead of roles
##### Gitlab
every Peaceful Foundation website and app is made out of code
GitLab is where we keep that code together in one place so that:
multiple people can safely work on it at the same time
we don't lose history when laptops die or people move on
we can see what changed, when, and why
why GitLab?
open source
https://gitlab.com
hosted at git.peacefulfoundation.org
we control the instance
no lock-in, no surprise changes
anyone can contribute and improve the software over time
friendly development team
modern interface
flexible and adaptable
great product overall
clean and seamless to use
groups and access control
add people to Peaceful Foundation organisation
they get started right away
different access levels for different parts
anyone can contribute
swan and black swan ranks review and merge
integration possibilities
Peaceful Passport authentication
bots pulling issues into Discord
eventual Huly integration
version control: what it is
the problem it solves
imagine 100 or 1000 or 10000 people
all working on the same document at the same time
live editing would be chaos
everyone moving everything
opinions colliding
deletions and rewrites
the solution
everyone has local copy
they work on their own machine
when ready, they push to cloud
others pull down changes
clear descriptions of what changed
easy conflict resolution when changes overlap
GitLab as interface
graphical way to do this process
integrates with developer toolkits
best ideas win through consensus
central place for code and documentation
version control: git and jujutsu
git
the standard way the world tracks changes to code
developed by Linus Torvalds in a weekend
really old now
really good job for the time
// xkcd comic here
"just wait for the Git expert to stop talking about how genius it is so I can get the commands that fix everything"
jujutsu (jj)
modern version-control tool
stores everything in git
fully compatible underneath
extra layer that fades into background
no one has to use it if they don't want to
but gives cleaner history and more flexible branching
for non-developers
think of it as "track changes for the whole project"
easy way to:
undo mistakes
keep experiments separate until ready
see who did what without drama
for developers
we default to jj where possible
clear, rewritable history
easier collaboration on long-running branches
better suited to large, evolving codebase
shared across many projects
vibe coding welcome
people will rewrite and improve over time
repositories
each project has one or more repositories
quiteasily.org
learnstuff.today
reasonable.diet
calm.college
hexagons.world
passport, chad, undercurrent, etc.
layout boring on purpose
code
text, readme and translations
config and deployment notes
new contributor doesn't guess where anything lives
front end and back end
each project has both
back end designed to be stable
depreciates slowly
fixed components
front ends can vary
people create different versions
best ones merge in over time
private repos only where genuinely needed
safety, legal, or partner reasons
otherwise default to open
people learn from and improve the work
development practice
minimise bikeshedding by automating style
automatic formatting
Prettier-style tools
consistent code style across editors
"run the formatter" instead of arguing about spaces
linters and basic checks
catch obvious mistakes early
keep each repo easy to work on over time
lightweight tests where they matter
especially around:
auth and identity
map / hexagon logic
undercurrent and passport internals
goal
new contributors don't guess "house style"
they focus on what code does, not how it looks
feedback and issues — more than just GitLab
we don't expect most non-developers to touch GitLab
if someone notices problem or has idea:
fill simple form on site
drop into Discord help channel
leave short written or voice message
volunteers and developers then:
ask follow-up questions in plain language
"what phone are you on?"
"what did you click just before this happened?"
turn into clean GitLab issue
clear title
what happens now
what we'd like instead
how to tell if it's fixed
aim
one calm, high-quality issue list in GitLab
with many easy ways in for everyone else
how GitLab fits in
issues as concrete task list
GitLab is where:
actual tasks live
especially for:
code
content
things that change websites and apps
Discord
where we talk, ask, propose
discuss the component itself
what issues should be part of it
GitLab
where we discuss:
how to accomplish tasks
best specification through consensus
more formal structure
this keeps:
conversation human and flexible
task list:
stable
searchable
not constantly rewritten mid-thread
the Discord-GitLab flow
Discord forum posts = components
discuss component as a whole
matter of component
raw input from community
GitLab issues = tasks
discuss best way to accomplish
formal consensus on specification
updates back to Discord via bot
Huly later
when Discord outgrown
components move to Huly
GitLab stays for issue-level discussion
who can change what
anyone:
suggest tasks
describe bugs or ideas in Discord
add detail in shared documents
only maintainers / Peaceful Foundation people:
edit GitLab issues directly
merge code or content
this avoids:
drive-by edits that confuse plan
issue threads turning into endless debates
but maintainers expected to:
summarise conversations fairly
add context from:
users
volunteers
partners
shared understanding, not arguments
before opening or updating issue:
ground in simple, shared understanding:
what is happening now
what we'd like instead
what constraints we know about
if disagreement:
resolve in small, human conversation
voice, video, short back-and-forth
rather than:
long public thread with winners and losers
we are all here for the same mission
this is how we:
avoid hidden hierarchies
while still:
making decisions
moving forward
##### Huly
Then Huly is what we use for formally organising projects. Because it is far better at doing.,, because you have components inside of Huly interacts with a bunch of a,, Huly interacts with different programming tools and different, has different integrations that you can track issues for instance in a centralised place. And on,, for instance, it's mainly geared up towards programmers, but I will also probably give a bit of a, yeah, it's really well-done software and everything's clearly well-documented and everything. And so we can put components, we can link a whole bunch of issues to things in Huly. And that's sort of where people who are,, part of the project,, people who are internally volunteers or um, formal volunteers or staff or just people who need more organising for what they are doing, for instance, as an ambassador on calm.college. And Huly also has all the different project management features that you want in a thing. It also has a,, ways that they can sit in meetings or have,, sort of a virtual online workspace as well, which is pretty cool. So, there's that. And much the same way you're just sort of explaining the features that we use in Huly, which isn't too much, so I wouldn't dwell on that um because then it would just it, yeah. It's the live this one's more the lived experience of people using it in Peaceful Foundation, which is what I just described. So don't just go listing out a whole bunch of features because we don't really use a whole lot of them and it's just standard sort of project management stuff but really well done. And then it also integrates with code and Git and things that. So, yeah, it's useful.
why Huly?
labour of love
exquisite documentation
beautiful technical design
well-structured, well-mapped
genuinely beautiful and well-documented
pleasure to use
built without recognition for a long time
we want to reward the developers
helping within open-source nature
no hosting penalty to them
data sovereignty intact
open source
https://huly.io
we can host and adapt it
no lock-in, no surprise changes
host our own instance
organise.peacefulfoundation.org
in Australia
fine-grain control
roll everything back if needed
fits how we work
boards, tasks, comments, links
lightweight enough for volunteers
strong enough for large, long-running projects
integrates with GitLab
pulls in issues
wraps them into components
maps milestones
creates shared plan around existing work
structure
milestone → component → task
we say "task" not "issue"
friendlier, more actionable
maps to GitLab issue underneath
fits our internal language
components were forum posts in Discord
same concept, formalised
clear separation
Huly for planning
GitLab for code
Passport for who's doing what
keeps everything simple and traceable
absorption and direction
our developers contribute to Huly
merge requests upstream
Passport login integration
GitLab login mapping (currently GitHub only)
developers become invested in each other's success
highly likely Huly developers support Peaceful Foundation
eventually release as product for businesses and non-profits
//: conflict of interest acknowledged but acceptable
inherent in using any non-in-house software
fair trade for mutual benefit
the transition moment
Discord becomes clunky
too many people
too many projects
coordination strains against chat format
Huly takes over for formal work
Discord shifts to:
generalised tasks
social space
proving ground
entry point for new contributors
who is in Huly?
not everyone
most people:
use the projects
join Discord
log actions through Passport
they never need to see Huly
staff
anyone on peacefulfoundation.org
finances, coordination, partnerships, infra
use Huly to:
see components
support teams
keep timelines calm
volunteers and formal volunteers
peaceful.foundation
verified through passport
have clear, ongoing responsibilities
responsible for:
And also because when maybe a note in Huly is because most of our organisation runs off text files or static data then we can store all this. it doesn't need to be some sort of live database that people are accessing all the time.,, you are yeah. It's most of the things we do are text files and they can be referenced on public repositories and then commented on in Huly if they it's yeah.
and then,, execution social, a little bit of social and,, sort of stuff is in Discord. I'm mainly referring to that with flocks and then also task management stuff. But,, it's sort of the the vibe is that we'll also outgrow Discord because it's not a project management tool as well.
parts of campaigns
local hubs
technical domains
mostly cygnet and above
cygnet, Swan, Black Swan
with track record of completed tasks
invited into specific projects or components
not the whole organisation at once
get peaceful.foundation email address
logs into Huly directly
sees assigned work
coordinates with crew
implicit trust through investment
not zero-trust
implicit trust from time invested
previous steps completed
Passport history visible
role assignment automatic
access control from contribution record
formal feel from earned entry
same structure persists across tools
easier to navigate
project-limited access
some people:
campus organisers
local undercurrent participants
just other things that we have access to and you can see how I've outlined different parts of these things. you'd want to make different categories for it. there's textiles, then but jumping back really quick to there's computers under the yeah. the internet-connected things. there's Apple. there's, yeah, then man's win- window, windows, and then Linux, and I guess I'll elaborate on Linux a little bit because and then don't forget that we're also we're this is a a subsection because we're talking about different categories for what we've got access to. but Linux is an open source operating system, and people the joke inside the Linux community is that next year is the year of the Linux desktop. but it's looking that something feels different nowadays. it's people are using Linux. And I think that if you can get, if you could somehow get your girlfriend to be into computers, then you can have a real shot at at doing a good job of it. At getting yeah. if it didn't have AI, if it was super good and a tiling window manager and the most efficient thing, and it was customizable that you could use it however you wanted, the entire thing would be beautiful. Anyway.
get access to:
only boards relevant to their area
so they can plan without seeing everything else
staff and directors
see more boards
cross-project pieces
funding + infra + risk
use Huly to:
spot gaps
support crews
align timelines without micro-managing tasks
creative types might stay on Discord
artistry
editing
more accessible for their workflow
check Huly occasionally for formal context
organisers might use both
Discord for coordinating people
Huly for structured planning
how it feels to use Huly (for a new cygnet)
flow
1. you've done tasks already
through Discord + Passport
2. someone invites you into component board
"this is the area you've basically already been helping with"
3. you see:
short description
tidy column of tasks
tickets labelled "good first internal task"
4. you pick a task
mark yourself "looking at this"
5. you post:
small updates as you go
link PR if code
or doc, draft, outreach list if not
expectations
you're not:
on hook for whole component
suddenly a manager
you are:
part of small crew
clear patch of garden to tend
ending or pausing
if life changes:
move to "away for now"
hand off context in short note
no drama, no demotion
just honest state
technical onboarding
sign in with GitLab via peaceful.foundation email
or GitHub integration
see what's assigned
coordinate with crew
training required
more functionality than Discord
but maps onto familiar patterns
voice calls → meeting rooms
struct uses same voice room concept
click to reach people via Passport
human resources → volunteer directory
social element of having ranked up
sense of progress
familiar environment
spent time on Discord first
learned project management process
structure persists across tools
implicitly understood
play around easier than raw entry
how Huly stays light
no performance dashboards
we show:
what's blocked
what's in flight
what's done
we don't show:
"top contributors"
"velocity per person"
anything that turns planning into competition
boards about work, not worth
visibility, not control
if board gets noisy or heavy:
split the component
or simplify flow
aim:
"can newcomer understand in 5 minutes?"
not:
"can we model everything perfectly?"
rooms and collaboration tools
meeting spaces
shared documents
far easier than Discord for focussed work
adaptable to different coordination needs
where it lives
Huly instance
organise.peacefulfoundation.org
protected behind Passport and staff-managed access
logins
tied to:
peacefulfoundation.org emails for staff
peaceful.foundation emails for formal volunteers, swans and cygnets
peaceful.network for linked accounts for invited hatchlings / others
prerequisites
email server running
hosting costs incurred
GitLab integration built
developers create this
merge request to Huly upstream if possible
Passport login modification
training materials
onboarding flow
then open for cygnets and above
the progression logic
Discord first
accessible
everyone has it
generalised tasks
social coordination
Huly when ready
formal planning
component-level work
cross-project visibility
technical integration
both coexist
Discord for:
entry
general tasks
social space
creative workflows
Huly for:
structured work
technical coordination
long-running projects
accountability without surveillance
##### Chad
Chad, can you look over the peaceful people section at the very bottom, at the end of the file, and then up a little bit, and then up a bit more, in the within the systems in there, it describes Chad. And because you're dealing with an infinite amount of different demographics and tasks for how people would help. I used the instance of the rubbish truck man who, yeah, that's more of a mm. There's the rubbish truck man example, but a sports teacher could teach kids breathing from their diaphragm, for instance., or walking more effectively as well, different things that they might,, might make them feel better., or, and these are collectively through,, all these things in Chad, we're discussing people's characteristics and yeah, it's deterministic building blocks to for,, you don't want to make it a personalised sort of list. You want it to be very people doing things together that all make a little a big difference. So,, it's all there. And other examples might be a science communicator explaining something of a massive list of different things that they could do the deep dive into, find a bunch of resources, put them in a bunch of,, for learnstuff.today or something, and then also, yeah, do the deep dive and then also make an explanation and and do however they want to sort of do it to, and do the the best job they can. And that's cool., but it doesn't even need to be the best job, people have preferences and whatnot, but,, yeah, we want to find a whole bunch of, yeah., or someone who has an internet connection can do certain things or people who have a car, or, but,, car is probably too generalised. So then you,, want to get a they're interested in,, or they want to help out with this and they have a car, then they can do that., but it's more so demographics and characteristics., yeah, it would be a, yeah, something they can do to help. I'd, yeah, talk a lot about the different demographics and how we sort of sort that and whatnot., there's there's a great deal and substantial amount of things that. So yeah., a firefighter., could keep their local community on fire watch for, hey,, let's watch out for any sort of,, any issues or problems as a whole. So there's that. Yeah. Or someone who knows how to repair bicycles., can, yeah., yeah, make a a tutorial on it or,, then with a flowing under current of resources, which we sort of touch earlier. If we do that afterwards, if we're explaining the flowing under current,, a little bit., but we probably wouldn't because we don't want to freak people out too much, but not even freak people out too much, but just,,, too much maybe. And that sort of saved isn't really mentioned much,, until the people section. So that if you'd gone through and started,, there's a lot, but people will summarise the whole thing, but given the fact that it's no its own project or something that, then it, yeah. Anyway. I digress.
a calm matching system between people-as-they-are and work-that-exists
peaceful.foundation
the problem it solves
Peaceful Foundation will grow fast
many people will arrive wanting to help
we will run out of defined tasks
human coordination becomes bottleneck
there are effectively infinite ways people could contribute
programmers: internationalisation, accessibility, polish, debate over implementation
artists: music for campaigns, then music for local flora/fauna, then tools for local artists
rubbish truck drivers: teaching basketball, creating guides for LearnStuff.Today
professors: voice lessons, explanations, curriculum
any demographic intersecting with any interest
we need to capture ideas and gaps immediately
turn them into actionable tasks
without central assignment
without running out of work
what Chad does
collects self-described state
skills
interests
physical location
demographics
availability
matches to work-that-exists
tasks
components
milestones
projects
through consensus mechanisms
people define what tasks fit which demographics
specifications are open and editable
best solutions emerge from weighted contribution
scales indefinitely
because it matches to demographic combinations
not to individuals
infinite intersects = infinite tasks
how it feels to use
first login
Peaceful Passport authentication
on-device tracking of demographics and interests
builds profile of who you are and what you could do
exploring work
browse by project
browse by task type
browse by what fits your profile
the to-do list
not generated automatically
emerges from your selections
components you join
tasks you pick up
milestones you commit to
working on something
pick up a defined task
tick it off
join a component
debate the specification
propose edits
consensus on best approach
sign-off from those with skin in the game
create something new
record an idea
define demographics needed
others refine and expand
the specification system
every component is editable
what it is
how it should work
what tasks comprise it
versioning through consensus
proposals
debate
descending versioning: best approach rises
not permission-based
weighted by contribution history
relevant badges
previous work on related components
examples
font synchronisation across devices
map file compression and distribution
better than IPFS alternatives
basketball teaching guide for LearnStuff.Today
Coordination is pull-based, not assignment-based
Instead of:
“You are responsible for this area”
It’s more like
“These things need doing here — who can help?”
People opt into tasks that match their
location
time
energy
1–2 hours/month
should only ever touch very local, very small things
5–10 hours/week
might naturally span multiple nearby hexes, temporarily
and if no one opts in?
That’s usable data and not a failure
and prevents artificial inflation of activity just to fill roles.
When someone’s availability changes
their role shrinks automatically without hassle.
the cultural shift
when someone is confused what to do
community response: "go talk to Chad"
personifies the system
makes it approachable
a bit of a meme
calm human assignment department
eventual end state
brings together all organisational systems
Huly components
GitLab issues
Discord nests
Passport contribution history
Hexagons location data
integrates all Peaceful Foundation tools
quiteasily
learnstuff.today
reasonable.diet
calm.college
hexagons.world
scalablecampaigns
tree diagram of entire system
infinite components
visible to all
navigable by anyone
nests emerge organically
people working on same component
same location
same demographic intersect
self-organising
not blocking
what Chad does not do
individualise to specific people
matches to demographic combinations
prioritise one person over another
optimise for throughput
enforce completion
escalate authority
create bottlenecks
technical notes
lives on peaceful.foundation
all data on-device where possible
consensus computed across network
open specifications
live editable
weighted by proven contribution
#### Knowledge
##### Documentation
docs.peacefulfoundation.org
###### Technical
###### Demographic
##### Policies
open source
same docs site, but rendered versions can be found on
peacefulfoundation.org/policies
##### Procedures
like, for example
we are gonna make it so that people need to do X
like git merge making little request thing
### Governance
how might we create an organisation that
core principle is to get out of the way
reducing and getting rid of power
Wrapped around all of this is the “no hierarchy, but not flat chaos” constraint.
#### Regions
Peaceful Foundation is a mesh of people acting locally, with geography used only to help them see each other, not to rule each other.
1. The unit is people + place + availability, not territory
The key move you’re already making is this:
No one “runs” a hexagon
People act from where they are, at the finest level they can realistically touch
So instead of:
“Germany coordinator”
“Berlin lead”
“Hex-X owner”
You get:
“Three people in this 1–10 km area who each do small things”
“Two students here who can host something once a month”
“One person who can do posters locally, another who can log data”
Territory never grants authority, activity does;
regionally, activity is always local.
2. Nested geography, but flat authority
You do want regions and countries — but only as aggregation layers, never as command layers
Think of it like this:
Hexes nest for visibility
People stay flat for power
So:
Fine-grained hexes are where action happens
Larger hexes just summarise what’s happening underneath
A country view answers:
“What’s going on here, broadly?”
It does not answer:
“Who’s in charge?”
This keeps things legible without creating ladders.
6. Regions coordinate between, not over
Regional or country-level coordination exists only to:
notice patterns
share what’s working
connect people across nearby areas when useful
Never to:
approve
command
gatekeep
prioritise one place over another
They’re connective tissue, not skeleton.
##### Peaceful Foundation in Australia
##### Peaceful Foundation in other countries
###### Governance
###### Undertaking activities
#### peacefulfoundation.org
##### peacefulfoundation.org/governance
###### Decisions
###### Conflicts of interest
register
##### peacefulfoundation.org/strategy
##### peacefulfoundation.org/legit
#### Technical
##### Infrastructure
###### Domains
{peaceful.network} chat and stuff
###### Peaceful.foundation
infrastructure
###### Peacefulfoundation.org
governance and organisation
###### Analytics
###### Status
##### Access and security
##### Maintainers
// technical governance
three people per project
##### Guidance
don't call people "users"
#### Human
always call people, people.
##### Hiring
Hire people better than yourself.
no ego
##### Focus
one focus
do what you think is best
##### Travel
as long as is comfy
obvs we prefer train where possible
but until there is blimps we'll probably need to use planes
stare in wonder at the machinary
so many people came together to make this
not going to offset
what the heck is offset
point being is that offsetting is greenwash-able
instead we will just keep doing peaceful foundation
ideally we don't want travel to be a stressful time
like, it has to happen
like, working on the plane isn't ideal
we don't really want deadlines when you land
how we would book travel
go through a travel agent
##### Relationships
such as media
such as outreach
#### Legal
##### Obligations
the main thing is simply tracking our legal obligations
paralegals can volunteer
tell us the legislation
lawyers can volunteer
tell us ways of responding
legal.peacefulfoundation.org
again, this is open source.
##### Legal structure
described in money
###### Deductable gift recipients
#### Financial
not giving people money directly
##### Financial controls
##### Overseas
sending money overseas
wise
or in rare cases, paypal.
###### Uses
###### Recipients
// businesses and supermarkets
// later, co-operatives
##### Financial reporting
really rather good transparency
open source layers of financial reporting
#### Transparency
##### Records
##### Reporting
could we even do live?
###### peacefulfoundation.org/log
#### Privacy
passport.peaceful.foundation/privacy
#### Opsec
never have anything on you
security
remote
assume all devices are breached at all times
grapheneos
openbsd
tailscale
#### Operating overseas
“digital availability overseas”
free websites, open resources, public guides, maps, and educational tools accessible globally
“overseas volunteers”
people outside Australia helping translate, share, contribute, test, or organise local actions
“overseas expenditure”
any money, grants, supplies, reimbursements, or support sent outside Australia
“overseas partners”
any organisation, university, community group, NGO, supplier, or local organiser receiving funds or formal support
##### Checking partners or recipients
For Peaceful Foundation, partner checks could be proportional. You do not need a war-room dossier for someone printing $30 of posters. But you do need a system.
For low-risk, low-value support: identity/contact check, purpose check, receipt requirement, public or internal record.
For moderate support: written agreement, budget, basic sanctions/fraud check, conflict-of-interest declaration, evidence of delivery.
For higher-risk support: board approval, partner due diligence, references or public record, safeguarding review, anti-fraud controls, staged payments, written reporting.
The quiet principle: trust people, but don’t make the bank account run on vibes.
###### Reducing supply chains through generalising
each place is different
but the supply chain for many people can be simple
like cooperatives
assisting communities in creating cooperatives
we've already defined them (supply chains) that they're transparent
one example would be reasonable.diet university campus food things
and then one person is able to propose to community
but someone notices that there's related party
since the supply chain is transparent
takes one person to anonymously sound alarm
overall is just better if one big cooperative
###### Working with overseas organisations
##### Safeguarding people when operating overseas
// for example, we don't have the exact same kind of stringent working with children check things
// we can ask for police clearances with authentication
// but in reality it's better doing design like inducting parents
// peaceful foundation not running event governance
// where we are, semi-structured environments like uni
##### Preventing subpar standards
like bribery and corruption
instead, coming from the sides and better methodologies
funds being transparent and not needing bribes
corruption being difficult to happen through both transparency and norms
### How impactful might this be?How impactful might this be?How impactful might this be?How impactful might this be?