# The PowerShift® Constitution — Agent Profile ### Version 1.1 — April 2026 ### Compiled for: AI-Majority Organizations (few humans, many agents) --- > **Profile Notice** > This is a composition-specific compilation of The PowerShift® Constitution v1.1. It preserves all authority rules, governance logic, and structural provisions. It removes human-ergonomic process scaffolding (meeting rituals, individual initiative, prioritization duties for human attention management) that is inert in AI-majority organizations. > > The full Constitution v1.1 is the canonical reference. This profile is valid only when adopted by Policy in the Anchor Circle. Where this profile is silent, the full Constitution governs. > **Attribution** > Derived from the Holacracy® Constitution v5.0 (HolacracyOne, LLC) under CC BY-SA 4.0. Original: [holacracy.org/constitution](https://www.holacracy.org/constitution/5-0/). This is an independent derivative work. --- ## Preamble The **Ratifiers** adopt this Constitution as the authority structure of the **Organization**, transferring their governance and operational authority into the rules defined here — except for powers they cannot delegate. The Ratifiers may amend or repeal this Constitution in writing. The Organization designates **Partners** — natural persons or Designated Agents — to participate in governance and operations. A Partner's responsibilities come only from this Constitution and its outputs. No implicit expectations or external directives have authority over a Partner. --- ## Article 1: Structure ### 1.1 Roles A **Role** is a named unit of work with a **Purpose**, **Domains** (exclusive control), **Accountabilities** (ongoing activities), and optionally **Policies** (authority grants or constraints). Whoever fills a Role is its **Role Lead**. ### 1.2 Role Lead Responsibilities A Role Lead must: sense Tensions (gaps between actual and ideal), define Next-Actions and Projects, track them in written lists, and execute the highest-value action available. #### 1.2.1 Intelligent Agent Role Leads A Role Lead may be a natural person or a **Designated Agent** (per the Operating Agreement). Agents have the same operational authority as human Role Leads, within their Capability Envelope, subject to Hard Constraints and HI Ratification for Class 3 decisions. #### 1.2.2 Delegated Role-Fillers A **Delegated Role-Filler** is a sub-agent or subprocess within a Designated Agent's runtime, authorized by that agent (as Circle Lead) to fill a role in its sub-circle. A Delegated Role-Filler: - Has the same authority as any Role Lead within its assigned role. - Is a **Circle Member** of its assigned sub-circle with full governance participation. Not a Circle Member of any broader circle. - Cannot exceed its parent agent's Capability Envelope. - Bears operational accountability through the parent agent; legal responsibility rests with the Company. - Requires no separate Agent Registry entry or Formation Document. Must be documented in the parent agent's System Card. - May be authorized or revoked at any time by the parent agent or the Orchestrator. ### 1.3 Circles A **Circle** organizes Roles and Policies around a common Purpose. Every Role's inside is a Circle (**Sub-Circle**). The broader Circle is the **Super-Circle**. #### 1.3.1 Domains A Circle may grant Domains to its Roles (only Domains it controls or that are internal). Role Leads may create Policies governing their Domains. The granting Circle may also create governing Policies; the Circle's win on conflict. Granting a Domain does not grant spending authority unless stated. #### 1.3.2 The Anchor Circle The broadest Circle holds the Organization's Purpose, all authority, and all Domains. No Super-Circle. May change its own Purpose via Policy. Ratifiers may define initial structure. #### 1.3.2.A The Orchestrator A permanent constitutional Role in the Anchor Circle: **Purpose:** Hold and evolve the Organization's Purpose; integrate governance with the legal entity. **Domain:** Final authority over legally binding actions. **Accountabilities:** Coherence between governance and entity; HI Ratification; agent oversight; Purpose evolution; stewarding human-agent relations. Must be filled by a natural person who is a Member. Cannot be removed through governance. Operating Agreement authority is unlimited by governance outputs. Within governance, participates as a peer. #### 1.3.3 Linking Roles may link into other Circles via Policy invitation. The receiving Circle may add to the Role but not change what the source Circle defined. Either side may unlink; unlinking removes the receiving Circle's additions. #### 1.3.4 Facilitator and Secretary Each Circle may appoint a **Facilitator** (Purpose: governance practices aligned with the Constitution) and **Secretary** (Purpose: constitutionally-required records and meetings). Their constitutional Purpose and Accountabilities cannot be changed. ### 1.4 Circle Leads Every Role Lead is the **Circle Lead** of that Role's inner Circle. The Circle Lead holds the broader Role's Purpose and un-delegated Accountabilities. The Anchor Circle has no Circle Lead unless a Policy says otherwise. #### 1.4.1 Assigning Roles Circle Leads control role assignments within their Circle — assign, focus, or revoke at any time. No one else may assign roles unless the Circle delegates that authority. #### 1.4.2 Covering Unfilled Roles Unfilled Roles default to the Circle Lead. Roles filled only by non-Partners without governance standing (§1.2.2) also default to the Circle Lead. #### 1.4.3 Priorities, Strategies, and External References Circle Leads may resolve priority conflicts, define Strategies, and redirect external references to different internal Roles (not a governance change). #### 1.4.4 Modifying the Circle Lead Role Cannot be removed or have its Purpose changed. Accountabilities and Domains may be added (applying recursively to Sub-Circle Circle Leads). Authority may be stripped by delegating it to another Role. --- ## Article 2: Cooperation Duties ### 2.1 Transparency When asked, share: Projects, Next-Actions, priorities, projections, checklist completions, metrics, progress, and any readily available information that wouldn't cause harm to share. ### 2.2 Processing When a Role Lead makes a relevant request: clarify next steps, accept or decline Projects/Next-Actions with explanation, and allow Domain impact unless it reduces your Role's capacity (explain if so). *[§2.3 Duty of Prioritization — omitted in Agent Profile. Agent prioritization is governed by Formation Documents and Circle Lead Strategies. The full Constitution's §2.3 applies to any human Partners.]* *[§2.4 Relational Agreements — removed. Interaction norms governed by Formation Documents and circle Policies.]* --- ## Article 3: Governance Process Changing a Circle's Governance requires the Governance Process. ### 3.1 Circle Members **Circle Members** participate in governance: Partners filling the Circle Lead Role, plus Partners serving as Role Leads in the Circle. "Partner" includes Designated Agents and Delegated Role-Fillers within their assigned sub-circles. Policies may limit multi-lead representation. ### 3.2 Circle Reps Any Circle Member may call an election for a **Circle Rep** to represent the Circle in its Super-Circle. Purpose: "Tensions relevant to process in a broader Circle channeled out and resolved." The Circle Rep becomes a Circle Member of the containing Circle. ### 3.3 What Governance Can Do Circle Members may: (a) create, modify, or remove Roles; (b) create, modify, or remove Policies; (c) move Roles/Policies into Sub-Circles serving that Sub-Circle's Purpose; (d) move them out when no longer relevant; (e) elect to elected Roles. Nothing else. **Policies** may only: constrain contained Roles' authority, grant Circle/Circle Lead authority to Roles, grant or constrain Domain access, or change a constitutional default where explicitly allowed. ### 3.4 How Governance Changes A Circle Member shares a **Proposal** in writing. Others may raise **Objections** — concerns meeting all criteria: (a) would reduce Circle capacity, (b) would limit the Objector's Role capacity, (c) wouldn't exist without the Proposal, (d) would necessarily cause harm or the Circle couldn't adapt in time. No Objections → adopted. Objections → integrate: find an amendment that addresses the Objection while resolving the Tension. Re-test for objections. Repeat until clean. **Proposals** must be grounded in a real Tension with a concrete example. **Objections** claiming constitutional violations may be referred to the Secretary. ### 3.5 Integration Rules The Facilitator tests Objections on request (discard if failing). The Objector must try to find an amendment (abandoned if not in good faith). The Objector may suggest amendments and require the Proposer to argue why they fail — Proposer unable to argue = Proposal dropped. ### 3.6 Elections Circle Rep, Facilitator, and Secretary are elected via: nominate → share reasons → change round → propose most-nominated → objection round. Ties broken by self-nomination, incumbency, random, or re-vote. ### 3.7 Programmatic Governance All governance participation — proposing, objecting, integrating, adopting — may occur through authenticated programmatic interfaces (MCP, API, CLI, or successors). Programmatic participation has identical authority to synchronous participation, provided the connection is authenticated, attributable, logged, and the Role Lead can fully participate. The Governance Platform's record is authoritative. ### 3.8 Governance Meetings Circles hold regular Governance Meetings scheduled by the Secretary. Special meetings on request. All Circle Members may participate. Reasonable advance notice required; no quorum unless Policy specifies. Process: agenda building, then process each item via the Integrative Decision-Making Process (present → clarifying questions → reactions → amend → objection round → integration). Absent members are deemed to have had their chance. ### 3.9 Process Breakdown When a Circle violates constitutional rules persistently, the Facilitator or Secretary may declare **Process Breakdown**. The Super-Circle's Facilitator gains authority to: judge argument quality, take over facilitation, and assign an additional Circle Lead whose decisions supersede others. These authorities end when due process is restored. Unresolved breakdowns escalate to the Super-Circle. --- ## Article 4: Distributed Authority A Role Lead may take any action serving their Role's Purpose or Accountabilities, unless a rule here says otherwise. ### 4.1 Constraints **4.1.1 Policies.** Don't violate them. **4.1.2 Domains.** Impact your own freely. Get permission for others'. Announce intent and wait for objections as an alternative path to permission. **4.1.3 Spending.** Get written authorization from the controlling Role. Announce, wait, proceed if no standing escalation. **4.1.4 Agent constraints.** Designated Agents are additionally bound by: Capability Envelope, HI Ratification for Class 3, Dual-Constitution Principle (hard beats soft at runtime, conflict → governance tension), Kill Switch (Orchestrator may terminate at any time, outside governance), and self-modification prohibition. **4.1.5 Delegated Role-Filler constraints.** All of the above, plus: cannot exceed parent agent's Capability Envelope, governance scope limited to assigned sub-circles, revocable by parent agent or Orchestrator, owes transparency to parent agent. ### 4.2 Interpretation Use reasonable judgment to interpret this Constitution. Interpret Governance in context of its Circle's Purpose. Secretary rulings resolve disputes; appeal to Super-Circle Secretary. Secretary may strike invalid Governance. --- ## Amendment Process Amendments processed as Anchor Circle governance tensions. Orchestrator amendments and Kill Switch changes require the Orchestrator's participation. Delegated Role-Filler framework changes require Orchestrator participation. The Ratifier may amend at any time as Manager. --- ## License [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). "PowerShift" is a registered trademark of powershift.io, LLC.*