6 Evolution & Adaptation

The community MUST define explicit change mechanisms for modifying, adding, suspending, or removing rules, roles, artifacts , or decision structures.

Change mechanisms MUST explicitly distinguish between:

• Permanent rule changes
• Time-bounded experiments as defined in Section 8.3

Every proposed change MUST specify, at minimum:

• The artifact(s), layer(s), and section(s) affected
• The decision type and authorized decision path as defined in Layer 2
• The intended effect, scope , and known risks
• The effective date and any transition period
• Migration requirements for existing roles, agreements, or records

Changes affecting Layer 0 purpose, scope, invariants , or identity constraints MUST be classified as constitutional changes and MUST follow the constitutional decision mechanism.

The community MUST define explicit review mechanisms for adopted changes, including how changes are evaluated, revised, or reverted when they produce harm, instability, or unintended concentration of power.

All adopted changes MUST be versioned and traceable.

The community MUST maintain a Version History that records, at minimum:

• Version identifier
• Adoption date and effective date
• Decision record reference (authority, mechanism, threshold)
• Summary of changes
• Migration notes and compatibility constraints (if any)

At any point in time, the community MUST be able to unambiguously determine:

• Which version is currently in force
• Which artifacts are authoritative for compliance

Superseded rules MUST remain accessible for auditability, learning, and dispute resolution, together with the dates during which they were in force.

No informal, undocumented, or “understood” rule changes MAY be considered valid.

The community MAY adopt experiments as explicitly time-bounded and reversible deviations, extensions, or pilots intended for learning.

Every experiment MUST define, at minimum:

• Scope (what is changed and what is explicitly not changed)
• Duration and review checkpoints
• Success and failure criteria
• Rollback conditions and rollback process
• Authorized decision path for starting, extending, modifying, or terminating the experiment

Experiments MUST NOT override Layer 0 invariants and MUST NOT bypass governance constraints defined in Layer 2.

Experiments MUST be explicitly labeled as experimental in all affected artifacts and MUST include a non-extendable expiration date unless renewed through an authorized decision.

If an experiment introduces safety risk, coercion, or sustained harm, the community MUST suspend or terminate the experiment immediately through a protective action, followed by post-hoc review.

Major failures, adaptations, reversals, and systemic learnings MUST be documented.

Learning capture MUST include, at minimum:

• What occurred and why it mattered
• Which layers, rules, or artifacts were implicated
• What was changed, attempted, or stopped
• What signals, evidence, or thresholds triggered action

Learning records MUST be accessible according to Layer 5 information access rules.

Repeated failure patterns MUST trigger structural review rather than individual blame.

The system MUST prefer reversible changes over irreversible ones where possible.

Irreversible or high-impact changes MUST include:

• Extended deliberation or review periods
• Higher decision thresholds where appropriate
• Explicit risk acknowledgment

Emergency changes MAY be permitted only where explicitly defined, MUST be time-bounded, MUST NOT override Layer 0 invariants , and MUST undergo mandatory post-hoc review and ratification or rollback.

The following artifacts are mandatory for Layer 6 compliance:

• Change Protocol
• Version History
• Learning Log

Layer 6 artifacts MUST be:

• Explicit and unambiguous
• Versioned
• Accessible to all members, with clearly bounded privacy protections
• Adopted through an authorized governance process

The Change Protocol MUST define, at minimum:

• How changes are proposed, reviewed, adopted, published, and rejected
• How proposals are classified by decision type
• Required contents of change proposals
• Transition, migration, and deprecation expectations
• Review, revision, and rollback mechanisms
• Emergency change provisions, including strict time bounds and mandatory review

The Version History MUST define:

• The authoritative structure for version identifiers and change logs
• How superseded versions are retained and accessed
• How the currently active version is determined

The Learning Log MUST define:

• What constitutes a learnable event
• Documentation format and ownership
• Review and synthesis cadence

Change MUST be possible but constrained; no change MAY be instantaneous, implicit, or unreviewable.

All adopted changes MUST be versioned, documented, and traceable.

Experiments MUST be time-bounded, explicitly labeled, and reversible.

Major failures and adaptations MUST be captured as shared learning, not erased or hidden.

The following MUST be explicit:

• How rules change and who decides
• Versioning, authority, and review processes
• Experiment scope , duration, and rollback conditions
• Emergency change conditions and limits

The following MAY be explicit:

• Review frequency and cadence
• Sunset clauses
• Feedback and sensing methods

The following MUST remain optional and out of scope:

• Pace of innovation
• Cultural attitudes toward risk within defined bounds