Layer 0 · Identity
4 Identity Constraints Register
- Layer: 0 — Identity & Scope
- Status: Stub — not yet adopted
- RCOS reference: §2.4, §2.5
Identity constraints declare the non-negotiable boundaries on participation, behavior, and governance that define what this community fundamentally is and is not. Constraints listed here apply to all members, roles, and activities within the governed scope. They may not be enforced implicitly or informally — each constraint includes a defined enforcement pathway.
Governance Constraints
:::rcos{clauses=“2.4.1, 2.4.2”} :::
<Governance constraints on how authority is held and exercised — to be defined.>
IDConstraintEnforcement mechanismAddedDecision recordIC-001[link]
Economic Constraints
:::rcos{clauses=“2.4.1, 2.4.2”} :::
<Economic constraints on how the community and its mechanisms may be used economically — to be defined.>
IDConstraintEnforcement mechanismAddedDecision record
Ecological Constraints
:::rcos{clauses=“2.4.1, 2.4.2”} :::
<Ecological constraints on the community’s relationship with ecosystems and biodiversity — to be defined.>
IDConstraintEnforcement mechanismAddedDecision record
Structural and Cultural Constraints
:::rcos{clauses=“2.4.1, 2.4.2”} :::
<Structural and cultural constraints on the community’s identity — to be defined.>
IDConstraintEnforcement mechanismAddedDecision record
Ethics and Lifestyle Constraints
<Ethics and lifestyle constraints — to be defined.>
IDConstraintEnforcement mechanismAddedDecision record
Enforcement Principles
:::rcos{clauses=“2.4.3, 2.4.4”} :::
:::rationale{title=“Why require constraints to be testable and enforceable?”} Writing a constraint that cannot be acted on is performative — it creates the appearance of accountability without the substance. Testability means there is a defined process through which a member can raise a violation. If no such process exists, the constraint is an aspiration, not a rule. Making that distinction explicit here is what separates implicit culture from enforceable governance. :::
Identity constraints MUST be testable and enforceable through defined processes, and MUST NOT be enforced implicitly or informally.
ConstraintEnforcement statusNotes
Changes to the Register
Identity constraints may only be added, modified, or removed through a Constitutional decision, as defined in the Decision Matrix (Layer 2) and the Change Protocol (Layer 6). Any change must be recorded in the Version History (Layer 6).
Ratification Record
- Adopted:
- Decision type: Constitutional
- Version:
- Decision record: