Joint Operating Committee - Capabilities Deployment, Part V

 Capabilities Deployment — Part Five: Epistemes

We have recently begun referring to Epistemes within Synallagi. The capability they represent has always been part of our design. What needed clarification was the dual role previously assigned to the Work Order. We have therefore separated those roles into two distinct products. The Work Order retains its traditional purpose of assigning time and resources to work. The Episteme gives a separate identity to the coordinated research and development of knowledge and capabilities. Both organize work and resources; the distinction makes their respective purposes clearer.

Artificial Intelligence presents an opportunity to reinvigorate engineering and geological research constrained by inadequate financial resources. One of the important relationships identified through People, Ideas & Objects’ research is the reciprocal development of science and innovation. Scientific research informs innovation. Applying those innovations generates evidence, questions and discoveries that further develop the sciences. Our ability to move through that cycle more quickly, while maintaining the quality of the work, will determine how rapidly capabilities advance.

Producers have their own responsibility: developing the highly specialized capacities and capabilities needed to advance the engineering and geological sciences and apply them commercially. The generic, “soup-to-nuts” producer-operator model becomes increasingly difficult to sustain as the depth of expertise required expands. Each producer cannot economically maintain every specialization when its own operations provide insufficient work to keep those specialists productively engaged. The resources required to compete across every discipline would overwhelm the commercial value of doing so.

The market solution proposed within Synallagi’s Capabilities Deployment sub-module addresses this problem. Producers can develop depth in particular capabilities, undertake research that advances those capabilities, and make them available to others through the marketplace. They can also obtain complementary expertise from other participants. Specialization becomes commercially viable when a capability can serve a broader market, providing the volume of work needed to sustain both its application and its continued development.

This is where the Episteme has a practical role. Consider ten small producers with a shared hypothesis that could have applications across their operations. The cost of investigating it may be prohibitive for any one of them. Together, they could pool financial resources, technical knowledge, relevant data and operating experience, supported by substantial Artificial Intelligence capacity. Their engineers and geologists would define the hypothesis, direct the investigation and evaluate the resulting evidence.

The purpose would be to establish whether the hypothesis holds, under what conditions it applies, and whether it can support a commercially useful capability. A successful result could become part of the participating producers’ capability offerings. Research that none could justify independently would become possible through shared costs and a broader opportunity to apply the results.

The Episteme therefore connects collective research with the development of specialized capabilities. Those capabilities can subsequently be deployed through Work Orders, with the people, time and resources required for their application. This gives Synallagi a practical means of advancing the question at the centre of Capabilities Deployment: how quickly can hypotheses become profitable production? This is how a producer reduces their organizational latency through applying Synallagi New Discipline of science based pursuit of oil & gas guided by commercial outcomes. 

To pronounce Episteme: 

Defined: 

Part II — Conceptual Model

1. Purpose and placement

Capability Deployment connects a requirement with suitable capabilities, authorized commitments, work, accounting consequences and an evaluation of results. Its commercial purpose is to support reserves preservation, performance and profitability. A need may originate in Planning, a technical observation, an obligation, a financial deficiency or research.

The Engineers and Geologists interface presents the work. Business Operations Management supervises its continuity across sub-modules and service providers. Capability Deployment organizes the engagement. Responsible Synallagi components maintain their own authoritative records, calculations and decisions.

The supervisory role includes identifying dependencies, obtaining authorized results, following progress and referring exceptions to the responsible people. It does not transfer every business function to Business Operations Management. A calculation belongs to the capability responsible for it; the supervisor establishes when its result is required and how an authorized process uses it.

The Marketplace Interface enables engineers and geologists to find and engage vendors, suppliers, service providers and specialized capabilities. This Business Operations Management sub-module connects with the Petroleum Lease, Resource and Financial Marketplace modules. Its detailed functions belong in Business Operations Management — Marketplace Interface.

1.1 Specialists, clients and a New Discipline

Engineers and geologists are the primary users of Business Operations Management. The interface begins with the individual, the selected Joint Operating Committee and the producer or producers represented in that engagement. A specialist may be an employee assigned to the employer's JOCs, an independent professional serving several producers and JOCs, or hold separately approved relationships of both kinds. Capability Deployment manages the business arrangements through which that specialist's capabilities are engaged.

An engagement identifies the specialist, contracting or supplying party, client, beneficiary, represented party and applicable JOC. These roles must remain distinguishable: the organization paying for work, the party represented in an approval and the owner of information need not be the same. Employment or expertise alone does not confer authority in a client context.

Security & Access Control already establishes one persistent Synallagi identity with multiple separately approved assignments. The selected assignment determines information access and permitted action. Switching clients must not transfer another client's data, authority, commitments or Intellectual Property permissions. Ending one assignment removes its derived access without terminating unrelated assignments.

Capability Deployment contributes to a New Discipline: engineers and geologists connect scientific judgment with transaction design, actual economics and accountable results. Reducing Organizational Latency means shortening the interval between recognizing an opportunity or deficiency and carrying out the authorized response. The objective is timely, evidenced action through the appropriate decisions and dependencies.

Planning, Marketplace Interface and Capability Deployment provide connected areas of work within Business Operations Management. Engineers and geologists must participate with the user community in defining and validating the tools they need, during initial development and throughout Synallagi's life. Artificial Intelligence can support scientific productivity within these governed processes; the specialist's access to the interface does not grant an AI agent independent authority.

Success requires engineers and geologists to have clear, complete and timely access to the information and functions needed for their approved work. Employment status must not become an artificial barrier to a client's information. Trust, as a developing Organizational Construct, must be incorporated with explicit representation, accountability, confidentiality and the producer's Intellectual Property rights. These arrangements protect IP and industrial secrets while enabling the work. The design must identify and resolve missing access that prevents success; it must also preserve the agreed client context and disclosure rights.

2. Relationships at a glance

The diagram shows responsibilities and exchanges, not a mandatory sequence or a settled database schema.

flowchart TD

    UI["Engineers and Geologists interface"] --> BOM["Business Operations Management: supervision"]

    BOM --> CD["Capability Deployment: engagement coordination"]

    RC["Producer Research & Capabilities"] -->|Selected publication to a specific JOC| KL["Knowledge     & Learning"]

    PL["Planning and identified requirements"] --> KL

    KL --> CD

    CD --> POOL["Pooling: agreed capabilities and availability"]

    CD --> WO["Work Order: operational financial deployment"]

    CD --> EP["Episteme: retained research functions"]

    FUND["Independent funding approvals and participant AFEs"] --> WO

    FUND --> EP

    CD --> ICC["Industrial Command & Control"]

    ICC --> JOB["Job Order: authorized field instruction"]

    WO --> AC["Accounting Voucher and allocation processes"]

    EP --> AC

    AC --> GL["Participant General Ledgers and Joint Account consequences"]

    MBR["Monthly JOC Material Balance Report"] --> AC

    AC --> REVIEW["Commercial assessment and outcome review"]

    REVIEW --> PL

Security & Access Control applies to every exchange. Autonomous Asynchronous Transaction Orchestration communicates defined work, results and exceptions between service providers. Arrows indicate a business connection; they do not grant access or expenditure authority.

