How do places build the
capacity to learn together?
Start with an organizing network and the programme it runs. Then follow one documented case of workshop experience moving from one place to another — a workshop held in Whatcom, and a debrief of it discussed on Vashon eight days later. Then the practical question neither account settles: who keeps the shared information alive afterwards.
Source-linked accounts from the network and participating groups. Our Victoria workshop proposal is labelled where it appears. Follow the workshop-to-commons learning cycle.
Landscape groups and their network
Explore the groups in the current directory and the programme that supports their learning.
loading the collection…
The relationships, as the sources state them
Relationships to investigate
Landscape stewards named on the public group page
Published stewardship roles, with links to the group’s own account.
Sources for this step
Workshop learning shared between places
Follow a workshop debrief from Whatcom into Vashon’s planning.
Whatcom held a mapping workshop on July 17. Vashon met on July 25, discussed a debrief of that workshop, and published its own account on July 26. Whatcom's organizer published a write-up on July 31 — after Vashon's account, so what travelled was a debrief, person to person, not a published article. Two separate accounts, from two places, with one thread running between them.
The accounts describe a workshop debrief informing another group’s planning. Step 5 explores how a shared note could make that learning easier to revisit and adapt.
Sources for this step
Who keeps the shared information alive?
A workshop ends. Somebody has to hold what came out of it. Who, and for how long, and paid by whom?
Vashon’s account raises this practical question through the example of an earlier newsletter ending. A maintained commons needs an agreed role, time and resources between gatherings.
Sources for this step
What we propose for a Victoria workshop
If the return trip is the fragile part, what would we actually commit to returning?
Our proposal: participants notice and interpret together, correct their representation, and choose what to share. A steward tends the resulting questions, offers, needs and source-linked accounts in the knowledge commons. Agreed work and later observations return as revised knowledge. Witnessing, objection and refusal remain available.
Try the six-step walkthroughWhat we are reasoning from
These three lines run from a documented record to our proposal. The record at each start is sourced; the line itself is ours, and is an argument rather than a finding.
How knowledge could travel between commons
Step 2 is social learning: a person described a workshop to other people, and they acted on it. Nothing was federated between two commons, and the exchange demonstrated below did not carry it. Whether any software was involved along the way — a message, a shared document — the two accounts do not say, and neither does this page.
There is a separate demonstration on this site of the other thing — a practice note offered by one commons to another over KOI-net, held for review, and accepted or rejected locally. It is a rehearsal between two synthetic nodes built for the demonstration. It did not carry the Whatcom-to-Vashon exchange, and neither Whatcom nor Vashon took part in it.
Sources and acquisition dates
Follow each account to its original publication. Directory and programme updates are dated separately from the workshop accounts.