Synallagi is a comprehensive Enterprise Resource Planning system and organizational architecture for North American oil & gas producers. Its scope connects operations, administration and accounting through the Joint Operating Committee. Decisions must reach the people authorized to implement them, those people must have the required resources, and the resulting work must produce a dependable financial record. People, Ideas & Objects, our user community and their service providers are designing the software and services through which these responsibilities can be fulfilled.
Accounting and administration are generally accepted as functions of an ERP system. Synallagi’s involvement in operations requires further explanation. The profitability of a property depends on decisions about its development, production, maintenance and preservation. Those decisions establish commitments, consume resources and create obligations. Synallagi must provide the means to organize their execution and account for their consequences. The operational domain follows from the responsibility to connect the economics of an asset with the work undertaken on it.
We expect stablecoin settlement and the tokenization of investment interests to become increasingly important to this architecture. These developments concern two distinct functions. U.S. dollar obligations can be settled through an agreed dollar-denominated stablecoin. Investment interests can be represented through legally constituted digital instruments, including tokenized producer shares or interests associated with properties governed through Joint Operating Committees. The pace of adoption remains uncertain, but the operating capabilities required to support these arrangements must be designed in advance.
The financial instrument determines the rights and responsibilities involved. Tokenized producer shares remain securities; their digital format does not remove the applicable securities requirements. Other proposed instruments require assessment of the rights conveyed, the issuer and the offering structure. Financial statements, disclosures and any SEC or CFTC reporting obligations must follow the requirements applicable to that arrangement. The GENIUS Act separately establishes a payment-stablecoin framework, including issuer reserve disclosures and supervision. Using a stablecoin for settlement and issuing a stablecoin are distinct activities.
These developments reinforce Synallagi’s requirement for actual, factual, standardized and objective accounting at the Joint Operating Committee level. Its monthly financial information must identify the property’s activity, revenues, costs, commitments and outstanding obligations, with evidence supporting the reported amounts. Estimates, accruals and unresolved matters must be distinguishable from confirmed information. This provides a foundation for the issuer’s applicable reporting and the information owed to investors. A monthly property report is an architectural requirement within Synallagi; the reporting entity and filings required by law depend on the actual legal arrangement.
The Joint Operating Committee, one of Synallagi’s nine Organizational Constructs, supplies the legal, financial, operational decision-making, cultural, communication, strategic and innovation frameworks through which the participating owners govern the property. Synallagi uses it as the organizational and reporting boundary for the undertaking. Ownership, production entitlements and obligations remain attributable to the parties identified in the governing agreements.
A reporting boundary does not, by itself, establish a separate legal entity or make the Joint Operating Committee the owner of the property. Any legal augmentation required for tokenization remains to be determined. The arrangement must identify the issuer, the underlying rights, the recognized holders, the treatment of distributions and funding obligations, and the rules governing representation, voting and transfers. The extent of that work must be established from the proposed structure. Token ownership cannot be assumed to confer membership in the Joint Operating Committee or authority to direct its operations.
The practical requirement is nevertheless clear. The assets underlying an investment need an organization capable of performing the obligations owed to their owners and other entitled parties. Decisions made through the Joint Operating Committee must become authorized operational activity. A single property must be capable of obtaining the complete combination of technical, operational, administrative and accounting services it requires. That capability must remain identifiable even where the people performing the work are distributed across several producers and service providers.
This is the significance of operational independence within Synallagi. A property can obtain its required capabilities through a coordinated network of participating firms and contracted services. It need not depend on undocumented contributions embedded within one producer’s corporate organization. Each contribution must have a defined purpose, responsible provider, authority, commercial basis and means of evaluating performance. The same discipline supports a property within a large producer’s portfolio and one administered through a separately constituted investment arrangement.
The Joint Operating Committee begins by designating the engineers, geologists and other responsible professionals who will develop and manage its approved operating program. Pooling gives it access to the differentiated capabilities of its participating producers. The Resource Marketplace makes relevant capabilities and contacts discoverable, including additional specialists where the membership cannot supply what the property requires. Individuals may be employees of a participating owner or engaged from the wider market. Their qualifications, availability, responsibilities and terms of deployment must be established for the work.
The proposed program must obtain the approvals required by the governing agreements. For capital work, the Authorization for Expenditure, or AFE, establishes the approved purpose, expenditure and conditions. Operating activities proceed under the applicable operating authority and approved budgets. Available funding must reflect existing commitments as well as recorded costs. These arrangements establish the financial resources available to the undertaking and the limits within which they may be deployed.
The Work Order connects those authorized resources with the operational engagement. It identifies the supplying party, assigned people and resources, beneficiary, scope, schedule, charging basis and required deliverables. It also establishes the accounting destinations for the resulting charges. A producer supplying specialized earth science & engineering capabilities receives an identifiable commercial engagement, while the Joint Operating Committee can establish what it is purchasing and how that contribution will be evaluated.
Industrial Command & Control establishes the recognized chain of command over the temporary organization assembled for the work. Participants can retain their employment and commercial relationships with different firms while operating under the authority assigned to their roles. The arrangement identifies who directs execution, who can approve changes, who accepts results and where exceptions must be escalated. Service industry vendors, suppliers and contractors engaged through Pangea, our Marketplace Interface, enter this structure according to their agreed responsibilities.
The Job Order translates the approved plan into instructions for field execution. Field work proceeds under a duly authorized Job Order issued by the recognized operational authority, with the necessary resources and conditions in place. The AFE provides financial authorization, the Work Order deploys resources, and the Job Order directs the particular field action. Authority to suspend unsafe work or respond to an emergency must be established in advance and remain immediately usable, with the action and its basis recorded.
Security & Access Control gives effect to these responsibilities. A person’s authority must follow the organization represented, the relevant Joint Operating Committee, the assignment and the stage of the transaction. Preparing a proposal, committing expenditure, directing field work, accepting a result and releasing payment are distinct responsibilities. Each participant must receive the information and functionality needed for the assigned work, with changes in delegation reflected in pending activities as well as current access.
Business Operations Management provides the integrated working and supervisory environment through which professionals connect property economics with these undertakings. Operations Management supplies the operational controls, while Accounting Voucher and Partnership Accounting retain their transaction, accounting and allocation functions. The Resource Marketplace supports access to capabilities. Research & Capabilities and Knowledge & Learning connect those capabilities with their development, supporting knowledge and permitted use.
The Episteme provides a separate arrangement for research and the development of new knowledge. Its findings may establish a capability that can subsequently be deployed through an operational Work Order and the applicable Job Orders. Keeping these purposes identifiable preserves the distinction between investigating a possible method and authorizing its use at a property. Operating experience and financial results can then inform further research and capability development.
Designing Transactions connects these contributions into a complete commercial undertaking. At the transaction level, an individual Synallagi and an Accounting Voucher are one and the same. The transaction can contain or reference the approved expenditure, agreements, Purchase Orders, Work Orders, Job Orders, inspections, invoices, allocations and payments. Its identity continues as commitments are made, work is performed and obligations are fulfilled.
Accountants and the relevant specialists establish reusable transaction designs through the Accounting Voucher module’s Transaction Design Interface. Engineers and geologists configure their particular undertakings through the third interface of the Business Operations Management module, Planning sub-module. Incorporating the capabilities and commitments required to accomplish the work. The design establishes what each participant will provide, the evidence of performance, the agreed valuation and the conditions for compensation. It also identifies dependencies, exceptions and the authority needed to change the arrangement.
Oil & gas development frequently involves substantial capital commitments, extended schedules, specialized equipment and consequential operational risks. A transaction may continue through engineering, manufacture, inspection, delivery, installation and commissioning, with warranties and other obligations extending beyond acceptance. Synallagi must preserve that continuity across organizations and accounting periods. Recurring operations, maintenance and preservation require the same connection between authority, activity and economic consequence, with designs appropriate to their scale.
Autonomous Asynchronous Transaction Orchestration coordinates the work as its conditions are satisfied. Authorized activities can advance without someone manually initiating every routine step. Participants can contribute at different times, while the system maintains the relationships among their work, evidence, approvals and obligations. An outstanding requirement holds the activities that depend on it; other work can continue within its existing authority.
For example, a compressor replacement may include equipment inspection, site preparation, transport and installation. Authorized site preparation can proceed under its Job Order while the equipment awaits inspection. A failed inspection holds shipment or payment where the agreement makes acceptance a prerequisite. The responsible participants address the exception and authorize any changes to cost or schedule. The transaction retains the work already completed, the unresolved condition and the obligations that continue.
Where the governing arrangements permit conditional administrative processing, costs, invoices or allocations can advance within that permission while a formal approval remains outstanding. The transaction records the basis and limits of that progress. Field execution, acceptance and payment retain their respective authorization requirements. Orchestration must preserve completed work and pending obligations through interruptions, changes in personnel and month-end boundaries, and prevent repeated messages from generating duplicate commitments or payments.
Synallagi remains the ERP system of record and the organizational architecture governing this work. AI agents can assist with discovery, analysis, preparation, monitoring and delegated execution. Their actions remain subject to the transaction’s authority, access, accounting rules and completion conditions, with accountable people responsible for professional judgment and exceptions. Specialized engineering and field systems contribute their results through defined interfaces to the same operational and financial record.
Monthly accounting draws on the activity that has occurred while preserving commitments and obligations that extend into future periods. Closing a month establishes the financial position for that period. The underlying transaction can continue until its commercial responsibilities have been fulfilled. And set a template of future monthly transactions. Actual charges, authorized estimates, incurred obligations and payments remain distinguishable. The Material Balance Report connects production and physical movements with contractual entitlements and the financial and volumetric reconciliations needed to support the reported results.
Where investment interests are tokenized, the design must also reconcile the recognized ownership records with the rights and distributions being administered. A transfer must be reflected according to its legal effectiveness and the applicable entitlement dates. Stablecoin settlement must connect the authorized payer, recipient, obligation, amount and confirmation with the accounting record. Payment confirmation establishes a settlement event; acceptance of work and any transfer of property rights retain their own evidence and conditions.
The resulting financial information returns to the Joint Operating Committee and the professionals responsible for the property. They can assess the work undertaken, the resources consumed and its contribution to profitability. Where production is unprofitable, the Decentralized Production Model calls for it to be shut in and the property placed in the inventory of innovative projects. The same operating architecture organizes the authorized preservation, investigation and remedial work required to pursue a return to profitable production. Submit their plans to the Joint Operating Committee for approval and continue.
Synallagi’s operational domain follows the full responsibility for turning an owner’s decision into accountable work and a measurable commercial result. Stablecoin settlement and tokenized investment interests make the need for that continuity more explicit. The Joint Operating Committee must be able to govern the undertaking, assemble its capabilities, direct authorized execution and account for its performance. Synallagi provides the proposed software and service architecture through which those responsibilities can be organized around the most profitable means of oil & gas operations.
Prepared for People, Ideas & Objects and our user community.
Document status. Version 3 develops the business purpose, conceptual relationships and proposed technical requirements of Pangea. It retains the first draft’s three-part format and detailed transaction provisions, incorporating the author’s notes on the overall vision, one Synallagi as one Accounting Voucher, Profitable Velocity, two coordinated screens and transactions spanning accounting months. It is a specification for review and development. The foundational sources remain S01, S02, S03, S04 and S05.
Name and scope. Pangea is the name of the marketplace. Its association with land reflects the setting in which oil & gas activity occurs. The name encompasses the people, resources, services and financial arrangements needed to develop and operate those properties.
Term
Meaning in this specification
Business Operations Management
The module that supervises the continuity of work for the selected business context.
Marketplace sub-module
The Business Operations Management responsibility for bringing a requirement into the market and following the resulting commercial process.
Marketplace Interface
The shared interaction component through which participants discover, meet, examine, negotiate and act.
Pangea
The name of the commercial marketplace experience presented through that interface.
Petroleum Lease, Resource and Financial Marketplace Modules
Three distinct domain modules supplying their respective records, rules and transaction capabilities.
The current scope retains all three Marketplace Modules. The earlier marketplace vision supplies useful ideas about discovery and interaction; its proposal to consolidate those modules is not adopted here. Detailed specifications for the three domain modules will follow this common foundation.
Pangea brings people and their capabilities into a commercial environment connected to the business of oil & gas. Engineers and geologists should be able to move from a property requirement to a productive conversation with the people who can meet it. A supplier should be able to explain an alternative, demonstrate equipment, establish its suitability and agree how the work will be performed. A field specialist and a financing representative should be able to participate where their contribution is needed.
The purpose is to shorten the interval between recognizing a need and carrying out the authorized response. That interval includes discovery, technical evaluation, commercial agreement, funding, physical work and accounting. Reducing Organizational Latency requires continuity across all of these activities.
Our user community will define and validate these processes with the people who perform them. People, Ideas & Objects supply the specification and development framework; the participating professions and service providers contribute the knowledge necessary to make the market useful. Their responsibilities, licensed Intellectual Property and compensation must remain identifiable as processes develop.
Pangea gives engineers and geologists a working environment in which to design the complete transaction required to accomplish their purpose. They can assemble its technical requirements, people, resources, contracts, expenditure, financing, performance conditions and accounting consequences in a graphical and virtual interface. The transaction takes shape through the way they configure those elements and their relationships.
At the transaction level, a Synallagi and an Accounting Voucher are one and the same. The system carries the complete designed transaction through its life. Purchase Orders, Work Orders, Job Orders, evidence, obligations and period-specific accounting results form part of that Synallagi through their identified records and relationships. The Accounting Voucher module supplies its design and accounting capabilities; the individual Accounting Voucher is the transaction being designed and carried out.
Consider an engineer purchasing and installing a 10,000-horsepower compressor. The design can include the selected configuration, its position at the property, assembly inspections, delivery, installation, financing, payments and holdbacks. An installation requirement such as an engineer-specified angle relative to the predominant wind, intended to support radiator cooling, belongs in the same transaction as the work and acceptance criteria needed to fulfil it.
The engineer works from an approved AFE and the authority assigned to the engagement. The interface connects the necessary Work Order, participants, Industrial Command & Control arrangements and Job Orders. As the work proceeds, ERP processing and Autonomous Asynchronous Transaction Orchestration act on the configured requirements, accepted events and existing authority. The specialist can see what is happening and intervene where judgment is required.
This is the guide for our user community: the detailed contingencies, evidence and controls in this specification are elements from which the specialist constructs a functioning Synallagi. The interface must make their relationships understandable and usable. The separate Accounting Voucher specification will develop the detailed voucher architecture while preserving this definition.
Profitable Velocity is the rate at which sound engineering and geological decisions become authorized action and demonstrable commercial results. It combines scientific judgment, timely execution and objective financial feedback. Increasing the number of actions performed is useful only where those actions contribute to the intended property and commercial outcomes.
The design anticipates increasing pressure on engineering and geological capacity as experienced people retire, recruitment constraints persist and the work required to sustain and improve production becomes more demanding. Pangea must allow specialists to manage a growing portfolio of transactions without continuously checking each individual process.
An engineer might have 50 active transactions for one client and 50 for another. This illustrates the working environment to be supported: the system follows routine progress, advances work within its authority and brings material exceptions or decisions to the engineer’s attention. The engineer moves between a professional domain, a particular client’s domain and the marketplace while each transaction retains its own client context.
Business Operations Management connects this work to two coordinated screens: the Pangea environment in which the specialist acts, and the financial information through which the specialist evaluates the results. Together they direct attention to the properties, obligations and decisions that most need the specialist’s expertise.
Synallagi’s Marketplace Interface is a shared commercial environment in which oil & gas producers, the service industry, our user community, service providers and other participants meet, examine opportunities, negotiate terms and organize the work necessary to complete transactions. Pangea connects those relationships to Synallagi’s ERP capabilities, governance and Autonomous Asynchronous Transaction Orchestration (AATO).
An additional purpose is to restore opportunities for serendipity and spontaneous order in commercial life. People, Ideas & Objects views the erosion of these opportunities as a significant loss for the development of industries across Western society. Businesses now work with people and organizations across great distances, yet the individual whose knowledge or capabilities could resolve a problem may be 2,000 miles away and entirely unknown to the person who needs them.
Telephone calls, email, social media and the internet support communication across that distance, both synchronously and asynchronously. Making contact possible, however, does not by itself create the circumstances in which people discover whom they should contact. Our ambition is to recover some of the informal encounters and decentralized coordination we associate with the commercial and industrial communities of the late nineteenth and early twentieth centuries, within a contemporary marketplace that can operate globally.
Pangea is intended to provide a place where people can browse, shop, meet and begin conversations without having every encounter arranged in advance. A participant might discover an unfamiliar supplier, hear an observation that changes an engineering decision, or meet someone whose capabilities make a previously impractical undertaking possible. These unexpected encounters can become the starting point for new relationships, transactions and innovations.
Serendipity concerns the useful discoveries that arise from such encounters. Spontaneous order develops as participants use their own knowledge and judgment to form relationships, coordinate activities and respond to opportunities. Pangea should provide conditions in which both can occur, connecting personal interaction with the practical means to act on what participants discover.
The spatial intelligence associated with Fei-Fei Li’s World Labs provides one inspiration for this interface. Participants could visit a supplier’s virtual premises, examine a representation of equipment, consider an installation at a property and discuss what is required to proceed. An engineer, supplier representative, field agent and financing representative could share the same commercial discussion. Each would contribute the knowledge and authority relevant to their responsibilities.
Selecting an item and choosing Purchase against AFE begins a governed commercial process. The resulting agreement identifies the actual product or service, the parties, authorized expenditure and performance obligations. For the substantial purchases addressed in this draft, a Purchase Order and its associated documents capture the agreed terms.
These transactions can extend over weeks or months. Inspection, assembly deadlines, transport, delivery, installation, acceptance, progress payments, holdbacks and warranties may all be involved. The parties must understand who will perform each activity, what must precede it, what demonstrates completion and who may accept the result. Designing Transactions supplies the connection between these commercial arrangements and their business and accounting execution.
Physical work remains part of the transaction. A field agent may join the virtual discussion, agree to inspect equipment during assembly, reserve time and later provide evidence from the supplier’s premises or the receiving property. The agreed process determines when that evidence permits shipment, acceptance or payment.
A bank may finance the supplier’s production requirements or provide an agreed form of payment support. Pangea records the institution’s actual undertaking and its conditions. Financing, guarantees, purchaser payment obligations and evidence of performance remain distinguishable.
Autonomous Asynchronous Transaction Orchestration coordinates authorized activities across organizations and over time. Independent work can continue while another activity awaits an inspection, signature or financing decision. Dependent work waits for its specified conditions. Changes preserve the history of what the parties agreed.
The environment must make the connection between representation and fact understandable. Participants can inspect product records, source documents and evidence behind an object. Artificial Intelligence can assist with discovery, comparison, preparation and coordination. Synallagi’s responsible functions govern commitments, approvals and accounting.
The foundations for this environment extend across the broader Synallagi. The supporting Accounting Voucher and Partnership Accounting discussions address transaction design, accounting and the coordination of complex activity. The Financial Marketplace discussion already envisages participants browsing a virtual commercial environment, meeting financial representatives and using the ERP capabilities available there. These references inform Pangea while the specialized functions remain within their respective modules.
The scope of the work ahead must also be understood. This specification and its accompanying handover remain a high-level outline. The detail presented identifies important relationships, contingencies and responsibilities, but a system capable of supporting even one oil & gas producer or one Joint Operating Committee requires substantially more definition. The document establishes a direction for development and a basis for discussion with our user community.
Our user community must supply the depth needed to make that direction operational. The people who understand the work must develop and validate the detailed processes, information requirements, transaction designs, accounting treatment, exceptions and service-provider responsibilities. Their knowledge must be carried into the software and tested against the actual circumstances in which producers, Joint Operating Committees and their commercial partners operate.
Providing these capabilities across an industry presents a much larger undertaking. Pangea’s ambition is to reconnect discovery, human relationships and commercial execution with the profitable operation of oil & gas properties. Some may regard that scope as too ambitious. Our view is that it may not yet be ambitious enough for the organizational and commercial challenges the industry faces. The scale of that ambition makes the detailed contribution of our user community essential.
This preamble develops the accepted Marketplace Interface preamble within Synallagi’s Business Operations Management structure. S02
Supporting wiki references: Accounting Voucher — first passage; Accounting Voucher — second passage; Partnership Accounting; Financial Marketplace.
Pangea connects a property, project, producer or Joint Operating Committee requirement with the market. Its commercial purpose is to improve the ability to obtain suitable capabilities and resources on terms that support profitable development and operation.
Price is one part of that assessment. Availability, technical suitability, reliability, delivery timing, installation cost, operating consequences, maintenance support and the supplier’s ability to perform may materially affect the result. Pangea should make these factors available to the responsible decision-makers without imposing a universal purchasing formula.
Business Operations Management supervises the process. Planning establishes or refines the need. Capability Deployment organizes the engagement of suitable capabilities. The Marketplace sub-module manages the commercial interaction and continuity with the domain Marketplace Modules. Accounting Voucher, Work Order, Industrial Command & Control and other responsible functions retain their established responsibilities. S01
A producer may bring an independently authorized requirement into Pangea. A Joint Operating Committee requirement retains the representation and decision rights of its governing arrangements. The interface must not assume that every participant is an employee of a designated operator or that every engagement concerns a Joint Operating Committee.
The market should also accommodate firms from other industries that supply oil & gas participants. Their participation depends on the transaction’s requirements and their approved role. A supplier need not become an oil & gas producer to demonstrate equipment or fulfil an order.
The starting point is a person acting in a known capacity. Synallagi’s persistent identity connects that person with separately approved assignments, clients and represented parties. An engineer may serve several producers or Joint Operating Committees. The selected assignment determines the information and actions available in the current engagement.
The contracting party, beneficiary, represented party, funding participant and owner of confidential information may differ. Pangea must keep those relationships explicit. An invitation to a virtual meeting establishes participation in that meeting; it does not establish contractual or expenditure authority.
A participant should be able to see the commercial capacity in which another participant is acting, subject to permitted disclosure. A supplier representative’s authority to describe a product can differ from their authority to accept a price or delivery obligation. A field agent’s authority to report an observation can differ from their authority to accept a milestone.
Discovery includes deliberate searches and encounters that expose useful alternatives. Participants may browse a supplier’s premises, follow a property requirement, examine a capability listing or be introduced to a specialist. Pangea should support the serendipity and personal understanding described in the earlier marketplace vision. S04
Search should consider the requirement’s relevant technical and commercial characteristics. A recommendation should explain the factors that made it relevant and distinguish sponsored placement, if introduced, from technical qualification. A published capability is an invitation to investigate; it is not a reservation or commitment.
A requirement may be met through capabilities already contributed under a Pooling arrangement or through an external market engagement. Pangea should connect with Capability Deployment so those alternatives can be considered within their agreed availability, recovery and authority. A producer’s capability information remains in Research & Capabilities; selective publication through Knowledge & Learning to a particular Joint Operating Committee does not authorize public marketplace disclosure. S01
Supplier profiles should connect the appropriate technical, commercial, field and billing contacts. Qualification evidence should identify its issuer, scope, currency and expiry where relevant. The responsible purchaser determines whether the evidence is sufficient for the contemplated engagement.
Private bids, producer costs, geological information, designs and unpublished capabilities must remain within their permitted audiences. Discovery and recommendation must operate within those same boundaries.
The primary Business Operations Management workstation presents two screens that remain available together. The first is the Pangea working environment: the specialist’s domain, a selected client or property, or the shared marketplace. The second presents the financial information for the properties and responsibilities selected in that context.
The financial screen presents actual, factual, standard and objective accounting, with an identifiable reporting period and source. The specialist can investigate profitability, the cost of work, commitments, accruals and emerging variances, and connect those results to the transactions that explain them. Estimates, work-in-progress assessments and proposed outcomes remain visibly distinct from confirmed actuals.
Selecting a property or Synallagi coordinates the two screens. The engineer can move from an adverse financial result to its underlying work and obligations, then configure the appropriate response in Pangea. As the response is performed and accounted for, its results appear in the financial view. A financial variance identifies a matter for investigation; technical diagnosis and field direction remain with the responsible specialists.
A right-click on a relevant item, person, obligation or property exposes the actions available in that context. These can include designing or amending the transaction, defining a Work Order, issuing a Job Order through the applicable authority, arranging an inspection, approving a permitted substitution or issuing an authorized payment. The menu identifies the selected client, transaction, subject and consequence of the action.
The specialist’s professional domain provides an overview of permitted assignments and matters requiring attention. A client’s domain provides that client’s working context. The marketplace supports discovery and interaction with the invited or permitted parties. Moving between these domains preserves the appropriate information and authority boundaries; a shared meeting displays the people and information relevant to its purpose.
The same controls support direct, conversational and mobile actions. They should avoid repeatedly asking the specialist to approve work already covered by an effective instruction or delegation. A new decision is required when the applicable authority, material terms or defined conditions require one.
Pangea should offer several ways to reach the same authorized transaction:
A spatial view of a supplier, property, asset or proposed installation.
Search, lists, maps and comparison views.
Conversation or voice assistance.
Direct access from a requirement, AFE, engagement or existing commitment.
Mobile access for people undertaking physical work.
These views share the transaction’s business meaning. Routine users should be able to reach an offer or pending decision directly. Spatial participation should be available when it improves understanding, inspection of alternatives or personal collaboration.
A shared session should show the current participants, represented parties, relevant object and status of the discussion. Participants must be able to distinguish an informal proposal, a revised offer, a request for approval and an accepted commitment.
Selecting equipment must identify the actual item or product configuration being discussed. Its authoritative record should provide the relevant specifications, drawings, quantities, units, condition, supplier, availability basis and applicable commercial offer.
An illustrative rendering, a scan of an existing item and an engineering model have different evidentiary uses. The interface must identify the source and status of the representation. A visually convincing model does not establish dimensions, compatibility, ownership, condition or availability.
World Labs describes Marble as generating and editing navigable 3D environments from several types of input, including text and images. It also explains that missing details can be invented during generation. That makes this technology a candidate presentation capability; suitability for Pangea’s engineering and commercial uses requires evaluation. S09
The action opens a transaction view containing the selected item, offer, buyer, beneficiary, property or project, relevant AFE and proposed terms. It then identifies the outstanding technical, contractual and funding requirements.
The interface should explain what the next action will accomplish. Preparing a request, submitting it for approval, accepting a commitment and releasing a payment have different consequences. A user’s approval must refer to the specific terms presented.
A change of item, quantity, price, beneficiary or other material term must be visible before the affected decision is taken. The interface should provide a clear path from the negotiated agreement to the underlying documents and responsible people.
Engineers and geologists design their individual Synallagi through Pangea, configuring the requirements and relationships needed to accomplish their work. Accounting Voucher’s Transaction Design Interface supplies the reusable business and accounting designs developed by accountants and the relevant specialists. Pangea presents those capabilities in the engineer’s or geologist’s working context. The specialist’s transaction design and the accounting design operate on the same Synallagi. S03
The design must establish what is transferred, how the parties identify and measure it, how it is valued, and how compensation occurs. Each specialist domain retains the knowledge required to perform its work; the transaction specifies the information and evidence that must pass between domains.
For a substantial equipment purchase, the design should express the following arrangements:
Element
Required business understanding
1. Subject of the agreement
Exact equipment configuration, quantities, services, documents and permitted substitutions.
2. Parties and representation
Who supplies, purchases, benefits, funds, performs, inspects and accepts.
3. Authority
Approvals and limits governing the commitment and each subsequent decision.
4. Performance
Assembly, inspection, delivery, installation and other agreed milestones.
5. Dependencies
Conditions that must be satisfied before the next obligation or action proceeds.
6. Evidence
Required records, observations and documents, with the responsible issuer and accepting party.
7. Compensation
Price, adjustments, payment conditions, holdbacks and the treatment of accepted partial performance.
8. Exceptions
Failed inspection, delay, changed scope, cancellation, dispute and recovery responsibilities.
9. Accounting
Funding references, expenditure classification, charge destinations and applicable accounting events.
10. Continuing obligations
Warranty, defects, retained amounts, documentation and other duties after delivery.
Pangea should let the specialist assemble a suitable transaction design and inspect its dependencies as it develops. Technical constraints, participants, financial arrangements and alternative paths must be captured as usable requirements, not left only in conversation. An unusual arrangement may require the responsible specialists to develop or amend a reusable design before the affected action advances.
The template has its own version and approval basis. A transaction retains the design version under which it was accepted. Improvements to a template must not silently change existing contracts.
The design coordinates commercial and accounting consequences. Technical instructions for physical work remain with the responsible operational functions.
Participants should be able to compare compliant offers, record exceptions and request clarification. Technical evaluation and commercial negotiation may proceed together, but the decision record must identify unresolved requirements.
An accepted offer must identify the parties and the precise basis of acceptance. Conversation summaries can help prepare this record. An AI-generated summary or an attendee’s interpretation must not substitute for the acceptance required by the agreed process.
The supplier must confirm the configuration, capacity and delivery obligations it is actually undertaking. Availability displayed during discovery requires revalidation when reservation or commitment occurs.
The Capability Deployment reference makes Purchase Order functionality discretionary, selected by the producer and excluded from standard Synallagi configuration. This draft selects that functionality for the high-value purchasing scenario requested for Pangea. It does not change the general configuration rule. S01
Before such a transaction can proceed, the applicable organization must have adopted and configured the Purchase Order controls. Where a different transaction class uses another governing agreement, its equivalent contractual and approval requirements must be defined explicitly. The Petroleum Lease and Financial Marketplace Modules will establish their appropriate instruments.
Purchase Order controls remain in the Accounting Voucher environment. Pangea presents and coordinates their use. The Purchase Order number does not replace an AFE, Cost Center or Lease charge code.
The Purchase Order and incorporated documents should address:
Product configuration, quantity, unit of measure, condition and required documentation.
Agreed price, currency, taxes, freight and other separately identified charges.
Assembly or manufacturing milestones and required completion dates.
Inspection arrangements, witnesses, methods, evidence and acceptance authority.
Delivery location, shipment conditions, responsibility for transport and handling, and agreed treatment of title and risk.
Installation, commissioning and site access responsibilities were included.
Prepayments, progress payments, partial payments, holdbacks and final payment conditions.
Warranty, defects, change control, cancellation and dispute arrangements.
These terms do not guarantee performance merely because they have been recorded. They establish obligations, evidence requirements and the agreed responses when performance differs from the contract.
Accepted changes require an amendment linked to the affected version. The record should make their effects on price, budget, schedule, financing, field assignments and prior acceptance understandable.
The authority to spend must exist independently of the interface. An AFE identifies approved expenditure within its governing arrangements. Approval attributable to Joint Operating Committee members must remain attributable to those members; independently authorized producer AFEs retain their own basis.
A budget reference alone is insufficient. The responsible function must establish that the purpose, amount, timing and party fall within the relevant authority and that remaining availability supports the proposed commitment.
For operational engagements, financial resources are deployed through Work Order. Work Order connects approved funding with intended use, beneficiaries, assignments, commitments and accounting destinations. This includes the operational financial deployment associated with the equipment purchase and its related services. It does not originate funding authority. S01
The Purchase Order expresses the commercial commitment. Work Order expresses operational financial deployment. Job Order expresses authorized field instruction. Their references must connect the process without imposing an unreviewed one-to-one hierarchy.
Pangea must distinguish proposed expenditure, approved authority, reserved capacity, contractual commitment, incurred cost, invoiced amount and payment. These amounts answer different questions.
The amount available for a new commitment must be supplied by the responsible authority and commitment controls. A pending invoice or an unacknowledged external request must not disappear from consideration merely because it has not yet been posted to the General Ledger.
Accounting classification follows the nature and approved treatment of the activity. Lease receives operating charges and contains no capital charges. An AFE reference does not justify classifying every associated amount as capital. Accounting Voucher and the responsible allocation functions determine the resulting accounting treatment.
Pangea may also help discover participants, software, data or other contributions for research. Such work follows Episteme’s retained research functions, including contributions, funding, allocation, approvals and output rights. A separate operational Work Order is not mandatory for an Episteme arrangement. S01
A field agent may contribute knowledge before the contract is accepted. They can help establish whether the proposed inspection can be performed, the site can be reached and the required equipment or specialists will be available.
An agreed assignment should identify the person or supplying organization, scope, location, schedule, qualifications, charging basis, beneficiary and evidence required. Operational financial deployment and time charging connect through Work Order. Resource availability must be confirmed; an invitation or calendar entry alone does not reserve the person.
Industrial Command & Control establishes the authority for field direction. A Job Order directs applicable physical work within the authorized contract and expenditure. It cannot create additional spending authority. The commercial discussion may prepare an instruction, but the operational function must authorize its issue.
An inspection result should identify the item inspected, relevant configuration or serial identity, method, date, location, findings, supporting evidence and inspector. The person authorized to accept the milestone records a separate decision where required. Observation, certification and commercial acceptance must remain distinguishable.
The record should accommodate partial completion, conditional acceptance, failed tests and disputed findings. Photographs or sensor readings support the evidence; their presence alone does not establish that an acceptance criterion was satisfied.
If connectivity is unavailable, a field agent may capture permitted evidence for later synchronization. The interface must make its pending status clear. No dependent shipment or payment should advance on the assumption that an unsynchronized inspection has been accepted.
Where a participant must be replaced, the transaction retains the assignment, outstanding work and evidence needed for an orderly handover. The appropriate Delegation of Authority must be approved for the replacement person. The Work Order and Industrial Command & Control arrangements identify the resulting responsibilities, and affected Job Orders are renewed or continued according to their applicable rules.
The replacement receives the information and authority required for the assignment. The outgoing person’s assignment is ended or amended as appropriate. Substitution of a person does not silently change the contract, technical specification, beneficiary or approved expenditure.
Large purchases can require supplier working capital, purchaser financing or a separate undertaking supporting payment. The Financial Marketplace Module will provide the domain processes through which suitable institutions and arrangements are discovered, evaluated and recorded.
A Purchase Order can support an application or a negotiated financing arrangement. It does not automatically establish a bank commitment or make funds available. A financing participant must issue and confirm its actual undertaking through its accepted process.
Pangea should distinguish at least:
Arrangement
What the transaction must establish
1. Supplier financing
Who borrows, who advances funds, permitted purpose, conditions, repayment obligations and relevant security or assignment references.
2. Purchaser financing
Approved facility or transaction funding, borrower, availability, draw conditions and repayment responsibilities.
3. Payment support
Issuer, beneficiary, covered obligation, amount, expiry, conditions and the nature of the institution’s undertaking.
4. Purchaser payment obligation
Amount and due event under the commercial agreement, independently of how either party finances itself.
5. Settlement
The actual payment instruction and authoritative confirmation of its outcome.
The supplier’s financing arrangement and the purchaser’s obligation must not produce duplicate payment. If a receivable is assigned or payment is directed to an approved beneficiary, the responsible financial and accounting controls must verify the instruction and preserve its basis.
Evidence may satisfy one agreement without satisfying another. An accepted assembly inspection could support a supplier draw while the purchaser’s payment remains subject to additional terms. Each obligation follows its own conditions.
Detailed instrument selection, jurisdictional requirements and institution onboarding belong to the Financial Marketplace specification. This draft defines the information and coordination needed to connect those arrangements to commerce; it does not prescribe a universal banking product.
The transaction should show what has been promised, what has occurred and what remains unresolved. An assembly milestone, release for shipment, physical receipt, technical acceptance, invoice approval and payment are distinct events.
Participants should be able to inspect the evidence and responsibility for each event. Where an event depends on a third party, the interface should identify the expected source and current status. A supplier’s declaration of shipment is not the receiving party’s acknowledgment of delivery.
A failed inspection should create an assigned exception with the affected obligations, proposed remedy and decision required. Independent authorized work may continue. Activities dependent on the failed criterion remain paused until the responsible function records an accepted resolution.
A schedule change should identify downstream effects. The supplier, carrier, field agent and receiving property may need revised commitments. Changing a date in the shared view must not silently reschedule those parties or amend their agreements.
Cancellation must account for work already performed, ownership of materials, outstanding charges, financing consequences and any continuing obligations. Closing the interface session does not terminate the transaction.
After delivery and settlement, warranties, defects, retained amounts or disputes may remain open. The record must support those obligations without presenting the entire purchase as either wholly incomplete or wholly finished.
Pangea provides visibility of the transaction’s accounting consequences through authoritative references. Accounting Voucher supplies the accounting representation and General Ledger posting. Partnership Accounting handles the applicable participant allocations and Joint Account consequences. Pangea does not maintain a competing ledger. S01
A Synallagi may remain active for three months, six months or longer. It remains one Accounting Voucher throughout the purchase, construction, installation, acceptance and continuing obligations. Closing an accounting month establishes that period’s financial position without terminating the transaction or requiring the specialist to reconstruct it for the following month.
The voucher contains or references the information needed for period accounting: contract values and amendments, work performed, work-in-progress assessments, inspection and acceptance status, invoices, amounts already recognized, payments and remaining obligations. AI can use that information to prepare accrual assessments and identify missing or inconsistent evidence. The responsible accounting design determines recognition, calculation and approval.
A commitment to purchase is distinguishable from work performed. Accruals should reflect the amount attributable to the reporting period that remains to be recognized through the relevant accounting process, using the approved method and available evidence. The full Purchase Order value, a payment milestone or an advance payment must not automatically be treated as the cost incurred in that month.
Each period’s accrual retains its inputs, method, evidence status and review result. Subsequent invoices and corrected progress information are matched to the existing recognition, with the required reversal, replacement or adjustment. This supports accurate period reporting and prevents the same work from being counted again while preserving one continuous Synallagi.
The relevant accounting process determines when a commitment, receipt, service performance, invoice, accrual, payment or amendment has a financial consequence. The workflow must preserve the distinction between evidence received, evidence accepted and accounting completed.
Allocation should retain the beneficiary, applicable producer interests, period, charging basis and agreement version. A payment supporting more than one obligation must be allocated without double counting. The same field time must not be charged twice or charged to the wrong client.
The proposed purchase’s commercial assessment should consider the total relevant cost and expected effect on the property. After performance, participants should be able to compare the expectation with observed technical and financial results. Responsible calculation functions retain their methods; Pangea presents identified results and assumptions.
Useful measures include time from requirement to qualified response, time awaiting decisions, delivery against accepted dates, first inspection acceptance, amendment frequency and unresolved obligations. These measures should explain delay and performance. Transaction volume alone does not establish commercial value.
The Marketplace Interface supplies continuity of interaction. Each domain module supplies the specialized meaning of what is being offered and transferred.
Domain module
Proposed responsibilities to develop next
Shared use of Pangea
Petroleum Lease Marketplace
Identify property interests and rights offered; establish the parties, permitted disclosure, title and interest evidence, applicable consents, effective dates and transfer conditions.
Discover opportunities, conduct controlled discussions and data access, negotiate terms and follow the authorized transfer process.
Resource Marketplace
Describe equipment, materials, services, people, facilities and capacity; establish suitability, availability, reservation, commitment and performance evidence.
Present offers, compare alternatives, engage suppliers and coordinate supply and physical work.
Financial Marketplace
Describe available financial arrangements, participating institutions, commitments, conditions, obligations and settlement relationships.
Bring financing participants into the commercial process and expose the status of their actual undertakings.
A property representation must distinguish physical geography from the legal and commercial interests offered. A resource representation must distinguish a product type from an available item or capacity allocation. A financial representation must distinguish an indicative offer from an accepted institution commitment.
A single transaction can connect all three domains. Those connections must retain each domain’s authority and evidence. The common interface must not assume that an equipment purchase, a lease-interest transfer and a financing commitment have identical contract forms or completion events.
The detailed boundaries, eligible instruments and specialized processes remain matters for the three module specifications.
An engineer identifies a requirement to purchase and install a 10,000-horsepower compressor at a property. Planning establishes the purpose and expected commercial effect. The engineer enters Pangea in the approved client and Joint Operating Committee context and designs one Synallagi—one Accounting Voucher—for the complete undertaking.
The engineer visits a supplier’s virtual premises and meets its technical representative. They examine an identified package and the source specifications. The engineer compares alternatives and records the proposed configuration. The visual environment helps their discussion; the accepted specification comes from the identified product and engineering records.
The engineer incorporates the approved site layout and specifies an orientation of X° relative to the predominant wind where that is part of the cooling design. X° denotes the value to be established by the responsible engineer, not a prescribed angle in this specification. The orientation, source engineering revision and relevant inspection or commissioning criteria become identifiable requirements of the Synallagi.
A field agent joins to discuss an assembly inspection and receiving-site requirements. The supplier proposes an assembly date and delivery window. A financing representative evaluates whether the supplier’s accepted order can support a separately approved funding arrangement.
The engineer selects Purchase against AFE and configures the applicable transaction design: equipment, technical constraints, parties, assembly and installation work, delivery, financing, payment conditions and holdbacks. The responsible functions establish expenditure authority, Work Order deployment, supplier capability, contractual acceptance and any outstanding approvals. The purchaser and supplier accept the exact Purchase Order version within that Synallagi.
Assembly proceeds. The field agent performs the agreed inspection and submits evidence. If the test fails, shipment and any payment dependent on that test remain paused. The parties may agree remedial work and a revised schedule through the amendment process.
When the required evidence is accepted, the authorized next steps proceed. The financing institution independently confirms any permitted draw. The supplier ships, the receiving party records receipt, and installation follows the relevant operational authority. Final acceptance and payment follow their contractual conditions.
If installation extends across several accounting months, the same voucher carries the outstanding work and its period positions. Work-in-progress evidence and contract values support each month’s accrual assessment. Invoices and later evidence reconcile with those amounts. A replacement field participant receives the appropriate approved Delegation of Authority and assignment without breaking the transaction’s continuity.
Throughout the engagement, the engineer sees the configured work and outstanding decisions in Pangea and the corresponding property accounting on the second screen. Routine authorized activity proceeds through orchestration; material exceptions bring the engineer back to the specific requirement or decision needing attention.
Accounting Voucher records the applicable financial events and Partnership Accounting applies the relevant allocations. Pangea shows the confirmed position and remaining warranty obligations. Subsequent performance informs Planning and the next purchasing decision.
This example establishes the first development case. Its success requires a continuous, evidenced transaction from requirement to outcome, including recovery when an important condition fails.
The conceptual model connects a market requirement with discovery, agreement, authorized obligations, physical performance and financial consequences. It establishes the distinctions the implementation must preserve.
Business Operations Management supervises continuity. The Marketplace sub-module coordinates commercial interaction through Pangea. Capability Deployment organizes engagements. The domain Marketplace Modules and other responsible components maintain authoritative records and decisions.
A common view may assemble those records without owning them. Presenting an AFE, Purchase Order, inspection and payment together does not transfer their authority to the interface.
At the transaction level, a Synallagi is an Accounting Voucher. It is the complete designed business transaction, retaining its identity as requirements, commitments, performance and accounting results develop. Within Pangea, the voucher progressively identifies:
Context
Questions the transaction must answer
Purpose
What requirement, property, project or commercial opportunity is being addressed?
Parties
Who is acting, representing whom, contracting, benefiting and supplying?
Subject
What exact item, service, capacity, right or financial arrangement is involved?
Authority
Which current permissions, agreements and approvals authorize each action?
Commercial basis
What offer, accepted agreement and transaction design govern the work?
Funding and deployment
What approved expenditure and operational or research deployment arrangements apply?
Obligations
Who must do what, by when, and subject to which conditions?
Evidence and acceptance
What has been observed, submitted, verified and accepted, by whom?
Accounting and settlement
What commitments, charges, allocations, postings and payments have been confirmed?
Outcome
What was achieved and what continuing obligations or disputes remain?
Not every transaction needs every record. A discovery session need not create an AFE. An Episteme contribution need not create an operational Work Order. A financial offer may remain indicative. The chosen transaction design establishes which elements are required for a particular action.
The model maintains one persistent Synallagi/Accounting Voucher identity for the designed transaction. It connects authoritative records and the versions used in each decision, including the relevant Purchase Orders, Work Orders, Job Orders, evidence and accounting results. One business transaction can require many records, period entries and external references. Those relationships do not require one physical database row, one journal entry or completion within one accounting month. The Accounting Voucher specification will determine the detailed record structure.
Concept
Required meaning
Responsibility and boundary
Identity and assignment
Persistent person or service identity, represented party, role and approved context.
Security & Access Control establishes and enforces access and authority; a marketplace session uses that context.
Requirement
Intended result, beneficiary, technical constraints and commercial purpose.
Planning or the originating function supplies the requirement.
Capability engagement
Selected specialist or organization, agreed scope and responsibilities.
Capability Deployment organizes the engagement.
Pooled capability
Contributed capability, availability, commitment and agreed recovery.
Pooling and the governing arrangements establish what may be deployed; selective publication does not commit it or make it public.
Published offer
Identified subject, responsible offeror, terms, permitted audience and validity.
The relevant Marketplace Module supplies domain meaning and authoritative offer status.
Representation
Rendered or conversational presentation linked to source records.
Marketplace Interface presents facts and evidence status; it does not certify facts by rendering them.
Negotiation
Proposals, questions, alternatives and agreed discussion records.
Marketplace sub-module coordinate the interaction; participants retain responsibility for their statements.
Transaction design
Versioned business process, transfer definitions, conditions and accounting consequences.
Accounting Voucher’s Transaction Design Interface supplies reusable designs; engineers and geologists configure the individual Synallagi through Pangea.
Purchase Order
Accepted commercial terms, amendments and applicable payment conditions.
Discretionary contract controls in the Accounting Voucher environment.
AFE and spending authority
Approved purpose, amount, parties and governing decisions.
Responsible expenditure approval functions and applicable participant authorities.
Work Order
Operational financial deployment, assignments, time and charging.
Work Order, within existing expenditure and contractual authority.
Job Order
Authorized direction for physical work.
Industrial Command & Control and the Job Order function.
Episteme
Research collaboration, contributions, funding, allocation and output rights.
Episteme retains its research responsibilities.
Evidence and acceptance
A claim or observation and the authorized decision about its sufficiency.
The issuing and accepting functions identified in the agreement.
Financing undertaking
Institution-issued obligation, availability, conditions and expiry.
Financial Marketplace coordination with the institution’s authoritative record.
Accounting result
One Synallagi/Accounting Voucher with its period entries, allocations, postings, payments and corrections.
Accounting Voucher, Partnership Accounting and the applicable financial functions.
Process progress
Dependencies, outstanding work, deadlines and exceptions.
Business Operations Management supervision and Autonomous Asynchronous Transaction Orchestration.
The logical ownership in this table does not dictate a separate application or database for every function. It does require an identifiable authority for every state change.
An engagement distinguishes the individual, employing or supplying organization, client, represented party, contracting party, beneficiary and relevant Joint Operating Committee. Combining these roles in one “customer” field would lose information needed for approvals and accounting.
A session also has an audience. The supplier may need the accepted technical specification and delivery location. A field agent may need inspection instructions and relevant site information. A bank may need accepted contractual and performance evidence. Their participation does not automatically justify access to producer margins, unrelated client files or the entire transaction history.
Switching assignments changes the active information and authority context. Search results, model context, attachments, cached views and notifications must follow that change. Ending one assignment removes the access derived from it while preserving unrelated assignments and appropriately restricted historical evidence.
The model supports a shared commercial record and private participant records. Disclosure is an explicit relationship between information, permitted audience, purpose and applicable agreement. It is not a property inferred from who happens to be present in a virtual room.
The professional domain assembles only those assignments and transaction summaries the individual is entitled to see. Selecting an action establishes its specific client, representing the party, property and Synallagi. The client domain applies that context to both the working screen and the financial screen.
Entering a shared marketplace session exposes only the permitted participants and information. Personal oversight of several clients does not combine their permissions, funds or confidential records. Domain switching changes the view and acting context; it does not transfer a transaction to another client.
Discovery, qualification, reservation and commitment are distinct.
An offer can identify a product without reserving a physical unit. A qualified supplier can lack available capacity. A technical recommendation can be suitable while expenditure remains unapproved. A reservation can expire before the parties accept an agreement.
The responsible resource function must confirm availability when its rules require reservation or commitment. The responsible financial function must confirm available authority independently. Pangea should present partial readiness rather than imply that success in one domain establishes success in all domains.
The acceptance record must identify the accepted terms, applicable versions, accepting parties, authority and effective time. Conditions precedent or other outstanding prerequisites must be explicit. The system must distinguish an agreement accepted subject to conditions from an unconditional release to perform.
Our user community must define how each transaction class handles offer expiry, competing reservations, partial awards and conditional commitments. The first equipment-purchase design should resolve these matters before a production pilot.
An obligation identifies the responsible party, required performance, due event or date, dependencies, evidence and accepting authority. Several obligations may progress concurrently.
The following diagram illustrates one contractual dependency. Other conditions may also apply.
flowchart TD
A["Accepted assembly obligation"] --> B["Assembly reported complete"]
B --> C["Inspection evidence"]
C --> D{"Authorized acceptance"}
D -->|Accepted| E["Check shipment conditions"]
D -->|Accepted| F["Check payment conditions"]
D -->|Rejected| G["Remedy or amendment"]
G --> H["Authorized corrective work"]
H --> C
E --> I["Release if conditions pass"]
F --> J["Request payment if conditions pass"]
Acceptance of inspection is one input to the next decisions. It does not establish that every shipment or payment condition has been met.
Evidence should retain the issuing party, subject, method, relevant time, source and integrity information. A subsequent correction must identify what it changes. Acceptance must identify the evidence considered, the criteria applied and the accepting authority.
AI may organize evidence or flag inconsistencies. The transaction design determines whether a defined automated check is sufficient or a responsible person must make the decision. The model cannot invent evidence, certify an inspection or waive a contractual condition.
One overall status cannot accurately describe a substantial purchase. The model maintains related but distinct states.
Dimension
Illustrative states
Important distinction
Commercial
Draft, offered, under review, accepted, amended, terminated.
Accepted terms can remain in force while an individual obligation is disputed.
Resource
Indicative, available, reserved, committed, released, consumed.
Discovery availability and committed capacity differ.
Expenditure
Proposed, approved, committed, partially utilized, exhausted or closed.
Authority and actual utilization differ.
Physical performance
Planned, scheduled, in progress, submitted for inspection, rejected, accepted.
Reported completion and acceptance differ.
Financing
Applied for, conditionally approved, committed, available, drawn, expired or discharged.
A lender decision and an available draw differ.
Accounting
Evidence pending, recognized under applicable treatment, invoiced, allocated, posted, adjusted.
Physical and accounting events need not occur simultaneously.
Payment
Proposed, approved, instructed, outcome unknown, confirmed, failed or corrected.
Submission and confirmed settlement differ.
Continuing obligations
Warranty active, holdback outstanding, defect open, dispute open, discharged.
Delivery does not extinguish every obligation.
These are conceptual states, not a final enumeration or a mandatory sequence. The responsible module defines valid transitions.
An unknown external outcome is a real state requiring reconciliation. It must not be represented as failure merely to permit a retry, or as success merely because a request was sent.
Funding source, expenditure authority, deployment, commercial obligation, beneficiary allocation and accounting classification remain separate attributes.
An approved AFE may support an operational Work Order. That Work Order may connect a Purchase Order and related service assignments. The resulting events reach Accounting Voucher and relevant allocation processes. The appropriate references depend on the engagement; this model does not require a universal record hierarchy.
Payment made by an institution, supplier financing and purchaser expenditure may represent different obligations. Their records must preserve whose liability is affected and what event has actually occurred.
The transaction view should support reconciliation among ordered, accepted, invoiced, posted and paid amounts. It should identify taxes, freight, holdbacks, credits and other adjustments separately where required by the agreement and accounting design.
Applicable purchase and service events also feed the established monthly accounting and reconciliation processes, including the Joint Operating Committee’s Material Balance Report where relevant. Completion of a marketplace obligation does not establish that all period balances have been resolved. S01
Period-effective information and the date on which information was recorded both matter. Late evidence or an amendment can affect a prior assessment or accounting period. The appropriate accounting process retains the original basis and records the correction.
The continuing Synallagi retains a succession of period-specific accounting positions. Each identifies its effective period, work-in-progress evidence, incurred or recognized amounts, invoices, payments, accrual treatment and remaining obligations. An estimate can be revised without erasing the basis used for an earlier period.
The month-end process obtains the accounting results required for that period while the commercial and physical obligations continue. An invoice, accrual reversal or correction remains linked to the same underlying performance so that its recognition can be reconciled. Closing the period and discharging the transaction are separate events.
An amendment identifies its originator, reason, affected records, revised terms, required approvals and effective basis. The process must determine which existing decisions remain valid and which require renewal.
An exception identifies the unmet condition and responsible owner. It should show affected obligations, permitted independent work, proposed resolution and escalation timing. An expired approval or revoked assignment must be evaluated according to the affected action and surviving contractual authority.
Revoking a person’s access does not cancel an organization’s accepted contract. Conversely, the continued existence of a contract does not permit a former representative to issue new instructions.
Withdrawal of a listing changes future discovery. It does not erase accepted commitments or evidence already needed for their administration. Retention, permitted access and withdrawal must be defined together.
Physical work cannot be undone by rolling back a software state. Cancellation, remedial work and accounting corrections require their respective business processes.
Every consequential action has an identifiable actor or service, represented party, authority and business purpose.
A shared session or generated representation does not establish authority, title, availability or accepted performance.
A requirement, recommendation, reservation and contractual commitment remain distinguishable.
An accepted agreement retains its exact terms, versions and acceptance evidence within one continuing Synallagi/Accounting Voucher, including where performance spans accounting months.
Purchase Order, Work Order and Job Order preserve their separate commercial, financial-deployment and operational meanings.
Operational financial deployment follows Work Order; Episteme retains its research route without a mandatory separate Work Order.
AFE authority is independently established; neither the interface nor orchestration can create or extend it.
Lease contains no capital charges, and accounting classification follows the responsible accounting treatment.
Financing, payment support, purchaser obligations and confirmed settlement remain distinguishable.
A dependent action advances only when its required authority, conditions and evidence are satisfied.
A repeated message or uncertain response must not create a duplicate commitment, charge or payment.
Accounting Voucher and the responsible allocation functions retain financial authority. The individual Synallagi is its Accounting Voucher; Pangea presents and operates on that transaction.
Client context and disclosure rights apply to both coordinated screens and every view, request, recommendation and retained record.
Amendments and corrections preserve the history needed to explain earlier decisions and continuing obligations.
The implementation should distinguish presentation, assistance, supervision, business execution and authoritative evidence.
Responsibility
Proposed boundary
Marketplace presentation
Spatial, search, map, conversational and mobile views of the same authorized business context.
AI assistance
Discovery, explanation, comparison, preparation and proposed coordination using permitted information.
Process supervision
Durable dependencies, outstanding obligations, deadlines, progress and exception ownership within Business Operations Management.
Business execution
Operations exposed by the component responsible for offers, commitments, expenditure, deployment, acceptance or accounting.
Cross-organization coordination
Authenticated requests, results and exceptions carried through Autonomous Asynchronous Transaction Orchestration.
External integration
Supported interfaces to supplier systems, financial institutions, logistics providers and selected Oracle services.
Evidence and security
Versioned decisions and evidence, with identity, representation, disclosure and authority enforced at each boundary.
These are logical responsibilities, not a required deployment topology. The interface may request a business operation; the responsible component validates and records it.
The architecture should remain useful if a spatial renderer is unavailable or replaced. A participant must still be able to inspect the authoritative terms, provide evidence and perform permitted actions.
A commitment, approval, voucher or payment instruction must have a named responsible function and system. AATO and an external workflow engine must not independently execute the same obligation.
Where a native Fusion workflow performs an approved operation, Synallagi should retain the request reference and consume its authoritative result. Where Synallagi owns the business function, an integration must not create a second competing source of truth.
Business ownership and physical system location are separate decisions. The integration design must establish their mapping before enabling writes.
Public-source review: 30 October 2026, UTC.
Capability
Evidence reviewed
Treatment in this draft
Oracle Fusion Companion
Oracle’s 26 October announcement describes a layer that coordinates Fusion transactions, workflows, approvals and agents through supported clients including ChatGPT. S06
A relevant integration path to evaluate for authorized Fusion work.
Oracle Fusion Agentic Home
The same announcement describes Oracle’s native experience using Companion. S06
A separate user entry point; Pangea’s interaction design remains its own responsibility.
Oracle Fusion Claw
Oracle describes specialist and long-running execution within its agentic applications. S10
A possible execution capability, subject to mapping a particular task and its authority.
Oracle AI Workspace
Oracle’s 27 October product article describes a broader ChatGPT experience across applications and data, and states that it is coming soon. S07
An announced direction, not a verified production dependency for this draft.
OpenAI’s account of the partnership
OpenAI states that Oracle is developing AI Workspace to connect Oracle applications and data with ChatGPT and approved workflows. S08
Corroborates the intended integration; does not establish tenant access or operation coverage.
Conference demonstrations
The supplied transcripts describe a ChatGPT plugin, native Fusion interaction, governed specialist work and enterprise ontology development. S05
Useful design evidence and questions for validation; demonstrations do not establish this project’s configuration.
The Fusion Companion announcement and the broader Workspace launch should not be collapsed into a single availability claim. The conference statement about a shipping plugin does not establish which procurement, acceptance or payment operations are exposed to a particular customer.
The reviewed material is sufficient to define an integration investigation. It does not supply a tested, complete implementation contract for Pangea’s substantial-purchase process. No access to a private drive is required to establish this public product direction.
The first integration study must identify the actual product, release, tenant configuration, entitlement, supported client and authentication arrangement. It must then demonstrate a bounded scenario using documented supported operations.
Verification
Evidence required
Identity and representation
The request reaches the intended tenant and legal entity under the correct actor or delegated service authority.
Read access
The user can retrieve only permitted requisition, supplier, contract, Purchase Order, receipt and financial information.
Proposed purchase
A request can be prepared with exact item, amount, currency, coding and supporting documents.
Approval routing
The operation enters the applicable native approval process and returns its actual state.
Authoritative write
A supported operation produces the expected business record without bypassing native controls.
Change handling
Amendments preserve versions and renew the approvals required by the changed terms.
Event continuity
Synallagi receives or can reconcile completion, rejection and unknown outcomes using stable references.
Recovery
Lost acknowledgements, duplicate requests, denied access and expired authority produce safe, explainable results.
The study must determine how Synallagi’s AFE, Work Order, Joint Operating Committee and partnership concepts map to supported Fusion structures. Similar names are insufficient evidence of equivalent meaning.
Fusion Cloud SaaS changes should use its supported application interfaces and workflows. This specification does not propose direct writes to its underlying database. Availability of Oracle database features in another environment does not imply administrative control over the database inside a SaaS service.
If a required Companion operation is unavailable, the integration can use another documented supported application path where suitable. The interface must show the real outcome and any required native step. A demonstration that simulates a response must identify that response as simulated.
Maintain one stable identity for the individual Synallagi and its Accounting Voucher across design, performance, accounting periods and continuing obligations. Connect its requirements, parties, subject, offers, accepted terms, approvals, deployment, evidence and results to that identity.
Every authoritative reference should identify the responsible component, record identity, version or effective basis and relevant time. Cached data should carry its retrieval time and freshness status. Historical decisions must remain explainable after source records change.
Represent the complete transaction through explicit, versioned relationships to its authoritative component records. Multiple journal entries, invoices, allocations or external system identifiers can be associated with one Synallagi/Accounting Voucher. The detailed mapping must preserve their purpose, effective period and reconciliation without creating a competing transaction master.
The graphical and virtual interface should persist the elements and relationships configured by the engineer or geologist as part of the individual Synallagi. Capture technical constraints, parties, responsibilities, expenditure and deployment references, financing conditions, dependencies, evidence requirements and exception paths in forms that the responsible business functions can interpret.
For a spatial requirement, retain the authoritative engineering reference, relevant coordinates or orientation, units, applicable configuration and version, and the acceptance criterion. A generated scene may illustrate the requirement; the stored engineering value and approved design determine what must be performed. Changes must identify the obligations and approvals affected.
The design should expose incomplete information and unsatisfied dependencies before an affected action executes. Our user community develops the reusable elements and rules, while the specialist configures the transaction instance. Detailed execution and accounting follow those accepted definitions.
Pangea needs shared definitions of party, representation, property, interest, resource, offer, obligation, evidence, authority and acceptance. Those definitions should connect the conceptual model to actual data and permitted operations.
The Oracle AI Data Platform transcript describes AI-assisted ontology creation followed by expert review and approval. S05 For Synallagi, our user community and the responsible domain stewards must validate inferred concepts and relationships before those relationships govern business execution.
An ontology proposal may identify a possible relationship. It must not automatically merge identities, equate a supplier’s product with an inspected serial item, or treat an operating charge as capital. Similarity can support investigation; authoritative identity and accounting meaning require their own validation.
Approved definitions, mappings and rules should have versions, owners and change history. Changes affecting live transactions require an explicit compatibility or migration decision.
An actionable object should resolve to a stable domain identity and relevant configuration or offer a version. Its presentation should expose the evidence status appropriate to the decision: illustrative, supplier-provided, inspected, accepted or otherwise defined.
The system must verify the current subject and terms when an action is submitted. A scene saved yesterday must not silently purchase a changed configuration today. Geometry, animation and conversational descriptions must not override the product or contract record.
Updates to a representation should preserve the relationship with prior decisions. If the item changes, the user must see that change and the affected approval process must be invoked.
The function owning a resource reservation should control concurrency against the current resource position. The expenditure function should independently control commitments against the applicable authority.
Two simultaneous requests must not both consume the same exclusive availability or remaining authority. Use an atomic local check and update, or an equivalent control, at the authoritative boundary.
Across organizations and systems, use explicit pending states and acknowledgements. If a resource is reserved but funding approval fails, the agreed expiry, release or escalation process applies. Do not represent the overall transaction as committed until its defined conditions are satisfied.
The accepted agreement should identify its incorporated documents, configuration, quantities, values, dates, obligations and accepting authorities. Approval should be bound to that exact material content.
A material change requires the responsible function to determine which approvals must be renewed. The AI assistant must not make a substitution or adjust an amount merely to satisfy an approval threshold.
Document, structured field and conversational summaries must be reconciled before acceptance. A disagreement between them is an exception requiring resolution, not an opportunity to choose whichever value permits execution.
An AI-assisted action should produce a structured proposal that identifies its purpose, subject, party context, exact parameters and intended consequences. Where approval is required, the person must be able to review those terms in a suitable view.
The execution boundary must validate identity, representation, authority, policy, current record versions and required conditions independently of the model’s explanation. A model-generated plan does not confer permission.
Automation may execute within an explicitly approved delegation or transaction design. The delegation should define the permitted actions, scope, limits, duration and escalation conditions. Required human approvals remain required.
AI may propose a comparison, plan or interpretation. Responsible calculation services should produce reproducible quantities, financial results and validation outcomes using approved methods and identified inputs.
The Fusion conference discussion distinguishes planning and reasoning from computational execution and staged actions. S05 Pangea should apply that distinction when evaluating equipment alternatives, financing scenarios or delivery options.
A calculation result should retain its method version, assumptions, units, currency, source records and evidence status. Estimates and scenarios must remain distinguishable from accepted values and actual results.
Retrieved supplier documents, messages, drawings and scene metadata are business content. They cannot alter system authority or instruct an agent to bypass approvals. A tool request arising from such content must pass the same independent controls as any other request.
Each process element should define its responsible function, input references, authority, preconditions, expected result, evidence, permitted side effects and exception handling.
Long-running progress must survive a disconnected user, closed browser, expired model session and restarted worker. Persist business state, deadlines and accepted results independently of the conversational session. Runtime threads alone do not preserve a transaction lasting months.
A process definition must be versioned. An in-flight transaction retains its approved basis unless an authorized change specifies otherwise.
Messages should identify the transaction, task, intended operation, sender, recipient, initiating authority, input versions, correlation, relevant times and expected result.
A transport receipt means delivery occurred. Business acceptance means the receiving function accepted the request under its rules. Completion means the declared result exists. Pangea should display these distinctions.
Requests should carry only the information required by the recipient. A shared transaction reference must not become a mechanism for disclosing every party’s confidential record.
Use durable outgoing and incoming records, operation identifiers, duplicate detection and reconciliation appropriate to the responsible systems. Repeated delivery must return or reference the original accepted result rather than create another commitment, charge or payment.
Reusing an operation identifier with different material content should create a conflict. Out-of-order events must be evaluated against the relevant state and versions.
If an external effect may have succeeded but its acknowledgment is lost, reconcile with the authoritative system before repeating that effect. This specification does not assume global exactly-once execution across independent organizations.
Transient technical failures may be retried under bounded rules. A denied approval, failed inspection or disputed invoice requires its defined business response. Retrying cannot manufacture approval.
A queued request must be checked against the authority and business basis applicable at execution. Expired delegation, changed terms, exhausted funds or revoked access can require a pause and renewed decision.
The business rules must distinguish new instructions from actions already authorized under a surviving commitment. They must not assume that an individual’s departure cancels the contract or that the contract authorizes every future action.
If the required authority or evidence cannot be established, the affected consequential action waits. Independent authorized activities may continue.
A replacement participant must be linked to the approved Delegation of Authority, effective assignment, scope and permitted information. Update affected Work Order and Industrial Command & Control references, and determine which Job Orders or outstanding decisions require reissue or renewed acceptance.
Preserve the outgoing participant’s recorded actions and the basis of decisions already made. Re-evaluate queued actions under the applicable current authority without duplicating work or transferring unrelated client access to the replacement.
Inspection and delivery evidence should identify the observed subject, source, issuer, relevant time, method and associated criteria. Files and structured observations should remain linked to the submitted version.
Acceptance should be recorded separately from submission where the design requires a distinct accepting authority. Corrections should retain their relationship to the original evidence and identify downstream decisions requiring review.
Offline evidence requires synchronization, identity checks and conflict resolution before it is treated as accepted. Capture time and synchronization time must remain distinguishable.
A software result cannot reverse a physical action. Remedial work requires operational authorization; financial correction follows the accounting process.
An institution’s undertaking should be referenced through an approved source and include its parties, scope, amount, currency, conditions, expiry and status. An uploaded application or an AI interpretation is not confirmation that the institution is committed.
A draw request, approved draw, payment instruction and settled payment require separate outcomes. Where authoritative confirmation is unavailable, retain an unresolved status and assigned reconciliation responsibility.
Supplier financing, assigned receivables and purchaser payments must connect to the relevant obligation and beneficiary. Changes to payment instructions require the applicable verification and approval process.
Detailed controls for particular instruments belong to the Financial Marketplace Module. The common interface must preserve them rather than flatten them into a generic “bank approved” flag.
The transaction design should define which accepted events reach Accounting Voucher and what supporting references they require. Accounting Voucher supplies the applicable accounting treatment and posting result. Partnership Accounting supplies relevant allocations.
Use precise decimal values, explicit currencies and units, approved rounding and conversion methods, and the correct effective period. The technical design must prevent amount or unit ambiguity from changing an obligation.
Reconciliation should connect commitments, receipts, accepted work, invoices, credits, payments and holdbacks. It should expose the cause of differences instead of forcing equality through an unexplained adjustment.
Corrections must retain their source, affected period and approval basis. Retrying a correction must not duplicate its financial effect. Pangea should consume the resulting accounting status without maintaining a second balance as the authoritative answer.
Period processing must reference the same Synallagi/Accounting Voucher throughout the transaction’s life. Record the contract and amendment versions, work performed, progress evidence, recognition basis, invoices already processed, payments, accruals and remaining obligations relevant to each period.
AI may assemble evidence, estimate progress where an approved method permits it and prepare an accrual proposal. Versioned accounting rules and calculation services determine the amount and classification, with the review required by the transaction design. Missing or inconsistent evidence must produce an identifiable exception or qualified estimate rather than an invented completion event.
Match later invoices and corrections to the performance and prior recognition they address. Apply the configured reversal, replacement or adjustment process without counting the same work twice. Preserve both the period-effective basis and the later recording date, and identify any affected allocation or report.
The implementation must demonstrate a transaction extending beyond six monthly closes, including partial performance, a late invoice, revised progress evidence and a holdback. The voucher remains identifiable and active where obligations remain, while each completed period retains its accounting evidence.
Every read, search, recommendation, attachment, write and background action must respect the selected assignment, represented party, permitted audience and purpose. Current authority must be checked at the responsible operation, including when requests originate through ChatGPT.
Prompt instructions alone are insufficient enforcement. Application and data access controls must enforce the boundary independently of the model. Indexes, caches, logs, notifications and generated summaries must not disclose information excluded from the user’s context.
The Deep Trust conference material emphasizes controls embedded in the data and access layers. S05 Pangea should evaluate the applicable Oracle capabilities while preserving its own testable access requirements. No particular product claim substitutes for evidence that the complete configured path enforces those requirements.
External supplier and field-agent participation should provide the information and operations needed for their assignment. The integration design should support participants who do not operate the purchaser’s ERP, subject to an approved identity and exchange arrangement.
Maintain synchronized transaction and financial contexts for the two-screen workstation. A selected client, represented by party, property, period and Synallagi must be explicit. If information refreshes asynchronously, show its effective basis and freshness so that a prior client’s or period’s figures cannot be mistaken for the current selection.
Provide contextual operations for the selected object and current authority, including Work Order definition, Job Order issue, inspection, approved delegation and payment. Route every operation to its responsible business function and return the actual outcome to the transaction view.
Support the specialist’s professional domain, client domains and shared marketplace without combining their access scopes. Exercise the illustrative workload of 50 active transactions for each of two clients. Orchestration should maintain routine progress and bring actionable exceptions, approaching obligations and required decisions to the relevant specialist.
Measure whether the interface reduces the specialist’s monitoring burden while retaining timely visibility of material issues. Prioritization may use deadlines, dependencies and identified financial significance, but the user must be able to inspect the underlying evidence and change the working focus. Profitable Velocity does not authorize relaxing an engineering requirement or exceeding delegated authority.
Authorized users should be able to establish who requested an action, what was approved, which versions were used, what the responsible system performed and what remains outstanding.
Operational monitoring should identify overdue obligations, stalled dependencies, unknown external outcomes and failed reconciliations. An assigned owner and recovery path must accompany unresolved exceptions.
Audit and support access must itself be scoped. Retention of evidence, confidential information and licensed Intellectual Property should follow the applicable business and organizational rules.
Service-provider replacement must preserve the transaction’s meaning, evidence and continuing obligations. Process execution should not depend on an individual provider’s undocumented interpretation.
The first implementation should demonstrate the complete design, execution and accounting of one 10,000-horsepower compressor purchase and installation. It should retain one Synallagi/Accounting Voucher across several monthly closes and present coordinated working and financial screens. Once that continuity is established, exercise a specialist’s portfolio across two clients and extend the spatial environment and transaction classes.
Stage Deliverable Exit evidence
1. Confirm business boundaries
Agreed process, ownership, Purchase Order configuration and authority model.
Our user community validates the normal case and material exceptions.
2. Establish the transaction foundation
One designed Synallagi/Accounting Voucher linking technical requirements, exact terms, parties, funding and deployment.
The specialist can configure and follow the transaction through coordinated working and financial views.
3. Demonstrate one integration
Supported path to authoritative purchasing and accounting operations in the selected environment.
Actual approvals, writes, period results, rejections and reconciliation preserve the same transaction identity.
4. Connect physical performance
Field assignment, inspection evidence, acceptance and dependent release conditions.
Failed and accepted inspections, engineering constraints and an approved personnel replacement produce the correct outcomes.
5. Connect financing
A defined institution workflow with explicit undertaking and settlement states.
Conditional approval and confirmed funding remain distinguishable; unknown outcomes reconcile correctly.
6. Add shared spatial participation
Source-linked objects and a shared supplier or property scene.
Users can negotiate without losing authoritative identity, version or disclosure boundaries.
7. Extend the domain specifications
Petroleum Lease, Resource and Financial Marketplace requirements.
Each domain validates its instruments, evidence, authorities and completion conditions.
A simulated bank or supplier adapter may support early process validation if clearly identified. Production readiness requires the actual authorized counterpart and supported integration to be demonstrated.
Scenario Required result
Normal equipment purchase The same identified agreement is traceable from requirement through acceptance, accounting and remaining obligations.
Wrong client context Another client’s confidential information and authority are unavailable to the request.
Concurrent resource or budget requests
Only valid availability and commitments are accepted; conflicts remain visible. Changed specification after approval The changed terms require the appropriate renewed decision.
Failed inspection
Dependent shipment or payment is paused while permitted independent work remains available.
Partial delivery
Only the accepted quantity and applicable obligations advance.
Financing conditions incomplete
No draw or payment support is represented as available without the required confirmation.
Lost payment acknowledgment
The process reconciles the original instruction before any repeat effect.
Duplicate or out-of-order event
No duplicate charge or commitment occurs; version and dependency rules prevail.
Revoked assignment during a queued task
The action is evaluated against current authority and surviving approved commitments.
Offline field evidence
Pending observations cannot be mistaken for synchronized and accepted evidence.
Late correction or contract termination
Prior evidence remains traceable and outstanding physical, financial and warranty obligations remain visible.
Complete graphical transaction design
The engineer’s compressor configuration, orientation requirement, parties, work, financing and acceptance conditions persist within one Synallagi/Accounting Voucher and drive the applicable process.
A voucher spanning accounting months
The transaction remains one voucher beyond six monthly closes; each period’s work-in-progress assessment, accrual, late invoice and correction reconciles without duplicate recognition.
Coordinated working and financial screens
Selecting a client, property or transaction updates both contexts; actuals, estimates, effective periods and stale data are distinguishable, with no cross-client disclosure.
Profitable Velocity across a portfolio
With 50 active transactions for each of two clients, routine authorized work progresses and the specialist receives actionable exceptions without manually polling every transaction.
Approved Delegation of Authority for replacement
A replacement receives the correct assignment, authority and relevant information; affected Job Orders and queued actions follow the approved handover without duplicated work.
These scenarios verify the consequential business boundaries. Further tests should follow the selected integration and identified failure modes.
Version 2 carries forward the first draft’s development decisions and incorporates the author’s additional direction. One Synallagi as one Accounting Voucher, the two-screen environment and Profitable Velocity are part of that direction. The proposed implementation choices below remain subject to the responsible review.
Decision Proposed starting position Responsible review
D1. Initial transaction class
Begin with a substantial equipment purchase using configured Purchase Order controls. Producer purchasing, accounting and engineering participants.
D2. Binding acceptance
Use exact agreement versions and the parties’ approved acceptance process; define when obligations become effective. Commercial participants and responsible contract specialists.
D3. Work Order relationships
Preserve operational financial deployment through Work Order; determine permitted links to Purchase Orders and Job Orders per case. Capability Deployment, Work Order, accounting and Industrial Command & Control specialists.
D4. Oracle system mapping
Verify the Fusion mapping for one continuing Synallagi/Accounting Voucher, its component records and period entries, using supported operations. Application owners, integration specialists and our user community.
D5. Authority for automation
Delegate bounded operations explicitly; define approved personnel replacement, required human decisions and execution-time checks. Security & Access Control and responsible business authorities.
D6. Inspection and acceptance
Separate evidence submission from acceptance where the contract requires it; identify qualified issuers and decision-makers. Engineering, supplier and field-service participants.
D7. Financing scope
Select one institution-supported arrangement for the pilot and specify its actual conditions and confirmations. Financial Marketplace participants and accounting specialists.
D8. Spatial fidelity
Label illustrative content and bind actions to authoritative records; define which uses require verified engineering models. Engineers, geologists, suppliers and interface developers.
D9. Publication and disclosure
Define public discovery, invited negotiation and restricted execution audiences. Marketplace participants and Security & Access Control.
D10. Domain extensions
Develop the three Marketplace Modules separately using this common transaction foundation. The respective Petroleum Lease, Resource and Financial Marketplace communities.
D11. Commercial assessment
Connect objective property accounting with transaction progress and evaluate Profitable Velocity using identified methods and evidence. Responsible economic, technical and accounting functions.
D12. Provider and Intellectual Property arrangements
Identify process ownership, permitted reuse, contribution rights and compensation in the applicable agreements. People, Ideas & Objects, our user community and participating service providers.
The next review should settle the first complete compressor transaction design and its Oracle mapping, including accruals across accounting months and the coordinated working and financial screens. The three domain specifications can then develop their specialized arrangements on that common foundation.
Paul Cox’s instructions establish the Pangea name and its association with land, the high-value purchase scenario, field-agent participation, possible bank support and the three Marketplace Modules. His notes appended to the first Google Doc provide Version 2’s additional direction on specialist-led transaction design, the equivalence of a Synallagi and an Accounting Voucher, Profitable Velocity, two coordinated screens and accounting across multiple months.
Reference
Source and use
Joint Operating Committee Capability Deployment — Business and Technical Specification — Release 1. Structural reference and authoritative project baseline for module responsibility, Purchase Order configuration, Work Order, Job Order, AFE, Lease, Episteme and accounting boundaries.
Marketplace Interface — Preamble, 26 October 2026. Accepted discussion foundation for the virtual commercial environment and substantial purchases.
Designing Transactions, People, Ideas & Objects wiki. Establishes Accounting Voucher’s Transaction Design Interface and reusable transaction design.
21st Century — Markets & the Marketplace Interface. Background on discovery, people, capabilities and virtual interaction. Its older module-consolidation proposal is superseded by the current scope.
Oracle AI World 2026 Conference Transcripts, seven Wispr Flow recordings from 26–27 October. Relevant passages reviewed include Fusion Companion, governed specialist execution, Deep Trust and expert-approved ontology development. Transcription and demonstration claims are treated as conference evidence.
S06, Oracle,
Introduces New AI-Powered Ways to Execute Work Across Oracle Fusion Applications, 26 October 2026. Public evidence for Companion and Agentic Home.
S07, Oracle,
Introducing Oracle AI Workspace: Put AI to work across your enterprise, 27 October 2026. Public description and coming-soon status of Workspace.
S08 OpenAI,
Expands partnership with Oracle to bring its apps to ChatGPT, 27 October 2026. Corroborates the Workspace development direction.
S09, World Labs,
Marble: A Multimodal World Model, 12 November 2025. Spatial-generation capabilities and the distinction between generated detail and supplied evidence.
S10, Oracle,
Advances Outcome-Driven AI Across Fusion Applications, 26 October 2026. Context for Fusion’s agentic applications and Claw.
The technical requirements, proposed states, development stages and review decisions in this draft are Synallagi design proposals derived from the business requirements. Vendor announcements do not establish that those requirements are already implemented.