3. The developing Synallagi transaction

A Synallagi is the transaction whose applicable elements and attributes are progressively defined by the modules. Its context connects purpose, parties, representation, authority, agreements, commitments, deployment, evidence, accounting and outcomes.

The conceptual model proposes a persistent transaction reference with links to authoritative records and their relevant versions. Some information may be presented together without being stored together. A technical implementation must preserve both the current position and the basis on which earlier decisions occurred.

Security & Access Control supplies the comparatively stable foundation accepted in A.3. Business Operations Management coordinates the changing business context: approved AFE or Lease expenditure, deployment authority, available commitments, current instructions and results. Comparatively stable does not mean permanently authorized. Authority and permitted access continue to be checked as people, roles and work change.

Not every transaction requires every element. Confidential research need not establish a JOC, operational Work Order, Job Order or Lease. An operational engagement may require several of these. Shared references and exact cardinalities remain to be designed with the user community.

4. Business concepts and responsible functions

The engagement, publication and assessment concepts are proposed model distinctions. Their eventual record names and storage boundaries are not settled by this table.

5. From capability to commitment

A producer develops its strengths and records them in Research & Capabilities. It chooses which information to publish into a specific JOC's Knowledge & Learning context. The publication should identify the capability, permitted audience, supporting information and the version presented.

Discovery, availability and commitment are different facts. A capability can be visible without being available; it can be available without its use being approved. A proposal becomes a commitment only through the applicable authority and terms. The model must allow current reservations and commitments to affect a further request without exposing confidential engagements elsewhere.

Pooling assembles resources from producers, suppliers and service providers for the relevant work. For producer resources, cost recovery through the Joint Account supports the continued development and maintenance of their capabilities and distinct competitive advantages. The beneficiary, compensation basis, accepted work and accounting treatment must be identifiable.

Detailed reservation rules, priorities between competing demands and treatment of overruns remain for software-development specification. The conceptual distinction prevents an availability display from being mistaken for permission to commit.

6. Financial deployment and operational direction

6.1 Work Order

The Work Order connects operational financial resources to approved sources, purpose, beneficiary, assignments, commitments and charging destinations. It supports specialist time and charging under the approved arrangement. A charge code identifies an accounting destination; it does not by itself authorize expenditure.

A Work Order cannot create an AFE or enlarge an independently approved budget or contract. Its changing commitment position must remain connected to the authorization governing the work.

6.2 Industrial Command & Control and Job Order

Industrial Command & Control imposes the recognized chain of command over pooled people from different organizations. Accountability is exercised through the JOC's members and governing arrangements.

The Job Order directs the particular field action issued by the recognized authority. Field execution requires the appropriate Job Order and must remain within its instruction and the previously approved contractual arrangements. A Job Order creates no additional spending authority.

Work Order and Job Order are mutually exclusive business tools with distinct purposes. This does not prevent an engagement from needing both. The model does not prescribe that one contains, generates or is the mandatory parent of the other. Their shared references, amendment dependencies and authorization checks remain part of decision D5.

6.3 AFE, Lease and discretionary Purchase Order

Authorization for Expenditure establishes the approved expenditure purpose, budget and participant approvals. Lease supplies the monthly accounting context for JOC revenue, royalties and operating costs. No capital costs are chargeable to Lease; capital accounts cannot receive operating charges.

Purchase Order functionality is discretionary and excluded from the standard configuration. Where selected, it supports vendor qualification, contract terms, progress payments, holdbacks and acceptance. It preserves the underlying AFE, Cost Center or Lease coding and existing approval authority.

7. Episteme retains the research functions

Episteme names the temporary research-collaboration capability previously housed in Work Orders. Renaming preserves its functioning. It is not merely a directory of researchers or a reference attached to an operational Work Order.

Its arrangement captures the meeting of minds before commitments and costs require retrospective reconstruction. The model retains:

• Research purpose, selected participants, authorized representatives and confidential formation.
• Cash and noncash contributions, including expertise, samples, data, computing resources and time.
• The agreed valuation or treatment of each contribution and evidence of acceptance.
• Funding sources, budgets, commitments, approvals and the authorized deployment of resources.
• The agreed distribution of research costs and benefits, distinguishable from the sources satisfying that arrangement.
• Time, charging and accounting support, including references to participant accounts and applicable allocation processes.
• Output ownership, permitted use, disclosure, copying, assignment and later access under the agreement.

Participant AFEs may supply independently approved funding. Eligible operating-cost contributions can be charged to Lease under separate spending approval, and producers may contribute internally generated resource charges under approved arrangements. Lease remains an operating accounting destination and accepts no capital costs; an internal charge does not itself create cash or spending authority. Episteme cannot originate an AFE for the research group and cannot enlarge a participant's approval. A separate Work Order is not mandatory. Funding, contribution and approval controls remain within the research arrangement rather than being removed by the exception.

A participant's cash contribution, its share of research cost and its rights to output are separate concepts. They may be connected by agreement, but cannot be presumed equal. A noncash contribution likewise requires agreed treatment; its inclusion must not automatically create a cash receivable or payment.

Research participation does not automatically inherit a property's working-interest allocation. It need not constitute a JOC. Where a JOC independently approves an eligible contribution, that funding authority remains distinguishable from the research group's own agreement.

Funding source also differs from accounting classification. An AFE reference does not transform an operating research charge into capital. The responsible accounting functions must apply the appropriate treatment.

Research subjects and material remain confidential during selected outreach and after formation. Non-rival knowledge does not imply unrestricted use. Research completion does not publish findings to Knowledge & Learning. Any permitted disclosure is a separate authorized action.

Conditional contributions, funding shortfalls, overruns, withdrawal and changes in membership remain capabilities to develop. Their detailed rules are unresolved; this does not remove them from Episteme's intended functioning.

An Episteme may combine contributions from several producers and individual researchers. Examples include independently approved capital contributions eligible for exploration treatment, including cash funding for those costs; valued historical data associated with a property or group of wells; and software, computing time and other overhead contributions treated as current-period expenses in the illustrated arrangement. Engineers' and geologists' time may contain both capital and expense elements. Each contribution retains its source, agreed valuation, beneficiary, approval and classification. Cash funding, the contributed resource and the resulting cost are different facts: classification follows the underlying activity and applicable treatment, not the label Episteme or the fact that cash changed hands. The lease contains no capital costs. Detailed classification and allocation rules remain with the responsible accounting functions and user community.

8. Service providers and process coordination

One possible operational path is:

1. Planning identifies a requirement and Knowledge & Learning supplies relevant permitted capability information.
2. Capability Deployment organizes the engagement and obtains the required approvals.
3. Work Order deploys operational financial resources.
4. Industrial Command & Control and Job Order provide field direction where required.
5. Specialized providers record work, accounting consequences and allocations.
6. Commercial assessment and outcome review inform subsequent decisions and Planning.

A research path uses Episteme's retained functions and independently approved participant funding. It does not add a Work Order simply to imitate the operational path. A later field deployment arising from research follows its own operational approvals.

