Essay
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.
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.
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 Five Execution Patterns
Pattern 1 — Circle Direct Execution
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.
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
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.
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.
Pattern 3 — External Contractor
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. 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.
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.
Pattern 4 — Persistent Internal Execution Body
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 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.
When it suits: The organisation has reached a scale where persistent operational infrastructure is necessary. Critical assets 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 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 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.
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 can create rigidity and bureaucratic inertia before the governance layer has matured enough to supervise it well.
Pattern 5 — Hybrid Execution
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. 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.
Task Characteristics and Pattern Selection
| Task Characteristic | Preferred Patterns |
|---|---|
| Bounded deliverable | xSTF or External Contractor |
| Recurring operation | Persistent Execution Body |
| Requires stable custody | Persistent Execution Body |
| Requires professional certification | 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 (audit/evaluation) | External Contractor |
| Cross-domain coordination | Multi-Circle xSTF |
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.
Execution Patterns Across Organisation Types
Open-source software consortium: Repository custodians and infrastructure operators → Persistent Internal Execution Body. Specification drafting → xSTF. Legal and compliance → External Contractor or execution body legal function. Security audits → External Contractor (independence required).
Decentralised research collective: Fieldwork, laboratory operations, data management → Persistent Internal Execution Body. Peer review → xSTF. Grant management, financial reporting → Persistent Internal Execution Body. Ethical review → xSTF with high W_h in ethics.
Global non-profit or NGO: Field operations, regional offices → Persistent Internal Execution Body. Specialised programme delivery → External Contractor. Investigation and evaluation → External Contractor (independence). Communications → Circle Direct or xSTF.
Decentralised Autonomous Organisation (DAO): Multi-sig wallet custodianship → Persistent Internal Execution Body or formally appointed individual custodians. Protocol deployment → xSTF or execution body technical team. Legal entity representation → External legal counsel or registered execution body entity. Community programmes → xSTF or Circle Direct.
Establishing a Persistent Execution Body
The execution body is established by Resolution. The Circle with mandate over organisational structure 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. Custodial mandates are explicit — what it holds, it holds because the Collective said so. Constraint reporting is a formal obligation, not an assumption. And the execution body cannot govern itself — its internal structure is management; any action that affects the Collective's governance, commitments, or assets requires a Circle mandate.
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
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.