Joint Operating Committee Capability Deployment
Business and Technical Specification — Release 1
Business Operations Management · Release 1 · October 15, 2026
This release establishes the reviewed business, conceptual and technical specification for Joint Operating Committee Capability Deployment. It provides the current basis for the wiki and user-community handoff. Detailed calculations, record relationships, contribution contingencies and implementation decisions identified in the specification remain for development. This is a specification baseline, not a claim of completed software.
The Joint Operating Committee needs the capabilities required to operate its properties profitably, preserve its reserves and pursue worthwhile opportunities. Those capabilities may reside with its participating producers, an individual specialist, a service provider or a research collaboration. Their usefulness depends on being available when required and supported by clear authority, agreed compensation and reliable accounting.
Synallagi proposes to remove designated operatorship and organize the required capabilities through Pooling. Each producer develops its particular strengths and contributes them to the Joint Operating Committees in which it participates. Additional capabilities are obtained from the market. This allows specialization and the division of labor in the sciences of geology and engineering to extend across organizations, while each engagement retains its own purpose, participants, commitments and accountability.
Capability Deployment brings these arrangements together within Business Operations Management, presented through the Engineers and Geologists interface. It connects a requirement with suitable capabilities, the authority to engage them, the work performed, its accounting consequences and the evaluation of results. These activities contribute to the developing Synallagi transaction. Accounting, participant allocation, security and operational direction continue through their responsible Synallagi components.
Synallagi is organized around the Joint Operating Committee and its requirements. Its intended use extends across producer sizes, from start-ups to firms the size of Exxon. A producer's size does not change the need to identify the applicable property, agreement, authority, contribution and accounting treatment.
Our user community includes engineers, geologists, accountants, administrators and the people who provide services to the industry. Their combined knowledge is necessary to describe both the technical work and the business arrangements that make it possible. Capturing those arrangements while people agree to them gives subsequent processing a reliable basis and reduces the need to reconstruct their intentions after costs have been incurred.
Engineers and geologists are the primary users of Business Operations Management. Its interface begins with the individual, the selected Joint Operating Committee and the producers represented in the engagement. A specialist may work as an employee within assigned JOCs or as an independent professional serving several producers and JOCs. Capability Deployment organizes these client engagements and their approved capabilities, contributions, work and accounting consequences.
One persistent Synallagi identity can carry several separately approved assignments. The selected context determines the party represented, the information available and the authority to act. Security & Access Control prevents information or authority from one client assignment carrying into another. The engagement must provide the producer-private information required for the approved work. The specialist's authority to represent a participant or approve a transaction remains separately established.
Capability Deployment contributes to a New Discipline connecting scientific judgment, transaction design, actual economics and accountable results. Reducing Organizational Latency means shortening the time between recognizing an opportunity or deficiency and implementing the authorized response. Planning, Marketplace Interface and Capability Deployment support that work through their respective responsibilities.
Engineers and geologists must work with the user community to define and validate the tools needed for science and innovation, both initially and throughout Synallagi's life. Artificial Intelligence is a proposed contributor to that productivity within the established information, authority and accountability boundaries.
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.
The objective is reserves preservation, performance and profitability. Engineers and geologists need to see how their technical decisions affect actual costs, production, recoverable reserves and the recovery of invested capital. Accountants need the technical and contractual context that explains those results. Capability Deployment connects that information to people who can act on it.
A requirement may arise from new development, maintenance, research, an obligation or a financial deficiency. A well's disappointing financial result can prompt a technical investigation, just as a technical observation can prompt a commercial review. The purpose is to identify the appropriate response and make its effects visible. Greater production alone does not establish that the work improved the property's economics.
The price maker strategy supplies the commercial discipline: each producer uses market price and the detailed economics of its interests to make independent business decisions. Breakeven calculations make the relevant cost and recovery requirements visible and help identify deficiencies requiring action. Where property action requires Joint Operating Committee approval, those decisions are exercised through the applicable governing arrangements. Capability Deployment provides the means to obtain expertise and carry out authorized responses.
The Marketplace Interface enables engineers and geologists to find and engage vendors, suppliers, service providers and specialized capabilities through Synallagi's integrated business functions. This Business Operations Management sub-module connects with the Petroleum Lease, Resource and Financial Marketplace modules. For its detailed function and capability, see Business Operations Management — Marketplace Interface.
Business Operations Management — Planning is the principal setting for Research & Capabilities. Capability Deployment draws on plans and identified requirements through the Knowledge & Learning module to organize approved work. The results of that work can inform subsequent planning, subject to the information's permitted use.
Planning and Capability Deployment share the use of Pooling, Industrial Command & Control, Episteme and other relevant capabilities. Planning may examine the expertise and resources needed for proposed work; deployment establishes and carries out the approved engagement. A planning requirement does not itself commit resources or authorize an operation. Shared capabilities retain their meaning and authority across the sub-modules, and their detailed exchanges remain to be specified.
Business Operations Management provides the supervisory and coordination role across its sub-modules for the selected Joint Operating Committee. The sub-modules define particular capabilities; the overall module connects their use into coherent operating processes. It follows what initiates work, the information required, applicable approvals and dependencies, progress, results and exceptions requiring attention.
Responsibility is distributed across three levels. Each sub-module or responsible Synallagi component defines its business function, calculations, records, rules and results. Business Operations Management coordinates when and how those functions are used together. The Conceptual Model and technical companions specify the relationships, exchanges, transaction states and implementation required to support that coordination.
A detailed formula remains with the capability responsible for its calculation. Business Operations Management coordinates when the calculation is needed, which authorized inputs and applicable version are used, and how the result affects commitments, expenditure or subsequent decisions. The same principle applies to record relationships: the responsible components maintain their authoritative records, while module-level coordination defines the business connections between them.
One possible process path begins when Planning identifies a requirement. Knowledge & Learning supplies the relevant capability information; Capability Deployment organizes the engagement; Work Orders deploy its financial resources; Industrial Command & Control and Job Orders direct field execution; accounting records the consequences; and results inform subsequent planning and performance evaluation. This is an illustrative path. Other work may begin at a different point, branch, return for further investigation or proceed concurrently where its dependencies and authority permit.
These processes are broken down into individual elements performed by specialized service providers. Each provider handles its defined element of the coordinated process, with an identifiable input, required work, result and responsibility. A sub-module may therefore involve several providers, and a provider's defined service may support more than one process. This division of work makes specialization operational while preserving accountability for each contribution.
Autonomous Asynchronous Transaction Orchestration coordinates execution and communication between those elements. It conveys the relevant information, requests, completion evidence and exceptions so that the next eligible activity can proceed under its defined conditions. Asynchronous operation allows elements to progress when their inputs and approvals are available, without requiring every participant to act at the same time. Dependencies and authorization requirements continue to govern the work.
Business Operations Management provides the supervisory view of the overall process and the decisions or exceptions requiring attention. Autonomous Asynchronous Transaction Orchestration carries the defined work and communications across the participating services and responsible components. Each service provider remains accountable for its element; orchestration supplies no authority beyond the governing arrangements.
As the process advances, the Synallagi transaction carries or references the relevant authority, commitments, assignments, service results and accounting consequences. Its connected business context develops through these contributions, while the source records remain with their responsible components. Capability Deployment specifies what it contributes, requires and returns; coordination across the sub-modules is developed at the Business Operations Management level.
A Synallagi is the transaction whose relevant elements and attributes are progressively defined by the modules. Security & Access Control establishes its identity, representation, role, authority and access context. Business Operations Management adds the more detailed and changing business context needed to act: authorized AFE spending, authorized Lease spending, Work Order authority, operational instructions, commitments and the other applicable elements of the engagement.
Security provides the comparatively stable foundation; Business Operations Management develops the more variable business context. The foundation continues to evaluate authority and access as relationships, assignments and transaction conditions change. Passing an access check therefore enables the relevant work in context; it does not grant permanent authority regardless of subsequent changes.
The business elements form part of the Synallagi transaction itself. They connect the parties and their authority with the resources deployed, work performed, accounting consequences and outcomes. As further modules are developed, they’ll contribute additional elements, attributes and relationships. The responsible components continue to maintain their authoritative records.
Transaction context
Relevant elements
Business responsibility
Identity and authority
Person or governed automated identity, represented party, role, permitted action, information scope and current authority.
Security & Access Control enforces the applicable governing arrangements.
Expenditure and resources
Authorized AFE or Lease spending, contractual basis, purpose, budget and existing commitments.
The responsible approval and accounting functions establish the basis. Work Orders deploy operational financial resources; Episteme retains the corresponding research functions and deploys independently authorized participant funding without a mandatory separate Work Order.
Assignment and direction
Work Order authority, assigned capability, charging context, command authority and applicable Job Order.
Work Order deploys financial resources and supports assignments; Job Order directs field work within previously approved contracts.
Plans and capability
Relevant plan or requirement conveyed through Knowledge & Learning, permitted research findings and capability availability.
Planning, Research & Capabilities, Knowledge & Learning and Pooling retain their respective responsibilities.
Accounting and outcomes
Work evidence, rates where applicable, charges, allocations, General Ledger postings, amendments, compensation and evaluation.
Accounting Voucher and the related accounting functions supply financial evidence; outcome evaluation develops with the Synallagi Targeting Framework.
The conceptual model will define how the transaction carries or references these elements and their history. The business requirement does not prescribe one physical record containing everything, or require every transaction to contain every element. It requires the relevant context to remain connected and attributable as work progresses.
Business Operations Management will continue to develop with its sub-modules and the wider Synallagi specification. Changes must identify the affected business requirements, responsible components and companion layers, preserve the basis of earlier authorized work, and be reconciled through the user community. Operational and accounting amendments retain their own authorities.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Revenue Per Employee is a discretionary method for determining charge-out rates for engineers and geologists supplied by producer firms. Where selected, it uses an industry-based standard methodology. Its purpose is to allow producers to recover the cost of developing and maintaining capabilities 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.
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.
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 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.
The Decentralized Production Model supplies the wider basis for independent production decisions under Synallagi's 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.
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.
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.
Pronunciation: Listen to People, Ideas & Objects Episteme pronunciation reference.
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.
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. Lease contains no capital costs. Detailed classification and allocation rules remain with the responsible accounting functions and user community.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Requirement
Status
Business evidence needed for review
CD-01 — Respect component responsibilities.
Established
Capability Deployment coordinates the work; accounting, participant allocation, security and operational direction remain attributable to their responsible components.
CD-02 — Preserve transaction purpose and authority.
Established
The parties, work, charging basis, accounts, agreement and applicable approvals can be identified.
CD-03 — Keep Work Order and Job Order distinct.
Established
Work Order deploys financial resources and supports assignments/time charging; Job Order supplies field instructions and grants no expenditure beyond previously approved contractual arrangements. Detailed references remain with the user community.
CD-04 — Retain discretionary Purchase Orders.
Established
Standard configuration excludes the feature; selected use preserves the underlying charge codes and contract authority.
CD-05 — Keep capital and operating accounting separate.
Established
Lease contains no capital charges; funding source does not silently determine research classification.
CD-06 — Respect research confidentiality and funding.
Established
Episteme membership, contributions and output rights follow its agreement; the group originates no AFE and inherits no automatic property working-interest allocation. It retains the research functions previously housed in Work Orders and deploys independently approved participant funding without a mandatory separate Work Order.
CD-07 — Preserve monthly reporting integrity.
Established
Each JOC has a Material Balance Report with the required financial, material, system and partnership balance; estimates and amendments remain identifiable.
CD-08 — Preserve rates and commitments.
Established business intent; detailed rules pending
Where the discretionary Revenue Per Employee method is used, its industry-based standard methodology and authorized rate/period are identifiable; previous commitments affect further commitment decisions.
CD-09 — Connect commercial findings to authorized action.
Integration proposal; F1, F2, F9
The finding, assumptions, investigation, decision and resulting authorized work can be followed without inferring diagnosis or approval from an alert.
CD-10 — Retain detailed economics and continuing recovery.
Integration proposal; F3, F4, F8
Well detail, shared allocations, earlier expenditure, additions and recovery contributions remain identifiable; statutory reporting and commercial evaluation are distinguishable.
CD-11 — Use actual costs and comparable methods.
Integration proposal; F5
Actual overhead, units, allocation methods and period/configuration status are visible without suppressing material property differences.
CD-12 — Evaluate contribution and compensation.
Integration proposal; F6, F7
Expected and observed outcomes, price/assumption changes, accepted work, charges and settlement can be reviewed separately; attribution methods develop with the Synallagi Targeting Framework.
CD-13 — Develop the Synallagi transaction context.
Established architectural direction; representation pending
Relevant security and business elements remain connected as modules contribute additional attributes; authority continues to be checked as context changes.
CD-14 — Connect Planning through Knowledge & Learning.
Established business direction; detailed exchanges pending
Relevant plans and requirements reach deployment through Knowledge & Learning; shared use of Pooling, Industrial Command & Control and Episteme preserves their authority and information boundaries.
CD-15 — Deploy operational financial resources through Work Orders.
Established
Operational financial resources are traceable through the Work Order to their independently approved source, purpose and beneficiary. Research funding retains equivalent traceability through Episteme's own arrangements.
CD-16 — Post accounting through Accounting Voucher.
Established
Accounting consequences, allocations and amendments reach the applicable General Ledger through the responsible accounting processes.
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.
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.
Matter
Development needed
Work Order and Job Order references
The user community determines shared contract, operation or evidence references and approved-change procedures. Preserve Work Order financial deployment and the separate Job Order function without introducing containment or duplicate spending authority.
Joint-interest decisions
Define how differing producer assessments are exercised through the property's governing decision rights.
Commercial calculation
Assign the responsible calculation service and specify recovery/return parameters, allocation, freshness and revision methods. No universal recovery period is adopted here.
Revenue Per Employee
Specify and validate the industry-based standard factor, conversion, grades, engagement representation and rate-amendment rules. Use is discretionary. No special small-producer/start-up floor is specified; producer size does not restrict Synallagi use.
Performance attribution
Develop through the Synallagi Targeting Framework, currently being written, the evidence distinguishing specialist contribution from changing prices, allocations or concurrent work.
Commitments and contingencies
Develop resource conflicts, budget overruns, research withdrawal and conditional commitments through the user community.
Period changes and continuing charges
Specify accrual replacement, amendment propagation, connected reconciliation and continuing task/charge triggers through the user community.
Synallagi transaction representation
Define applicable elements, attributes, relationships, source references, states and history without assuming every transaction requires every element.
Planning and shared capabilities
Specify the Knowledge & Learning connection and exchanges with Planning while preserving shared capability and information boundaries.
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.
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.
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.
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.
Concept
What must be understood
Responsibility and boundary
JOC and governing arrangement
Members, property context, applicable interests and decision rights
Governing organizational and agreement records establish authority; the JOC is distinct from its accounting records.
Producer capability
Expertise, resources, evidence and permitted use
Research & Capabilities retains the producer's capability information.
Scoped capability publication
What the producer makes available to a particular JOC
Knowledge & Learning supplies permitted information; publication does not commit the capability.
Requirement
Purpose, technical or financial finding, beneficiary and desired outcome
Planning or the originating function supplies the need; deployment coordinates its response.
Engagement
Agreed work, parties, scope, compensation and evidence of approval
Capability Deployment connects the arrangement to authoritative contracts, deployment and accounting records.
Pooling arrangement
Resources contributed, availability, commitments and agreed recovery
Pooling assembles capabilities; governing arrangements establish who may commit them.
Work Order
Operational financial resources, specialist assignment, time and charging
Work Order deploys approved resources; it does not originate any funding authority.
Command assignment and Job Order
Recognized field authority, instruction, scope and execution evidence
Industrial Command & Control establishes command; Job Order directs the authorized field action.
Episteme arrangement
Research purpose, membership, contributions, funding, allocation, approvals and output rights
Episteme retains the research functions formerly housed in Work Orders.
AFE and Lease context
Approved purpose, spending authority and accounting destination
Independent AFE approvals establish expenditure authority; Lease captures revenue, royalties and operating costs, with no capital charges.
Accounting evidence
Accepted work, time, valuation, allocation, voucher and posting references
Accounting Voucher posts the General Ledger; Partnership Accounting handles relevant joint allocations and Joint Account consequences.
Material Balance Report
Monthly financial, material, system and partnership balance
A specialized Accounting Voucher for each JOC, with period-specific configuration and identifiable amendments.
Commercial assessment
Actual economics, assumptions, recovery and alternatives
The responsible calculation capability owns the method and result; coordination uses authorized, identified versions.
Outcome review
Expected versus observed result and relevant influences
Review informs future capability selection and Planning; attribution develops with the Targeting Framework.
The engagement, publication and assessment concepts are proposed model distinctions. Their eventual record names and storage boundaries are not settled by this table.
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.
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.
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.
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.
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.
One possible operational path is:
Planning identifies a requirement and Knowledge & Learning supplies relevant permitted capability information.
Capability Deployment organizes the engagement and obtains the required approvals.
Work Order deploys operational financial resources.
Industrial Command & Control and Job Order provide field direction where required.
Specialized providers record work, accounting consequences and allocations.
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.
The following dimensions are proposed for detailed design, rather than one universal status list:
Dimension
Illustrative distinctions
Why it matters
Arrangement
Proposed, approved, amended, withdrawn
Preserves the terms and version accepted.
Resources
Indicated, reserved, committed, released
Separates availability from authorized use.
Work
Ready, in progress, paused, completed, disputed
Makes execution and exceptions visible.
Accounting
Estimated, accepted, posted, amended, reconciled
Distinguishes operational completion from period and ledger status.
Evidence
Preliminary, confirmed, superseded
Prevents later decisions from silently relying on obsolete results.
Outcomes
Expected, observed, reviewed
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.
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.
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.
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.
The Engineers and Geologists interface presents the selected JOC or permitted research context. Business Operations Management supervises processes across sub-modules. Capability Deployment organizes engagements, while responsible components retain authoritative business decisions, calculations and records.
Autonomous Asynchronous Transaction Orchestration communicates defined tasks, results and exceptions among specialized service providers. A provider may perform one element of a larger process. Business responsibility must remain explicit even where several providers operate software or perform tasks on behalf of the same function.
The architecture should distinguish:
Responsibility
Proposed implementation boundary
User interaction
Contextual views and authorized requests through Engineers and Geologists.
Process supervision
Durable process and dependency records, progress views, deadlines and exception assignment within Business Operations Management.
Engagement coordination
Requirement, capability selection, agreement references and links to approved deployment and outcomes.
Business decisions
Authoritative component operations that validate and record their own approvals, commitments and transitions.
Communication
Authenticated asynchronous delivery, durable receipts, correlation and recovery through orchestration.
Accounting and evidence
Authoritative vouchers, allocations, postings, measurements and period-specific histories.
Security
Current identity, representation, role, authority, permitted audience and purpose checks across each boundary.
These are logical responsibilities, not a required number of applications, databases or service-provider companies. Vendor and deployment topology choices require a later architecture decision. This companion does not presume that a particular cloud or software product already implements them.
Each coordinated engagement should have a stable reference connecting its requirement, parties, applicable JOC or research context, approvals, agreements, deployment, evidence and results.
An authoritative reference should identify the responsible component, record identity and the version or effective basis used. Cached information should carry its source version and retrieval time. Where records have business-effective periods and later recording dates, retain both so that amendments can be interpreted correctly.
A common transaction view is not a second authoritative accounting ledger. It may assemble information from component records and retain the evidence needed to explain a decision.
Work Order, Job Order, Episteme, AFE, Lease, accounting voucher and Material Balance Report must remain distinguishable. An engagement can connect applicable records without prescribing a universal containment hierarchy.
D5 must settle the permitted Work Order/Job Order references, scope checks, amendments and renewed authorization before production implementation. This companion does not specify one Work Order per Job Order, a mandatory Job Order for all research, or a Work Order parent for Episteme.
A proposed relationship record should express its purpose, source, target, governing agreement and effective version. Referential checks belong at the component boundary responsible for the relationship. Deletion or supersession of a source must not silently erase historical evidence.
Research & Capabilities retains the producer's capability information. Publication to Knowledge & Learning should explicitly identify the target JOC, permitted content, publisher's authority and source version. A publication operation must not default to all JOCs or the wider market.
The receiving view must enforce audience and purpose restrictions. Search indexes, cached results, notifications and logs must not reveal unpublished capabilities or confidential research subjects.
Changing or withdrawing a publication should affect future discovery according to an agreed policy. Historical records needed to explain an authorized engagement may require retention under restricted access. Retention and withdrawal rules must be specified together; withdrawal is not a promise that already disclosed information can be recalled.
Availability displays are advisory until the authoritative resource function accepts a reservation or commitment. Concurrent requests must not both succeed against the same remaining availability where the resource rules prohibit that outcome.
The component owning the relevant commitment should perform an atomic check and update, or an equivalent concurrency control, against its current position. Across independent components, use explicit pending states and acknowledgements rather than pretending there is one instantaneous global transaction.
Resource reservations and financial commitments are different constraints. Acceptance of one does not prove the other has succeeded. The supervisor should expose partial completion, identify what remains pending and follow an agreed release or escalation procedure.
Priority, expiry, reservation renewal and conflict resolution remain user-community decisions.
Every service-provider element should specify:
Business purpose and responsible function.
Required authoritative inputs and acceptable versions or freshness.
Authority required to request, approve and execute it.
Preconditions and dependencies.
Result, evidence and acceptance criteria.
Permitted side effects, including whether it commits funds or posts accounting.
Timeout, retry, dispute and escalation behavior.
Information disclosure and retention rules.
The provider's identity and the authority under which it acts must remain visible. Replacing a provider must not change the business meaning of the task or silently expand its access.
Process definitions should be versioned. An in-flight engagement should retain its applicable process basis; adopting a new definition requires a specified migration or continuation decision.
The following is a proposed message envelope, not a final API schema:
Information
Purpose
Message identifier and operation key
Identify a delivery and the intended business operation separately.
Transaction, process and task references
Connect the message to the engagement and work element.
Message type and schema version
Identify a request, acknowledgement, result or exception and its interpretation.
Sender, responsible function and intended recipient
Establish accountability and routing.
Initiating actor and authority references
Identify the claimed basis for the action; the receiver must validate it.
Input record references and versions
Preserve the business facts supplied.
Correlation and causation references
Connect a result to its request and an amendment to its cause.
Effective period and relevant timestamps
Distinguish business timing from delivery timing.
Expected state/version and expiry, where applicable
Prevent stale requests from acting against changed conditions.
Result status and evidence references
State what the responsible component actually accepted or performed.
Confidentiality and audience context
Constrain disclosure and downstream use.
A transport acknowledgement means a message was received. An accepted request means its business preconditions were satisfied. A completed task means its declared result exists. Those distinctions must remain visible to the supervisor and user.
The envelope should carry references and only the information needed by the recipient. It must not become a mechanism for copying every participant's confidential records to every provider.
Proposed reliability mechanisms include durable outgoing messages committed with the responsible local change, durable incoming-message receipts, duplicate detection and explicit processing outcomes. Equivalent designs are acceptable if they satisfy the same failure scenarios.
Delivery may occur more than once or arrive out of order. Duplicate delivery must not create a second commitment, charge, payment or posting. Deduplication should use the intended business operation and preserve the original accepted result. Reusing an operation key with materially different content should raise a conflict.
An out-of-order message must be held, rejected or reconciled under a defined rule. Arrival order alone must not determine the governing contract, rate or accounting period.
The system must not claim universal exactly-once effects across independent services. Where an external side effect succeeds but its acknowledgement is lost, reconcile with the authoritative external reference before retrying the effect.
A queued request does not preserve unlimited authority. The executing component must validate the current actor or delegated service authority, permitted purpose, applicable agreement, remaining commitment position and any relevant expiry.
For a delayed action whose authority or business basis has changed, pause or reject it and refer the exception to the responsible function. Do not silently substitute a new budget, contract, beneficiary or rate to make the request succeed.
The design must define which actions can continue under existing approved commitments after a role change and which require renewed approval. That is a business policy decision supported by technical enforcement.
Transient delivery failures may be retried under bounded rules. Business rejections require corrected inputs or an authorized decision. A pending human approval is a business state, not a transport failure to be retried until it succeeds.
Cancellation must account for work already performed, financial obligations and participant rights. A compensating accounting entry is not a reversal of physical field work. The orchestrator must never issue an automatic contrary field instruction merely to restore a software state.
A failed or abandoned process requires an assigned owner, visible remaining obligations and a documented recovery path. Operational safety and physical authorization remain with the responsible operational functions.
Operational deployment must link approved funding, purpose, beneficiary, assignments, commitments and accounting destinations through Work Order. The responsible function checks available authority before accepting further commitments.
Job Order processing separately verifies recognized Industrial Command & Control authority, applicable instruction and contractual scope. No request can use a Job Order to enlarge approved expenditure. Changed scope or budget must pass the relevant amendment and approval process.
Where the agreed process requires both financial readiness and a field instruction, orchestration may follow both prerequisites. Their detailed relationship remains D5; orchestration does not establish a universal record hierarchy.
Episteme requires its own arrangement and contribution controls. Participant AFEs may provide independently approved funding. Eligible operating-cost contributions may be charged to Lease under separate spending approval, and producers may contribute internally generated resource charges under approved arrangements. Lease accepts no capital costs. An internal resource charge must be distinguished from a cash contribution and does not itself create spending authority. No mandatory separate Work Order is introduced.
The design should support two related views: the agreed distribution of research costs and benefits, and the funding or contributions supplied to satisfy the arrangement. Contributions can include cash, time, samples, data, facilities, software and computing resources.
For each contribution, retain contributor, agreed nature, valuation or treatment, quantity or amount where relevant, acceptance evidence, conditions, funding approval references, applicable account treatment and delivery or commitment status. These fields are proposals; their exact schema remains to be agreed.
A noncash contribution must not automatically trigger a cash payment. Its accounting consequence follows the accepted agreement and the responsible accounting treatment. Cash shortfalls cannot be hidden by treating any unvalued contribution as equivalent funding.
The research arrangement must retain budgets, approvals, commitments, allocations, charging and output rights inherited from the former research Work Order function. Independent participant approvals are not replaced by a fictional group-issued AFE.
Conditional contributions and withdrawal require explicit dependencies. Before affected work proceeds, the responsible functions must establish whether required conditions are satisfied and funding remains authorized. Detailed contingency rules remain open, not removed from scope.
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.
JOC AFE approval is attributable to its members under the applicable governing arrangements. Independently approved producer AFEs retain their own authority. Funding an eligible Work Order or Episteme contribution with an approved AFE is supported; neither deployment tool creates or extends the approval.
Funding validation and accounting classification should be separate checks. Leases must reject capital charges; capital accounts must reject operating charges. Research classification must follow the nature and applicable treatment of the contribution, irrespective of an AFE funding reference.
Purchase Order functionality is discretionary and excluded from standard configuration. If enabled, it must connect contract acceptance, progress payments and holdbacks to the existing approval and coding structure.
Revenue Per Employee is also discretionary. If used, store or reference the authorized method version, factor period, grade, conversion basis, rate and units. Do not infer an hourly rate from an annual revenue figure without the approved conversion method. A new monthly factor must not silently reprice previously authorized work.
There is no producer-size eligibility threshold or special small-producer/start-up floor.
Accepted work, time, charges and contribution treatment should reach Accounting Voucher through defined accounting requests. Relevant participant allocation and Joint Account consequences belong to Partnership Accounting and the responsible allocation functions.
Provider acceptance, voucher creation, ledger posting, settlement and collection are distinct results. The supervisor should show their status through authoritative references and avoid interpreting a submitted invoice as a completed payment.
Producer pooled-resource cost recovery must be traceable through the Joint Account. This does not prescribe the same legal or payment arrangement for every supplier or research participant.
Each JOC's monthly Material Balance Report must identify the reporting period, configuration, contracts, included wells and relevant allocation bases. Close or clearing must be prevented while required financial, material, system or partnership balances remain unresolved.
Estimates and accruals must remain distinguishable from confirmed evidence. The detailed design must carry forward the source's next-month reversal approach, with specified replacement, late-data and exception handling. It must prevent double counting when confirmed information arrives after an estimate has been reversed or replaced.
A revision should retain the original evidence and affected period, identify its cause, invoke the appropriate accounting amendments and follow dependent allocations and reports. Reprocessing an amendment must not duplicate its financial effects.
The downstream-allocation example's 90-day sequence is illustrative. It is not a universal deadline after which data becomes immutable. Connected reconciliations determine the outstanding work; an accounting balance alone does not establish physical measurement accuracy.
The responsible calculation capability must define and version its method. The coordinating process should request a result using an identified scope and basis, including relevant wells, producer interests, period, currency, units, prices, actual costs, overhead, allocation basis, invested capital, additions and recovery contributions.
The result should identify method version, input references, assumptions, evidence status, calculation time and limitations needed for the decision. No fixed recovery period, return parameter or breakeven formula is adopted here.
Source amendments may require recalculation. Preserve the earlier assessment, the revised result and the affected decisions; do not erase the basis on which authorized work was originally undertaken.
Physical-production economics, financing or hedge effects, statutory reporting treatment and commercial recovery must remain distinguishable. Aggregated views should retain access to well details and shared allocations.
A financial anomaly should create a reviewable finding with evidence and an assigned recipient. It must not automatically issue field instructions or infer a technical diagnosis.
An authorized response may include investigation, correction, preservation, shut-in or a return to production. The JOC continues its other responsibilities. Each response retains the applicable financial and operational authority.
Outcome evaluation should connect expected technical and financial results to observed evidence, accepted work, charges and collections. Identify changes in prices, allocation and concurrent work that could affect attribution. Detailed methods develop with the Targeting Framework; this companion specifies the evidence needed, not a completed causal model.
During suspension, production-dependent service provider tasks should cease when their triggering activity ceases. Preservation, investigation, amendments and other continuing obligations retain separate triggers. The technical design must not implement suspension as a blanket deletion of all charges.
Enforce permissions at each authoritative service and data access boundary, including background tasks. A process identifier or message reference must not grant access by possession alone.
Research access must respect confidential formation, membership, approved additions and output rights. Non-rival output does not imply public disclosure. Knowledge & Learning publication requires separate permitted-use checks.
Audit records should identify requests, approvals, material state changes, versions and responsible actors without copying unnecessary confidential payloads. Define access, retention and export rules for those records before deployment.
The supervisory view should expose blocked dependencies, pending approvals, overdue tasks, conflicting versions, uncertain external effects, unresolved accounting balances and unaccepted outputs. Every exception needs a responsible recipient and a next permissible action.
Recovery design must cover interruption between local changes and delivery, provider unavailability, lost acknowledgements and restoration from backups. After restoration, reconcile process status with authoritative commitments, vouchers and external results before resuming work that could duplicate an effect.
Availability targets, recovery objectives, retention periods and monitoring thresholds remain to be agreed with the responsible functions. They are implementation gates, not invented service guarantees.
These requirements preserve the Security & Access Control model and define the engagement and evidence relationships required by Capability Deployment.
Use one persistent personal identity with separately approved employment, consultancy, representation and JOC assignments. Every material request must identify the active assignment, represented party, beneficiary and relevant client/JOC. The user interface should make that context clear before consequential action.
Context separation must apply to searches, cached results, exports, notifications, background tasks and AI-assisted work as well as visible screens. Switching context must not reuse another client's permissions or restricted material. Ending one assignment revokes or reevaluates access derived from that assignment while preserving separately authorized work and required historical evidence.
Evaluate representation and segregation-of-duties conflicts when a specialist serves multiple parties. A permitted consultancy relationship does not waive conflicts on an individual approval or transaction.
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.
Access acceptance checks must demonstrate that an assigned specialist can obtain all information and functions required to complete the approved work. Record denied or missing necessary access as an engagement exception with a responsible owner and resolution path. Trust mechanisms are to be developed with the user community; they must operate together with the existing representation, confidentiality and IP-rights model.
Retain authoritative references identifying the relevant IP, rights holder or licensor, authorized user or organization, license or agreement, permitted work and beneficiary, effective period, restrictions and permitted treatment of results. These are proposed information requirements, not a legal interpretation of any particular license.
Check the applicable permission before protected material or methods are used, including by an AI workload or external service provider. Client access, professional qualification and ability to operate the software do not substitute for the IP permission. Do not infer permission to disclose, sublicense, copy or train an AI system from permission to perform the engagement.
A changed or expired license must trigger review of affected future work under the governing terms. Historical evidence and continuing rights require their own retention and access basis; neither blanket deletion nor indefinite unrestricted reuse is assumed.
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.
Connect each value claim to its engagement, contribution, baseline, observations, assumptions, period, evaluation method/version and supporting records. Preserve the responsible evaluator and approval evidence. The Targeting Framework owns the agreed evaluation and distribution rules; Business Operations Management follows their use and outcomes.
Separately identify the hourly charge or salary arrangement and any agreed incremental-value compensation, including beneficiary, liable party, applicable terms and allocation basis. Acceptance of a technical result or publication of a performance statement must not itself create a payment entitlement.
Prevent duplicate recognition of the same incremental value across periods, engagements and contributor claims. Define reconciliation, disputes and recalculation when inputs change. Approved compensation reaches Accounting Voucher and relevant allocation processes through existing controls. Formulae, percentages and recognition rules remain for user-community development.
Detailed evaluation evidence is available only to authorized participants and auditors. A public performance statement requires a separately approved release containing anonymized results. Keep a restricted provenance reference connecting the released statement to its evidence, method/version and approval.
Review proposed releases for identifying source information and indirect identification through combinations of client, location, timing, formation or small populations. If the permitted disclosure cannot be achieved, withhold or revise the release. The user community must establish the release and anonymization criteria.
Preserve versions of cumulative performance statements. A subsequent correction to underlying evidence must trigger review of dependent statements and an authorized correction process. A public statement must not expose the restricted provenance or imply that a value claim has been independently verified unless that verification occurred.
Record the relevant times at which a finding or opportunity is recognized, reviewed, approved, made ready and acted upon. Identify waits for information, authority, resource availability, external dependencies and execution. Measures must distinguish stages and legitimate waiting conditions rather than rewarding bypass of required review.
Use these observations to improve the New Discipline with engineers, geologists and the user community. Targets and interpretation remain to be agreed; reduced elapsed time alone does not establish improved commercial performance or justify weaker authority checks.
Develop the component responsibility contracts and unresolved decisions first. Then build a representative operational path and an Episteme research path against controlled data. Include provider boundaries and failure recovery from the beginning.
Before production use, resolve D5; define funding and resource concurrency; approve research contingencies, classification and access rules; specify rates and calculations where enabled; establish amendment propagation; define specialist client contexts, IP permissions and value-evidence controls; and complete security and operational recovery review.
The Companion Review and Development Register supplies concrete scenarios and expected outcomes for that work. Passing a simulation demonstrates only the tested behavior under its stated assumptions. Operational readiness requires implemented component integrations, approved policies and evidence from the actual deployment environment.