How_to_Build_a_Commons/HowToBuildACommonsWorkbooks
2
0
Fork 1
mirror of https://github.com/How-To-Build-a-Commons/HowToBuildACommonsWorkbooks.git synced 2026-04-19 16:51:04 +00:00
Code Issues Projects 1 Releases Packages Activity

formatting

Browse source
This commit is contained in:
Kevin Harrington 2025-10-19 10:38:58 -04:00
parent 3e990b0780
commit 7ffb116374
1 changed files with 5 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

7
ScopeSequencing.tex
View file

@ -152,6 +152,7 @@ A commons can be managed in a very large variety of ways. Members create the rul
Lets review some design principals used by commons across the world for stable commons. These principals were derived by Ostrum from a datasets of commons that have been operating for at least 200 years. Lets review some design principals used by commons across the world for stable commons. These principals were derived by Ostrum from a datasets of commons that have been operating for at least 200 years.
"
\begin{enumerate} \begin{enumerate}
\item {Clearly defined boundaries} \item {Clearly defined boundaries}
@ -195,6 +196,8 @@ For commons that are parts of larger systems:
Appropriation, provision, monitoring, enforcement, conflict resolution, and governance activities are organized in multiple layers of nested enterprises. Appropriation, provision, monitoring, enforcement, conflict resolution, and governance activities are organized in multiple layers of nested enterprises.
"\footnote{"Ostrum p90"}
\end{enumerate} \end{enumerate}
\vspace{0.2cm} \vspace{0.2cm}
Always remember that building a common is a step-by-step process. You will start with whatever resources and rules you have, and add to the framework over time. The whole idea is to have the rules reflect the needs of the members of the commons. We are all screw-ups some times, and that is ok! We can always evolve our systems over time and bring them in line with our shared values. Always remember that building a common is a step-by-step process. You will start with whatever resources and rules you have, and add to the framework over time. The whole idea is to have the rules reflect the needs of the members of the commons. We are all screw-ups some times, and that is ok! We can always evolve our systems over time and bring them in line with our shared values.
@ -303,7 +306,7 @@ Within a Commons, once the external entity has been assigned Private Property ri
\begin{minipage}[t]{0.72\textwidth} \begin{minipage}[t]{0.66\textwidth}
\vspace{0pt} \vspace{0pt}
"In a typical village, the only people likely to pay cash were passing "In a typical village, the only people likely to pay cash were passing
travelers, and those considered riff-raff: paupers and ne'er-do-wells so travelers, and those considered riff-raff: paupers and ne'er-do-wells so
@ -332,7 +335,7 @@ Within a Commons, once the external entity has been assigned Private Property ri
%This generates the check %This generates the check
\end{minipage}% \end{minipage}%
\vspace{0.2cm} \vspace{0.2cm}
\begin{minipage}[t]{0.25\textwidth} \begin{minipage}[t]{0.33\textwidth}
\vspace{0pt} \vspace{0pt}
\centering \centering
\begin{turn}{90} \begin{turn}{90}