Fruit Haven

Layer 6 · Evolution

Version History

  • Layer: 6 — Evolution & Adaptation
  • Status: Active — updated with each adopted change
  • RCOS reference: §8.2, §8.6

This is the authoritative human-readable record of all adopted changes to Fruit Haven’ RCOS implementation. The currently active version is the most recent entry at the top of this file. Superseded rules remain accessible via git history.

v1.1.0 — 2026-06-10

  • Effective date: 2026-06-10
  • Decision record: proposals/passed/2019-05-17_federation-sovereignty.md
  • Decision type: Constitutional
  • Mechanism: Consensus
  • Summary: Integrated the “FH Federation” Sovereignty Doctrine (passed by consensus in 2019) into the formal RCOS layers. Extracted community sovereignty details into a dedicated Federation Protocol.
  • Layers affected: Layer 2
  • Artifacts changed: 2-governance/02-governance-protocol.md, 2-governance/04-federation-protocol.md
  • Migration notes: None

v1.0.0 — 2026-05-19

RCOS definition8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.6.4, 8.7.2
  • 8.2.1 All adopted changes MUST be versioned and traceable.
  • 8.2.2 The community MUST maintain a **Version History** that records, at minimum:
  • 8.2.3 At any point in time, the community MUST be able to unambiguously determine:
  • 8.2.4 Superseded rules MUST remain accessible for auditability, learning, and dispute resolution, together with the dates during which they were in force.
  • 8.2.5 No informal, undocumented, or “understood” rule changes MAY be considered valid.
  • 8.6.4 The Version History MUST define:
  • 8.7.2 All adopted changes MUST be versioned, documented, and traceable.

Read 8.2 Versioning and Authority in the RCOS spec ↗

Why record every adopted change?
Version history is what turns governance from memory into evidence. Every adopted change must say what changed, when it became effective, what decision authorized it, and which artifacts moved, so future members can reconstruct the current system without relying on oral history or private context.
  • Effective date: 2026-05-19
  • Decision record: proposals/passed/2019-05-17_fh1-bylaws.md
  • Decision type: Constitutional
  • Mechanism: Consensus Meeting
  • Summary: Initial adaptation of the Fruit Haven Bylaws to the RCOS architecture, mapping purpose, identity constraints, membership states, treasury rules, land allotment, and consensus-based governance rules to the corresponding RCOS layers.
  • Layers affected: Layer 0, Layer 1, Layer 2, Layer 3, Layer 5
  • Artifacts changed: 0-identity/01-purpose-charter.md, 0-identity/04-identity-constraints-register.md, 1-membership/01-membership-agreement.md, 1-membership/04-membership-state-registry.md, 2-governance/01-decision-matrix.md, 2-governance/02-governance-protocol.md, 3-economy/02-treasury-ruleset.md, 3-economy/03-land-allotment-protocol.md, 5-operations/02-role-registry.md
  • Migration notes: Current property owners granted transitional “Active Member” status to resolve ambiguity. See 1-membership/04-membership-state-registry.md.

v0.0 — Repository Initialized

  • Effective date: 2026-04-21
  • Decision record: N/A — initial scaffold
  • Decision type: N/A
  • Mechanism: N/A
  • Summary: Repository structure initialized. All artifact files are stubs — no layer is yet compliant. No rules are in force.
  • Layers affected: All (scaffold only)
  • Artifacts changed: All files created as stubs
  • Migration notes: None — initial state

New entries are prepended above this line.

← Back to Evolution