Individual service providers can perform distinct elements of these processes. Each element needs a defined purpose, required information, responsible function, authority, result and exception route. Autonomous Asynchronous Transaction Orchestration carries the communications and follows dependencies. Business Operations Management makes overall progress and unresolved matters visible.

Work may branch, pause, return for investigation or proceed concurrently where dependencies permit. Completion of a service task means its stated result is available; it does not automatically mean the engagement is complete, the account is settled or the well is authorized to restart.

9. Lifecycle and history

The following dimensions are proposed for detailed design, rather than one universal status list:

Separates intended benefit from demonstrated contribution.

The responsible component governs valid transitions in its dimension. The supervisor follows the dependencies between them. Closing a work task cannot silently close accounting exceptions; changing a budget does not retroactively alter the authority under which earlier work occurred.

10. Economics, outcomes and monthly evidence

The commercial assessment must retain well-level detail, shared-cost allocations, actual overhead, earlier capital expenditure, subsequent additions and continuing recovery contributions. Consolidation should preserve the ability to explain a property's result and each producer's interest.

The model separates statutory reporting treatment from commercial recovery and recurring cash requirements. It specifies no universal recovery period, return rate or breakeven formula. Methods, assumptions, units, periods and versions must remain identifiable so that comparisons have meaning.

Revenue Per Employee is a discretionary charge-out method using an industry-based standard methodology to be developed. The authorized factor, grade, time basis and effective period must be retained when selected. No small-producer or start-up floor applies. The agreed service price is distinct from proof of the specialist's contribution.

A financial finding prompts investigation and a decision; it does not itself diagnose the technical cause or authorize shut-in. In the ten-well example, one deficient well may be investigated, preserved or suspended while the JOC continues overseeing profitable wells, research and authorized remedial work. Return to production requires updated assessment and the applicable operational authorization.

Every JOC requires a monthly Material Balance Report. Its financial, material, system and partnership balances must be satisfied before clearing or closing. Estimates remain identifiable, and amendments use the governing period's configuration. A balanced report does not prove every physical measurement correct.

Outcome review connects expected and observed results with accepted work, charges, collections and changed assumptions. Commodity prices, allocations and concurrent work may affect results independently of a specialist's contribution. Detailed attribution develops with the Targeting Framework.

10.1 Intellectual Property and the Targeting Framework

Intellectual Property is one of Synallagi's nine Organizational Constructs. A specialist's contribution may depend on IP owned personally or accessed through a license held by the specialist, employer or software provider. The engagement must identify the applicable rights, permitted purpose, beneficiary and restrictions. Professional qualifications, client access and IP permission are separate conditions; possessing one does not establish the others.

The Targeting Framework is intended to manage the evaluation, compensation, monetization and distribution of proven incremental value contributed by engineers and geologists. This value-based compensation is additional to the agreed hourly charge-out arrangement or salary. Its entitlement, calculation basis, allocation and payment terms must be agreed and authorized; the proposal establishes no automatic fee, royalty, percentage or transfer of ownership.

The conceptual model therefore connects an engagement and its IP basis to expected outcomes, observed evidence, the applicable evaluation method and version, an accepted value assessment, any agreed compensation entitlement, allocation and accounting results. A claim, an accepted assessment, an approved payment and a collected amount remain different facts. The responsible components retain their authoritative records.

Value must be objectively calculated, auditable and verifiable. Detailed evidence is open to authorized participants and auditors, while only approved, anonymized results may be released publicly. A cumulative performance statement for a specialist's marketing must remove identifying source data and retain a controlled path to its supporting evidence. Release requires its own authority and rights checks; anonymization alone does not authorize disclosure.

Methods must address price changes, concurrent work, amended allocations and other influences before attributing value. They must also prevent repeated recognition of the same contribution across engagements or periods. The user community and Targeting Framework development must define those methods, dispute procedures and compensation arrangements.

Transaction design lets the specialist connect approved objectives with applicable AFEs, Lease expenditure, Work Orders, Job Orders, discretionary Purchase Orders and electronic invoice approvals. Autonomous Asynchronous Transaction Orchestration carries the resulting work and evidence between responsible service providers. IP permissions, business approvals and accounting controls continue to apply at each relevant action.

When the intended work requires permission from an IP owner, Autonomous Asynchronous Transaction Orchestration coordinates the purpose-specific license process: identify the owner and intended use, obtain and record the agreed terms and authorized acceptance, establish the resulting permission, and then continue the protected work. It does not invent rights or treat a license request as a completed agreement. The responsible parties and functions retain authority over license terms, acceptance, charges and permitted use.

11. Rules the model must preserve

• JOC membership, contractual authority and current security context govern action; coordination does not create authority.
• Producer capability publication is scoped to the selected JOC and does not commit resources.
• Work Order deploys operational financial resources; Job Order directs field action within existing approvals.
• Episteme retains the former research Work Order functions without requiring a separate Work Order.
• Funding source, expenditure authority, contribution allocation and accounting classification remain distinguishable.
• AFEs for a Joint Operating Committee are approved by its members under the governing arrangements; independently authorized producer AFEs retain their own approval basis.
• Lease contains no capital charges; operating costs do not enter capital accounts.
• Accounting and participant allocation remain with their responsible functions.
• Research confidentiality and output rights continue through completion and later use.
• Purchase Order and Revenue Per Employee use remain discretionary.
• Financial alerts, completed service tasks and balanced reports do not confer unrelated authority.
• Historical decisions and accounting amendments retain their evidence, applicable agreements and versions.
• Producer size does not restrict Synallagi participation through a JOC.

Joint Operating Committee - Capabilities Deployment, Part IV

Power is nothing without control. For the career bureaucrat, control means concentrating authority at the centre of the firm. Yet the control required for commercial success in oil & gas must extend to the engineers and geologists responsible for the work. They need command of a project’s resources, access to its details, and the authority to act within the governance established by the Joint Operating Committee. They also need a clear understanding of the financial consequences of their decisions.

This is no longer the 1950s. As reservoirs are depleted, scientific knowledge advances and new technologies become available, the demands on these professionals increase. An organization’s ability to deploy their capabilities must keep pace. Delays in securing information, coordinating resources and obtaining decisions impose costs that technical excellence alone cannot overcome.

A prosperous and productive North American oil & gas industry—one capable of supporting energy independence and providing consumers with affordable, abundant and secure energy—must ultimately sustain itself through profitability. External capital can finance development, but the industry must generate the returns that justify that investment and provide for its continued renewal.

This argument begins with Synallagi position that the industry has failed to achieve genuine, sustained profitability over the past four decades. That is a bold assertion. It challenges readers to consider whether reported performance adequately reflects the full costs of production, including the capital consumed. Our interpretation is that investors’ demands for capital discipline reflect a related concern: production growth must earn its place through commercial performance.

Neither governments nor the investment community can be treated as an unlimited source of funding. The rapid expansion of AI infrastructure illustrates the scale of other demands on capital, with global data centre investment reaching approximately US$500 billion in 2024. Oil & gas producers cannot plan the next 25 years around an assumption that additional financing will always be available. Sustained profitability must provide the financial foundation. It would also give producers greater operational independence to pursue their own direction and vision.

