0.2 How the handbook works
Summary
The handbook explains durable concepts and guidance; live records hold current responsibilities and work. Numbered sections help you locate a topic, and status labels show whether material is adopted, proposed, or still being drafted. Editing or publishing a page does not adopt a policy.
0.2.1 Chapters, sections, subsections, and appendices
The handbook supports continuous training through six chapters: 0 Start here, 1 DNA, 2 Go deeper, 3 Lead, 4 Train others, and 5 Supplemental. Appendices A–E hold reference materials, further reading, citations, the glossary, and staff guidance. Start with DNA, then choose a deeper module, a leadership practice, or a training skill as your work calls for it.
Numbers show where a topic sits. 0 identifies this chapter; 0.2 identifies this section; 0.2.1 identifies this subsection. Appendix numbering follows the same pattern, such as A.1.2.
A chapter landing page summarizes the chapter and links to its sections. A section usually has its own page, with named subsections inside it. Each page has a Summary, a status, and a last-updated date. Summary and source lists are page elements, not extra numbered sections. The contents below read status directly from each page. Hover over a status symbol to see any note about unfinished material.
0.2.2 Beliefs, current practice, proposals, and open questions
Beliefs explain our outlook. They describe the reasoning and values behind our work. A belief alone does not establish a process, assign authority, or approve a new requirement.
Status shows adoption. An adopted page describes established guidance. Draft pages are unfinished material for review; proposal pages describe possible future practice; experimental pages describe trials; reference pages provide supporting material. Planned pages are outlines for future modules, awaiting review before content is filled in. Read the page's status and any qualifications before treating an instruction as settled. The status legend in the contents also distinguishes reference material from adopted guidance: both use ✅, with their full status on hover.
Labels show what isn't settled. A Proposal block describes a possible practice, with a dashed border so it can't be mistaken for current practice. A page that is still being written shows an Under construction banner at the top saying what is missing; read it as a starting point, not settled guidance. Publishing a page does not change decision rights or adopt its recommendations. Some practices are already in use; others are still taking shape as we prepare for more people to join.
0.2.3 Where authoritative information lives
Information lives in three places:
| Information | Where to look |
|---|---|
| Durable definitions, expectations, and repeatable guides | The handbook, checking page status |
| Current roles, owners, governance, priorities, and work | Atlas or live records linked from it |
| Current policy recommendations and campaign materials | The relevant Sapiens First website pages, including campaigns |
The handbook explains; Atlas records. The handbook covers our shared concepts, expectations, and practices. Atlas is the source of truth for current governance, work, priorities, and owners.
| The handbook tells you… | Atlas tells you… |
|---|---|
| What a role means | Who holds it now |
| How to plan a project | Which projects are live, and their records |
| How decisions get made | Who currently decides what |
Source of truth
Atlas holds current roles, circles, projects, priorities, and owners. This handbook explains the concepts, expectations, and practices behind them.
For example, the handbook can explain a role; Atlas records who holds it now. An empty or unclear record does not imply that a decision has been made. Ask the relevant role holder when a current assignment or record is unclear.
0.2.4 How to suggest changes
If wording is confusing or information seems outdated, tell the person responsible for that area or suggest an edit. Identify the page, explain the problem, and include a source or proposed wording when you can. Repository contributors can follow the contributor guide.
Keep a factual correction or editorial change distinct from a proposed organizational decision. When suggesting a new rule, show what needs agreement and preserve its proposal status until the appropriate decision has been made.
0.2.5 Find anything
Common questions, routed to the page, or the Atlas record, that answers them. The handbook explains how things work; Atlas holds who is doing what right now. Can't find your question? Try the search box or the Glossary.
Choose a starting point.
- 0.1 Welcome to Sapiens First — What Sapiens First is and who the handbook serves.
- 1.1 Story — What Sapiens First is and why the AI Crisis matters.
- 1.2 Strategy and 1.3 Culture — Theory of change, values, and pathways to action.
- 0.3 Getting involved — First steps, the Fellowship, and where to start as an organizer.
I want to know…
Where staff should start → E.1 Expectations and E.0 Beliefs about staff.
Where compensation is explained → E.2 Compensation
What Sapiens First is trying to accomplish → 1.1 Story and 1.2 Strategy
Our theory of change, and how we think we'll win → 1.2.1 Our theory of change
How membership and participation work → 1.4.4 Participation, responsibility, and employment
How the Fellowship works, and how many hours it takes → What to expect — Fellows aim for 5–10 hours a week.
What the Fellowship agreement says → Sapiens First Fellowship Agreement
Who is currently responsible for something → Atlas: current roles and role holders.
What projects are active right now → Atlas: current projects.
How decisions get made, and who decides what → 1.4.2 Roles, circles, accountabilities, and decision rights
How to propose or start a new project → 3.2.5 Project portfolio management
How to hand off a project when you're finishing → 3.2.6 Project execution and handoffs
How objectives and key results work → 3.2.2 Objectives and key results (OKRs)
How Sapiens First defines a metric → 3.2.3 Metrics
The difference between inputs, outputs, and outcomes → 3.2.3 Metrics
What we currently measure, and what our metrics show → Atlas: current objectives and metric values.
How to review metrics with a circle → 3.2.7 Reviewing performance of the strategy
How weekly planning works, and how to write a task that is actually actionable → 3.2.6 Project execution and handoffs
How to run a check-in, update, or general meeting → 3.4 Facilitation
How to start a local circle, or a chapter → A.2.8 Starting a local circle and 1.4.5 Local circles and movement growth — every local group starts as a circle; chapter criteria aren't adopted yet.
What circles currently exist, and where → Atlas: current circles.
How to run a gathering, or plan a peaceful action → A.2.6 Running gatherings and A.2.7 Planning peaceful actions
How to have an organizing conversation → A.2.10 Having organizing conversations and 3.3.1 The Organizer Conversation
How to train other organizers → 4 Train others — planned modules — and A.2.9 Training organizers
Our values, and the red lines nobody may cross → 1.3.1 Core values and 1.3.3 Behavioral commitments and red lines
How to give useful feedback, or grow through responsibility → 3.1.1 Feedback culture and 3.3.4 Supporting growth
A copyable template for a scope, plan, update, or handoff → A.2.1 Planning templates
What a specific term means → D Glossary
How roles and circles relate, and how to read one in Atlas → 1.4.2 Roles, circles, accountabilities, and decision rights
How the handbook and Atlas relate to each other → 0.2.3 Where authoritative information lives
Which pages describe settled practice, and which are proposals → 0.2.2 Beliefs, current practice, proposals, and open questions
Who to contact about a values or red-line concern → 1.3.3 Behavioral commitments and red lines