Essay · ch. 3 of 10
PAAS — Operational Execution
How enacted resolutions become real-world action
PAAS governs decisions. It does not govern implementation. Every enacted Resolution produces a mandate — a legitimate, audited instruction to act — but the mandate is not the action. Between "the Circle has decided" and "the thing has been done" lies an execution gap, and how that gap is bridged is one of the most consequential choices a PAAS-governed organisation makes.
The accountability invariant: No matter how a Resolution is executed, the Circle that held mandate over the decision owns the outcome. The aSTF audits the Circle, not the execution agent. The execution pattern does not move accountability — it only shapes how accountability is exercised.
Part I: The Execution Gap¶
A Resolution is enacted. The Integrity Engine has applied any system-bound parameter changes. A non-system directive now sits on record, addressed to one or more implementing Circles. What happens next is outside PAAS's governance mechanics — it belongs to the world.
The gap has several dimensions:
Physical custody. Some execution requires persistent access to real assets — a bank account, a code repository, a registered legal entity, a server. These assets cannot be held by a governance body that rotates its composition every few weeks. Someone, somewhere, must hold the keys — not as a governance act, but as a custodial one.
Continuity. Some tasks recur. Running payroll, maintaining infrastructure, filing regulatory returns — these cannot be re-commissioned from scratch each cycle. The expertise and institutional memory required to do them reliably accumulates in the doing of them. Temporary bodies disperse that accumulation.
Specialisation depth. Some execution requires expertise that is not present in the governing membership, nor easily assembled ad hoc. A Circle may legitimately decide to commission a coral reef survey without containing a single marine biologist.
Legal standing. Some actions require a named, legally recognised person or entity to execute — a signatory, a director, a registered contractor. Governance membership does not confer legal standing.
The execution patterns below address these dimensions in different combinations. Choosing the right pattern is itself a governance judgment — one the responsible Circle makes, subject to aSTF review.
Part II: Execution Patterns¶
Pattern 1 — Circle Direct Execution¶
What it is: The Circle members themselves perform the work, using their own capabilities and access. No separate execution body is involved. The deciders are also the doers.
When it suits: - The task is within the direct skill set of Circle members - No specialised access, custody, or legal standing is required - The task is bounded and completable within the Circle's active period - Speed and directness are valued over specialisation depth
How accountability works: The Circle is the executor and the decider. There is no accountability gap. The aSTF audits the Circle's decision and its execution in the same review.
Examples: - A Governance Circle that decides to revise its own onboarding documentation and writes the revision itself - A Communications Circle that decides to publish a statement and publishes it - A Research Circle reviewing and approving submitted papers when its members are themselves domain experts
Limitations: As the task grows in scale, duration, or required specialisation, direct execution becomes burdensome. Circle members are governance participants first — overloading them with execution work degrades deliberation quality.
Pattern 2 — xSTF Execution¶
What it is: The Circle commissions an Executional Short-Term Facilitator (xSTF) for the task. The xSTF is assembled, executes the mandate, files its deliverable, and dissolves. The Circle receives the work product and remains the accountable party.
When it suits: - The task requires competences not concentrated in the commissioning Circle - The task is bounded in time and deliverable - The work benefits from a fresh team assembled specifically for the purpose - The task does not require persistent custody of assets or legal standing - Cross-domain coordination is needed (multi-Circle xSTFs handle this cleanly)
How accountability works: The xSTF reports to the commissioning Circle. The Circle owns the work product. If the deliverable is used as the basis for a subsequent motion, that motion's aSTF review will examine both the quality of the work product and the Circle's judgment in accepting and acting on it.
Examples: - A Treasury Circle commissions an xSTF to research funding mechanisms for a proposed programme before a budget motion is filed - A Protocol Engineering Circle commissions a multi-Circle xSTF to draft a specification that affects both security and user experience domains - A Membership Circle commissions a vSTF to verify a credential claim — this is itself a specialised xSTF variant with a defined process
Limitations: xSTFs dissolve. A task that recurs, requires persistent access, or builds institutional memory across cycles is poorly served by a mechanism designed for bounded, temporary work. The xSTF pattern works best for defined outputs, not ongoing operations.
Pattern 3 — External Contractor¶
What it is: The Circle commissions a third party — an individual, firm, or organisation external to the Collective — to perform the work. The contractor operates under normal contractual terms, not governance terms. They have no governance standing in the Collective; their relationship to it is commercial.
When it suits: - The required expertise does not exist within the Collective's membership - The task is bounded and contractually specifiable - Legal standing or professional certification is required (a licensed surveyor, a registered audit firm, a qualified legal counsel) - The task produces a deliverable the Circle can evaluate and accept - The Collective does not need or want to internalise the capability
How accountability works: The commissioning Circle is accountable for the quality of the brief it issued, the selection of the contractor, and its judgment in accepting the deliverable. The contractor is accountable under the contract's terms. The aSTF does not audit the contractor — it audits the Circle's stewardship of the engagement.
Examples: - A Legal Circle engages an external law firm to draft terms and conditions for the organisation's public agreements - A Research Circle commissions an independent laboratory to conduct fieldwork that the Collective has mandated but cannot perform internally - A Treasury Circle appoints an external auditor for the annual financial review - A Technology Circle contracts a security firm to conduct a penetration test
Limitations: External contractors have no continuity obligation beyond the contract term. Institutional knowledge leaves with them. Recurring or operationally critical functions are poorly served by repeated external contracting — the overhead is high and the knowledge never accumulates inside the organisation.
Pattern 4 — Persistent Internal Execution Body¶
What it is: The Collective establishes a standing execution body — a distinct organisational entity, not a governance body — that exists to carry out the mandates of the Collective's Circles on an ongoing basis. This body has its own internal structure, employs or engages its own personnel, and holds the custodial assets (credentials, accounts, legal standing) that persistent operations require.
This pattern is the organisational equivalent of each Circle independently contracting for its own execution needs, but pooled into a single body for efficiency, continuity, and coordination. Where each Circle would otherwise maintain its own contractors, the persistent execution body provides those capabilities centrally — with internal departments or teams mapping to what each Circle would otherwise commission separately.
When it suits: - The organisation has reached a scale where persistent operational infrastructure is necessary - Critical assets (accounts, repositories, legal registrations, physical premises) require stable custodians who are not governance participants - Operational continuity across Circle compositions is essential - Specialist staff need to build and retain institutional knowledge - Legal or regulatory obligations require named, accountable individuals in operational roles
How accountability works: Each Circle supervises the part of the execution body whose work falls within its mandate — exactly as it would supervise an xSTF it commissioned. The execution body does not govern; it executes under mandate. A Circle's instruction to the execution body flows from an enacted Resolution. The execution body surfaces operational constraints (capacity, resource limits, technical blockers) back to the relevant Circle as factual input into deliberation — not as governance acts, but as the information the Circle needs to govern well.
The aSTF audits the Circle on its stewardship of this relationship: did the Circle's instructions to the execution body reflect the enacted Resolution faithfully? Did the Circle act appropriately on constraints the execution body surfaced? Did the deliverable match the mandate?
The brain-body relationship: The Collective is the governing mind; the execution body is the operational body through which it acts in the world. The body has no will of its own in governance terms — it manifests the decisions of the mind. But the body can and must report accurately on what is physically possible. A Circle may instruct a programme to be funded; the execution body's finance team reports that current reserves are insufficient. The Circle then decides what to do with that information. The execution body does not override the Circle — it informs it.
Personnel and governance membership: Staff in the execution body may or may not be members of the Collective. Where they are, their governance membership and their operational role are entirely separate. A staff member who is also a Circle member exercises governance authority as a Collective member — their operational role gives them no additional governance standing. Equally, their Circle membership gives them no operational authority beyond their defined role in the execution body.
This separation is essential. The same person may scrutinise a report filed by their own operational department while sitting in their Circle capacity. The role separation is structural, not honorary.
Examples:
Open-source software consortium: The execution body employs the people who hold the repository merge permissions, manage the CI/CD infrastructure, handle financial accounts, and maintain legal registrations. Protocol changes are decided by the Protocol Engineering Circle; the execution body's technical team implements them. The person who actually merges pull requests works for the execution body — they may or may not be a Collective member. Their merge action is the execution of a Circle mandate, not a governance act.
Climate research collective: The execution body houses the research department (laboratory staff, field teams, data managers), the administration team (payroll, procurement, travel logistics), and the legal team (contracts, compliance, grant management). Research priorities are decided by the Research Circle; the execution body's research department carries them out. When the execution body's administration reports that a proposed programme exceeds available budget, the Treasury Circle decides whether to reallocate, defer, or seek additional funding.
Global non-profit: The execution body runs the regional offices — employing field staff, holding local bank accounts, maintaining relationships with in-country partners. The Community Relations Circle sets programme priorities; the regional offices execute them. A regional director approached by the Collective's representatives to take on that role may never become a Collective member — they are employed to execute, not to govern.
Limitations: A persistent execution body introduces organisational complexity and the overhead of managing an ongoing employment or contracting relationship. It is appropriate only when the organisation has reached sufficient scale and stability to justify it. Premature institutionalisation of an execution body can create rigidity and bureaucratic inertia before the governance layer has matured enough to supervise it well.
Pattern 5 — Hybrid Execution¶
What it is: A combination of the patterns above, applied across different parts of a single mandate — or across the organisation's different operational domains. A Circle may use its execution body for ongoing operational work while commissioning an external specialist for a bounded deliverable within the same programme. An xSTF may be assembled to design a system that the execution body will then operate.
When it suits: - Different components of a mandate have genuinely different execution requirements - A transition is underway — the organisation is building towards a persistent execution body and is using external contractors and xSTFs in the interim - A specific deliverable requires external specialist input even within a programme the execution body otherwise handles
How accountability works: Each component is supervised by the relevant Circle using the accountability model appropriate to its execution pattern. The Circle must ensure that the components integrate coherently — coordination across patterns is a governance responsibility, not an execution one.
Example: A Technology Circle decides to migrate the organisation's infrastructure to a new platform. The execution body's technical team handles the ongoing migration work (Pattern 4). An external security firm conducts an independent audit of the new architecture before cutover (Pattern 3). A cross-Circle xSTF coordinates the migration timeline with the Communications and Community Circles (Pattern 2). The Technology Circle owns the whole.
Part III: Task Characteristics and Pattern Selection¶
The following characteristics should inform the pattern choice. No single characteristic is determinative — the combination matters.
Permanence and Continuity¶
| Need | Suited Patterns |
|---|---|
| One-time bounded deliverable | External Contractor, xSTF |
| Recurring but episodic | xSTF (recommissioned), External Contractor |
| Continuous ongoing operation | Persistent Internal Execution Body |
| Long-term institutional memory required | Persistent Internal Execution Body |
Custody Requirements¶
| Custody Type | Suited Patterns |
|---|---|
| No special custody needed | Any |
| Custodial access to accounts, credentials, repositories | Persistent Internal Execution Body |
| Legal registration or named signatory required | Persistent Internal Execution Body, External Contractor (where legal standing is their specialty) |
| Professional certification required for the act | External Contractor |
Specialisation¶
| Specialisation Profile | Suited Patterns |
|---|---|
| Competence exists in the Circle | Circle Direct Execution |
| Competence exists in the wider membership | xSTF |
| Competence must be built and retained internally | Persistent Internal Execution Body |
| Competence exists externally and need not be internalised | External Contractor |
Scale and Frequency¶
| Scale / Frequency | Suited Patterns |
|---|---|
| Small, occasional | Circle Direct, xSTF, External Contractor |
| Large, occasional | External Contractor, xSTF (multi-Circle) |
| Small, continuous | Persistent Internal Execution Body (team within it) |
| Large, continuous | Persistent Internal Execution Body |
Security and Sensitivity¶
| Security Profile | Suited Patterns |
|---|---|
| General work, no elevated security considerations | Any |
| Requires stable, named, accountable individuals | Persistent Internal Execution Body |
| Requires external independence (e.g. financial audit) | External Contractor |
| Requires internal independence (e.g. integrity audit) | aSTF / jSTF (these are PAAS-native, not execution patterns) |
Part IV: The Accountability Invariant in Detail¶
Regardless of execution pattern, the accountability chain is:
Resolution enacted
→ implementing Circle receives mandate
→ Circle supervises execution
→ execution produces outcome
→ Gate 2 aSTF audits the Circle's stewardship
→ Integrity Engine logs determination
The execution agent — whether an xSTF, an external contractor, or a persistent execution body — is the Circle's extended arm. The Circle does not transfer accountability when it delegates execution. It extends its reach while retaining its obligation.
What "supervises" means in practice:
Supervision is not micromanagement. A Circle that has mandated the construction of a facility does not supervise every pour of concrete. It supervises:
- That the brief it issued reflected the enacted Resolution faithfully
- That constraints surfaced by the execution agent were acted on appropriately
- That the deliverable, when received, is assessed against the mandate
- That deviations — whether justified by operational necessity or not — are documented and disclosed
A Circle that accepts a deliverable that materially diverges from the Resolution, without documenting why, will face that gap in Gate 2. A Circle that acts appropriately on an execution body's constraint report — filing a new motion to adjust the mandate — is exercising good stewardship, not admitting failure.
What the execution agent owns:
The execution agent owns the quality of its own work. A contractor who delivers substandard work is accountable under contract. An xSTF that files a misleading report is accountable under PAAS's judicial track. A persistent execution body whose finance team misrepresents the organisation's financial position faces consequences through the employment relationship and, where a Collective member is involved, through the judicial track.
These are separate accountability channels. They do not relieve the Circle of its stewardship obligation — they run in parallel with it.
Part V: Dual Roles — Governance and Execution¶
In practice, especially in smaller organisations, the same individuals often participate in both governance (as Collective members) and execution (as staff, contractors, or operational agents). This is structurally unproblematic provided the roles are kept analytically separate.
The separation is functional, not physical. A person wearing their Circle hat exercises governance authority. The same person wearing their operational hat executes mandates. Neither hat gives them powers that belong to the other.
The functional separation matters most in two situations:
When a Circle member's operational role gives them information relevant to a deliberation: They should bring that information into the Cell as a contribution, attributed to them, subject to the same deliberation as any other evidence. Their operational insight is valuable input — it does not become a governance veto.
When a Circle is deliberating on a matter that affects the execution body: A Circle member who is also staff in the execution body should declare that dual role. Their competence still applies; their independence is reduced. The aSTF composition balancer will factor this in.
Examples of clean dual roles:
A staff member in the execution body's technical team is also a member of the Technology Circle. When the Circle deliberates on infrastructure architecture, her operational knowledge of what the current systems can support is directly relevant input. She brings it as a contribution; the Circle weighs it alongside other evidence. When the Circle's decision produces a mandate for the technical team, she implements it as a staff member — her Circle membership gives her no special authority to interpret or vary the mandate.
A finance officer in the execution body is also a Circle member in the Treasury Circle. When the Treasury Circle deliberates on budget allocation, his operational knowledge of the organisation's actual cash position and committed expenditure is essential context. He provides it as a contributor. When the Treasury Circle issues a mandate that affects the finance team, he implements it. If the mandate is operationally difficult, he reports that constraint through the appropriate channel — not by exercising his Circle membership to reopen deliberation unilaterally, but by surfacing the constraint to the Circle through the normal reporting relationship.
Part VI: Execution Patterns Across Organisation Types¶
Open-Source Software Consortium¶
Typical mandate portfolio: Protocol decisions, contribution standards, release schedules, security policy, governance of the specification process.
Execution considerations: Code review and merge authority requires stable, trusted individuals holding repository access. These cannot be rotated through xSTFs without creating security and continuity risk. Community management, documentation, and conference organisation suit xSTF or lightweight execution body models.
Suggested pattern mix: - Repository custodians and infrastructure operators → Persistent Internal Execution Body or long-term appointed roles with formal custodial mandate - Specification drafting → xSTF (competence-assembled for each major version) - Legal and compliance (entity filings, licence enforcement) → External Contractor or execution body legal function - Security audits → External Contractor (independence required)
Decentralised Research Collective¶
Typical mandate portfolio: Research priorities, publication standards, grant allocation, ethical review, data governance.
Execution considerations: Fieldwork and laboratory work require specialist staff. Grant management and financial reporting require persistent custodianship. Peer review suits the xSTF model naturally — it is exactly the kind of bounded, competence-assembled, episodic work xSTFs are designed for.
Suggested pattern mix: - Fieldwork, laboratory operations, data management → Persistent Internal Execution Body or contracted research teams - Peer review → xSTF (the governance-native form of this already common practice) - Grant management, financial reporting → Persistent Internal Execution Body - Ethical review of novel research proposals → xSTF with high W_h in ethics and relevant domain (maps to the existing aSTF/judicial track logic)
Global Non-Profit or NGO¶
Typical mandate portfolio: Programme priorities, beneficiary criteria, resource allocation, partner relationships, public communications.
Execution considerations: Regional delivery requires on-the-ground staff with local knowledge, relationships, and in some cases legal standing in local jurisdictions. These staff need not be Collective members — the Collective commissions programmes, the field teams deliver them.
Suggested pattern mix: - Field operations, regional offices → Persistent Internal Execution Body (regional teams as internal departments) - Specialised programme delivery (e.g. medical intervention) → External Contractor with relevant professional qualification - Investigation and evaluation → External Contractor (independence from the programmes being evaluated) - Communications, knowledge products → Circle Direct or xSTF
Decentralised Autonomous Organisation (DAO)¶
Typical mandate portfolio: Protocol governance, treasury allocation, partnership agreements, community programmes.
Execution considerations: Treasury management requires persistent custodianship of wallet access. Protocol changes require individuals with technical authority to deploy contracts. Legal agreements may require a registered legal entity.
Suggested pattern mix: - Multi-sig wallet custodianship → Persistent Internal Execution Body or formally appointed individual custodians with clear mandate and accountability framework - Protocol deployment → xSTF (bounded, specific, auditable) or execution body technical team - Legal entity representation → External legal counsel or registered execution body entity - Community programmes → xSTF or Circle Direct
Part VII: Establishing a Persistent Execution Body¶
For organisations that have determined that a persistent execution body is appropriate, the following design considerations apply.
The execution body is established by Resolution. The Circle with mandate over organisational structure — typically a Governance Circle — files a motion to establish the body, defining its scope, its relationship to each Circle, its reporting obligations, and the custodial mandates it will hold. The aSTF reviews whether this structure is consistent with the Collective's tenets and enacted governance parameters.
The execution body's structure mirrors the Collective's governance domains. If the Collective has Circles for Treasury, Technology, Research, and Community, the execution body will have departments or functional teams corresponding to each. Each Circle supervises its corresponding part of the execution body. Cross-functional issues within the execution body are surfaced to the relevant Circles jointly.
Custodial mandates are explicit. Each asset the execution body holds on behalf of the Collective — accounts, credentials, registrations, physical assets — should be explicitly defined in the establishing Resolution or in subsequent Resolutions. The execution body does not accumulate custodial authority informally. What it holds, it holds because the Collective said so.
Constraint reporting is a formal obligation. The execution body's obligation to report operational constraints to the relevant Circles should be defined, not assumed. A finance team that knows a programme is underfunded has an obligation to say so — the mechanism for doing so should be established in advance, not improvised under pressure.
The execution body cannot govern itself. Its internal structure, employment terms, and operational procedures are matters of management. But any action that affects the Collective's governance, commitments, or assets requires a Circle mandate. The execution body does not pass resolutions; it receives them.
Summary¶
EXECUTION PATTERN SELECTION GUIDE
Task characteristic → Preferred pattern(s)
─────────────────────────────────────────────────────────────
Bounded deliverable → xSTF or External Contractor
Recurring operation → Persistent Execution Body
Requires stable custody → Persistent Execution Body
Requires professional cert. → External Contractor
Expertise in Circle → Circle Direct
Expertise in membership → xSTF
Expertise must be retained → Persistent Execution Body
Legal standing required → Execution Body or Ext. Contractor
Independence required → External Contractor
(for audit / evaluation)
Cross-domain coordination → Multi-Circle xSTF
─────────────────────────────────────────────────────────────
ACCOUNTABILITY INVARIANT (always)
Execution agent executes
Circle supervises and owns the outcome
aSTF audits the Circle's stewardship
Integrity Engine logs the determination
─────────────────────────────────────────────────────────────
DUAL ROLE PRINCIPLE (always)
Governance authority flows from Circle membership
Operational authority flows from the employment or
contractual relationship with the execution body
Neither contaminate the other
Dual roles must be declared in relevant deliberations
The execution pattern chosen is itself a governance decision — one the responsible Circle makes, documents, and owns. The aSTF will, in time, assess whether the pattern served the mandate well. Organisations that choose their execution patterns deliberately, match them to the characteristics of the tasks they face, and supervise them actively are doing the work of governance. The system is designed to support that work, not to substitute for it.
PAAS Operational Execution — Patterns and Guidance Companion document to OrbSys_v7.md, OrbSys_engines_v2.md, OrbSys_bootstrap_v2.md Addresses the execution layer downstream of enacted Resolutions.