Achieving that outcome requires us to reconsider how the work is organized. Structures that served earlier periods of oil & gas development should be judged against today’s scientific, operational and commercial demands. Their historical success provides no assurance that they can manage the speed and complexity now confronting the industry.

Synallagi proposes a decentralized approach in which engineers and geologists direct the technical work with explicit authority, access to specialized capabilities and visibility into project economics. They continue to advance and apply their sciences while evaluating how each proposed intervention changes costs, revenues and profitability. The Joint Operating Committee provides the project-level framework through which that authority is established and exercised.

This is the purpose of the Joint Operating Committee — Capability Deployment sub-module within Synallagi’s Business Operations Management. It is designed to bring expertise, resources, decision-making authority and financial accountability together where the work occurs. Market-based access to the capabilities of our user community and their service provider organizations supports that work. Reducing organizational latency allows technical knowledge to become timely, accountable action.

Control becomes meaningful when the people responsible for results have the information, resources and authority necessary to deliver them. Synallagi’s A New Discipline brings those elements together, aligning the advance of science and technology with the commercial demands of a market-based economy.

11. Pooling

Access to specialized capability

Pooling is the organizing principle running through Capability Deployment. Participating producers make their specialized capabilities available to the Joint Operating Committee, supplemented by capabilities obtained from the market. Each producer can develop distinctive strengths without maintaining every capability needed for every property in its portfolio.

Each participating producer captures their capabilities in the Research & Capabilities module of Synallagi. Then determines which capability they’ll publish to the specific Joint Operating Committees Knowledge & Learning module which provides the publishable description of those producer capabilities. The description then helps identify relevant expertise; the engagement process must establish its suitability, availability and permitted use in the actual operating context.

Pooling connects that supply with a defined requirement. Planning can use it to assess the capability needed for proposed work; Capability Deployment uses it to assemble the resources for the approved engagement. Requirements reach deployment through Knowledge & Learning. The distinction between a possible future need and a current commitment remains visible.

Pooling supports an organization assembled for the work, with the appropriate technical expertise, administration and service support. The people providing a capability retain their own organizational relationships while undertaking the assignment and its applicable responsibilities.

Availability, commitments and authorization

A capability can be known, available, committed or assigned. These are different business facts. An attractive listing is insufficient if its resources have already been committed elsewhere. Current commitment information and the responsible authorization controls must prevent the same resource from being promised incompatibly to different engagements.

The governing arrangements establish who may commit a capability and approve its use. Work Order deploys the financial resources and records the applicable assignment and charging context. Field direction follows Job Order and Industrial Command & Control. Current availability, commitments and authority contribute to the applicable Synallagi transaction context. Detailed reservation rules, competing demands, overruns and changes in availability remain for the user community to specify during software development.

Compensation and continuing improvement

The cycle continues after work is performed. Charges must be accounted for, allocated and processed under the agreed payment terms. The producer's ability to recover its costs and maintain its capabilities and distinct competitive advantages is part of the business purpose of Pooling.

The financial integration connects the compensation of pooled resources through the Joint Account. Accepted work, invoices, settlement and demonstrated contribution provide different evidence. The permitted learning from an engagement can inform future capability selection and improvement, while confidential or restricted knowledge retains its agreed access and use conditions.

12. Industrial Command & Control

Recognized authority across organizations

Industrial Command & Control establishes the recognized operational chain of command for people pooled from participating producers, suppliers, vendors and service providers. Its purpose is to make direction and accountability clear through the members of the Joint Operating Committee.

The operational role identifies who can direct the relevant work. Joint Operating Committee governance determines the applicable collective decisions and approvals. Contractual and expenditure authority determine what has been committed. Individual representation determines on whose behalf a person acts. These responsibilities must be connected without treating them as interchangeable.

Security & Access Control supplies identity, representation, scoped access, delegation and enforcement. Access to information or an application function is not, by itself, authority to approve expenditure or issue a field instruction. The action must be supported by the Joint Operating Committee members applicable business authority and current transaction context.

Industrial Command & Control can also support Planning where recognized direction and accountability are required. Its use across sub-modules preserves one consistent capability, with authority limited to the relevant work and operating context.

The route from information to accountable action

Capability Deployment presents the requirement and the information needed to respond. Recognized participants investigate and assess the alternatives; the relevant authorities approve the engagement and its commitments; financial resources are deployed through Work Orders; command authority issues the appropriate Job Order for field execution. Assignment, time, accounting and participant allocation retain their respective records and contribute the relevant context to the Synallagi transaction.

The financial integration requires evidence of who made the decision, the authority relied upon and the information considered. A financial warning or automated finding creates no new authority. Autonomous Asynchronous Transaction Orchestration carries out defined processes and communicates work, results and exceptions between service providers under the responsible components' rules. Its permitted actions, dependencies and intervention points are coordinated at the Business Operations Management level and detailed in the relevant conceptual and technical companions.

Work concludes through evidence of performance and the required acceptance, accounting and compensation processes. A continuing financial deficiency may then generate a further authorized response. (Shut-in production.) This closes the connection between information, expertise, action and review while preserving the opportunity to learn and improve.

Business requirements and review basis

The following map supports review and the later conceptual model. Established entries carry the supplied business definitions and explicit decisions already made by industry or People, Ideas & Objects into this specification. The designation records the adopted business basis; it does not by itself establish that a proposed Synallagi formula or procedure is an implemented industry standard. Integration proposal entries translate the accepted financial argument into proposed business requirements. Detailed controls and calculations remain to be developed.

Specialist, IP and value requirements

CD-17 — Support specialist client engagements. An employee or independent engineer/geologist can work across separately approved producer and JOC assignments using one persistent identity. The active context identifies the represented party, client and beneficiary and prevents information or authority carrying between assignments. Business direction established; detailed engagement and conflict rules remain for development.

CD-18 — Preserve Intellectual Property permission. Each engagement identifies the applicable ownership or license basis and permitted use. Professional qualification, technical access and client authority do not replace IP permission. Business direction established; detailed rights representation and change handling remain for development.

CD-19 — Evaluate and compensate proven incremental value. The Targeting Framework connects contribution evidence, assessment, agreed additional compensation, allocation and accounting. Detailed evidence is restricted to authorized participants and auditors; public performance results require approval and anonymization. Business direction established; formulas, attribution, compensation terms and release criteria remain for development.

CD-20 — Reduce Organizational Latency through accountable action. The New Discipline connects scientific and business decisions with their authorized execution. The process can identify delays and dependencies without treating bypassed authority as improved performance. Business direction established; measurement and interpretation remain for development.

Representative review cases

The five cases developed in the outline remain the basis for business review: a single deficient well in a ten-well property; a completion specialist assigned across producer and JOC boundaries; confidential geological research; a downstream allocation amendment; and production-dependent service tasks during suspension. Their accounts, authority and evidence should be traceable through the sections above. They are specification examples, not completed software tests or proof of financial outcomes.

Matters reserved for further specification

Joint Operating Committee - Capabilities Deployment, Part III

 Preparation of the Joint Operating Committee - Capability Deployment sub-module of the Business Operations Management Module has prompted an update to the Security & Access Control Module previously published as part of our handover process. I have revised that specification and republished it in full through the wiki. This brief note records the amendment.

