Showing posts with label Synallagi. Show all posts
Showing posts with label Synallagi. Show all posts

Sunday, November 15, 2026

Designing Transactions

Synallagi · Background · Handover · 5 November 2026

Please Note:

The vision behind Synallagi comes into focus in this seemingly obscure topic: an ERP system that captures the substance and detail of the work undertaken throughout oil & gas. Through Autonomous Asynchronous Transaction Orchestration, Synallagi coordinates that work and the people, capabilities and resources involved, with a single purpose: providing the most profitable means of oil & gas operations, everywhere and always.

Designing Transactions is how Synallagi connects a business purpose with the people, capabilities, authority, resources and accounting necessary to accomplish it. The design establishes what the participants intend to achieve, what each party undertakes to provide, how performance will be established and how the resulting value, costs and obligations will be accounted for. We are designing Synallagi so that these arrangements can carry through into execution, with routine processing performed by computers and professional attention directed to the decisions that require it.

Everything undertaken in Synallagi is focused on providing the most profitable means of oil & gas operations. Transaction design gives that purpose a practical expression. An engineering decision must connect with the authority to act, the capability to perform the work and the financial information needed to evaluate its result. An accounting process must preserve the business meaning of the activity it records. A commercial agreement must remain usable by the people and systems responsible for fulfilling it.

The economic foundation includes Carliss Baldwin and Kim Clark’s paper, Where Do Transactions Come From? A Network Design Perspective on the Theory of the Firm. They examine production as a network of tasks and transfers, explaining the additional work required to turn a transfer into a transaction: defining a common basis for what is exchanged, measuring it, establishing its value and arranging compensation. Where these activities can be performed economically influences where transactions can occur.

We apply that reasoning by asking the participants to establish a precise subject of exchange. A unit of service might be an accepted allocation calculation, an inspection or a completed accounting process. An equipment purchase requires an identified configuration and quantity. Each design establishes the evidence of delivery, the agreed valuation and the conditions of compensation. The design must also justify its own complexity: useful divisions of work depend on interfaces that participants can understand and operate economically.

Richard Langlois and Nicolai Foss’s Capabilities and Governance: The Rebirth of Production in the Theory of Economic Organization adds a complementary perspective. Production depends on specialized knowledge, including knowledge that is difficult to articulate or transfer. Coordinating people who possess different capabilities is itself an economic problem. Their work supports examining the ability to organize productive activity alongside the costs and incentives associated with exchange.

For Synallagi, this means evaluating the complete commercial result of a proposed arrangement. A low administrative cost cannot compensate for unsuitable equipment, unavailable expertise or a poorly coordinated installation. Shared software and reusable designs should reduce repetitive processing costs, while differences in capabilities, timing and coordination will continue to influence profitability. The actual costs and benefits must remain measurable; standardization does not establish that transaction costs will become identical or immaterial in every circumstance.

Friedrich Hayek’s The Use of Knowledge in Society provides another foundation: economically useful knowledge is dispersed among individuals who understand particular circumstances. Coordination depends on enabling them to act on that knowledge and communicate what others need. Synallagi applies this principle through specialization and clearly defined exchanges of information. An accountant, an engineer and a supplier each contribute their own expertise, with sufficient shared information to coordinate their responsibilities.

This is also the relationship between transaction design and Pangea, our Marketplace Interface. Pangea is intended to help people discover capabilities, meet one another, discuss alternatives and form commercial relationships. Its synchronous and asynchronous channels should create opportunities for serendipity and spontaneous order across geographic and organizational distances. Designing Transactions gives participants a practical means to act on what they discover. Useful encounters can develop into agreements whose obligations, authority and performance remain connected.

Transactions is an Organizational Construct within Synallagi. It organizes commitments and their fulfilment across the boundaries of the producer firm, the Joint Operating Committee and the market. The Joint Operating Committee supplies the applicable property context and decision rights. Markets provide access to capabilities and resources. Trust is supported by identifiable responsibilities, evidence and accountability. Transaction design connects these arrangements to the particular work being undertaken.

At the transaction level, an individual Synallagi and an Accounting Voucher are one and the same. This is the complete designed business transaction, retaining its identity as requirements become commitments, work is performed, costs arise and obligations are settled. It can contain or reference many records: agreements, Purchase Orders, Work Orders, Job Orders, inspections, invoices, allocations, accounting entries and payments. Those records contribute to one continuing commercial undertaking.

The Accounting Voucher module provides the Transaction Design Interface through which accountants and the relevant specialists develop reusable business and accounting designs. Engineers and geologists use those capabilities through Pangea to design their particular Synallagi. The accountant establishes the processing and accounting arrangements; the technical specialist configures the requirements and relationships needed to accomplish the work. Suppliers, field personnel, financing participants and other professionals contribute the knowledge and commitments relevant to their responsibilities.

The distinction between a reusable design and an individual transaction is essential. A design can serve many engagements while each transaction retains its own parties, terms, authority, evidence and financial consequences. Each Joint Operating Committee can use common methods without surrendering the particular circumstances of its property or agreements. Improvements to a template require an identifiable version; applying an improvement to an existing transaction requires the appropriate review and authorization.

Consider an engineer purchasing and installing a 10,000-horsepower compressor. A material undertaking which the engineer is responsible for. The final costs may fall within the $15 to $20 million range. The commercial purpose begins with the property requirement and the expected effect on profitable operations. Through Pangea, an engineer can examine an identified equipment configuration, discuss alternatives with the supplier and bring a field specialist or financing representative into the conversation. The resulting design connects the selected equipment with assembly, inspection, transport, installation, commissioning, compensation and continuing obligations. The engineer is delegating his authority to those who are able to bring those skills to the Synallagi. Work Orders and Job Orders are how this is accomplished.

The engineer can include a technical requirement such as the compressor’s orientation relative to the predominant wind where that affects the cooling design. That requirement must connect to the applicable engineering record, installation instruction and acceptance criteria. The graphical or virtual representation helps people understand and discuss the arrangement; the identified specifications and accepted evidence establish what must actually be delivered and installed.

Selecting Purchase against AFE connects the proposal to the applicable Authorization for Expenditure and its approved purpose, amount and conditions. The transaction identifies the person acting, the party represented, the beneficiary and the authority for each consequential decision. A specialist serving several clients retains the correct client context throughout the engagement. Operational financial resources are deployed through Work Order, and field instructions proceed through Industrial Command & Control and the applicable Job Orders.

For this substantial purchase, the configured Purchase Order records the commercial agreement. It can establish assembly deadlines, inspection requirements, shipment and delivery conditions, installation responsibilities, progress payments, holdbacks, warranties and remedies for failure. Purchase Order functionality follows the producer’s adopted configuration. Other transaction classes retain their appropriate agreements and instruments. Research collaboration follows Episteme’s arrangements for contributions, funding, approvals and output rights.

A field agent can participate while the transaction is being designed, agree the scope and timing of an inspection, and subsequently supply the required evidence. The design identifies who may accept that evidence and what the acceptance permits. A failed assembly test holds the shipment or payment that depends on it, while separately authorized site preparation may continue. The affected participants can agree remedial work and any changes to cost or schedule within the same transaction history.

A bank may provide supplier financing, purchaser financing or an undertaking supporting payment. Each arrangement must identify the institution’s actual commitment and its conditions. The design connects these obligations without confusing them: an inspection might support a supplier’s financing draw while a purchaser’s payment remains subject to further performance. Where an authorized settlement uses a stablecoin, the accounting and confirmation requirements must be defined for that method. Confirmation of payment remains distinct from evidence of delivery, acceptance or any required transfer of rights.

Autonomous Asynchronous Transaction Orchestration carries the designed process forward. Autonomous means that eligible work can proceed under established instructions and authority without someone manually initiating every step. Asynchronous means that participants and activities can progress on different timelines. Orchestration coordinates their inputs, obligations, evidence, results and exceptions so that each activity proceeds when its own conditions are satisfied.

This allows commercial progress to be separated from the completion of every related administrative step. Where members of a Joint Operating Committee have reached verbal consensus and the governing arrangements permit conditional processing, invoices, costs and allocations can be prepared or processed while a formal ballot, signature or approval remains outstanding. The missing authority stays visible, the provisional status remains explicit and the transaction advances only within the permission already available. Finalization or payment requiring that outstanding approval waits for it.

The design therefore needs to identify which activities may proceed, which depend on unresolved matters and who must address an exception. Once the required approval or evidence arrives, the process resumes from its recorded position. Progress must survive an interrupted session, a system restart or the replacement of a participant. Repeated messages must not create duplicate commitments, charges or payments. These are requirements for maintaining the commercial integrity of work conducted across organizations and over time.

An individual Synallagi can remain active for three months, six months or longer. It remains one Accounting Voucher throughout its commercial life. Closing an accounting month establishes the financial position for that period while outstanding work, commitments and continuing obligations remain attached to the same transaction. Reusing a design in another engagement and carrying an existing transaction into another month are separate activities.

Period accounting draws on the work performed, accepted evidence, contract terms, invoices and amounts already recognized. A purchase commitment, an advance payment and an incurred cost represent different circumstances. The approved accounting design determines the appropriate treatment. When later invoices or corrected information arrive, they reconcile with existing recognition through the required adjustment. This continuity supports reliable monthly reporting without reconstructing the transaction or counting the same work twice.

Processing can consequently occur throughout the month as information becomes available. Service providers can distribute their work more evenly, investigate exceptions earlier and reduce the accumulation of unresolved items at month-end. The objective is to shorten the interval between economic activity and dependable financial information while preserving the evidence and authority on which that information rests.

The organization of service-provider work follows the same principles. Our user community brings its professional knowledge into the designs, and its independent service-provider organizations perform, supervise and improve their defined services. A process may involve several providers, each responsible for an identifiable contribution. The parties establish the input, work, result, charging basis and evidence required for that contribution.

Consider a Joint Operating Committee producing natural gas and liquids through a processing facility. The relevant designs can connect measured production with production accounting, processing arrangements, sales, royalties, allocations and the applicable provider services. Each process uses the information necessary to perform its work and returns an identifiable result. An agreed, evidenced unit of work supports the associated charge and its attribution to the correct beneficiary and period.

When production ceases, the production-dependent processes and charges cease with it. Any remaining contracted obligation or separately authorized work must be identified on its own basis. This supports the Decentralized Production Model by making the relationship between activity and administrative cost explicit. It also provides a basis for distinguishing the actual work required by different commodities, properties and operating arrangements.

Common designs allow the cost of developing reusable knowledge and software to be shared across many uses. Each engagement retains the costs actually attributable to it and the agreed basis for any shared charges. The licensed Intellectual Property, contribution rights and compensation of the participating service providers must remain identifiable. Reuse creates an opportunity to improve productivity while supporting the organizations responsible for maintaining and advancing the capability.

Transaction design also changes the relationship with the service industry. Suppliers and contractors contribute to the definition of feasible work, evidence and commercial terms. Their technical, field, commercial and accounting contacts should be available to the appropriate participants through the Resource Marketplace. Designing an arrangement together can identify gaps before commitment, reduce conflicting expectations and establish a more dependable basis for performance and payment. Profitable operations require capable counterparties with sustainable commercial arrangements.

Artificial Intelligence can assist throughout this work. It can help locate suitable designs, compare offers, prepare transaction elements, identify missing information, assess progress and bring exceptions to the responsible professional. Conversational access can help a specialist investigate a property’s costs and follow them to the underlying commitments and work. These capabilities operate within the transaction’s established authority, information boundaries and accounting rules.

Where an AI agent has delegated execution authority, that authority must have a defined scope and remain attributable to a responsible party. A recommendation, a proposed amendment and an accepted commitment have different consequences. The transaction must preserve those distinctions and the evidence supporting each action. Participants need to be able to understand, challenge and correct the result, including when a process encounters circumstances its design did not anticipate.

Trust develops through this continuity between responsibility, action and evidence. A participant can establish what was agreed, who had authority, what work occurred, what remains unresolved and how the financial consequences were determined. Each party receives the information appropriate to its role and rights. As we have stated elsewhere, trust does not scale through supervision alone. It scales through architecture.

Business Operations Management provides the supervisory view of this work. The proposed two-screen environment places the Pangea working context alongside the relevant financial information. An engineer or geologist can move from a property’s result to the transactions that explain it, design an authorized response and subsequently examine its technical and financial consequences. Estimates, commitments, actual costs and payments remain identifiable within that view.

This is the basis of Profitable Velocity: the rate at which sound engineering and geological decisions become authorized action and demonstrable commercial results. A specialist may have many transactions progressing across several clients. The system should advance routine authorized work and direct attention to the decisions or exceptions that need the specialist’s expertise. Increasing the volume of activity has value only where it contributes to profitable outcomes.

Those outcomes must inform subsequent decisions. Transaction design connects expenditure, capabilities and performance to the property economics reported for the Joint Operating Committee. 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 relevant specialists can then develop the changes necessary to return it to profitable production. Transaction design provides the means to organize, authorize, execute and evaluate that work.

The Petroleum Lease, Resource and Financial Marketplace Modules will apply this common discipline to their distinct subjects of exchange. Property interests, equipment, professional services and financing arrangements each require their own terms, evidence and completion conditions. Pangea provides continuity of interaction, while the responsible modules retain their specialized functions. A single Synallagi can connect contributions from several domains without obscuring their separate obligations.

Our user community must develop and validate the detailed designs that make these relationships operational. That work includes the definitions of services, accounting treatment, permitted conditional processing, authority, compensation, exceptions and recovery. Every design must be tested against the actual circumstances in which the participants work and improved through experience. The architecture establishes the direction; the knowledge of those who perform the work supplies its substance.

Designing Transactions makes the connection between knowledge and profitable action explicit. It gives accountants an active role in designing commercial processes, enables engineers and geologists to organize complete undertakings, and provides service providers with defined contributions and responsibilities. People, Ideas & Objects, our user community and their service-provider organizations are developing these capabilities around one purpose: Synallagi makes oil & gas profitable, everywhere and always.

Saturday, November 14, 2026

Pooling

Pooling establishes how Synallagi assembles the earth science & engineering capabilities required by each Joint Operating Committee. Participating producers contribute specialized people, knowledge, skills and experience, supplemented by capabilities acquired through the marketplace. The Joint Operating Committee directs their application to the property. This brings the relevant expertise to the point where operational decisions are made, responsibility is assigned and financial results are measured.

People, Ideas & Objects combines automation, specialization and the division of labor with Synallagi’s other Organizational Constructs to support a culture of preservation, performance and profitability. Pooling applies these principles to the development and deployment of producers’ earth science & engineering capabilities. It enables each producer to build a distinct competitive advantage while giving each Joint Operating Committee access to a broader range of expertise than any participating producer could reasonably maintain on its own.

The economic difficulty begins with the expectation that an individual producer must possess the full range of capabilities required to operate every property in its portfolio. As scientific understanding advances and technical disciplines become more specialized, maintaining that breadth becomes increasingly demanding. Different reservoirs, development stages and operating conditions require different combinations of knowledge, skills and experience. Retirements and the time required to develop professional competence add to the challenge. Expanding headcount alone cannot resolve the underlying problem of how those capabilities are organized and used. People, Ideas & Objects anticipates these challenges could ultimately jeopardize a producer’s capacity to sustain profitable operations.

Maintaining comprehensive internal capabilities also creates a utilization problem. A producer may retain a specialist for work that arises intermittently, while another property requires that expertise immediately. Across independently organized firms, idle capacity and unmet demand can coexist. The organizational boundary prevents available knowledge from reaching the activity where it could create the greatest value. Earth science & engineering professionals face artificial constraints on their ability to offer specialized technical skills throughout the broader commercial marketplace.

Within Synallagi’s organizational design, pooling replaces the operator designation as the basis for concentrating technical capabilities in a single producer. The Joint Operating Committee becomes the organization through which participating producers assemble, direct and account for the resources required by the property. Each producer develops the capabilities in which it can establish an advanced and distinctive competitive advantage and makes those capabilities available for authorized deployment. Operating responsibilities are assigned explicitly to the people and Joint Operating Committees undertaking the work.

For example, one producer may contribute specialized reservoir knowledge, another completion expertise and a third production optimization capabilities. Service providers supply additional technical and administrative services. The Joint Operating Committee combines these contributions according to the property’s requirements, with defined responsibilities, schedules and commercial terms. Its available capabilities therefore extend across its participating producers and the marketplace.

This arrangement allows specialization to deepen without requiring every producer to duplicate every advance. Producers concentrate investment on the knowledge, methods and experience that distinguish their businesses. Work that can be performed more effectively by specialized service providers moves into the marketplace, where those providers can develop their own capabilities and serve multiple customers. The division of labor extends throughout the organization of the work, allowing each participant to contribute where it can create the most value.

The Research & Capabilities and Knowledge & Learning modules support this development and deployment of expertise. They connect the capabilities a producer is building with the knowledge required to apply them and the opportunities available through its Joint Operating Committees. Through the Joint Operating Committee–Capabilities Deployment sub-module and the marketplace, requirements can be matched with qualified resources. Availability, scope, performance expectations and compensation become matters that can be identified and coordinated explicitly.

The sharing of non-rival costs provides a complementary economic foundation. Professor Paul Romer’s work distinguishes knowledge that can be used repeatedly from the scarce human effort required to develop and apply it. A documented method can inform work on several properties without being consumed by its first application. An engineer’s time, however, remains limited and must be scheduled and paid for. Pooling combines better utilization of specialized people with wider authorized use of the knowledge they develop. Romer, “Human Capital and Knowledge.”

Synallagi applies this distinction by providing the means to recover the costs of developing valuable knowledge across the activities that benefit from it. Producers retain incentives to invest in research, learning and innovation because the deployment of their capabilities has a commercial basis. Intellectual Property, confidentiality and authorized access are established through the terms of participation and supported by the Security & Access Control module. A Joint Operating Committee receives the information and capabilities required for its work within those defined rights.

Pooling also requires operational discipline. Industrial Command & Control establishes the chain of command for the temporary organization assembled by the Joint Operating Committee. Individuals may remain employed by different producers or service providers while working under the authority assigned to their roles in that operation. Decisions, instructions and responsibilities must be clear to everyone involved. The Joint Operating Committee must be able to determine who is accountable for an activity, what authority that person holds and how performance will be assessed.

Job Orders and Work Orders connect authorized activities with the people, time and resources assigned to them. Epistemes support the knowledge dimension of capabilities deployment, while Work Orders retain their role in assigning time and resources. Together, these mechanisms connect technical requirements, operational execution and the financial record. The contribution of a participating producer becomes identifiable work undertaken for a defined purpose.

The Partnership Accounting module captures the associated time, direct expenses and other authorized charges against the appropriate joint accounts. Costs are attributable to the activities and properties that incurred them, with a clear basis for allocation among the working interest owners. This gives the Joint Operating Committee visibility into the resources consumed and gives the contributing producer a means to recover the cost of supplying them. The resulting financial information supports the evaluation of both the work performed and the property’s profitability.

Deployment therefore establishes a second revenue stream for the producer, alongside the revenues earned from its petroleum production. This revenue stream is designed, at a minimum, to offset the full cost of building and maintaining its earth science & engineering capabilities. Commercial terms must support that objective while preserving accountability for the work and charges accepted by each Joint Operating Committee. The economic value comes from better technical outcomes, higher utilization and reduced duplication; the transactions provide the means to compensate those supplying the capabilities.

The producer consequently has two related means of realizing value from its scientific and engineering investments. It can improve the performance of its land & asset base through profitable reserve expansion, improved production deliverability and cost reductions. It can also earn revenue by deploying its specialized capabilities to the Joint Operating Committees in which it participates. Both reinforce the incentive to develop expertise that produces measurable commercial results. Production increases and technical achievements must contribute to profitability.

Making this arrangement work requires an Enterprise Resource Planning system that supports the organization being proposed. Capability identification, access rights, operational authority, scheduling, commitments, cost capture and settlement must operate together. A decision to deploy a specialist must carry through to the person’s assignment, access to the necessary information, execution of the work and recognition of the resulting charges. Synallagi provides the common software framework through which these relationships can be administered across organizational boundaries.

People, Ideas & Objects draws on Professor Anthony Giddens’ structuration theory and Professor Wanda Orlikowski’s work on technology and organizations. This research examines how people shape technology and how its use influences organizational practices and structures. Our application of that research is that the software supporting producers must be able to accommodate changes in how work is organized, authority is exercised and knowledge is deployed. Those changes must be reflected in the systems through which the industry conducts its business. Orlikowski, “The Duality of Technology.” Orlikowski and Robey, “Information Technology and the Structuring of Organizations.”

People, Ideas & Objects, our user community and their service providers will therefore maintain a permanent software development capability. As science, technology, commercial requirements and operating practices advance, Synallagi and our user communities service provider organizations must advance with them. Pooling gives North American oil & gas producers an organizational means to deepen their competitive advantages, bring those capabilities into productive use and recover the costs of sustaining them. Its continued development must remain directed toward the most profitable means of oil & gas operations.

Monday, November 09, 2026

Pangea, Part VI

7. Physical Evidence, Financing and Settlement

T-15 — Preserve the evidence chain

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.

T-16 — Verify external financial undertakings and outcomes

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.

8. Accounting, Allocation and Period Integrity

T-17 — Request and reconcile authoritative accounting

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.

T-17a — Automate accruals within one continuing voucher

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.

9. Security, Trust and Operations

T-18 — Enforce the selected context throughout

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.

T-18a — Coordinate two screens and a portfolio of transactions

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.

T-19 — Make operation and responsibility observable

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.

10. Development Sequence and Review Gates

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.

Required acceptance scenarios

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.

11. Decisions for Our User Community

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.



Source and Decision Register

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

S01

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.

S02

Marketplace Interface — Preamble, 26 October 2026. Accepted discussion foundation for the virtual commercial environment and substantial purchases.

S03

Designing Transactions, People, Ideas & Objects wiki. Establishes Accounting Voucher’s Transaction Design Interface and reusable transaction design.

S04

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.

S05

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.