This guide explains the component types that compose the DNA of the OpenCivics Consortium Agreement. ## Overview The Agreement is organized into four main categories: - **Identity** — Core meaning and intentionality - **Structure** — Roles, Groups, and Assets - **Protocols** — Procedures and processes - **Agreements** — Role-specific compacts that transclude relevant content --- # Identity Components Identity components define the foundational purpose, values, and direction of the Consortium. ## Identity Component Types - **Vision**: What OpenCivics envisions for the future (future aspiration) - **Purpose**: Why OpenCivics exists (present, core reason for existence) - **Mission**: What OpenCivics does to fulfill its purpose (present activities) - **Functions**: Core activities and capabilities - **Mandates**: Core commitments and boundaries - **Values**: What OpenCivics stands for (continuous ethical guidance) - **Worldview**: How OpenCivics understands the context it operates in ## Vision - **Description:** What OpenCivics envisions for the future - **Temporal Focus:** Future long-term aspiration - **Scope:** The world OpenCivics seeks to help create - **Function:** Provides inspiration and direction for long-term efforts - **Test:** This is compelling enough to inspire action and specific enough to guide decisions ## Purpose - **Description:** Why OpenCivics exists - **Temporal Focus:** Present and ongoing - **Scope:** Core reason for existence - **Function:** Provides the fundamental justification for OpenCivics existence - **Test:** This is compelling enough to inspire action and broad enough to encompass all activities ## Mission - **Description:** What OpenCivics does to fulfill its purpose - **Temporal Focus:** Present and ongoing - **Scope:** Organizational activities and functions - **Function:** Guides what OpenCivics does and how it allocates resources - **Test:** This is specific enough to guide decisions but broad enough to allow evolution ## Functions - **Description:** Core functions served by the OpenCivics Consortium in supporting open civic innovation - **Temporal Focus:** Present and ongoing - **Scope:** Operational capabilities and service areas - **Function:** Defines what the Consortium actually does for members and the field - **Test:** These functions would be recognizable to an outside observer watching the Consortium operate ## Mandates - **Description:** What you are obligated to do - **Temporal Focus:** Present and continuous - **Scope:** Organizational obligations and responsibilities - **Function:** Defines non-negotiables and ethical boundaries - **Test:** These obligations would be upheld even in difficult circumstances ## Values - **Description:** What OpenCivics stands for - **Temporal Focus:** Present and continuous - **Scope:** Guides internal conduct, cultural tone, and ethical posture - **Function:** Shapes behavior, design decisions, and protocols at all levels - **Test:** If this value was violated, OpenCivics would feel out of integrity even if its mission was achieved ## Worldview - **Description:** OpenCivics fundamental assumptions about how the world works - **Temporal Focus:** Present and continuous - **Scope:** Philosophical and theoretical foundations - **Function:** Shapes how OpenCivics understands problems and designs solutions - **Test:** These assumptions guide OpenCivics approach even when not consciously thinking about them --- # Structure Components Structure components define the organizational form through which identity is enacted. Structure is composed of Roles, Groups, and Assets. ## Roles Roles define individual membership types with distinct rights, responsibilities, and access levels. - **Description:** A named position within the Consortium that an individual or organization can hold - **Membership Basis:** Criteria and process by which the role is entered - **Scope:** The boundaries of what the role includes and excludes - **Function:** What the role contributes to the Consortium's functioning - **Test:** Role holders would know what's expected and how to navigate their membership ### Role Document Structure - **Purpose:** Why this role exists - **Criteria:** Requirements for holding the role - **Responsibilities:** What the role holder is expected to do - **Benefits:** Access and opportunities the role provides - **Term and Accountability:** Duration and review mechanisms - **Governing Protocols:** Protocols that apply to this role --- ## Groups Groups define collective bodies that coordinate, deliberate, and make decisions together. - **Description:** A named assembly of role holders that convenes for shared purpose - **Composition:** Which roles participate and how membership is determined - **Scope:** The boundaries of authority and activity - **Function:** What the group accomplishes for the Consortium - **Test:** Group decisions would be recognized as legitimate by the broader membership ### Group Document Structure - **Purpose:** Why this group exists - **Composition and Membership:** Who participates and how - **Functions and Authority:** What the group does and decides - **Operations:** How the group convenes and works - **Communication and Engagement:** How information flows - **Accountability and Feedback:** How the group is held responsible - **Integration:** How the group relates to other bodies - **Related Roles:** Roles that participate in the group - **Related Assets:** Assets the group stewards or utilizes - **Related Protocols:** Protocols governing the group's function --- ## Assets Assets define shared resources stewarded for collective benefit under specified protocols. - **Description:** A named resource held in common for the benefit of the Consortium - **Location:** Where the asset is accessed or maintained - **Scope:** What the asset includes and its boundaries - **Function:** What the asset enables or provides - **Test:** The asset would be accessible, well-maintained, and aligned with mission ### Asset Document Structure - **Description:** What the asset is - **Location:** Where it lives - **Stewardship:** Who maintains it - **Access:** Who can use it and how - **Usage Requirements:** Conditions for use - **Related Roles:** Roles with access or stewardship responsibilities - **Related Protocols:** Protocols governing the asset --- # Protocol Components Protocols are formalized processes governing Consortium operations. Each protocol specifies authority, scope, and procedures for repeatable coordination. ## Protocol Types - **Role Protocols:** Govern how specific roles operate, transition, and relate - **Group Protocols:** Govern how collective bodies function and coordinate - **Asset Protocols:** Govern how shared resources are managed and used - **Cultural Protocols:** Govern how community rhythms and practices unfold ## Protocol - **Description:** A named, formalized procedure for a specific domain of Consortium operations - **Authority:** Who has decision rights under this protocol - **Scope:** What's included and excluded from the protocol's governance - **Function:** What the protocol accomplishes for the Consortium - **Test:** Following the protocol would produce consistent, fair, and transparent outcomes ### Protocol Document Structure - **Description:** What the protocol governs - **Protocol Type:** Category (Role, Group, Asset, Cultural) - **Related Roles:** Roles affected by or involved in the protocol - **Related Groups:** Groups with authority or involvement - **Related Assets:** Assets governed or utilized - **Authority:** Who has decision rights - **Purpose:** What the protocol accomplishes - **Scope:** What's included and excluded - **Procedures:** Step-by-step processes - **Timeline:** When things happen - **Integration:** How the protocol connects to other components --- # Agreement Components Agreements are role-specific compacts that members affirm upon joining. Each agreement transcludes relevant content from Identity, Structure, and Protocols to create a complete picture of membership. ## Agreement - **Description:** A named membership compact for a specific role - **Audience:** The role holder affirming the agreement - **Scope:** Everything the role holder needs to understand and commit to - **Function:** Establishes mutual commitment between member and Consortium - **Test:** The member would understand their rights, responsibilities, and what they're committing to ### Agreement Document Inclusions - **Introduction:** - Welcome statement identifying the role - Statement that this document constitutes the membership agreement - Affirmation of alignment with Consortium identity and ethics - **Transcluded Content:** - Relevant Identity components (Purpose, Values, Mandates) - Role definition from Structure - Applicable Protocols - Access and benefits summary - Term and accountability expectations - **Affirmation:** - Statement of commitment - Signature or acceptance mechanism --- # How Components Relate ``` Identity (why) → Structure (who/what) → Protocols (how) → Agreements (commitment) ``` - **Identity** provides the grounding that all other components serve - **Structure** creates the organizational form through which identity is enacted - **Protocols** operationalize structure through repeatable processes - **Agreements** bind members to the whole through role-specific commitments Components are cross-referenced throughout: - Roles link to their governing protocols - Groups link to their member roles and stewarded assets - Protocols reference the authority that governs them - Agreements transclude relevant content from all categories --- # Navigation - **Main Document:** [[OpenCivics Consortium Constitution]] - **Indices:** - [[Identity/Identity Index|Identity Index]] - [[Structure/Structure Index|Structure Index]] - [[Structure/Roles/Roles Index|Roles Index]] - [[Structure/Groups/Groups Index|Groups Index]] - [[Structure/Assets/Assets Index|Assets Index]] - [[Protocols/Protocols Index|Protocols Index]] - [[Agreements/Agreement Index|Agreement Index]]