We will continue this practice as the development of each module reveals changes needed in previously published specifications. At this early stage of the handover, publishing a separate file identifying every change would add little value. Readers should consult the wiki for the latest published version. In this instance, the Security & Access Control specification grew from 14,379 to 19,758 words—an increase of 5,379 words distributed throughout the document. Its fundamental purpose remains unchanged; the specification now accommodates the requirements arising from this sub-module. We should expect further amendments across module boundaries as the handover progresses.

What readers are beginning to see is how Synallagi will accelerate both the planning and execution of their projects. There is one condition: our user community needs robust participation and direction from the engineers and geologists who will use these interfaces to manage the commercial side of their work. Their participation is essential to translating the demands of their disciplines into useful working environments within Business Operations Management.

For this sub-module, the starting point is the Joint Operating Committee’s approval of an operation involving capital expenditures. Engineers and geologists must then translate that authorization into detailed deployment plans and carry the project through to completion, either managing the work themselves or handing responsibility to production engineers where appropriate. Those production engineers must also participate in designing the interfaces they will use. The transition from an approved decision to completed work is precisely where the Joint Operating Committee - Capability Deployment sub-module must prove its value.

People, Ideas & Objects’ objective is to increase the speed and throughput of the engineering and geological disciplines. I have not witnessed the industry’s brain trust facing a combination of pressures quite like this. Cultural influences and the industry’s poor performance have weakened its ability to attract new entrants, while experienced professionals continue to retire. Developing the experience and judgment needed to lead can take a decade or more. We cannot assume that expertise leaving the industry can simply be replaced on demand. Meanwhile, the technical difficulty of producing the incremental barrel continues to challenge these disciplines, and society’s demands for energy remain unabated.

Specialization and the division of labor are the organizational methods People, Ideas & Objects has chosen for Synallagi to address these pressures. For illustration, assume the industry realizes only 75% of the productive potential of its existing engineering and geological capabilities. One constraint is the need for individual operators to retain sufficient expertise and capacity to respond to whatever their property portfolios may require. That readiness has value, but it can also leave scarce capabilities unused and unusable within one producer while they are needed elsewhere.

The Joint Operating Committee - Capability Deployment sub-module is intended to give these professionals the hands-on commercial workspace needed to deploy their capabilities and manage their projects toward profitable outcomes. By enabling engineers and geologists to apply their specialties across a region or wherever their expertise is needed in the industry’s marketplace, we can begin to release capacity constrained by the boundaries of individual producer firms. We believe this broader application of specialization and the division of labor can increase the productive contribution of the industry’s existing brain trust, substantially reduce Organizational Latency, and establish a “New Discipline.”

7. Revenue Per Employee

Supporting the development of capabilities

Revenue Per Employee is a discretionary method for determining charge-out rates for engineers and geologists supplied to Joint Operating Committees. Where selected, it uses an industry-based standard methodology. Its purpose is to allow producers to recover the cost of developing and maintaining hyper specialized capabilities and capacities when those capabilities are used by Joint Operating Committees.

It is an operative charging mechanism as well as a performance rationale. The proposal connects the producer's Revenue Per Employee factor, the individual's applicable grade or rate, the hours recorded in the Work Order and the account benefiting from the work. The source proposes that the factor be updated monthly.

Defining the rate

Illustrative junior, intermediate and senior grades are 50, 75 and 90 percent of the factor. Those percentages remain proposals for evaluation and agreement; they are not approved tariffs or validated current industry values.

No special small-producer or start-up floor applies. Synallagi use follows participation in the Joint Operating Committee, regardless of producer size. The detailed charging parameters remain part of the industry-based standard methodology to be developed.

The user community must specify the revenue and employee measures, measurement period, conversion to a time-based rate and applicable grades within the industry-based standard methodology. Discretionary use does not mean that every producer independently redesigns that methodology. Synallagi supports Joint Operating Committee use across producer sizes, including start-ups and major producers.

Each engagement must retain the rate actually authorized and its effective period so that later factor changes do not obscure the basis of an earlier charge. The implementation of rate changes and amendments belongs in the subsequent specification work.

Evaluating contribution

A producer-level revenue measure does not establish an individual's causal contribution to a particular property's profit. The engagement's expected technical result and its observed financial effects provide additional evidence for evaluating the capability deployed.

The financial integration therefore distinguishes the agreed service price from the demonstrated result. Outcome evaluation and attribution will develop with the Synallagi Targeting Framework, currently being written. A higher commodity price, a change in allocation or concurrent work may affect the property's results independently of the specialist's work. Reviews should identify these influences and support better future capability selection; the specification leaves the detailed attribution method for development.

Payment and collection information, in turn, show whether the agreed compensation has actually reached the provider and can support continued capability development.

Intellectual Property, incremental value and the Targeting Framework

Intellectual Property is one of Synallagi's nine Organizational Constructs. An engineer's or geologist's contribution may use IP owned personally or accessed under a license held by the specialist, employer or software provider. Each engagement must preserve the applicable permissions and restrictions; the ability to access a client workspace does not establish the right to use every method or disclose its results.

The Targeting Framework is intended to manage the evaluation, compensation, monetization and distribution of proven incremental value created by engineers and geologists. This compensation is additional to the agreed hourly charge-out arrangement or salary and depends on agreed, authorized terms. No automatic fee, royalty or percentage is established here.

The value must be objectively calculated, auditable and verifiable, using identifiable methods, assumptions and supporting evidence. Detailed evidence remains restricted to authorized participants and auditors. Only approved, anonymized results may be released publicly, including cumulative performance statements used in a specialist's marketing. Such statements retain a controlled connection to their supporting evidence without exposing identifying sources.

The user community must develop attribution, valuation, allocation, dispute and correction methods through the Targeting Framework. Price movements, concurrent work and amended accounting information must be considered before attributing value. A demonstrated result, an agreed compensation entitlement and an actual payment remain distinct. Approved accounting consequences continue through Accounting Voucher and the relevant allocation functions.

Designing Transactions lets the specialist connect the business objective with the applicable expenditure approvals, operational instructions, commitments and electronic invoice approvals. Autonomous Asynchronous Transaction Orchestration communicates the authorized work and results between responsible service providers. Neither a value claim nor an IP license independently grants operational or expenditure authority.

When the intended work requires permission from an IP owner, Autonomous Asynchronous Transaction Orchestration coordinates the purpose-specific license process: identify the owner and intended use, obtain and record the agreed terms and authorized acceptance, establish the resulting permission, and then continue the protected work. It does not invent rights or treat a license request as a completed agreement. The responsible parties and functions retain authority over license terms, acceptance, charges and permitted use.

8. Decentralized Production Model

From commercial assessment to action

The Decentralized Production Model supplies the wider basis for independent production decisions under Synallagi price maker strategy. This section describes its implications for deploying capabilities. The assessment brings market price together with actual operating costs, actual overhead, invested-capital recovery and the applicable return requirement at the well, property and producer-interest levels.

Capability Deployment turns a finding into work that can improve the outcome. The response may be a simple correction, further investigation, preservation, suspension or an authorized return to production. Needs for further research or assessment can inform Planning, with the relevant plans and requirements connected to deployment through Knowledge & Learning. Continuing an activity because it increases physical output is insufficient where the additional production fails the commercial test.

The operating and recovery evaluation must remain visible alongside other sources of cash. Financing or hedge settlements may affect the producer's financial position; they should not obscure the performance of physical production. The detailed calculation method and its responsible service remain for specification.

Example: one well in a ten-well property

One well in a ten-well Joint Operating Committee may underperform while the other nine remain profitable. The responsible participants examine its production, attributable costs, shared allocations and recovery assumptions. A suitable specialist can investigate the deficiency and recommend the response.

The investigation may identify a correction that restores profitable operation without suspension. If suspension is authorized, the affected well can be preserved while the other wells continue, subject to their operating dependencies and governing arrangements. Avoiding the deficient production can improve the property's financial performance and make resources available for investigation and improvement. The effect must be demonstrated in the property's results.

The Joint Operating Committee will continue to oversee profitable wells, preservation, research and authorize remedial work. Return to production follows an updated commercial assessment and the required operational authorization.

Service tasks during suspension

Transaction design makes the relevant administrative and accounting tasks responsive to their activity triggers. Where a production input ceases, the corresponding production-dependent service task and bill are not generated. Investigation, preservation, prior-period amendments and other authorized continuing work retain their own triggers and charge bases.

This is the operational means of varying those costs with the work performed. The detailed catalog of continuing accounts and contractual contingencies remains with our user community. Actual costs and their causes must remain visible when comparing continued operation, suspension and restoration.

9. Episteme

Pronunciation: Listen to People, Ideas & Objects Episteme pronunciation reference.

Definition: 

Organizing confidential research

Episteme is the distinct capability for a temporary research collaboration. It brings selected participants together around a hypothesis, technical problem or research opportunity without requiring them to form a Joint Operating Committee.

The project lead approaches selected producers, suppliers or other relevant participants. The subject of the research and its material are confidential. Formation is based on controlled outreach. Once the group is established, participation is restricted to its members and subsequently approved additions, with access enforced through Security & Access Control.

Contributions, funding and results

Participants can contribute expertise, samples, seismic information, computing resources, software, cash or other agreed resources. Their arrangement must capture the substance of each contribution, its treatment, the authorized funding source and the agreed distribution of costs and benefits before work begins.

Research participation does not automatically adopt a property's working-interest allocations. The contribution arrangement supplies its own basis. An independently approved AFE may provide eligible funding; Episteme deploys the resources made available to the collaboration but cannot issue that AFE itself. Financial resources may be sourced through independently approved participant AFEs. Eligible operating-cost contributions may also be charged to Lease under separate spending approval, and producers may contribute internally generated resource charges under approved arrangements. Lease accepts no capital costs. Internal charges are distinguishable from cash contributions and do not themselves create spending authority. Episteme retains the research functions previously housed in Work Orders: recording the agreed purpose, cash and noncash contributions, funding sources, budgets, commitments, allocation, approvals, time and charging, accounting support and agreed output rights. These functions remain part of Episteme; a separate Work Order is not mandatory. The funding sources and the agreed distribution of research costs remain distinguishable. Accounting Voucher and the relevant allocation functions express the approved arrangement in the participants' accounts and General Ledgers. 

The research output can be non-rival: one member's use of knowledge need not prevent another member from benefiting from it. Rights to disclose, copy, assign or reuse the output nevertheless depend on the participants' agreement. Completion of research does not automatically make its findings publishable through Knowledge & Learning.

An Episteme may combine contributions from several producers and individual researchers. Examples include independently approved capital contributions eligible for exploration treatment, including cash funding for those costs; valued historical data associated with a property or group of wells; and software, computing time and other overhead contributions treated as current-period expenses in the illustrated arrangement. Engineers' and geologists' time may contain both capital and expense elements. Each contribution retains its source, agreed valuation, beneficiary, approval and classification. Cash funding, the contributed resource and the resulting cost are different facts: classification follows the underlying activity and applicable treatment, not the label Episteme or the fact that cash changed hands. The lease contains no capital costs. Detailed classification and allocation rules remain with the responsible accounting functions and user community.

Example: a geological hypothesis

A geologist proposes a hypothesis to selected producers operating in a relevant Rocky Mountain setting. Contributions include the hypothesis, three samples from two producers, an engineer's implementation expertise and a described $100,000 funding contribution from two other firms' independently approved AFEs. The source does not specify how that cash contribution is divided, and this example makes no allocation assumption.

In this example, the resulting knowledge is for the participating members' exclusive use and is not assignable or copied to others. Its commercial value may lie in a successful finding or in establishing that an approach does not work. Any subsequent deployment follows the permitted use of that knowledge and its own work approvals.

Episteme can be used within Planning and in connection with Capability Deployment. The relevant findings may inform subsequent plans or engagements through Knowledge & Learning only within their permitted disclosure and use. Reuse of the capability across sub-modules does not broaden access to the research.

Participant withdrawal, conditional contributions and other complex contingencies remain for user-community development.

10. Material Balance Report

Monthly financial and volumetric integrity

Every Joint Operating Committee requires a monthly Material Balance Report. It is a specialized Accounting Voucher that brings together the month's accounting and volumetric activity. The Joint Operating Committee is the governing organizational context; its report and Accounting Voucher are the accounting records through which that activity is represented.

Closing requires financial debits and credits to balance and the required volumetric balances to be achieved. Material balance addresses the volumes within the reporting context. System balance addresses connected inputs and outputs. Partnership balance addresses allocation among the relevant participants, royalty holders and other entitled parties. The report must not be cleared or closed while its required balances remain unresolved.

Once balanced, the joint-account amounts, volumes and inventories clear to the relevant participant accounts through the applicable allocation processes. The agreements determine the allocation basis, including legal or chemical-composition methods where applicable. The business specification does not assume that an accounting balance proves the accuracy of every underlying measurement.

Period history and amendments

Production streams are associated with the relevant processing, gathering and sales contracts. Property changes, including additional wells and contracts, enter the applicable month's Accounting Voucher template. Prior configurations must remain available so that an amendment uses the context governing the period being changed.

Where information is unavailable, identified accruals or estimates support the prescribed accounting process, including subsequent reversal and amendment. They must remain distinguishable from confirmed measurements. The source's next-month reversal approach should be carried into the detailed design together with the rules for replacing estimates and resolving exceptions.

People, Ideas & Objects amendment example begins with a neighboring facility's revised production configuration. A downstream gas plant then recalculates its allocation to Joint Operating Committee Y. Applicable IoT evidence, Y's allocation agreements, sales contracts and royalty calculations support amendments to participant reporting and general ledgers.

The example describes reconciliation with major distribution carriers before the end of 90 days. That is an illustrative sequence, rather than a universal finality deadline. Completeness across the affected system must be supported by the connected reconciliations. The detailed propagation and exception rules remain for development.

Evaluating deployed work

The financial integration uses the resulting period information to evaluate an engagement's costs and effects. Well-level information and shared-cost allocations must remain traceable as results are consolidated and amended. A revised allocation can change a prior commercial assessment even though the physical work was completed correctly.

Material Balance Report supplies accounting and volumetric evidence. Accounting Voucher posts the relevant accounting results to the General Ledger. Reporting status, allocation changes and amendments contribute to the Synallagi transaction's evolving business context through those authoritative records.

The management-accounting evaluation combines the evidence with technical expectations and defined recovery assumptions. Closing the report does not itself establish profitability or complete the evaluation of a deployed capability.

Joint Operating Committee - Capability Deployment, Part II

 Today’s blog post examines the development of transaction templates and their associated Accounting Vouchers, together with the interfaces engineers and geologists will need to use them. These templates will support the planning and deployment of the commercial aspects of oil & gas operations, from filling a vehicle’s fuel tank to drilling a well. They will connect the work being undertaken with its financial consequences, providing visibility into commercial issues and opportunities as the project unfolds. This will substantially reduce organizational latency.

Accounting expertise will be available throughout. Engineers and geologists, however, must drive the operating requirements and help design the interfaces through their participation in our user community. Service providers will contribute the accounting expertise necessary to translate those requirements into dependable financial processes. We cannot build a system that meets your needs without comprehensive input and active participation from the engineering and geological communities.

These transactions may extend across several accounting months. Their associated Accounting Vouchers must maintain a continuous view of the project while recognizing costs and obligations in the appropriate accounting periods. Accruals will record costs already incurred for which invoices or final amounts remain outstanding. As actual charges become available, the corresponding accruals will be cleared or adjusted, ensuring that each cost is recorded once. Project completion will bring a reconciliation of recorded costs, outstanding obligations, and remaining estimates.

Once the transaction’s activities, responsibilities, and accounting treatment have been defined—with service providers supporting the accounting specifics—the template will provide the basis for what Synallagi describes as Autonomous Asynchronous Transaction Orchestration. This orchestration will coordinate the transaction as work progresses, information arrives, and authorized actions become due. The Accounting Voucher will record the financial consequences and retain the supporting evidence.

The engineer or geologist will manage the project according to their professional judgment and discipline, within the authority assigned to them. Our objective is to automate most routine accounting activity, with service providers managing accounting oversight, exceptions, reconciliation, and administration through Synnefa, our cloud offering. This will allow engineers and geologists to concentrate on the work and its commercial performance, supported by accounting that develops alongside the project.

1. Designing Transactions

Capturing the agreement

Designing Transactions establishes the business basis of an engagement before its recurring processing begins. The parties identify what will be delivered, how it will be measured, what value will be exchanged and how compensation will occur. The design captures their understanding while that understanding is available to the people making the agreement.

The Accounting Voucher provides the transaction-design capability. Accountants and the relevant business participants define the units of work, the beneficiary, the charging basis, the accounting destinations and the evidence required for processing. Standardizing, counting, valuing and compensating give a transaction an agreed meaning across organizational boundaries. Different Joint Operating Committees can use these common methods while retaining their particular contracts, operating configurations and capabilities.

The transaction design also identifies the event that causes work or AFE’s and Lease charges to arise. For production accounting, a production input can initiate the defined service-provider task, with billing based on the work rendered. The Accounting Voucher template supports reuse in subsequent months. Changes to the property or agreement must be reflected in the applicable version, while earlier configurations remain available for prior-period work, adjustments or corrections.

Connecting delivery and value

The financial integration adds the expected technical and commercial contribution to the engagement's description. Participants should be able to identify the problem, the proposed work, its anticipated cost and the result they intend to evaluate. An engagement to diagnose a well may deliver a reliable explanation and recommendations; an engagement to implement a correction may deliver a changed operating condition. Their acceptance evidence will differ.

Service delivery, payment entitlement and realized property performance are separate questions. An agreed service can be completed and payable before its effect on production or capital recovery is known. Recording the expected contribution enables later evaluation without silently changing the provider's agreed compensation into a performance-contingent arrangement.

The proposed automation follows the designed transaction, the applicable agreement and valid authority. It processes defined events and presents exceptions requiring attention. Accounting Voucher provides the accounting expression, including posting to the General Ledger. Business transaction design supplies the accounting and commercial basis; field direction proceeds through Operational Control.

The Synallagi transaction connects the applicable authorization, resource deployment, commitments and accounting results. Its design must retain the relationship between deployed financial resources and their authorized sources and destinations, through the Work Order for operational engagements and through Episteme for research collaboration. It must also accommodate approved changes without obscuring the basis on which earlier work occurred.

2. Operational Control

Innovation and execution

An innovative producer needs both the freedom to develop better methods and the ability to execute work under recognized authority. The Joint Operating Committee may assemble a temporary operating organization from several producers, vendors, suppliers and service providers. Everyone involved needs to understand who directs the work, which instruction applies and what has already been authorized.

Industrial Command & Control establishes that operational chain of command. The Job Order provides the particular field instruction issued by its recognized and designated authority. Field operations require the appropriate Job Order, and execution follows its authorized scope.

Job Order and contractual authority

Work Orders and Job Orders are mutually exclusive business tools. The Work Order deploys financial resources and supports specialist assignments, time and charging. The Job Order directs field action. Operational financial resources are distributed through a Work Order. Episteme retains the research functions previously housed in Work Orders and deploys independently approved participant funding without a mandatory separate Work Order. The operational financial deployment requirement does not make the Work Order a field instruction or prescribe a parent-child relationship between the two tools.

The user community will determine the shared references, detailed relationships and amendment procedures. The distinction already established is that operational financial deployment uses the Work Order, while operational direction uses the Job Order under recognized command authority. Episteme retains financial deployment and related controls for research collaboration.

A Job Order has no spending authority outside the previously approved contractual arrangements for its listed tasks. An instruction to perform work must therefore remain within the relevant contract and authority. Where a proposed action exceeds those arrangements, the required contractual and expenditure approvals must be addressed before the expanded action proceeds. The detailed amendment procedure remains for the user community to specify.

Acting on a financial finding

A financial anomaly should reach the people able to investigate its cause and assess a response. It may reveal a measurement problem, an unexpected cost, a production deficiency or an assumption that no longer holds. The finding initiates review; it does not establish a physical diagnosis or authorize expenditure by itself.

Technical and commercial participants develop the response under the applicable governing arrangements. Investigation, correction, preservation, suspension and restoration each require the appropriate authority and work arrangements. This gives financial information a route into operational decisions while preserving responsibility for those decisions.

3. Purchase Order

Discretionary contract control

Purchase Order functionality is discretionary and selected by the producer. Standard Synallagi configuration excludes it. Where selected, it supports the control of vendor relationships and significant contracts within the Accounting Voucher environment.

Its purpose includes qualifying vendors, conducting the bidding process, recording the agreed work and controlling payment against contractual conditions. Selection must consider the vendor's ability to perform the required work and meet the project's criteria. The lowest submitted price does not by itself demonstrate that capability.

Payments and coding

The approved contract supplies the basis for prepayments, progress payments, partial payments, holdbacks and final acceptance, as applicable. The Purchase Order records the relevant conditions so that Accounting Voucher processing can apply them. Final payment follows the contract's completion and acceptance requirements, including any unresolved holdbacks or other conditions.

The Purchase Order number does not replace or change the AFE, Cost Center or Lease charge code. Expenditure still reaches the appropriate accounting destination and retains its capital or operating classification. A payment under a Purchase Order must remain distinguishable from the evidence used to judge the engagement's eventual commercial contribution.

Producers choosing this functionality gain a further means of expressing and administering their contract controls. Its discretionary status does not remove the need for valid contracts, spending authority or accounting when the feature is absent. The detailed facility-project purchasing example and implementation of purchasing services remain matters for user-community development.

4. Work Order

Assigning expertise and recording its cost

The Work Order is the means through which financial resources are deployed for operational engagements. It also records a specialist's approved assignment and provides the basis for recording time and charging the appropriate beneficiary. It supports the deployment of producer capabilities across Joint Operating Committees and preserves the terms needed to recover the cost of providing them.

All financial resources distributed for the operational engagement pass through the Work Order. The record connects the approved source of those resources with their intended use, beneficiary, commitments and charging destinations. This deployment role operates within the existing expenditure and contractual authorizations; it does not originate an AFE or create authority beyond those arrangements.

The assignment identifies the person or resource, the work, its beneficiary, the agreed charging basis and the authorized accounting destinations. Time can be attributed to the applicable AFE, Lease, project, research or administration account as the work progresses. Accounting Voucher provides the accounting representation and General Ledger posting, and Partnership Accounting applies the relevant participant allocations and joint-account consequences. The Work Order's resource-deployment role remains connected to those accounting and payment functions; it does not establish a separate settlement system.

A specialist may work across several properties. Each assignment must remain identifiable so that one Joint Operating Committee's work is not charged to another and the same time is not charged twice. Resource commitments must also remain visible to those authorized to make them. A listing of expertise does not establish that the specialist is available or already assigned.

Research collaboration is organized through Episteme, described in section 9. Episteme retains the research functions previously housed in Work Orders, including participant contributions, funding, allocation, approvals and accounting support. Participants' approved time and charging arrangements can support research within that arrangement without a mandatory separate Work Order.

Example: a completion specialist

Producer X participates in Joint Operating Committee Y. Y requires X's completion capability, listed in Knowledge & Learning. X's COO proposes a trusted former employee as Senior Engineer. The engagement is agreed through Y's Joint Venture Agreement operating procedure, recorded through a Work Order and charged for the authorized hours against the completion AFE.

Where the discretionary Revenue Per Employee method is selected, People, Ideas & Objects example uses a $3 million annual reference and an agreed $300 hourly rate. These are illustrative inputs. The example does not establish a mathematical conversion between them or presume that the former employee is currently employed by X. The contracting and representation arrangement, and the rate derivation under the industry-based standard methodology, require specification.

The financial integration adds the expected completion outcome and a subsequent review of its technical and commercial effects. The record should allow participants to distinguish work accepted, charges processed, payment received and improvement demonstrated. Any field instructions retain their separate Job Order and Industrial Command & Control basis.

5. Lease

The operating accounting context

Lease is the accounting feature derived from the petroleum lease that captures the Joint Operating Committee's revenue, royalties and operating costs. It provides the monthly breakdown of those amounts through the financial statements being prepared. It separates day-to-day operating accounting from special-purpose capital expenditure recorded against an AFE.

No capital costs are chargeable to Lease. A shared view of property performance must preserve that separation. Bringing operating results and capital-recovery information together for analysis does not move capital expenditure into the Lease accounts.

Capability Deployment uses the Lease context when authorized work and charges relate to operations. The applicable authority for Lease spending forms part of the Synallagi transaction; the Lease charge code alone does not provide spending authority. The Work Order deploys the approved financial resources, while the Lease supplies the operating accounting destination.

The underlying record should retain the well or activity to which an amount is attributable and identify the basis of shared allocations. This detail permits an individual well's performance to be examined without losing the Joint Operating Committee's overall accounting relationship.

Actual costs and comparable information

The financial integration requires actual administrative and service-provider charges to remain visible. Where a cost is shared, the allocation method must be identifiable. A standard method supports comparison between properties, while the underlying information must preserve material differences in their physical conditions, contracts and work performed.

Monthly reporting supplies a period view. Current work may also need the latest available accounting and commitments. Users must be able to distinguish the selected period, estimates and subsequent amendments. These distinctions allow engineers and geologists to use financial results as evidence without treating every variance as a confirmed change in physical performance.

Lease serves this accounting purpose. Administration of petroleum rights and interests continues through the responsible property and agreement functions.

6. AFE — Authorization for Expenditure

Purpose, approval and commitments

The Authorization for Expenditure establishes the approved budget and purpose for capital outlays. It records the required participating Joint Operating Committee approvals and reports expenditure against the agreed budget. Supplementals and other approved changes form part of the continuing authorization history.

Deployment must remain connected to that approved purpose and the contractual arrangements for the work. Financial resources authorized through the AFE are deployed through Work Orders for operational engagements and through Episteme for research collaboration. The applicable AFE authorization, deployment authority and changing commitment position form part of the relevant Synallagi transaction context.

Budget availability must reflect commitments already made as well as expenditure already recorded. Live or near-live information must support controls that prevent the same available resources from being committed again; refreshing a displayed balance alone is insufficient.

The user must also be able to return to the relevant accounting period or production month. The historical view must preserve the approval and accounting context applicable at that time.

Commercial evaluation of additional expenditure

The financial integration connects a proposed capital engagement to its expected contribution. Participants need to see the additional expenditure, the production it is expected to enable or preserve, its timing and its effect on continuing capital recovery. A workover may improve performance without adding reserves; its commercial case should describe the benefit actually expected.

Earlier investment remains visible when additional work is undertaken. New expenditure cannot make an earlier recovery deficiency disappear from the commercial evaluation. The evaluation should distinguish opening unrecovered expenditure, additions, the actual contribution toward recovery and the remaining recovery requirement, using a defined method that avoids counting the same deficiency twice.

This is a management-accounting evaluation. Financial-reporting depletion, the carrying value of assets and the commercial recovery requirement remain separate measures. Any allowance for replacement of produced reserves must also be explicit and distinguishable from recovery of expenditure already incurred. This specification adopts no universal recovery period or return assumption and does not direct that operating losses be capitalized.

AFEs for a Joint Operating Committee are approved by its members under the applicable governing arrangements. An independently authorized producer research AFE retains that producer's approval basis. Approved AFE funding is appropriate for eligible Work Order or Episteme activity; the deployment record does not originate or enlarge that authority.

Research funding

An independently approved producer or Joint Operating Committee AFE may fund an eligible research contribution. A producer may also independently authorize an AFE for its research budget. Episteme can deploy the resources made available under those independent approvals; it cannot originate an AFE. Episteme retains the research functions previously housed in Work Orders and deploys those resources within the approved arrangements, without a mandatory separate Work Order. Episteme does not create the funding authority it relies upon.

Funding source and accounting classification remain distinct. Research contributions must be classified according to their nature and the applicable accounting treatment. A capital account cannot accept an operating charge merely because funding was described through an AFE. The precise mapping is a user-community development matter.