Appendix B — Example Artifacts (Non-Normative)

This appendix provides illustrative examples of artifacts referenced in the specification.
Examples are informative only and should not be treated as required formats or implementations.

B.1 Example Purpose Charter (Excerpt)

• Primary purpose (singular): “Maintain and steward a shared, regenerative living place that provides stable housing and ecological restoration.”
• Secondary purposes (bounded):
  • “Operate a small educational program on regenerative practices.”
  • “Run a member-owned cooperative for local food production.”
• Non-goals / exclusions:
  • “Not a political party.”
  • “Not a short-term project collective.”
  • “Not a for-profit real estate vehicle.”
• Conditions for purpose change:
  • “Purpose changes require a constitutional decision and full re-ratification.”
• Ratification record:
  • Adopted: 2026-01-01
  • Decision type: Constitutional
  • Version: 0.3
  • Decision record link: [placeholder]

B.2 Example Scope Declaration (Excerpt)

• In-scope assets:
  • Land parcel “North Field”
  • Buildings: “Common House”, “Workshop”
  • Shared funds: operating treasury, reserve fund
  • Shared infrastructure: water system, solar array, shared vehicles
• In-scope authority domains:
  • Governance rules and decision process (Layer 2)
  • Membership rules and states (Layer 1)
  • Treasury and shared resource allocation (Layer 3)
  • Operational coordination for shared work (Layer 5)
• Out-of-scope domains:
  • Personal income, private debt, and private bank accounts
  • Private relationships and private living spaces (except safety-critical conditions)
  • Off-site businesses not using community assets

B.3 Example Decision Matrix (Excerpt)

B.4 Example Internal Economy Protocol (Excerpt)

• Recognized contribution categories:
  • Labor (maintenance, construction, food production)
  • Care (childcare, elder care, conflict support)
  • Knowledge (training, documentation, facilitation)
  • Stewardship (resource maintenance, procurement oversight)
• Recording mechanism:
  • Weekly contribution log submitted by members
  • Monthly review by the Operations Circle for consistency and corrections
• Internal units (optional):
  • “Time credits” tracked in hours for certain shared allocations
• Accumulation constraints (if internal units exist):
  • Caps on balance
  • Expiration after 12 months unless renewed by review
• Dispute and correction:
  • Any member may request review of a record within 30 days
  • Corrections require documented rationale and are logged in a change history

B.5 Example Conflict Resolution Ladder (Excerpt)

1. Direct conversation (informal repair)
2. Facilitated mediation (neutral facilitator selected from an approved list)
3. Accountability intake (documented intake; anti-retaliation safeguards activated)
4. Accountability review (findings, repair plan, and proportional responses)
5. Governance decision (if authority, access, or roles must change)
6. Separation process (if required; coordinated with Layer 1 exit and separation protocol)

B.6 Example Change Proposal Template (Excerpt)

• Change title:
• Summary (1–3 sentences):
• Affected layers and artifacts (links):
• Change type:
  • Permanent change / Experiment
• Decision type and authorized decision path (Decision Matrix reference):
• Rationale:
• Risks and mitigations:
• Transition and migration plan:
• Rollback plan and rollback triggers:
• Effective date and review date:

B.7 Example Membership Agreement (Excerpt)

• Membership state on signing: Trial / Full
• Member rights (examples):
  • Access to the decision records defined as transparent
  • Participation rights according to decision type
  • A defined exit pathway at all times
• Member obligations (examples):
  • Contribution expectations as defined by role and membership state
  • Adherence to declared invariants and safety rules
  • Participation in minimum onboarding and review processes
• Due process reference:
  • “Any forced exit or access restriction follows Layer 4 due process and the exit protocol.”

B.8 Example Onboarding Protocol (Excerpt)

1. Provide access to RCOS artifacts (Layers 0–6) and local modules
2. Confirm explicit consent to Layer 0 and Layer 1 artifacts
3. Assign initial membership state and onboarding buddy
4. Complete safety and conflict process orientation
5. Review scope boundaries and what is out of scope
6. Record onboarding completion in the membership registry

B.9 Example Role Registry Entry (Excerpt)

• Role name: Treasurer
• Purpose: Maintain treasury records and execute authorized payments
• Authority scope:
  • Execute payments ≤ 500 within approved categories
• Limits:
  • No authority to approve budgets or alter transparency rules
• Term:
  • 6 months, renewable once without review
• Accountability:
  • Monthly published treasury report; quarterly audit check
• Appointment/removal:
  • Appointed by Finance Circle; removable by Governance Circle review

B.10 Example Treasury Ruleset (Excerpt)

• Transparency:
  • Monthly balance sheet and cash-flow summary published to all members
• Spending thresholds:

• Conflict-of-interest:
  • A requester may not approve their own spending request

B.11 Example Meeting Template (Excerpt)

• Meeting type: Operations
• Date/time:
• Facilitator:
• Attendees:
• Agenda:
  1. Check-ins (time-boxed)
  2. Review last actions
  3. Operational updates
  4. Decisions (if any)
  5. Next actions and owners
• Decision record (if used):
  • Decision type:
  • Authority:
  • Mechanism/threshold:
  • Outcome:
  • Effective date:

B.12 Example Learning Log Entry (Excerpt)

• Date:
• Trigger event:
• What happened (short narrative):
• Layers/artifacts implicated:
• Signals that triggered action:
• What changed (or what was tried):
• Outcome after review:
• Follow-up action owner and due date: