Samara Archives
- Welcome Samarians
- START HERE
- Status of the Chronicles
- How to Edit Pages
- How to Embed Media
- How to Structure Content
- How to Print Content
- Samara CSS
- What Has Worked so far and What we would do Differently
- Archived: Stroll in the Forest, SCARF, Hero's Journey
Welcome Samarians
This chapter is temporary and will be removed before the book is published
START HERE
Welcome Samarians!
Welcome fellow intrepid Authors! Let's write a book together!! :)
If you're editing already or ready to copy into a page watch this 3min overview first!
Just as in SEEDS it will make it much easier and give you context to go through all sections of this section of the wiki and the full introduction below as soon as you can ;)
Here's a quick intro to the Wiki.. enjoy!
Status of the Chronicles
The Chronicles of Samara are co-created directly inside this wiki space, every participants will get Editor rights and can work on separate pages.
Assigns
PG=Page, CH=Chapter
Order/synthesis of structure: Dmitriy, Joachim, Bongi
Cover: Joachim
PG: Preface: Identity Pod (Roz, Alan, Dmitriy, Trent)
PG: Dedication: Identity Pod (Roz, Alan, Dmitriy, Trent)
PG: Who this book is for: Joachim & Bongi.
PG: How to use this book: Joachim & Bongi
CH: Enter the World of Samara: Identity Pod (Roz, Alan, Dmitriy, Trent)
CH: Samara’s Stories : YOU :slight_smile: (All Quest) to add own pages (perhaps from individual boards in Miro). [If on Monday not everyone has added or perhaps these pages are not cohesive, we can set aside to put in v2.0]
PG: What Has Worked so far and What we would do Differently: YOU :slight_smile: (All Quest)
CH: Grow the Roots: Game Guide Primary Pod + Joachim
CH: Strengthen the Trunk: Justin
CH: Sprout the Branches
PG: What is a Pilot Project: Local Pilots Primary Pod (Drigo, Jared, Fabi, Sven)
PG: Relationship with Hypha Movement Building Circle (MBC): Tyler
PG: Our Current Pilot Support: Local Pilots Primary Pod (Drigo, Jared, Fabi, Sven)
PG: Tools and Technology: Joachim and Bongi
CH: Future Flowers and Seeds: Alan + Joachim + Irina + Bongi+ Tyler
Epilogue: Bongi + Joachim
Glossary: Any & All Editors
Reference: Trent
About the Authors: Alan + Bongi
Activities
Activity | Lead | Status | Comments |
Install BookStack Wiki on Cloudron | Joachim | Done | |
Register and invite all participants to Cloudron | Bongi | Done | Use Cloudron credentials |
Adjust and confirm the structure of the outline | Bongi: Some changes but big ones abandoned - finishing + editing needed most | Done | Via Miro Board |
Divvy up the work among all participants for each chapter | Irina | Open | Via Miro Board |
Launch hackathon and write, rewrite, cowrite, embed artifacts | All | Open | Artifacts from anyone |
Do a periodic group review and decide on status | Bongi: propose Thursday formal move to review in Trunk | Open | |
Do an editorial review and final approval | Bongi: propose Friday formal move to editing + final approval Monday | Open | UK vs US grammar and spelling rules, footnotes and ref notes, e.g. [Str2020] |
Update wiki formatting (fonts, colors, chapter icons) | Joachim | In Progress | Via Wiki Settings |
Deliver the wiki as PDF and/or epub for the TD call | Joachim | In Progress | Via https://convertio.co/ |
The best way to catch up on all the writing is from the left side "Recent Activity" here (click on the "Game Guide" breadcrumb thingy in the middle). As an admin you can also access the audit log below showing all edits ever done in the wiki.
Wiki Settings
- Public access to all pages (so we can share content without logging in)
- Editor access only via Cloudron accounts (so we know who can edit)
- Enable Comments (for quick feedback on content)
- WYSIWYG Editor enabled (we can switch to markdown if desired)
- Styling partially applied (font-size 1.1em, font-family: Cabin Sketch (for headings) and Open Sans)
Links
- Hypha Handbook (Rieki)
- Valve Handbook (Valve)
- Enspiral Handbook
- GitLab Handbook
- Notepad (Joachim)
- Miro Board (Paulo)
- Miro Board (Irena)
- Mural Board (Sanjay) - Hexagon Purpose Grid
- Google Slides Samara Starter Kit (Joachim)
- Google Slides Background Material (Joachim)
How to Edit Pages
Anyone with Editor
rights can create a new page or edit an existing page in this wiki.
Click on the Edit button on the right to edit the page. If you do not see the Edit button, you are probably not logged in. If you need an Cloudron account to log in, please contact Joachim.
Important: This is a co-creation space, so others will be able to review and edit your content. If you see this warning:
XYZ started editing in the last 60minutes and to be careful not to overwrite each others updates.
Do not edit the page and come back later (or contact the person currently editing the page). Otherwise your edits might be overwritten by the person who saves it last. For those currently editing pages, please save them as soon as you are done and don't leave them open (in a draft mode).
To leave any comments on the page, just mention them as italics on the page with your initials - JS
To update the Editorial status of a page, edit the page and click on the tag button (top right , see below) and type in one of the follwoing:
- created = new page, all edits welcome
- drafted = needs improvement
- completed = needs editorial review
- approved = ready for publishing
Then we can search for all of them using this query [=drafted] (for drafts) - click here to see this in action - https://guide.hypha.earth/search?term=%5B%3Ddrafted%5D
To sort pages into a different order, go back to the book or chapter view and click on the "Sort" button on the right. This will allow you to rearrange all chapters or pages in a new order. Don't forget to save the order (Click on the Save Order button at the very bottom of the form).
To track any revisions of your page (done by you or others), click on the "Revisions" link on the right of the page. You will see a screen like the one below, click on any entry to see what has changed on the page (text highlighted in red=removed, green=updated). If you restore a previous version, you will loose the edits between the current and the restored version.
To add some additional highlights to pages, use the following under Formats > Callouts or Blockquotes:
Everyone is good to go.
There is some danger using this technique!
This is some more information..
This is an important message
This is an important quote that helps to underline the text. This is an important quote that helps to underline the text. This is an important quote that helps to underline the text. This is an important quote that helps to underline the text. " -Fuller
To add structure to pages, see the dropdown in the editor called Formats and the sample below. Once you assign different headings, they will structure the content of the page and allow you to use a page navigation tool (on the left below). Don't worry about the formatting of the headers for now, we can change this for all pages in the Custom HTML Head Content section.
For more help, please visit the BookStack help documentation.
How to Embed Media
If you like to embed media assets on your page, edit this page, then click on one of the media assets and the Insert/edit Media button on the toolbar. Copy/paste the content of the Embed tab, open your page and insert your media asset with this code.
<iframe title="Notepad"
style="width: 100%; height: 450px;" // use 508px for docs
src="YOUR URL GOES HERE" >
</iframe>
How to Structure Content
Miro Board
Notepad
How to Print Content
Prepping
- The TOC is generated automatically by BookStack but is placed in front. Hence you need to copy and paste that content into a new page after the cover page. All links will be preserved in the process.
Printing
- In the wiki, go to the full page structure at https://guide.hypha.earth/books/the-chronicles-of-samara
- Click on Export on the right and select Contained Web File.html (this wil download an XHTML file)
- Open the file in Chrome
- Print the file and save as PDF (start with the cover page)
- Convert the XHTML into MOBI or ePUB or other formats at https://convertio.co/
Samara CSS
<!-- -->
<!-- PLEASE DON'T EDIT THIS FILE -->
<!-- CONTACT JOACHIM STROH FOR EDITS -->
<!-- -->
<link rel="preconnect" href="https://fonts.gstatic.com">
<link href="https://fonts.googleapis.com/css2?family=Amatic+SC&family=Cabin+Sketch:wght@700&family=Open+Sans&display=swap" rel="stylesheet">
<!-- script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script -->
<style>
table { font-size: 0.8em; width: 80% !important; background-color: #f8f8f8; }
table, td, th { border: 0px !important; padding: 10px !important; }
tr:nth-child(even) { background-color: #f2f2f2; }
.content-wrap h1, .content-wrap h2 { font-family: 'Cabin Sketch', cursive; /* use Amatic SC or Cabin Sketch */ }
.content-wrap h1 { font-size: 3.2em; margin-top: 1em !important; }
.content-wrap h2 { font-size: 2.1em; margin-top: 1em !important; }
.content-wrap h3 { font-size: 1.2em; }
.content-wrap h4 { font-size: 1.1em; }
.content-wrap h5 { font-size: 1em; }
.content-wrap a { color: #ff9900; } /* FED83D */
.CodeMirror, pre, #markdown-editor-input, .editor-toolbar, .code-base {
font-family: monospace;
}
@media print {
body, button, input, select, label, textarea { font-size: 0.7em; }
.page-content { column-count: 2; column-gap: 30px; column-rule: 1px solid gray; }
.cover, #bkmrk-page-title, h1 { column-span: all; page-break-after: always !important; break-before: always !important;}
h1 {margin-top: 1em !important;}
iframe { display: none; }
table { font-size: 0.6em; width: 80% !important; background-color: #f8f8f8; }
table, td, th { border: 0px !important; padding: 10px !important; }
tr:nth-child(even) { background-color: #f2f2f2; }
body { margin: 5%;}
h1[id^="chapter-"] { margin-top: 3em; font-size: 6em;}
h1[id^="page-5"] { display: none;}
p.cover img {width: 100%; object-fit: cover; column-span: all; page-break-after: always !important; break-before: always !important;}
}
</style>
What Has Worked so far and What we would do Differently
To be Archived for now.
Assigned: all Samara for input (deadline Friday) + Joachim for editorial review
Irina: Reconsidering if we are ready for this chapter now. Feel that Samara needs to go through some further reflections to come with a collective assessment of what worked and what didn't. Happy to leave this out for now.
Roz: Agree with Irina. Would like to build a habit of Retrospectives after key milestones, in order to build a continuous learning culture. A Retrospective at the end of our first Quest (and hence at the end of producing the Chronicle) would be appropriate, and the right time to address these questions.
Tyler: agreed ^.
Name:
Worked:
Do differently:
Name:
Worked:
Do differently:
Name:
Worked:
Do differently:
Irina: <3
Worked: The daily call with Rieki to build Samara foundations
Do differently: Create a clear purpose for each call
Worked: Trios for co-creation
Do differently: Clear structure for collective calls
Worked: Trusting that the right people will come
Do differently: Think twice before starting a startup with strangers from around the world :)
Worked: Creating gardens for knowledge
Do differently: Use Discord for chat and not more
Worked: Starting the work for Samara in winter time (no gardening activities)
Do differently: Make sure people are committed for a good amount of time before starting
Bongi:
Worked: Agreed minimal governance proposal.
Do Differently: Start and establish a v1.0:
- Which anyone can propose to evolve
- With very high participation required right at the beginning
- Sociocratic principles and distributed authority training/requirements and distinctions
Worked: Open meetings and deep exploration that fostered initial human connection. 1:1 that followed to enhance this.
Do Differently: Have more 1:1's at the beginning when the open time and initial connections are forming. Have that lead into revealing purpose very early on.
Worked: Quest proposal for Hypha.
Do Differently: Start it much sooner once clarity and definition of purpose is agreed to.
Worked: Working in focus groups of 3 and then shifting to 4 for starting work. Growing/ taking to larger group as topic/proposal/work material evolved.
Do Differently: Schedule rare ceremonial meetings for everyone (all sub groups) in org to attend. Schedule human/process/action meetings. Breakout rooms to check in personally with max 3 people. Do this at the end of any arduous cycle and have it flexibly scheduled very early on to anchor the coming together in a clear, anticipated and meaningful way.
Joachim: <3
Worked: Define some simple ground rules, then just do it
Do differently: Don't discuss rules and make them overly complex
Worked: Put trust at the front and center of what we do (trust people & process)
Do differently: Be overly skeptical to new approaches
Worked: Free flow of conversations
Do differently: Anchor conversations early on in principles and purpose
Worked: Zoom meetings (which comes at a cost)
Do differently: The asynchronous space in-between Zoom meetings
Worked: Diverge, then converge (be inclusive, listen to all voices)
Do differently: Converge, then diverge (be rigid, remove unneeded or unnecessary voices)
Archived: Stroll in the Forest, SCARF, Hero's Journey
Walk in forest:
In fact, the very idea for this book started with a gentle stroll through a forest, a virtual forest that is..
(click on the image to enter the forest and contact a Samarian if you want some company!)
As stewards of this forest we are seeking, (just like you are seeking in your stewardship in many areas) to nurture and learn in a way which supports a diverse and dynamic environment. May this environment serve multiple needs on multiple levels, but particularly the regenerative needs for growth and contribution, so that we can manifest the purpose that holds us together.
Like any good book (story, journey, cycle, creation), this is one that speaks of the Hero's Journey in each of us. It's about a beginning which calls us to act, the finding of a tribe, the meeting with a mentor, the inspiration to climb and the willingness to commit to going through the cave together to emerge into something new.
This journey is very new for Samara (ns), but already this universal pattern is playing out and the journey has fundamentally changed each individual who has stepped into it. The something new is emerging and we want you to walk through and out of the cave beside us into another dawn, familiar, but alive and new.
Inevitably diversity implies a greater variety of different points of view and this is a fundamental dynamic in any group, let alone those that seek to decentralize control, decisions and power and distribute authority. No story would be complete without seeing all the stages in a cycle and no D-HERO can realize their gifts and identity without every feature of a complete journey.
SCARF, Hero/Heroine's journey and other models: Synergy with SEEDS as part of org DNA.
There is recent talk about taking inspiration from the SCARF model (Status, Certainty, Autonomy, Relatedness, Fairness). Aims:
- Create processes on a group level that prevent or reduce a threat response in the individual.
- (Outside in change: external 3rd person change > Individual 2nd & 1st person internal change > org wide internal change)
- Agree standard learning processes specifically for higher/lower threat scan results; to help members grow and gain more insight as a result of tensions.
- (Inside out change: Internal Individual 1st person change > Internal Group 2nd person change > external 3rd person learning recorded)
The Heroine's/Hero's Journey could be used to judge the right time to use different tools and methods. At the same time it could help Samarans to sense into and align around the stages we are going through. It could help members and different sub-groups to respond with awareness and acceptance of appropriate co-created, agreed game rules for each stage.
The hero/heroine's journeys are easy to see as just another model or methodology.
There is a fundamental difference, however, between these two types of modelling:
- A model that is formed to be applied to a specific set of circumstances or contexts. We see this with multiple highly effective models designed for a purpose. Some of these are widely applicable, but still 'outside-in' formulated.
- A model which is identified and refined from a deeply embedded, pervasive and longstanding pattern that already defines behavior and perception. These 'mono-myths' are just that. These journey descriptions and phases describe the most basic cycles humans go through and how the subconscious parts of our system perceives learning and success.
The Hero/Heroine's Journey is an Emergent model. It has an ideal use case: determining how and when to use other models, tools, processes and cultural values. Checking what is happening in this way (which builds on Hypha's 'org scan' process), would channel rhythms dynamically to create safety or many other desired regenerative organisational 'states'.
This dynamic way of adjusting rhythm:
- Still gives structure and direction
- Explicitly encourages a sense-and-respond process
- Could prove useful in allowing flexible, yet fundamentally patterned tools for new DHO's.
It is interesting to reflect on this and see that Hypha seems to have more of a masculine cycle, at least with their focus on building and launching tools and services. Samara has created a much more feminine space for emergence and quality. Obviously any organization must balance masculine and feminine in order to both sense and act in balance. An organization which is too stuck in action is missing opportunities and growth and an organisation too focused on sensing may be too slow or ineffective. Some DHO's will need to be primarily more masculine or feminine in quality depending on their purpose and activities.
It would also be possible to combine these dynamic methods with some of the regenerative and thrive-ability patterns named in the SEEDS Constitution. The Constitution Part 1 is a compass, which is already used by many to navigate and actualize within the game of SEEDS.
For example, the three principles of life (article 3 of the Constitution) relates to the expansion and contraction mentioned above in Samara. These are held and nurtured by the 4 suns (external) and 4 moons (inward) - which make the 8 values.
"ARTICLE 3 - PRINCIPLES OF LIFE 3.0
This Constitution is our compass for guiding how SEEDS grows, develops, and evolves in harmony with the evolutionary process of life, based on three essential life principles:
3.1 We acknowledge how our universe exists and evolves as a single unified entity, an undividable wholeness. The universe is a single being.
3.1.1 This evolutionary principle helps us understand how we each form part of that wholeness and how to design and relate from this wholeness.
3.2 We acknowledge how our universe evolves coherently and is finely tuned to make life possible. The universe evolves through deepening coherence and increasing complexity.
3.2.1 This evolutionary principle guides us how to evolve and embody complexity in a way that is coherent with the wisdom of life, to finely tune our systems to become more generative (as opposed to the degenerative growth of dominating systems).
3.3 We acknowledge our universe as an expression of consciousness, a continual learning journey of discovery through which we develop our capacities to thrive together. We actualize our consciousness by learning, experimenting, collaborating, and sharing together.
3.3.1 This evolutionary principle reminds us to honour systemic autonomy and autopoiesis (self-creation, regulation and adaptation) in the way we grow, expand and evolve this Renaissance as a consciousness increasing process."
A final question: how would this apply in a more outreach/seeds spreading facing org like Samara, which does not primarily focus on building tools like Hypha?
There are potential synergies here for collaboration with the Movement Building Circle within Hypha. Samara and MBC could be synergised in a way which links directly to the SEEDS constitution, while uniquely applying this synergy to their own context.
Consider the huge wave of organisational change on the horizon.
Consider unknown numbers of DHO's predicted to form very soon within the SEEDS ecosystem.
We have used the analogy of new DHO's forming as in the mitosis of cells. The forming of a new cell retains almost all of the original DNA. Is that the case here?
With numerous wildly differing DHO's forming and evolving their own DNA, what ties them all together? The ecosystem does in some ways. The origins do in others. How do we foster flexibility and a fundamental cohesiveness in the structural and operational realities across the network? How do we cohere our rhythms with something fundamental across the network and encourage a free and unique expression in each case?