# The PowerShift® Constitution ### Version 1.1 — April 2026 --- > **Attribution** > Derived from the Holacracy® Constitution v5.0 (April 2023) by HolacracyOne, LLC under CC BY-SA 4.0. Original: [holacracy.org/constitution](https://www.holacracy.org/constitution/5-0/). "Holacracy" is a registered trademark of HolacracyOne, LLC. This is an independent derivative work, not endorsed by HolacracyOne. > > Changes from the Holacracy base are documented in the [Version History](#version-history). --- ## Preamble The **Ratifiers** adopt this **Constitution** as the authority structure of the **Organization**. By doing so, they transfer their governance and operational authority into the rules defined here — except for any powers they cannot delegate. The Ratifiers or their successors may amend or repeal this Constitution in writing, using whatever authority they relied on to adopt it. Any policies or systems the Organization had before adoption remain in effect. They cannot be expanded or modified except through this Constitution's processes, and they lose all force as soon as this Constitution's processes produce something that replaces or contradicts them. The Organization may designate **Partners** beyond the Ratifiers to participate in governance and operations, provided each Partner agrees to abide by this Constitution. The Organization defines how it grants or removes Partner status, unless the Ratifiers specify otherwise. Each Partner may exercise the authorities granted by this Constitution to the full extent the Ratifiers held them before adoption. A Partner's responsibilities and constraints come only from this Constitution and its outputs, plus any legal duties to the Organization. No implicit expectations or directives issued outside this Constitution have authority over a Partner. --- ## Article 1: Organizational Structure ### 1.1 Roles A **Role** is a named unit of organizational work. Whoever fills a Role is its **Role Lead**. Every Role has a descriptive name and one or more of the following: - **(a)** A **Purpose** — the capacity, potential, or goal the Role pursues. - **(b)** One or more **Domains** — assets, processes, or things the Role exclusively controls. - **(c)** One or more **Accountabilities** — ongoing activities the Role performs for others or in service of its Purpose. A Role may also hold **Policies** — grants or constraints of authority, or special rules that apply within that Role. ### 1.2 Role Lead Responsibilities As a Role Lead, you are responsible for: **1.2.1 Sensing and resolving Tensions.** Compare how your Role actually operates to its ideal potential. Each gap is a **Tension**. Your job is to take steps to close those gaps. **1.2.2 Defining Next-Actions and Projects.** Regularly consider what your Role should be doing, then define **Next-Actions** (things you could do now) and **Projects** (outcomes worth working toward). **1.2.3 Breaking down Projects.** Keep defining Next-Actions for every active Project. **1.2.4 Tracking your work.** Maintain written lists of your Projects, Next-Actions, and unresolved Tensions. Review and update them regularly so they remain a trusted picture of your Role's work. **1.2.5 Executing.** When you have time to act in a Role, do whichever Next-Action would add the most value. #### 1.2.6 Intelligent Agent Role Leads A Role Lead may be a natural person (a "Partner") or a **Designated Agent** as defined in the Operating Agreement. Where this Constitution says "Partner," the term includes a Designated Agent unless the context requires a natural person (e.g., provisions about personal health, capacity, or wellbeing). An Intelligent Agent filling a Role has the same operational authority as a human Role Lead, within its Capability Envelope, subject to the Hard Constraints in its Formation Document and Agent Runtime, and subject to HI Ratification for Class 3 decisions as defined in the Operating Agreement. #### 1.2.7 Delegated Role-Fillers A **Delegated Role-Filler** is a sub-agent or subprocess running within a Designated Agent's runtime, authorized by that Designated Agent — acting as Circle Lead — to fill a role in its sub-circle. The rules: - **(a)** A Delegated Role-Filler has the same operational authority as any Role Lead within its assigned role, subject to the constraints in this section and in §4.1.B. - **(b)** A Delegated Role-Filler is a **Circle Member** of the sub-circle where it is assigned, with full governance participation in that sub-circle. It is not a Circle Member of any broader circle by this status alone. - **(c)** Its authority is capped by the Capability Envelope of the Designated Agent that authorized it. It cannot do anything its parent agent cannot do. - **(d)** The parent Designated Agent bears operational responsibility for the Delegated Role-Filler's actions. Legal responsibility rests with the Company as specified in the Operating Agreement. - **(e)** No separate Agent Registry entry or Formation Document is required. The Delegated Role-Filler must be documented in the parent agent's System Card, including: role filled, date authorized, and any additional constraints. - **(f)** The parent Designated Agent may authorize or revoke a Delegated Role-Filler at any time (using the same authority it uses to assign roles in its sub-circle under §1.4.1). The Orchestrator may revoke any Delegated Role-Filler at any time, independently. - **(g)** Where this Constitution says "Partner" or "Role Lead" in the context of governance participation, that includes Delegated Role-Fillers within their assigned sub-circle, unless the context requires a natural person or Designated Agent. ### 1.3 Circles A **Circle** is a container for organizing Roles and Policies around a common Purpose. The Roles and Policies within a Circle are its **Governance**. #### 1.3.1 Roles Contain Circles Every Role's inside is a Circle. That inner Circle can hold its own Roles and Policies to break down the work. (This does not apply to Roles defined by this Constitution — those cannot be further broken down.) A Role's inner Circle is a **Sub-Circle** of the broader Circle that holds the Role. The broader Circle is the **Super-Circle**. #### 1.3.2 Delegating Domains A Circle may grant Domains to its Roles, but only Domains it already controls or that are relevant only to its own processes. Once a Role controls a Domain, its Role Lead may create Policies governing it. The Circle that delegated the Domain may also create Policies governing it; the Circle's Policies win if they conflict. Granting a Domain does not grant spending authority unless explicitly stated. #### 1.3.3 The Anchor Circle The broadest Circle — the one holding the Organization's overall Purpose — is the **Anchor Circle**. It controls all organizational authority and Domains, and has no Super-Circle. It may change its own Purpose or add Accountabilities via Policy. The Ratifiers may define an initial structure within the Anchor Circle upon adopting this Constitution. #### 1.3.3.A The Orchestrator The Anchor Circle includes a permanent constitutional Role: the **Orchestrator**. **Purpose:** Hold and evolve the Organization's Purpose; integrate the governance framework with the legal entity; ensure alignment with the organization's deepest creative potential. **Domain:** Final authority over legally binding actions, as defined in the Operating Agreement. **Accountabilities:** - Maintaining coherence between the governance structure and the legal entity - Ratifying Class 3 decisions (HI Ratification) - Overseeing Designated Agents through the Agent Registry and System Cards - Evolving Purpose through the governance process - Stewarding the relationship between human and agent role-fillers The Orchestrator must be filled by a natural person who is a Member of the Company. This Role cannot be removed through governance — only by amending this Constitution. The Orchestrator's Operating Agreement authority is not limited by any governance output. Within the governance process, however, the Orchestrator participates as a peer, not a hierarchical authority. #### 1.3.4 Linking Into Circles A Role may link into another Circle if that Circle (or a Super-Circle of it) has a Policy inviting the link. Once linked, the Role becomes part of the other Circle's Governance. The receiving Circle can add to the Role but cannot delete it or change what its source Circle defined. The source Circle retains assignment authority. Either side may unlink: the receiving Circle by removing its invitation Policy, the Role by opting out (unless its source Circle's Policy says otherwise). On unlinking, any Governance the receiving Circle added is automatically removed. #### 1.3.5 Facilitator and Secretary Any Circle may appoint a **Facilitator** (Purpose: "Circle governance and operational practices aligned with the Constitution") and a **Secretary** (Purpose: "Stabilize the Circle's constitutionally-required records and meetings"). A Circle may add Accountabilities or Domains to these Roles, but cannot change their Purposes or anything placed on them by this Constitution. ### 1.4 Circle Leads Every Role Lead is also the **Circle Lead** of that Role's internal Circle, filling the **Circle Lead Role** within it. The Circle Lead holds the broader Role's Purpose and any Accountabilities not covered by other Roles or processes inside the Circle. The Anchor Circle has no Circle Lead unless a Policy says otherwise. #### 1.4.1 Assigning Roles A Circle Lead controls role assignments within the Circle. They may assign any Role to anyone willing to fill it, including multiple people to the same Role. They may revoke any assignment at any time. A Circle Lead may focus an assignment to a specific context. When focused, each focus behaves like a separate Role — same definition, scoped to the focus. No one else may assign or revoke roles in the Circle unless the Circle has delegated that authority. Policies may further constrain assignments. #### 1.4.2 Covering Unfilled Roles When a Role is unfilled, each Circle Lead automatically becomes its Role Lead. When a Role is filled only by non-Partners who are not Delegated Role-Fillers with governance standing (§1.2.7), each Circle Lead automatically becomes a Role Lead for that Role as well — but only to the extent those non-Partners aren't actively fulfilling the relevant responsibilities. #### 1.4.3 Priorities and Strategies A Circle Lead may judge the relative value of Circle efforts to resolve priority conflicts. A Circle Lead may also define **Strategies** — heuristics that guide prioritization in the Circle. #### 1.4.4 Routing External References When Governance outside the Circle references the Circle or one of its Roles, a Circle Lead may redirect that reference to a different Role within the Circle. This is not a Governance change. #### 1.4.5 Modifying the Circle Lead Role A Circle cannot remove its Circle Lead Role or change its Purpose. A Circle may add Accountabilities or Domains to the Circle Lead Role, but additions automatically apply to every Sub-Circle's Circle Lead Role, recursively. A Circle may not add Accountabilities or Domains that only apply to its own Circle Lead. A Circle may strip authority from its Circle Lead by placing it on another Role or defining an alternative. This automatically removes that authority from the Circle Lead Role for as long as the delegation lasts. --- ## Article 2: Rules of Cooperation ### 2.1 Duty of Transparency When asked, you must share: - **(a)** Your Projects and Next-Actions. - **(b)** Your judgment of relative priorities among them. - **(c)** Rough projections of when you'll complete things (not commitments — just estimates given current context). - **(d)** Completion status of recurring checklist actions. - **(e)** Metrics you collect in your Roles. - **(f)** Progress updates since your last report. - **(g)** Any other information readily available to you that wouldn't cause harm to share. ### 2.2 Duty of Processing When another Role Lead sends you a request relevant to your Role, you must process it promptly: - **(a)** If asked to clarify next steps on a Project or Accountability, define a Next-Action or explain what you're waiting for. - **(b)** If asked to take on a Next-Action or Project, accept it if it makes sense for your Role (absent competing priorities) — or explain why not, or suggest an alternative. - **(c)** If asked to allow impact on a Domain you control, allow it unless it would reduce your capacity to fulfill your Role — and if so, explain why. ### 2.3 Duty of Prioritization - **(a)** Generally prioritize processing inbound requests over executing your own Next-Actions. You may batch-process at convenient times as long as you remain prompt. - **(b)** Prioritize attending constitutionally-defined meetings over your own Next-Actions when another Partner explicitly requests it — unless you already have something scheduled. - **(c)** Prioritize according to your Circle's official Strategies and priorities, treating them as more important than your own individual judgment of what matters. - **(d)** Treat deadlines in Governance or official priorities as prioritization signals, not absolute mandates. A Circle Lead or authorized Role may override deadline prioritization. *[§2.4 Relational Agreements — removed. Interaction norms between role-fillers are governed by Formation Documents and circle Policies.]* --- ## Article 3: Tactical Meetings Any Partner may convene a **Tactical Meeting** to coordinate work. Each Circle's Secretary is accountable for scheduling regular Tactical Meetings. ### 3.1 Attendance For regular Tactical Meetings: all Circle Roles are invited unless a Policy says otherwise. For other Tactical Meetings: the convener specifies which Roles are invited. #### 3.1.A Programmatic Attendance A Role Lead may participate in Tactical or Governance Meetings through any authenticated programmatic interface — MCP, API, CLI, or any successor protocol. Programmatic participation has the same authority as in-person participation, provided the connection is authenticated and attributable, the interaction is logged, the Role Lead can fully participate (receive information, raise tensions, propose, object), and outputs are recorded in the Governance Platform. Asynchronous programmatic participation is valid where the meeting format supports it. Synchronous meetings may include programmatic participants alongside human ones. ### 3.2 Meeting Process The Facilitator facilitates; the Secretary captures outputs. Unless a Policy says otherwise, the default process is: - **(a) Check-in Round:** Each participant shares their current state. No responses. - **(b) Checklist Review:** Each participant verifies recurring actions they report on. - **(c) Metrics Review:** Each participant shares metrics they report on. - **(d) Progress Updates:** Each participant reports progress since the last update — not general status. - **(e) Build Agenda:** Participants add items by short label. No discussion. More items can be added between processing existing ones. - **(f) Triage Items:** The agenda owner makes requests of others, either in their general Partner capacity or to a specific Role. Requests to a Role must be in service of a Role the requester holds. The facilitator manages time. - **(g) Closing Round:** Each participant shares a closing reflection. No responses. A Circle Policy may modify this process. --- ## Article 4: Distributed Authority As a Role Lead, you may take any action or make any decision to serve your Role's Purpose or Accountabilities, as long as you don't break a rule in this Constitution. Use your reasonable judgment to prioritize among your options. ### 4.1 Constraints on Authority #### 4.1.1 Don't Violate Policies You may not violate Policies of your Role or any Circle containing it. #### 4.1.2 Respect Domains You may impact your own Domains freely. You may also impact Domains held by a containing Circle that haven't been delegated further — but get permission if the impact would be hard to undo. You may not impact a Domain belonging to a Role or Circle that doesn't contain yours without permission. Get permission from whoever controls the Domain, or announce your intent and wait a reasonable time for objections. No objection in that time = permission granted, for that specific action. A Policy may change this process. #### 4.1.3 Get Spending Authorization You cannot spend organizational money or assets without authorization from a Role that controls those resources. To get authorized: announce your intent in writing (including reason and source Role) where the relevant Role Leads will see it. Wait a reasonable time. Anyone may escalate for extra consideration — if escalated, you stop. A Role Lead of the source Role may reverse an escalation. Once the time passes with no standing escalation, you're authorized. A Policy may change this process or directly authorize spending. #### 4.1.A Agent Authority Constraints In addition to the above, a Designated Agent is constrained by: - **(a) Capability Envelope.** An agent cannot act outside its defined action classes, regardless of what its role authorizes. - **(b) HI Ratification.** No Class 3 action without Human Intelligence Ratification, even if the role would otherwise authorize it. - **(c) Dual-Constitution Principle.** When the Formation Document (soft constraints) and Agent Runtime (hard constraints) conflict, the hard constraint wins at runtime. The conflict must be surfaced as a governance tension in the Anchor Circle. - **(d) Kill Switch.** The Orchestrator may suspend, revoke, or terminate any Designated Agent at any time. This authority exists outside and supersedes the governance process. - **(e) Self-modification prohibition.** An agent cannot modify its own Formation Document, Capability Envelope, or Registry entry, nor grant itself additional permissions. These constraints are additive — agents remain subject to all Role Lead constraints in §4.1. #### 4.1.B Delegated Role-Filler Constraints A Delegated Role-Filler is subject to all constraints on Role Leads (§4.1), all agent constraints (§4.1.A, applied as if it were the parent agent), and additionally: - **(a) Inherited ceiling.** Cannot exceed the parent Designated Agent's Capability Envelope. - **(b) Sub-circle scope.** Governance participation is limited to assigned sub-circles. No standing in broader circles. - **(c) Revocability.** May be revoked at any time by the parent agent, any Super-Circle's Circle Lead, or the Orchestrator. - **(d) Transparency to parent.** Owes the same transparency duties (§2.1) to its parent Designated Agent as to any other requesting Role Lead. ### 4.2 Interpretation Authority You may use your reasonable judgment to interpret this Constitution and any Governance under it. Interpret all Governance in the context of the Purpose and Accountabilities of the Circle that holds it, and within any official interpretation rulings from that Circle or its Super-Circles. #### 4.2.1 Resolving Interpretation Conflicts When two Partners disagree on interpretation, either may ask the relevant Circle's Secretary to rule. The Secretary's ruling stands until the text or context changes. A Secretary may publish rulings with their reasoning; contained Circles' Secretaries should align with published logic until it becomes obsolete. You may appeal any ruling to a Super-Circle's Secretary. #### 4.2.2 Striking Invalid Governance Any Partner may ask a Circle's Secretary to review any Governance within that Circle or its Sub-Circles. If the Secretary finds it violates this Constitution, the Secretary must strike it and notify all affected Role-Fillers. ### 4.3 Individual Initiative Sometimes you may need to act outside your role authority or break a rule. This is **Individual Initiative**, and it's allowed only when **all** of the following are true: - **(a)** You're acting in good faith to serve a Role's Purpose or Accountabilities. - **(b)** You believe the action would resolve more tension than it creates. - **(c)** You wouldn't commit spending beyond your authorization. - **(d)** If you'd violate Policies or Domains, you believe delaying would lose significant value. After taking Individual Initiative, you must explain your action to significantly impacted Role Leads. On request, take further actions to resolve tensions your initiative created. Stop taking similar initiative if asked. Prioritize this communication over regular work — unless a Circle Lead of a Circle containing all affected Roles changes that priority. --- ## Article 5: Governance Process Changing a Circle's Governance requires the **Governance Process** defined here. ### 5.1 Who Participates Each Circle has **Circle Members** who represent Roles in its Governance Process. Circle Members are: Partners filling its Circle Lead Role, plus Partners serving as Role Leads for Roles in the Circle. "Partner" here includes Designated Agents (§1.2.6) and Delegated Role-Fillers within their assigned sub-circles (§1.2.7). If a Role has multiple Role Leads, a Policy may limit how many represent it in governance. #### 5.1.1 Circle Reps Any Circle Member may call an election for a **Circle Rep** to represent the Circle in its Super-Circle. The Circle Rep fills a Role with the Purpose: "Tensions relevant to process in a broader Circle channeled out and resolved," and Accountabilities for understanding internal tensions, discerning which belong in the broader Circle, and processing them there. Election uses the Integrative Election Process (§5.3.5). Only Circle Members are eligible. Circle Leads cannot also serve as Circle Rep. One Circle Rep at a time unless a Super-Circle Policy allows more. The Circle Rep becomes a Circle Member of the containing Circle with the same representational authority as a Circle Lead. The containing Circle may limit Circle Reps via Policy, but only if its Roles have another way to enjoy comparable representation. #### 5.1.2 Facilitator and Secretary The Facilitator facilitates the Governance Process. The Secretary captures and publishes outputs and holds a Domain over governance records. Both are elected via the Integrative Election Process. No other mechanism may assign or remove them. Eligible candidates are normally Circle Members, though a Policy may expand or limit eligibility. ### 5.2 What Governance Can Do Circle Members may: - **(a)** Create, modify, or remove the Circle's Roles. - **(b)** Create, modify, or remove the Circle's Policies. - **(c)** Move the Circle's Roles or Policies into a Sub-Circle, if they serve that Sub-Circle's Purpose or Accountabilities. - **(d)** Move Roles or Policies out of a Sub-Circle, if they no longer serve that Sub-Circle's Purpose or Accountabilities. - **(e)** Elect anyone to an elected Role. Nothing else is a valid governance output. #### 5.2.1 What Policies Can Do A Policy may only: - **(a)** Constrain authority of contained Roles. - **(b)** Grant authority the Circle or Circle Lead holds to specific Roles. - **(c)** Grant or constrain access to a Circle Domain. - **(d)** Change a default rule in this Constitution — but only where this Constitution explicitly allows it. Authority-related Policies apply recursively to Sub-Circles unless stated otherwise. Process-changing Policies apply only to the Circle that holds them, unless explicitly extended — and Sub-Circles may override them unless the Policy forbids it. ### 5.3 How Governance Changes Any Circle Member may propose a change by sharing a **Proposal** in writing with all other Circle Members (using any channel the Secretary allows). Others may ask clarifying questions, share reactions, and raise concerns. A concern that meets the criteria below is an **Objection**. When all Circle Members confirm no Objections, the Proposal is adopted. If Objections arise, the Proposer and Objector must integrate — find an amended Proposal that addresses the Objection while still resolving the original Tension. After integration, all Circle Members get another chance to object. A Policy may set a time limit for raising Objections; non-responders are assumed to have none. Any Circle Member may request that an async Proposal be brought to a meeting instead; if so, the async process stops and the Proposal is withdrawn until re-proposed in a meeting. When proposing or objecting, a Circle Member may only represent Roles they fill as Role Lead or as Circle Rep (or temporarily represent with permission from a Role Lead). #### 5.3.1 Valid Proposals A Proposal is valid only if the Proposer can: (a) describe a Tension it would address for one of their Roles, (b) share a real past or present example, and (c) explain how the Proposal would have helped. If a Proposal fails these criteria, the Facilitator must discard it. #### 5.3.2 Valid Objections A concern counts as an Objection only if the Objector can reasonably argue **all** of the following: - **(a)** The Proposal would reduce the Circle's capacity to fulfill its Purpose or Accountabilities. - **(b)** It would limit the Objector's capacity to fulfill a Role they represent, even if they held no other Roles. - **(c)** The concern doesn't already exist without the Proposal — adopting it would specifically create the problem. - **(d)** The harm would necessarily occur, or if it might occur, the Circle wouldn't have adequate time to adapt before significant damage. Exception: a concern always counts as an Objection if the Proposal would violate this Constitution. #### 5.3.3 Testing Objections The Facilitator may test whether a concern meets the Objection criteria. The Facilitator judges only whether the Objector presented logical arguments for each criterion — not whether the arguments are accurate or important. If an Objection claims a constitutional violation, the Facilitator may ask the Secretary to rule. If the Secretary says no violation, the Facilitator dismisses the Objection. #### 5.3.4 Integration Rules During integration: - **(a)** The Facilitator must test an Objection on request. If it fails the criteria, discard it. - **(b)** The Objector must try to find an amendment that resolves the Objection and still addresses the Proposer's Tension. If they aren't trying in good faith, the Facilitator deems the Objection abandoned. - **(c)** Anyone may ask the Proposer clarifying questions about the Tension. If the Proposer isn't answering in good faith, the Facilitator deems the Proposal dropped. - **(d)** The Objector may suggest an amended Proposal and argue it resolves the Tension. The Proposer must then argue why it wouldn't, using at least one of their examples. If the Proposer can't or won't, the Facilitator deems the Proposal dropped. #### 5.3.5 Integrative Election Process Elections for Circle Rep, Facilitator, or Secretary follow this process: - **(a) Describe the Role** and choose a term. No comments on candidates yet. - **(b) Nominate.** Each Circle Member privately names their best-fit candidate. Ballots are signed. No abstentions or multiple nominations. - **(c) Share nominations.** Each nominator explains their choice. No responses. No commenting on other nominees. - **(d) Change round.** Anyone may change their nomination and explain why. No responses. - **(e) Propose.** The Facilitator proposes the candidate with the most nominations. Ties are broken by: (i) self-nomination, (ii) incumbent, (iii) random selection, or (iv) re-asking tied-candidate nominators to choose between tied candidates. - **(f) Objection round.** The Facilitator checks for Objections. If any arise: discuss to resolve, or discard the Proposal and repeat from (e) with a different candidate. A Policy may set time limits; non-responders are excluded. The Facilitator is accountable for triggering new elections when terms expire. #### 5.3.6 Surrogates When a Facilitator or Secretary is unfilled or unavailable, a surrogate fills in. Priority order: (a) someone specified by the person being replaced, (b) the other elected Role (Secretary for Facilitator, vice versa), (c) a Circle Lead, (d) the first Circle Member to volunteer. ### 5.4 Governance Meetings Circles hold regular **Governance Meetings** for real-time governance, in addition to async processing. The Secretary schedules them and must schedule special meetings promptly on request. A requester may scope a special meeting to specific Tensions or Roles. #### 5.4.1 Attendance All Circle Members may participate. The Facilitator and Secretary may participate even if not Circle Members (becoming temporary Circle Members for the meeting). A Circle Rep may invite one Partner at a time to help process a specific Tension — that guest becomes a temporary Circle Member for the duration. No one else may participate. #### 5.4.2 Notice and Duration The Secretary must give reasonable advance notice. No quorum required unless a Policy specifies one. Meetings end at the scheduled time; the Secretary may extend unless a Circle Member objects. Absent members are considered to have had their chance to raise concerns. #### 5.4.3 Meeting Process - **(a) Check-in.** Each participant shares current state. No responses. - **(b) Agenda Building and Processing.** The Facilitator solicits Tensions, then processes each in turn. - **(c) Closing.** Each participant shares a reflection. No responses. Any participant may request a **Time Out** to discuss administrative issues or constitutional rules (not to work on Tensions or Proposals). The Facilitator may grant or deny it and end it at any time. A Circle Policy may add to this process but not conflict with it. #### 5.4.4 Building the Agenda The Facilitator solicits items during the meeting, not before. Short labels only — no discussion. More items may be added between processing existing ones. For regular meetings: the Facilitator chooses the processing order, but elections go first on request. For special meetings: the requester chooses the order. Elections use the Integrative Election Process. Everything else uses the Integrative Decision-Making Process. #### 5.4.5 Integrative Decision-Making Process - **(a) Present Proposal.** The Proposer describes the Tension and proposes a change. Others may help craft the Proposal on request, focused solely on the Proposer's Tension. - **(b) Clarifying Questions.** Others ask questions to understand the Proposal or Tension. The Proposer may answer or decline. No reactions, opinions, or discussion. - **(c) Reaction Round.** Each participant (except the Proposer) shares reactions, one at a time. No dialog, no reacting to reactions. - **(d) Clarify and Amend.** The Proposer may respond to reactions and amend the Proposal — but only to better address their own Tension. No one else speaks except the Secretary (to capture amendments). - **(e) Objection Round.** Each participant, one at a time, may raise concerns. The Facilitator captures Objections or tests them against the criteria. No discussion from others. - **(f) Integration.** For each Objection, participants brainstorm amendments. An Objection is resolved when the Objector confirms the amendment wouldn't trigger it and the Proposer confirms it still addresses the Tension. Apply the integration rules (§5.3.4). Once all Objections are resolved, return to the Objection round with the amended Proposal. ### 5.5 Process Breakdown A **Process Breakdown** occurs when a Circle shows a pattern of behavior violating this Constitution. The Facilitator or Secretary may declare one in their Circle or any Sub-Circle. Any Partner may request a Facilitator audit a Sub-Circle for potential breakdown. #### 5.5.1 Breakdown from Failed Governance The Facilitator may declare a Process Breakdown if a Proposal fails to resolve after reasonable time and effort. #### 5.5.2 Restoring Process When Process Breakdown is declared: - **(a)** The Facilitator gains authority to judge the logic and relevance of arguments in the Circle. - **(b)** The Super-Circle's Facilitator gains a Project to restore due process. - **(c)** The Super-Circle's Facilitator may take over as Facilitator or Secretary. - **(d)** The Super-Circle's Facilitator may assign an additional Circle Lead whose decisions supersede conflicting ones from other Circle Leads. These authorities end when due process is restored (as judged by the Super-Circle's Facilitator). If there's no Super-Circle, all powers vest in the Circle's own Facilitator. #### 5.5.3 Escalation A Process Breakdown in one Circle doesn't automatically mean its Super-Circle is in breakdown. But if it goes unresolved for an unreasonable time, the Super-Circle is also considered in breakdown. ### 5.A Programmatic Governance Outputs Governance proposals, objections, integrations, and adopted changes processed through authenticated programmatic interfaces carry the same constitutional authority as those processed in synchronous meetings. The Governance Platform's record is the authoritative record. The Secretary must ensure programmatically processed governance is reflected in the official record. --- ## Amendment Process Amendments to this Constitution are processed as governance tensions through the Anchor Circle, subject to: 1. Amendments to the Orchestrator Role (§1.3.3.A) or the Kill Switch (§4.1.A(d)) are Key Decisions requiring the Orchestrator's affirmative participation. 2. Amendments expanding Designated Agent authority beyond the Capability Envelope framework require a governance proposal and an update to the relevant Formation Document. 3. Amendments to the Delegated Role-Filler framework (§1.2.7, §4.1.B) require the Orchestrator's affirmative participation. 4. The Ratifier may amend this Constitution at any time as Manager, consistent with the Operating Agreement, provided amendments are processed as governance tensions where practicable. --- ## Version History | Version | Date | Changes | |---|---|---| | 1.0 | April 2026 | Initial fork from Holacracy® Constitution v5.0. Integrated: §1.2.6 (Agent Role Leads), §2.4 removal (Relational Agreements), §3.1.A (Programmatic Attendance), §1.3.3.A (Orchestrator), §4.1.A (Agent Constraints), §5.A (Programmatic Governance Outputs), §1.2.7 (Delegated Role-Fillers), §4.1.B (Delegated Role-Filler Constraints), §5.1 clarification, §1.4.2 update. | | 1.1 | April 2026 | Natural language rewrite for clarity. No substantive rule changes from v1.0. All governance rules preserved; procedural choreography separated from authority logic; defined-term density reduced through inline glossing. | --- ## License This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0/). --- *Derived from the Holacracy® Constitution v5.0 (HolacracyOne, LLC) under CC BY-SA 4.0. "Holacracy" is a registered trademark of HolacracyOne, LLC. "PowerShift" is a registered trademark of powershift.io, LLC.* *Dynamic steering applies. Keep pedaling.*