Joint Operating Committee - Capability Deployment, Part I

 We resume the handoff of Synallagi further development to our user community with a detailed review of the Business Operations Management module. We have organized its functionality into three sub-modules: Planning, Marketplace, and Joint Operating Committee - Capability Deployment. Business Operations Management supervises and coordinates the activity across these environments, providing engineers and geologists with the commercial workspace through which they will manage the properties entrusted to them.

Understanding this module begins with understanding Synallagi approach to industry organization. We place the Joint Operating Committee at the centre of that organization, aligning producer compliance and governance with the industry’s legal, financial, operational, decision-making, communication, cultural, strategic, and innovation framework. This alignment provides the context for everything that follows.

Within Synallagi, the Joint Operating Committee becomes the primary focus of property management and commercial performance. The producer firm takes a supporting organizational position alongside the marketplace, while retaining its own responsibilities and obligations. This shifts attention toward the property, its economics, and the capabilities required to make it successful.

For engineers and geologists, the implications are substantial. Business Operations Management will provide their primary commercial workspace within Synallagi, bringing together the information, capabilities, and authorized actions they need to make decisions and evaluate results. It coordinates their work through the responsible Synallagi components, connecting technical judgment with commercial consequences.

Their opportunities need no longer be confined to one employer’s properties or the assignments available within a single firm. Through participating Joint Operating Committees, producer firms, and the marketplace, engineers and geologists will be able to apply their specialized capabilities wherever those capabilities are needed. A geologist with detailed knowledge of a particular formation or region, or an engineer with expertise in cost-effective fracturing techniques, could serve demand across the industry.

That broader opportunity carries greater accountability. Through our Targeting Framework, participants’ contributions will be evaluated against measurable outcomes, with financial rewards tied to the value they create. The framework addresses how an organizational structure becomes productive when:

• decision-makers share economically in the value they create;
• performance is measured against observable outcomes;
• authority is distributed locally;
• participants compete within common market rules; and
• successful practices spread without requiring one central planner to select every winner.

Today, we begin publishing the Joint Operating Committee - Capability Deployment sub-module. This is the environment through which engineers and geologists will bring together the capabilities, resources, and authorized work needed to achieve their objectives. It connects the opportunity to act with responsibility for the result.

We also foresee an industry in which digital assets play a growing role in ownership, financing, and settlement. In that future, tokenized securities could represent defined ownership interests in oil & gas assets and trade on regulated markets, much as shares do today. Stablecoins could provide a means of payment and settlement. These are distinct functions: one concerns the rights an investor owns; the other concerns how money moves.

The legislative timetable remains uncertain. On September 15, 2026, the U.S. Senate failed to advance the CLARITY Act in a procedural vote. Further consideration after the November election remains possible, but passage before January 2027 cannot be assumed. Senate Banking Committee statement; Reuters reporting.

In the model we envisage, tokenized ownership interests would connect investors to assets managed through Joint Operating Committee arrangements. The rights attached to those interests, including participation and representation, would be established through the underlying legal agreements. Engineers and geologists drawn from the oil & gas marketplace would provide the professional capabilities required to manage those assets under defined authority.

Their role would therefore expand. They would assume greater responsibility for the administration, management, and financial performance of the properties entrusted to them. Synallagi Business Operations Management module is designed to support that responsibility by connecting decisions, execution, and measurable commercial outcomes.

Tokenization also has significant implications for financial reporting. Recording a security on a blockchain does not remove its underlying securities-law obligations. The SEC has expressly stated that the format in which a security is issued does not change the application of federal securities laws. SEC statement on tokenized securities.

The specific reporting obligations will depend on the issuer, offering structure, jurisdiction, and applicable regulatory requirements. Quarterly reporting should therefore not be presented as an automatic requirement for every tokenized asset: existing U.S. reporting regimes already differ, including annual and quarterly reporting under the Exchange Act and annual and semiannual reporting under Regulation A Tier 2. SEC reporting guidance; Regulation A guidance.

Our commercial requirement is clear nonetheless. Investors need reliable financial information about the assets in which they participate. Synallagi is designed to support that requirement through financial statements and underlying records attributable to the relevant Joint Operating Committees and properties. Ownership, revenue, operating costs, overhead, capital commitments, and financial performance must be understandable and traceable.

This strengthens our case for Synallagi as a standard ERP system across the oil & gas industry. A marketplace for tokenized interests needs a dependable operating and financial foundation beneath it. Fragmented records, inconsistent reporting, and opaque property economics increase the difficulty and cost of participation. We intend Synallagi to provide the common foundation that connects ownership with accountable management and verifiable financial performance.

Joint Operating Committee - Capability Deployment

Business and Technical Specification — Release 1

Business Operations Management · Release 1 · October 15, 2026

This release establishes the reviewed business, conceptual and technical specification for Joint Operating Committee Capability Deployment. It provides the current basis for the wiki and user-community handoff. Detailed calculations, record relationships, contribution contingencies and implementation decisions identified in the specification remain for development. This is a specification baseline, not a claim of completed software.

Part I — Business Specification

Note to Our User Community

The Joint Operating Committee needs the capabilities required to operate its properties profitably, preserve its reserves and pursue worthwhile opportunities. Those capabilities may reside with its participating producers, an individual specialist, a service provider or a research collaboration. Their usefulness depends on being available when required and supported by clear authority, agreed compensation and reliable accounting.

Synallagi proposes to remove designated operatorship and organize the required capabilities through Pooling. Each producer develops its particular strengths and contributes them to the Joint Operating Committees in which it participates. Additional capabilities are obtained from the market. This allows specialization and the division of labor in the sciences of geology and engineering to extend across organizations, while each engagement retains its own purpose, participants, commitments and accountability.

Capability Deployment brings these arrangements together within Business Operations Management, presented through the Engineers and Geologists interface. It connects a requirement with suitable capabilities, the authority to engage them, the work performed, its accounting consequences and the evaluation of results. These activities contribute to the developing Synallagi transaction. Accounting, participant allocation, security and operational direction continue through their responsible Synallagi components.

Synallagi is organized around the Joint Operating Committee and its requirements. Its intended use extends across producer sizes, from start-ups to firms the size of Exxon. A producer's size does not change the need to identify the applicable property, agreement, authority, contribution and accounting treatment.

Our user community includes engineers, geologists, accountants, administrators and the people who provide services to the industry. Their combined knowledge is necessary to describe both the technical work and the business arrangements that make it possible. Capturing those arrangements while people agree to them gives subsequent processing a reliable basis and reduces the need to reconstruct their intentions after costs have been incurred.

Specialists and their clients

Engineers and geologists are the primary users of Business Operations Management. Its interface begins with the individual, the selected Joint Operating Committee and the producers represented in the engagement. A specialist may work as an employee within assigned JOCs or as an independent professional serving several producers and JOCs. Capability Deployment organizes these client engagements and their approved capabilities, contributions, work and accounting consequences.

One persistent Synallagi identity can carry several separately approved assignments. The selected context determines the party represented, the information available and the authority to act. Security & Access Control prevents information or authority from one client assignment carrying into another. The engagement must provide the producer-private information required for the approved work. The specialist's authority to represent a participant or approve a transaction remains separately established.

Capability Deployment contributes to a New Discipline connecting scientific judgment, transaction design, actual economics and accountable results. Reducing Organizational Latency means shortening the time between recognizing an opportunity or deficiency and implementing the authorized response. Planning, Marketplace Interface and Capability Deployment support that work through their respective responsibilities.

Engineers and geologists must work with the user community to define and validate the tools needed for science and innovation, both initially and throughout Synallagi life. Artificial Intelligence is a proposed contributor to that productivity within the established information, authority and accountability boundaries.

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

Commercial purpose

The objective is reserves preservation, performance and profitability. Engineers and geologists need to see how their technical decisions affect actual costs, production, recoverable reserves and the recovery of invested capital. Accountants need the technical and contractual context that explains those results. Capability Deployment connects that information to people who can act on it.

A requirement may arise from new development, maintenance, research, an obligation or a financial deficiency. A well's disappointing financial result can prompt a technical investigation, just as a technical observation can prompt a commercial review. The purpose is to identify the appropriate response and make its effects visible. Greater production alone does not establish that the work improved the property's economics.

The price maker strategy supplies the commercial discipline: each producer uses market price and the detailed economics of its interests to make independent business decisions. Breakeven calculations make the relevant cost and recovery requirements visible and help identify deficiencies requiring action. Where property action requires Joint Operating Committee approval, those decisions are exercised through the applicable governing arrangements. Capability Deployment provides the means to obtain expertise and carry out authorized responses.

Marketplace Interface

The Marketplace Interface enables engineers and geologists to find and engage vendors, suppliers, service providers and specialized capabilities through Synallagi integrated business functions. This Business Operations Management sub-module connects with the Petroleum Lease, Resource and Financial Marketplace modules. For its detailed function and capability, see Business Operations Management — Marketplace Interface.

Planning and shared capabilities

Business Operations Management — Planning is the principal setting for Research & Capabilities. Capability Deployment draws on plans and identified requirements through the Knowledge & Learning module to organize approved work. The results of that work can inform subsequent planning, subject to the information's permitted use.

Planning and Capability Deployment share the use of Pooling, Industrial Command & Control, Episteme and other relevant capabilities. Planning may examine the expertise and resources needed for proposed work; deployment establishes and carries out the approved engagement. A planning requirement does not itself commit resources or authorize an operation. Shared capabilities retain their meaning and authority across the sub-modules, and their detailed exchanges remain to be specified.

Supervision, service providers and process coordination

Business Operations Management provides the supervisory and coordination role across its sub-modules for the selected Joint Operating Committee. The sub-modules define particular capabilities; the overall module connects their use into coherent operating processes. It follows what initiates work, the information required, applicable approvals and dependencies, progress, results and exceptions requiring attention.

Responsibility is distributed across three levels. Each sub-module or responsible Synallagi component defines its business function, calculations, records, rules and results. Business Operations Management coordinates when and how those functions are used together. The Conceptual Model and technical companions specify the relationships, exchanges, transaction states and implementation required to support that coordination.

A detailed formula remains with the capability responsible for its calculation. Business Operations Management coordinates when the calculation is needed, which authorized inputs and applicable version are used, and how the result affects commitments, expenditure or subsequent decisions. The same principle applies to record relationships: the responsible components maintain their authoritative records, while module-level coordination defines the business connections between them.

One possible process path begins when Planning identifies a requirement. Knowledge & Learning supplies the relevant capability information; Capability Deployment organizes the engagement; Work Orders deploy its financial resources; Industrial Command & Control and Job Orders direct field execution; accounting records the consequences; and results inform subsequent planning and performance evaluation. This is an illustrative path. Other work may begin at a different point, branch, return for further investigation or proceed concurrently where its dependencies and authority permit.

These processes are broken down into individual elements performed by specialized service providers. Each provider handles its defined element of the coordinated process, with an identifiable input, required work, result and responsibility. A sub-module may therefore involve several providers, and a provider's defined service may support more than one process. This division of work makes specialization operational while preserving accountability for each contribution.

Autonomous Asynchronous Transaction Orchestration coordinates execution and communication between those elements. It conveys the relevant information, requests, completion evidence and exceptions so that the next eligible activity can proceed under its defined conditions. Asynchronous operation allows elements to progress when their inputs and approvals are available, without requiring every participant to act at the same time. Dependencies and authorization requirements continue to govern the work.

Business Operations Management provides the supervisory view of the overall process and the decisions or exceptions requiring attention. Autonomous Asynchronous Transaction Orchestration carries the defined work and communications across the participating services and responsible components. Each service provider remains accountable for its element; orchestration supplies no authority beyond the governing arrangements.

As the process advances, the Synallagi transaction carries or references the relevant authority, commitments, assignments, service results and accounting consequences. Its connected business context develops through these contributions, while the source records remain with their responsible components. Capability Deployment specifies what it contributes, requires and returns; coordination across the sub-modules is developed at the Business Operations Management level.

The developing Synallagi transaction

A Synallagi is the transaction whose relevant elements and attributes are progressively defined by the modules. Security & Access Control establishes its identity, representation, role, authority and access context. Business Operations Management adds the more detailed and changing business context needed to act: authorized AFE spending, authorized Lease spending, Work Order authority, operational instructions, commitments and the other applicable elements of the engagement.

Security provides the comparatively stable foundation; Business Operations Management develops the more variable business context. The foundation continues to evaluate authority and access as relationships, assignments and transaction conditions change. Passing an access check therefore enables the relevant work in context; it does not grant permanent authority regardless of subsequent changes.

The business elements form part of the Synallagi transaction itself. They connect the parties and their authority with the resources deployed, work performed, accounting consequences and outcomes. As further modules are developed, they’ll contribute additional elements, attributes and relationships. The responsible components continue to maintain their authoritative records.

The conceptual model will define how the transaction carries or references these elements and their history. The business requirement does not prescribe one physical record containing everything, or require every transaction to contain every element. It requires the relevant context to remain connected and attributable as work progresses.

Continuing development

Business Operations Management will continue to develop with its sub-modules and the wider Synallagi specification. Changes must identify the affected business requirements, responsible components and companion layers, preserve the basis of earlier authorized work, and be reconciled through the user community. Operational and accounting amendments retain their own authorities.

Security & Access Control - Target Architecture Brief

Target Architecture Brief

Date: 2026-08-12

The original Security and Access Control specification describes the business objective and vision for the module. The following companion architecture expands that vision into the trust, authority, accountability, cybersecurity, market, artificial intelligence, blockchain, stablecoin, wallet, and implementation concepts required to support Synallagi.

Introduction

Synallagi coordinates the activities of producer firms, Joint Operating Committees, service providers, suppliers, specialists, marketplaces, financial participants, technology providers, and other secondary tertiary industry participants in the North American oil & gas industry. These participants remain members of independently governed organizations while collaborating through common information, processes, transactions, markets, infrastructure, and operating objectives.

The specification is ecosystem-informed, user community-led, service provider-enabled, and technologically supported. Producers are participants but are not the exclusive or dominant source of operating knowledge. Engineers, geologists, accountants, administrators, contractors, service-industry firms, financial participants, technology providers, artificial intelligence specialists, cybersecurity specialists, and other disciplines contribute to the institutional and technical design.

Security and Access Control provides the trust, authority, cybersecurity, and accountability framework for that collaboration. Its purpose is to ensure that the right person or authorized system can perform the right action, on the right information or process, for the right organization, Joint Operating Committee, market, asset, transaction, or wallet context, within the right authority, at the right time, under acceptable conditions, with complete evidence.

This module is not limited to protecting screens or information. Within Synallagi, access is connected to the authority to act, responsibility to perform, and accountability for outcomes. The module implements the security aspects of Industrial Command and Control while preserving the legal, commercial, operational, market, cybersecurity, and information boundaries of every participating organization.

Security objectives

Synallagi shall:

• establish reliable identities for people, organizations, services, integrations, devices, wallets, and automated agents;
• distinguish authentication from Joint Operating Committee membership, organizational representation, system access, business authority, market authority, and wallet authority;
• enforce least privilege across functions, information, transactions, authority, markets, wallets, and time;
• support secure collaboration among independently administered organizations;
• protect producer-private, partnership, Joint Operating Committee, marketplace, regulated, personal, intellectual property, cybersecurity-sensitive, and public information according to ownership and classification;
• prevent or detect incompatible access and actions;
• provide timely provisioning, change, review, suspension, and revocation of access;
• preserve evidence sufficient to reconstruct consequential security and business decisions;
• maintain human accountability when automation or artificial intelligence is used;
• support blockchain, stablecoin, and crypto-based asset participation only under explicit policy and evidence; and
• fail safely when identity, policy, representation, information scope, cybersecurity condition, or authority cannot be established.

Synallagi operating model

Industrial Command and Control defines how authority, responsibility, coordination, and accountability are organized within producer firms, Joint Operating Committees, working groups, service relationships, markets, and other Synallagi constructs. It enables dispersed specialists to contribute under an explicit operating structure without requiring every producer to duplicate the same capabilities internally.

Hyper-specialization may produce roles narrower than today's generic engineering, geological, accounting, or administrative positions. A specialist may serve many producers and Joint Operating Committees because no single organization generates sufficient demand for that capability. Security policy shall permit this cross-industry work while restricting every specialist to the current assignment, process, information, authority, and evidence requirements.

Security and Access Control enforces that structure but does not define command solely through technical roles. A person may be responsible for work without holding approval authority. A person may have authority to approve a decision without receiving unrestricted access to all related information. A person may be able to operate an application function without possessing the commercial authority to bind a producer, Joint Operating Committee, market participant, or asset holder.

Synallagi shall therefore represent business role, duty, system privilege, information entitlement, authority, responsibility, and accountability as related but distinct concepts.

Organizational constructs

Synallagi Organizational Constructs define, support, and constrain the relationships and actions recognized by the application.

The nine organizational constructs currently identified are:

1. Joint Operating Committee.

2. Endogenous Technical Change and sharing of infrastructure.

3. Hyper-specialization and division of labor.

4. Markets.

5. Innovation.

6. Intellectual Property.

7. Information Technology.

8. Trust. (Draft as of August 2026)

9. Transactions. (Draft as of August 2026)

The Joint Operating Committee is the primary Organizational Construct and the governed context in which working-interest participants coordinate property operations. Pooling, specialization, and the division of labor replace the traditional operator and non-operator allocation as Synallagi's organizing model. Traditional operator terminology may still be received from agreements, regulations, historical records, and external systems, but it does not determine how Synallagi assigns work.

Identities and represented parties

Every human and non-human actor shall have a unique identity. The identity is the persistent subject to which authentication, organizational relationships, assignments, actions, and accountability are attached. It remains stable while employment, representation, Joint Operating Committee membership, market participation, duties, wallet authority, and business authority change.

An identity may be associated with one or more organizations through employment, directorship, contract, professional engagement, partnership representation, regulatory appointment, audit engagement, market participation, or another governed relationship. The existence of an identity or organizational relationship does not automatically grant access to a Joint Operating Committee, market, wallet, or Synallagi resource.

For every consequential action, Synallagi shall identify:

• the acting identity;
• whether the actor is human or automated;
• the organization represented by the actor;
• the applicable Joint Operating Committee, property, agreement, marketplace, wallet, transaction, or other operating context;
• the duty and authority under which the action is performed; and
• the policy decision that permitted or denied the action.

Where a person is entitled to represent more than one organization, Synallagi shall require an explicit representation context. A person shall not silently change represented parties within a transaction. Conflicting representation shall be prohibited or governed through an approved exception and mitigating control.

Identity proofing and authentication

The strength of identity proofing and authentication shall correspond to the risk of the available actions and information. Synallagi shall define assurance requirements for employees, partner representatives, contractors, service-provider personnel, auditors, administrators, marketplace participants, services, integrations, wallets, and automated agents.

Strong authentication shall be required for privileged administration, wallet-related actions, marketplace commitments, and material business actions. Synallagi shall support step-up authentication where transaction value, information sensitivity, changed circumstances, session risk, cybersecurity risk, or authority level requires greater assurance.

Authentication establishes control of an identity credential. It does not establish organizational representation, Joint Operating Committee membership, access to information, authority to commit a party, or authority over a wallet.

Federated identity

Synallagi shall support identity federation so participating organizations can authenticate their personnel through approved identity providers. Each federation relationship shall define the trusted organization, accepted technical method, required identity assertions, minimum assurance, attribute ownership, provisioning signals, incident notification, review, suspension, termination, and fallback procedures.

Federation establishes controlled trust in authentication assertions. Synallagi retains authority over Joint Operating Committee admission, representation, role, information scope, duties, market participation, wallet authority, and business authority.

Joint Operating Committee membership

Joint Operating Committee membership shall be a governed relationship among an identity, a represented organization, and a Joint Operating Committee. It shall identify the sponsor, basis of membership, effective dates, status, approved roles, duties, information scope, authority, and applicable agreements.

Membership shall be reviewed or revoked when relevant circumstances change, including termination or suspension of the person's organizational relationship, expiry or termination of a contract, change in pooling assignment, acquisition or disposition of a working interest, withdrawal or suspension of a partner, change in agreement or decision rules, change in assigned duties or professional qualifications, or a security incident affecting the person or represented organization.

Removing one Joint Operating Committee assignment shall not unnecessarily remove unrelated assignments held by the same identity. Conversely, continued employment shall not preserve access derived from an expired Joint Operating Committee assignment.

Roles, duties, privileges, and information entitlements

A business role identifies a recognized position such as working-interest representative, production engineer, controller, auditor, formation specialist, transaction designer, wallet administrator, marketplace participant, or Material Balance Report reconciliation specialist.

A duty identifies a coherent responsibility such as preparing an Authorization for Expenditure, reviewing a voucher, approving a work order, reconciling production, administering security, certifying access, qualifying a market participant, or reviewing settlement evidence.

A privilege permits a defined application or application programming interface action. An information entitlement limits that privilege to specific records and resources. Synallagi application programming interfaces are private and directly available only to licensed developers, approved user-community participants, service providers, and authenticated runtime integrations. Public users receive only the compiled or runtime application functions intentionally exposed to them.

Synallagi shall grant access through governed assignments rather than direct, undocumented grants to individuals. Stable duties should be reusable across organizations and Joint Operating Committees. Dynamic context such as Joint Operating Committee, property, well, agreement, working interest, market, wallet, authority amount, and assignment period shall not be hidden inside an uncontrolled proliferation of static role names.

Data classification and information boundaries

The existing distinction between producer information and partnership information remains important but is not sufficient for the full Synallagi environment. Information shall be classified according to ownership, contractual rights, sensitivity, regulatory obligations, operational impact, cybersecurity risk, market impact, intellectual property status, and permitted disclosure.

The classification model shall address at least:

• producer-private information;
• Joint Operating Committee and partnership information;
• pooled Joint Operating Committee and externally administered information;
• property, well, production, and technical information;
• agreements and working-interest information;
• accounting, voucher, Authorization for Expenditure, order, payment, revenue, and settlement information;
• service-provider and supplier information;
• research, knowledge, and intellectual property;
• marketplace-confidential information;
• wallet, blockchain, stablecoin, and crypto-asset participation information;
• personal information;
• regulated or legally restricted information;
• cybersecurity-sensitive information; and
• information approved for public release.

Access to one classification shall not imply access to another. Participation in a Joint Operating Committee shall not provide access to a producer's unrelated properties, strategy, private analysis, correspondence, or other confidential information. Similarly, information available within a Joint Operating Committee shall not be published or used in a marketplace without separate disclosure authority.

Business authority

The technical ability to operate a function shall not be treated as authority to make a business commitment. Synallagi shall represent authority independently and may constrain it by represented organization, Joint Operating Committee, agreement, transaction type, property, well, project, market, wallet, settlement instrument, monetary amount, working-interest threshold, voting requirement, professional discipline, transaction stage, effective period, and normal or emergency conditions.

Material actions shall be denied when authority is absent, expired, insufficient, ambiguous, inconsistent with the represented party, or inconsistent with the required accountability.

Delegation

Delegation enables continuity during absences, workload changes, emergencies, and temporary assignments. Every delegation shall identify the delegator, delegate, represented organization, operating context, delegated duties, delegated authority, excluded duties, limits, reason, start and end time, approving authority, conflict assessment, notification recipients, and revocation status.

A delegation shall not exceed the delegator's authority, bypass an applicable conflict rule, transfer unrelated privileges, or conceal accountability. Delegated access shall expire automatically and remain fully auditable.

Segregation of duties and conflicts

Synallagi shall prevent, detect, and manage assignment conflicts, transaction conflicts, and representation conflicts.

Examples include preparing and finally approving the same material transaction; requesting and provisioning one's own access; administering security and independently certifying the resulting access; acting for multiple parties in the same negotiation without an approved arrangement; controlling a wallet and approving a related settlement without independent review; or designing a market transaction and independently certifying its disclosure.

Where a conflict may be accepted, the exception shall identify its owner, rationale, duration, affected duties, risk, compensating control, reviewer, and expiry.

Access request and provisioning

An access request shall state the business purpose, requested role or duty, represented organization, Joint Operating Committee, information scope, authority, duration, sponsor, and required approvers. Synallagi shall evaluate the request against existing access, conflicts, sensitive privileges, qualifications, contracts, cybersecurity conditions, and policy.

Approved access shall be provisioned through controlled integration with Oracle and other required services. Synallagi shall reconcile approved access against actual access and investigate discrepancies.

Access lifecycle and revocation

Access shall remain valid only while all of its supporting relationships remain valid. Synallagi shall process joiner, mover, and leaver events and domain events such as assignment, novation, farmout, farmin, subsequent joint venture, Joint Operating Committee restructuring, pooling change, working-interest transfer, contract expiry, loss of qualification, market removal, wallet compromise, and security incident.

Revocation shall address roles, information grants, authority, delegations, sessions, credentials, pending approvals, owned work items, integration access, emergency assignments, wallet authority, and automated-agent access.

Access review and certification

Access shall be reviewed periodically and after material events. Reviews shall include identity and organizational relationship, Joint Operating Committee membership and representation, roles, duties, privileges, information entitlements, monetary and other authority, delegations, privileged access, emergency access, market access, wallet authority, service access, integration access, automated-agent access, conflicts, inactive access, unused access, and orphaned access.

Reviewers shall be sufficiently independent and knowledgeable to judge the access. Rejected access shall be removed within a defined period and verified.

Transaction and workflow controls

Authorization shall consider transaction state. Holding a duty does not permit an actor to perform an action at every stage of a process.

Recurring transaction designs shall be represented as governed templates. A template persists the generic roles, duties, workflow, information, controls, authority patterns, and audit evidence for a transaction type. Each use of the template supplies the participants, represented organizations, Joint Operating Committees, properties, values, dates, wallets, markets, and other context unique to that transaction.

For Authorizations for Expenditure, vouchers, Work Orders, purchase orders, job orders, production decisions, payments, marketplace transactions, stablecoin settlements, blockchain records, and other material processes, the specification shall define permitted initiators, required reviewers, authority thresholds, partner or voting requirements, incompatible actions, amendment rights, emergency procedures, required evidence, and final accountability.

Marketplace and external-party access

Each Synallagi marketplace shall define participant qualification, onboarding, disclosure rights, bidding or offering authority, conflict rules, commitment authority, signing, settlement, suspension, and removal.

Marketplace participation shall not provide implicit access to a participant's producer-private or Joint Operating Committee-confidential information. Information may cross from an operating context to a marketplace only under an explicit disclosure policy and attributable authority.

Service-provider and supplier access shall be bound to the employing organization, contract, Joint Operating Committee, work order, property, duty, qualification, and time period. Expiry of any required relationship shall trigger reevaluation or revocation.

Blockchain, stablecoins, wallets, and crypto-based asset participation

Synallagi may support blockchain records, stablecoin settlement, digital wallets, and crypto-based participation in oil & gas assets. These capabilities extend the Security and Access Control module because they affect identity, authority, ownership, financial reporting, settlement, disclosure, custody, and investor communication.

The system shall distinguish wallet control from beneficial ownership, market participation, voting rights, settlement authority, disclosure entitlement, and authority to receive Joint Operating Committee-level financial statements.

Where assets are securitized or represented through crypto-based instruments, Synallagi shall define:

• participant qualification;
• identity and wallet verification;
• beneficial ownership evidence;
• asset rights and restrictions;
• disclosure entitlements;

Joint Operating Committee-level reporting obligations;

• financial statement publication rules;
• settlement authority;
• stablecoin acceptance and reconciliation;
• custody and transfer restrictions;
• incident response for compromised wallets or keys;
• audit evidence; and
• regulatory or contractual constraints.

These capabilities should be developed in focused background pages before they are treated as final module requirements.

Privileged and emergency access

Security administration, role administration, policy administration, audit administration, wallet administration, market administration, and other privileged duties shall be separated from ordinary business activity and from independent review.

Emergency access shall be exceptional, strongly authenticated, narrowly scoped, time-limited, monitored, and reviewed promptly after use. Synallagi shall notify designated owners when emergency access is activated and shall retain the reason, actions, and resulting changes.

Services, integrations, and private application interfaces

Every service, integration, device, and automated process shall use a managed identity with a defined owner, purpose, privileges, information scope, credential lifecycle, and monitoring requirements. Credentials shall not be embedded in code or shared across unrelated integrations.

Application programming interface authorization shall enforce the same business and information policies as interactive use. An integration shall not acquire greater access merely because it operates outside the user interface.

Synallagi application programming interfaces are private. Direct access shall be limited to licensed developers, approved user-community participants, service providers, and authenticated runtime services. Compiled applications and user interfaces expose only the functions intentionally made available to their users.

Artificial Intelligence and automated agents

Artificial intelligence systems shall operate under identifiable workload identities and approved information scopes. Synallagi shall distinguish activity that is advisory, preparatory, submitted for approval, or autonomously executed.

An artificial intelligence system shall not infer organizational representation, commercial authority, wallet authority, market disclosure authority, or permission to disclose information. Material decisions and commitments shall remain subject to the same authority, conflict, authentication, and evidence requirements as human actions.

People, Ideas & Objects' intellectual property and Targeting Framework shall supply objectives and constraints for agentic activity. These guardrails must be translated into enforceable permissions, prohibited actions, escalation rules, monitored behaviour, and audit evidence. Prompt instructions alone are not sufficient control.

Cybersecurity, monitoring, and investigation

Synallagi shall treat cybersecurity as a core part of Security and Access Control. Monitoring shall detect suspicious authentication, anomalous access, excessive privilege, conflict violations, unexpected disclosure, compromised identities, privileged misuse, policy failures, unusual transaction activity, market manipulation signals, wallet compromise, integration abuse, and artificial intelligence misuse.

Synallagi shall record security and material business events sufficient to answer who or what acted, which organization is represented, in which Joint Operating Committee or operating context, what action is requested and performed, which resource and information were affected, which policy and authority applied, what changed, and how related events can be correlated.

Investigation access shall itself be controlled and audited.

Security incidents and recovery

Synallagi shall define procedures for compromised identities, unauthorized access, information disclosure, malicious or mistaken administrative changes, failed identity federation, unavailable authorization services, corrupted policy or audit information, compromised wallets, unauthorized market activity, artificial intelligence misuse, and integration abuse.

Response shall include containment, suspension or revocation, preservation of evidence, impact assessment, notification, recovery, restoration of trusted configuration, and post-incident improvement.

Privacy, retention, and information lifecycle

Personal and sensitive information shall be collected and used only for defined purposes and made available only to authorized parties. The specification shall identify ownership, stewardship, location or residency constraints, permitted disclosure, retention, legal hold, archival, and disposal requirements.

Security controls shall apply to exports, reports, analytics, attachments, integration copies, test environments, backups, artificial intelligence processing, blockchain records, marketplace records, and downstream systems.

Security administration and governance

Synallagi shall define accountable owners for identities, roles, duties, information, policies, Joint Operating Committees, authority templates, access certifications, conflicts, exceptions, audit, cybersecurity, markets, wallets, artificial intelligence guardrails, and security operations.

Changes to roles and policies shall be versioned and subject to impact analysis, conflict simulation, approval, testing, controlled deployment, reconciliation, and rollback. Delivered Oracle roles should be preserved where practical. Custom roles and policies shall follow governed naming, ownership, documentation, and review standards.

Oracle Cloud Enterprise Resource Planning

Oracle Cloud Enterprise Resource Planning provides standard capabilities for application privileges, job and duty roles, data roles and security contexts, security administration, access requests, access controls, access certification, and audit reporting. Synallagi shall use these capabilities where they accurately implement the required policy.

Synallagi may develop and deploy Java components within supported Oracle application-server environments where this forms part of the approved Synallagi architecture. Such components shall be maintained through controlled source, build, testing and deployment processes. Within the Security & Access Control module, extensions shall use or integrate with the authoritative Oracle and Synallagi identity, authorization, audit and security services. They shall not bypass those controls or depend upon undocumented Oracle product internals. Extensions to Oracle Fusion Cloud Applications shall use the extension and integration mechanisms supported for that service.

Synallagi-specific concepts including Joint Operating Committee membership, represented organization, pooling relationships, agreement scope, working interest, hyper-specialized duties, domain authority, delegation, marketplace participation, wallet authority, crypto-based asset rights, cybersecurity policy, and cross-organizational conflicts shall remain explicit domain concepts.

Standardized Security Components and Contextual User Assignments

Standardized and objective accounting information is fundamental to Synallagi. It allows each producer to trust that the potential unprofitability of its production is evaluated on the same basis as that of every other producer. The same principle shall apply to Security & Access Control.

Synallagi shall establish standardized security configuration components consisting of defined combinations of business roles, duties, privileges, data entitlements, authority limits and control requirements. Each component shall clearly identify the functions it permits, the information it exposes, the authority it conveys, the conflicts it creates, and its requirements for approval, delegation, certification and revocation. Producers and Joint Operating Committees may assign the appropriate combination of these components to an individual without independently redesigning that individual’s access. They will therefore understand the security, access-control and accountability consequences of every component assigned.

Synallagi shall not require a separate user identity for every producer, Joint Operating Committee, property, client or assignment in which an individual participates. Each person shall have one persistent Synallagi identity to which multiple, separately approved relationships and assignments may be attached. An engineer or geologist may therefore hold authorizations for several clients and Joint Operating Committees and may be authorized to initiate, review, recommend or approve specified classes of Authorizations for Expenditure within each assignment.

The standardized security component is reusable; the authority granted through it remains contextual. Qualification for a role, or assignment of that role in one organization, shall not automatically confer authority in another. Every authorization shall remain limited to the represented organization, Joint Operating Committee, property, agreement, transaction class, monetary threshold, effective period and other conditions under which it is granted. Synallagi shall evaluate the active context before permitting an action and shall prevent information or authority belonging to one assignment from carrying into another.

Measures and assurance

Security performance shall be measured. Measures should include time to provision and revoke access, expired access, orphaned access, excessive privilege, unused privilege, overdue certification decisions, unresolved conflicts, privileged access use, emergency access use, failed identity federation, anomalous access, denied access, audit coverage failures, wallet incidents, market access exceptions, artificial intelligence policy violations, and incident response time.

Requirements shall be verified through policy tests, role and information-access inspection, conflict simulation, lifecycle exercises, access-certification evidence, audit reconstruction, cybersecurity testing, failure testing, and periodic control assessment.

Open design decisions

The following topics should be developed through smaller background pages during subsequent detailed design and before the affected capabilities are approved for implementation:

• complete role and duty catalogue;
• market participation model;
• blockchain and stablecoin settlement model;
• wallet authority and beneficial ownership model;
• crypto-based asset securitization;
• Joint Operating Committee-level financial statement publication;
• cybersecurity incident taxonomy;
• artificial intelligence execution boundaries;
• Targeting Framework access rules;
• private application interface licensing controls;
• revocation timing by event type; and
• accounting firm participation in audit and assurance workflows.

Development Environment — Code Repository

Synallagi shall initially use Oracle Cloud Infrastructure DevOps Code Repositories as its canonical repository for approved specifications, scripts, source code and related development artifacts. Google Workspace shall remain the controlled collaborative environment. Approved supporting services may include Chrome Enterprise Premium, Gemini Enterprise and Google Voice, subject to applicable information-classification, access-control, licensing and security requirements. Working groups and confidential subject matter shall be separated according to information classification and authorized membership. Discussions and sensitive working material shall not automatically be committed to the code repository. A self-managed GitLab or another standards-based Git platform may be adopted later where documented requirements demonstrate that Oracle Cloud Infrastructure DevOps is insufficient.

Recommended information structure

• Information class
• Primary location
• Access model
• Published specification
• Google Sites and OCI repository
• Public or broadly readable
• General user-community work
• Dedicated Google Shared Drive
• Entire approved community
• Restricted working-group material
• Separate Shared Drive for each group
• Named group members only
• Approved technical specifications and code
• OCI DevOps repository
• Repository-specific OCI IAM groups
• Highly confidential strategy
• Separately administered encrypted workspace
• Minimum named individuals only
• Informal discussions and meeting records
• Appropriate Google Workspace location
• Retained only where necessary

Technical Specification Conclusion

Synallagi organizational model depends on collaboration without surrendering the independence, information rights, authority limits, cybersecurity requirements, or accountability of participating organizations. Security and Access Control enables that model by connecting trustworthy identities to explicit representation, hyper-specialized duties, information, authority, markets, wallets, transactions, evidence, and accountability.

Industrial Command and Control supplies the business structure. Oracle Cloud Enterprise Resource Planning supplies important standard security capabilities. Synallagi supplies the Joint Operating Committee-aware, market-aware, transaction-aware, and asset-aware policy model that joins them.

Closing Section - Security and Access Control Target Architecture Brief

Implementation note for potential users

The complexity described in this module is not accidental. It reflects the level of control required for Synallagi to support Joint Operating Committees, working-interest participants, markets, service providers, cybersecurity, artificial intelligence, blockchain-supported transactions, stablecoin settlement, wallets, and crypto-based participation in oil & gas assets.

For potential users, the first response to this complexity should not be discouragement. The first response should be recognition that this is the nature of the problem being solved. Synallagi is not attempting to add an access-control layer to a conventional enterprise system. It is defining the trust, authority, accountability, and evidence model required for a new form of oil & gas administration.

Several factors make this practical.

Oracle Database and Oracle Cloud Enterprise Resource Planning are designed to manage large-scale, highly controlled, security-sensitive enterprise conditions. Synallagi expects to rely on Oracle technologies where they are the appropriate foundation for identity, data security, role administration, access certification, audit, transaction processing, and integration.

Oracle Services may be engaged to confirm product fit, subscription requirements, supported integration patterns, security responsibilities and implementation design. Their involvement should reduce the burden on our user community to translate every requirement into technical implementation detail.

Artificial intelligence will be relied upon heavily in the analysis, development, testing, verification, and implementation of these requirements. This changes the nature of our user community's work. Users and service providers no longer need to carry the full burden of technical decomposition in the way they might have had to do in prior generations of software development.

Their work remains essential, but it changes shape. Our user community and service providers must ensure that the user's interfaces are usable, that complex requirements can be presented and processed in understandable ways, and that the systems and procedures exist to verify that specified requirements have been completed as required.

Much of this work is not yet fully written or defined. Synallagi will create new positions, new service opportunities, and new combinations of human and artificial intelligence activity. The most effective division of labor among users, service providers, artificial intelligence systems, Oracle Services, and People, Ideas & Objects will have to be discovered, tested, refined, and governed over time. This work should begin now in the minds of our user community and service-provider community.

The complexity of the Synallagi specification establishes an important boundary. Agentic Artificial Intelligence tools, used casually by individual producer firms to automate selected organizational actions, cannot responsibly substitute for the architecture described in this module. Security and Access Control cannot be reduced to scattered Artificial Intelligence agents performing "some" actions inside an organization without the required identity, representation, authority, accountability, cybersecurity, audit, revocation, and governance structures.

Any producer proposing to solve these issues through isolated agentic automation should first be directed to this module. The appropriate and responsible approach is not to bypass institutional design, but to build the security, access, trust, and accountability framework that allows advanced automation to be used safely.

Synallagi's position is therefore clear: artificial intelligence is essential to the future of the system, but it must operate inside governed architecture. The purpose of this module is to define that architecture.

Conclusion

The complexity of the People, Ideas & Objects Synallagi Security & Access Control module is formidable. Much of that complexity becomes understandable, however, when considered against the demands of the oil & gas industry and the relationships conducted through Joint Operating Committees, markets and the service industry. These relationships provide the business purpose behind the module’s processes, authorities and controls.

What is new is the maturation of Information Technologies and the transition from an Internet of data to an Internet of Value. Digital assets, including stablecoins, are moving toward a material role in the financial system because they can provide greater convenience, faster settlement and new forms of programmable financial control. Their adoption will introduce substantial requirements for security, authority, custody, verification and accountability.

Expecting every producer to develop the systems needed to participate safely in this environment is unrealistic. Assume, for a moment, that one producer commits the time and resources required to implement the necessary infrastructure. Who in the oil & gas industry will it transact with? To use a familiar analogy: to whom will it fax a document when it is the only firm with a fax machine?

Would that producer restrict its business to organizations claiming to have implemented equivalent systems? How would it determine whether those organizations had identified and corrected the same critical cybersecurity vulnerabilities? How could it know that their controls, identities, authorities and transactions could be trusted?

Beyond the handful of producers potentially capable of reaching this level of security independently, what common Intellectual Property, architecture and operating standards would be available to everyone else? Would other firms implement the requirements completely, or would their systems introduce vulnerabilities, malicious software and unauthorized access routes into the shared operating environment? What happens when the inadequately protected organization is a major trading partner, Joint Operator or service provider?

This is the Security & Access Control module: essentially the doors, windows and controlled entrances to the house. Ten other Synallagi modules must be developed and implemented, and comparable questions can be raised about each of them. What would the fixed cost be if every producer attempted to develop these capabilities independently? Under such a fragmented development model, could the industry realistically obtain the savings and benefits defined by Synallagi—including the price maker strategy and the dramatic reduction of overhead costs?

Synallagi offers the industry a unique value proposition: a common level of security, reliability and accountability that individual implementations cannot provide across the North American oil & gas producer and service-industry population.

Oil & gas defines itself through partnerships. Producers pool lands into spacing units, share the financial burden of exploration and development, and conduct operations through Joint Operating Committees. Properties are rarely owned entirely by one producer. Even where they are, royalty holders remain, and most substantial field activities are performed by the secondary service industry. The isolated producer is not one of the industry’s successful operating models. Its information systems cannot reasonably be designed as though it were.

Financial integrity, trust and accountability should therefore be among the producer’s primary concerns. Unless the industry is rebuilt upon an uncompromising level of accountability, it will not regain the confidence of investors and lenders or obtain the full benefit of their participation.

People, Ideas & Objects followed a longitudinal sample of North American oil & gas producers for almost a decade. The original sample of approximately 23 producers is reduced through consolidation to 11. Throughout this period, substantial amounts of producer cash have been directed toward dividends, share buybacks and debt reduction rather than the reconstruction of the industry’s organizational and productive capabilities. Individual debt repayments may result from lender requirements, scheduled maturities, refinancing decisions, commodity-driven cash flow or voluntary balance-sheet management. The broader pattern nevertheless demonstrates that investors and lenders continue to demand financial discipline and the return or protection of their capital. Producers have largely responded by muddling through within their existing organizational structures instead of undertaking the reconstruction required to restore sustained profitability, performance and accountability.

Security & Access Control is therefore more than one module within the Synallagi ERP application. Like every Synallagi module, it represents the only reasonable, effective and economically valuable way to address the industry’s persistent inability to operate profitably and accountably.

Synallagi creates a cost-effective development environment in which one comprehensive application-development cost can be amortized across every barrel of oil equivalent of productive capacity in North America. The alternative is for the industry to fumble independently through another decade while Artificial-Intelligence agents rip and tear at organizations that were never adequately designed for the environment in which they now operate.

The industry can instead take control of reserve preservation, organizational performance and producer profitability by implementing this New Discipline. It is the practical means by which Organizational Latency can be reduced throughout North American oil & gas.

Security & Access Control - People, Ideas & Objects and Oracle Corporation

Date: 2026-08-11

Purpose

Synallagi is based on Oracle Cloud Enterprise Resource Planning and the related capabilities of Oracle Cloud Infrastructure. This provides People, Ideas & Objects with a current, secure and extensible foundation for financial management, procurement, projects, identity, access governance, integration, data protection and cloud operations.

The purpose of this relationship is not to assemble every Oracle security product within Synallagi. It is to use Oracle capabilities where they satisfy the requirements of the application, extend them where Synallagi introduces a distinctive oil & gas operating requirement, and preserve a clear division of responsibility between the Oracle platform and the Synallagi business model.

Oracle provides many of the foundational controls needed to identify users, authenticate them, manage roles, govern access, protect data, monitor activity and maintain cloud services. Synallagi must determine how those controls apply to producers, Joint Operating Committees, service providers, suppliers, temporary working groups, properties, Work Orders, Industrial Command & Control and the other relationships through which the industry conducts its work.

This distinction is essential. Oracle can establish that a person is who they claim to be and provide the mechanisms through which access is granted or denied. Synallagi must establish what authority that person holds, within which organization and Joint Operating Committee, for which property and purpose, during what period, and subject to which business, financial, contractual and operational constraints.

A Capability-Led Architecture

The original People, Ideas & Objects specification is based substantially on the Oracle products available in August 2026. Many of the underlying requirements remain valid, but Oracle's product structure and the delivery of enterprise applications have changed materially.

Synallagi will therefore specify required capabilities before selecting individual Oracle products. A product or service will be included only where its function is required by the target architecture and is not already provided appropriately by Oracle Fusion Cloud Applications or Oracle Cloud Infrastructure.

The architecture will apply the following order of preference:

• Use the security and business controls delivered with Oracle Fusion Cloud Applications.
• Use Oracle Cloud Infrastructure identity, governance, integration and security services for Synallagi extensions and connected services.
• Use Oracle database security and recovery capabilities for databases controlled by People, Ideas & Objects.
• Introduce Oracle Fusion Middleware identity products only where an on-premises, hybrid or legacy integration requirement makes them necessary.
• Implement a Synallagi capability where the requirement is specific to the oil & gas operating model and is not the responsibility of the Oracle platform.

This approach reduces duplication, avoids unnecessary product dependencies and allows Synallagi to benefit from Oracle's continuing cloud development without binding its business design to a historical product catalogue.

Identity Across Organizational Boundaries

Synallagi operates across organizational boundaries. Its users include employees and representatives of producers, members of Joint Operating Committees, service providers, suppliers, contractors, professional advisers and participants in temporary research or operating groups. A person may represent more than one organization or exercise different responsibilities in different circumstances.

Oracle Cloud Infrastructure Identity and Access Management identity domains provide the current foundation for authentication, identity lifecycle management, federation, single sign-on and secure application access across Oracle and non-Oracle services. Oracle Fusion Cloud Applications environments are provisioned with an identity domain that is integrated with Fusion Applications and can support authorized extensions and integrations. Oracle identifies a custom partner application connected to Fusion Applications as an appropriate extension use case.

Synallagi will use identity federation so that participating organizations can authenticate their people through trusted organizational identity providers where appropriate. Federation reduces duplicate credentials and allows an organization to remain responsible for the primary employment or affiliation status of its people. It does not, however, automatically grant access to Synallagi or membership in a Joint Operating Committee.

Admission to Synallagi requires a governed relationship among:

• the person;
• the organization represented by the person;
• the trusted source of the person's identity;
• the person's approved Synallagi participation;
• any Joint Operating Committee or service-provider relationship;
• the effective period of that relationship; and
• the sponsor, approver or agreement under which participation is established.

Separate identity domains may be appropriate for distinct user populations, particularly non-employees and industry participants requiring separate administration, terms of use, profile management or consent. The final identity-domain design will be based on population, trust, administration, privacy, scale, subscription and operational requirements and will be confirmed with Oracle during implementation.

Identity Is Not the Industry Business Directory

An identity service should contain the information required to authenticate a person, associate that person with trusted identifiers and administer access. It should not become the master repository for every supplier profile, professional capability, calendar, commercial relationship or industry contact.

Synallagi will separate identity information from business-party information.

Oracle Fusion Cloud Procurement and Oracle Supplier Portal provide current capabilities for supplier registration, supplier-maintained profiles, contacts, products and services, user provisioning and controlled supplier access. The Resource Marketplace and other Synallagi capabilities will add the industry-specific descriptions, qualifications, availability, performance evidence and relationships needed by producers and Joint Operating Committees.

This separation allows a supplier or service provider to maintain relevant business information without being permitted to alter the security decisions of a producer or Joint Operating Committee. It supports data minimization: identity systems retain the minimum information needed for trust and access, while authoritative business applications retain the richer information needed for transactions and operating relationships.

One User Experience Without Repeated Authentication

Users should be able to move among authorized Oracle Fusion Cloud Applications, Synallagi extensions and connected services without repeatedly entering credentials. Current identity domains, federation and token-based authentication replace the former dependence on desktop-oriented enterprise single sign-on products.

The experience must remain secure and convenient. Sign-on policies, multi factor authentication, adaptive security, device and network conditions, session controls and stronger verification for sensitive actions will be applied according to risk. A routine inquiry and a material change to financial authority should not necessarily require the same level of assurance.

Authentication establishes confidence in identity. Synallagi must still evaluate authorization for every material request. A successful sign-on must never be treated as authority to view every record or perform every function available through the application.

The Oracle Fusion Cloud Application Security Foundation

Oracle Fusion Cloud Applications provide the first layer of application security. The Security Console supports user and role administration, role analysis, role hierarchies, role assignments, privileges, data security policies and related security management. Oracle Cloud Enterprise Resource Planning applies a relationship among the user, the role and the applicable data context. Oracle summarizes this as who can do what on which data.

Synallagi will use delivered Oracle roles, privileges and data-security mechanisms where they correspond to the required business responsibility. Custom roles will be created only where the delivered design does not meet the requirement, and they will grant the minimum privileges necessary.

Oracle's delivered data contexts include structures such as business units, ledgers, data access sets, asset books, legal entities, intercompany organizations, project organizations and other enterprise structures. These controls will be used wherever they align with Synallagi's financial, procurement, project and organizational requirements.

A Joint Operating Committee and its property context introduce additional relationships that cannot be assumed to exist in every delivered Oracle security structure. Synallagi must therefore supplement Oracle application security with its own governed context. The two layers must operate together:

Oracle security determines whether the user may perform the underlying application function and access the applicable Oracle business data.

Synallagi determines whether the user may perform that function for the selected Joint Operating Committee, property, role, purpose, Work Order, command assignment and effective period.

Neither decision is sufficient by itself when an action crosses both layers.

Joint Operating Committee Context and Authority

The Joint Operating Committee is a central authority boundary within Synallagi. When a user enters a Joint Operating Committee workspace, the system must establish a signed and time-bounded operating context containing the selected property, participating organization, active role, command assignment, governing agreement, ownership version, information classifications and allowed capabilities.

Every material request must be evaluated against that context. The evaluation may include:

• authenticated identity and current identity assurance;
• organization and representation relationship;

Joint Operating Committee membership;

• selected property and applicable agreement;
• active role and command assignment;
• delegated decision authority;
• technical, operational and financial authority;
• Work Order or other authorization;
• record ownership and relationship;
• information classification and Intellectual Property permission;
• purpose of access;
• effective date and time;
• segregation-of-duties restrictions;
• location, device or session risk where applicable; and
• emergency or exceptional authority.

Changes to any of these conditions must be reflected promptly in access. If a person leaves an organization, a producer withdraws from a property, a command assignment ends, a Work Order closes or delegated authority is revoked, the related access must expire without depending on a manual review of every application screen.

This dynamic evaluation is the modern expression of the objective originally assigned to Oracle Entitlements Server. Oracle roles and Oracle Access Governance provide important parts of the solution. The complete decision remains a combination of Oracle controls and Synallagi's business context.

Industrial Command & Control

Industrial Command & Control establishes operational roles, reporting relationships, delegation, escalation and effective assignments among the people and organizations participating in work. Security & Access Control ensures that those assignments are reflected in access to information, decisions and application functions.

• The two capabilities are related but must not be confused.
• Identity confirms the person.
• Industrial Command & Control establishes operational position and direction.
• Joint Operating Committee governance establishes decision rights.
• A Work Order authorizes participation, scope, funding and charging.
• Security & Access Control permits the information and system actions required to exercise valid authority.

Availability of a person or capability does not grant operational authority. Operational authority does not automatically grant authority to spend. Permission to view a record does not grant authority to approve it. One person may hold several roles, but Synallagi evaluates the role being exercised for the particular action.

Oracle's identity and governance services reduce the technical effort required to administer users and access. They do not replace the research, user-community design and application development required to model effective command and collaboration across independent organizations.

Temporary Working Groups and Work Orders

For innovation to be dispersed broadly throughout the industry and become a major focus of scientific development, substantially more collaborative research is required. Producers must be able to contribute to working groups formed through ad hoc relationships that are temporary and have a defined short-term purpose.

These working groups are not Joint Operating Committees. They are not organized around the governance and operation of a jointly owned property, and an Authorization for Expenditure is generally inappropriate. Participants may instead contribute assets, facilities, data, Intellectual Property, specialist talent, services or cash. Those contributions may need to be valued to establish each participant's entitlement to the resulting research, knowledge, Intellectual Property or other output.

Synallagi must therefore recognize the working group as a distinct organizational construct. It must establish its purpose, participants, contributions, decision rights, confidentiality, authority, duration, output ownership, permitted use, accounting treatment and completion conditions without forcing the relationship into a Joint Operating Committee or conventional capital-project model.

In the assessment of People, Ideas & Objects, these working groups have largely ceased to exist. A principal cause is the accounting burden placed upon contributors and originators. Their unusual and temporary relationships produce repeated questions about how contributions are authorized, valued, recorded, shared, recovered and reported. The administrative burden can become so great that the initiative is no longer worth pursuing.

One of the two principal purposes of the Synallagi Work Order is intended to resolve this problem. The Work Order may govern a temporary research or innovation collaboration, or authorize work undertaken for a property or Joint Operating Committee. For a working group, it establishes the common record through which participation, contributions, valuation methods, budgets, cost sourcing, charging, rights to output, approvals and closure are defined.

Federated identities and supplier or capability profiles provide trusted information about prospective participants. The Work Order establishes the business basis for their participation, including scope, funding, contribution, cost sourcing, charging and effective period. Industrial Command & Control assigns the operational structure. Security & Access Control grants the minimum access required for each participant's work.

Temporary access must therefore be:

• sponsored and approved;
• linked to a specific purpose and organizational relationship;
• limited to any relevant project, working group, Joint Operating Committee, property, records or functions;
• effective for a defined period;
• reviewed when the assignment changes;
• automatically removed when the assignment or Work Order ends; and
• retained in the audit evidence after the access itself expires.

Emergency access may be permitted where delay would create unacceptable operational, safety, environmental or financial risk. It must be time-limited, conspicuous, fully recorded and subject to prompt review and confirmation by the appropriate authority.

Identity Lifecycle and Delegated Administration

Access must follow the lifecycle of the person and the business relationship. Synallagi requires controlled processes for registration, sponsorship, verification, approval, provisioning, modification, suspension, recertification and removal.

Oracle Access Governance provides a current cloud-native foundation for identity orchestration, access requests, policy-based access, access reviews, access certification and remediation across cloud and on-premises systems. It integrates with Oracle Fusion Cloud Applications and can manage application accounts and role assignments.

Delegated administration is necessary because People, Ideas & Objects cannot maintain every participant's information centrally. Producers, suppliers and service providers should be able to maintain approved portions of their organizational and contact information and request access for their people. The receiving producer, Joint Operating Committee or People, Ideas & Objects authority retains control over what access is granted.

Delegation itself must be governed. A supplier administrator may manage eligible people from that supplier but must not assign internal producer roles, expand access beyond the supplier's permitted scope or approve the supplier's own exceptional privileges without independent control.

Access Requests, Reviews and Segregation of Duties

Oracle Access Governance and Oracle Fusion Cloud Risk Management provide current capabilities for access requests, access certification, sensitive-access analysis and segregation-of-duties controls. Preventive analysis can identify conflicting access before a requested role is provisioned. Periodic, event-based and targeted reviews can determine whether existing access remains necessary.

Synallagi will apply these capabilities to both conventional corporate responsibilities and the smaller, cross-company organizations formed through Joint Operating Committees.

Small organizations create a particular challenge because a limited number of people may perform several functions. Synallagi must identify material conflicts, prevent combinations that cannot be accepted and document compensating controls where complete separation is impractical. Compensating controls may include an independent approval, lower transaction limit, additional evidence, retrospective review, restricted duration or participation by another producer.

Oracle products can support internal control and provide compliance evidence, but their use does not make an organization compliant by itself. Compliance depends upon the complete design and operation of policies, responsibilities, controls, evidence, review and remediation.

Understanding Who, What, Why and How

The Security & Access Control strategy must explain more than whether access is technically allowed. Synallagi must preserve enough evidence to determine:

• who performed or attempted the action;
• which organization the person represented;
• which role and authority were exercised;
• which Joint Operating Committee and property were active;
• what information, function or transaction is involved;
• when and from what session the activity occurred;
• why access is required;
• which agreement, assignment, Work Order, decision or approval supported it;
• what policy decision is made;
• what result or change followed; and
• whether an exception, conflict or override occurred.

Raw technical logs cannot establish all of this meaning. Oracle services can record authentication, role, application and database activity. Synallagi must connect those records to its business context, authority records and transaction history.

Audit evidence must be protected from inappropriate alteration and retained according to legal, regulatory, contractual and business requirements. Amendments correct or supersede prior information without erasing the record that was effective when the original action occurred.

Access analytics should identify excessive privileges, unusual activity, dormant accounts, repeated denials, conflicting roles, inappropriate administrator activity and access that no longer corresponds to a valid business relationship. Analytics and artificial intelligence may assist reviewers, but material access and remediation decisions remain governed, explainable and reviewable.

Information Classification and Confidentiality

Synallagi will protect information according to its ownership, business relationship, sensitivity and permitted purpose. Relevant classes include producer-private information, Joint Operating Committee information, service-provider working information, market-disclosure information, confidential technical and reserve information, financial information, personal information, strategy and Intellectual Property.

Classification must apply consistently to transaction processing, search, reporting, analytics, notifications, documents, exports, caches, training data and generated content. Moving information into a report, analytical model or artificial intelligence process must not weaken its original restrictions.

Oracle Fusion Cloud application security and data contexts will protect information held in delivered applications. Synallagi-controlled databases may additionally use Oracle Database security capabilities. Transparent Data Encryption protects information stored in database files and backups. Oracle Database Vault can restrict inappropriate privileged-administrator access. Data Redaction or application controls may be used where particular displayed values require protection.

Encryption at rest and in transit is a baseline requirement, but encryption alone does not determine who may see information after it is legitimately decrypted. Identity, authorization, context, classification, auditing and key management remain necessary.

Database Security, Monitoring and Configuration

Oracle Data Safe provides a current cloud service for database security assessment, user assessment, sensitive-data discovery, masking, activity auditing, alerts, security policies and centralized management of Oracle Database firewall controls for structured query language activity. It will be evaluated as the principal security-management service for Synallagi-controlled Oracle databases.

Oracle Audit Vault and Database Firewall may be appropriate where Synallagi requires centralized audit collection and database activity monitoring across on-premises, hybrid, Oracle and non-Oracle databases. It is not automatically required for Oracle Fusion Cloud Applications, where the underlying database is operated as part of Oracle's cloud service.

Database firewall controls operate through configured or learned policies. They should not be described as automatically knowing every statement that is valid for every user and application. Their effectiveness depends upon deployment architecture, policy quality, monitoring, exception handling and continued maintenance.

Configuration security will be based on approved baselines, controlled changes, environment separation, automated deployment where appropriate, security assessment, drift detection, remediation and evidence. A configuration-management service should not be assumed to reverse every incorrect change automatically. Oracle Data Safe, Oracle Cloud Infrastructure services and Oracle Enterprise Manager may each contribute depending upon which party operates the database or platform.

Backup, Recovery and Historical Information

Backup and recovery are business-continuity capabilities, not simply storage functions. The Synallagi recovery architecture must establish:

• which information and services must be recoverable;
• acceptable data loss and restoration time;
• backup frequency and retention;
• encryption and key availability;
• administrative separation;
• protection against deletion, compromise and ransomware;
• regional and service-failure scenarios;
• long-term retention requirements;
• restoration testing; and
• evidence that recovery objectives are being met.

For Oracle Cloud databases, Oracle Database Autonomous Recovery Service provides a current managed backup and recovery capability with enforced backup encryption and isolation of backup infrastructure. The final service selection will reflect the databases used by Synallagi and the applicable subscription and recovery requirements.

Historical query is separate from backup. Oracle Flashback Data Archive can preserve database changes for authorized historical access where it is appropriate to the data model. It does not replace backup, an application transaction history, immutable audit evidence or formal records management.

Extending Oracle Fusion Cloud Applications

The Synallagi requirements that are not delivered directly by Oracle Fusion Cloud Applications will be implemented through supported cloud configuration, extension and integration methods.

Oracle Visual Builder Studio supports application extensions and additional application interfaces within the Fusion Applications ecosystem. Oracle Integration and secured application programming interfaces support controlled information exchange and process coordination. These capabilities provide the technical means to develop Joint Operating Committee workspaces, Industrial Command & Control, Resource Marketplace interactions, Work Order relationships and other Synallagi functions while continuing to use Oracle applications as authoritative sources for the business information they own.

Extensions must not duplicate or bypass Oracle controls. They must preserve:

• the authenticated user and active identity domain;
• Oracle application roles and data access;
• the selected Joint Operating Committee and property context;
• source-system ownership of records;
• transaction and approval controls;
• information classification;
• traceability across interfaces; and
• the security effects of changes in either Oracle or Synallagi authority.

Configuration and extension designs must accommodate Oracle's cloud update lifecycle. Security-critical workflows and integrations will be tested against scheduled Oracle updates before production adoption.

Conditional Use of Oracle Fusion Middleware

Oracle continues to provide Oracle Identity and Access Management products for on-premises and hybrid environments. These products remain relevant where Synallagi must integrate legacy applications, locally operated directories or customer-controlled infrastructure. They are not the default foundation for a cloud-first Synallagi implementation.

Where such requirements exist:

• Oracle Access Management may protect on-premises web applications.
• Oracle Identity Governance may support provisioning and governance across locally operated systems.
• Oracle Internet Directory or Oracle Unified Directory may provide directory services.
• Oracle Unified Directory virtualization may present controlled views across existing directories.
• Oracle Advanced Authentication and Oracle Adaptive Risk Management replace the former Oracle Adaptive Access Manager direction.
• identity federation is provided as an integrated capability rather than requiring the former standalone Oracle Identity Federation architecture.

The former Oracle Enterprise Single Sign-On Suite, Oracle Identity Analytics and Oracle Total Recall names should not be used as target-architecture products. Their required capabilities are now met through current identity domains, Oracle Access Governance, Oracle Fusion Cloud Risk Management, current database services and Oracle Flashback technology.

Every middleware addition creates licensing, operation, patching, availability, integration and specialist-support obligations. Its inclusion must therefore be justified by an explicit requirement and confirmed with Oracle.

Development With Oracle and the User Community

Oracle's current platform substantially reduces the amount of foundational security technology that People, Ideas & Objects must develop. It does not remove the need for sustained design and research.

The most difficult questions concern how independent organizations should work together: how authority originates, how it is delegated, how temporary groups form, how costs and obligations are accepted, how operational direction is exercised, how trust is established and how accountability is preserved. Those questions must be resolved with producers, engineers, geologists, service providers, security specialists, auditors, legal advisers and Oracle Services specialists.

People, Ideas & Objects will use our user community to test these requirements through representative operating scenarios. Development costs can then be amortized across the producer community while each participating producer receives the benefit of the common architecture and accumulated industry learning.

Implementation Principles

The following principles govern the relationship between Synallagi and the Oracle platform:

• Business authority is explicit and cannot be inferred solely from identity or organizational membership.
• Every material action is evaluated in the correct Joint Operating Committee, property, organizational and temporal context.
• Oracle-delivered controls are used before equivalent custom controls are developed.
• Synallagi extensions preserve rather than bypass Oracle application security.
• Identity information is separated from supplier, capability, contact and transaction information.
• Access is limited to the minimum information and functions required for an approved purpose.
• Temporary and delegated access has an owner, reason, effective period and automatic end condition.
• Authority to view, decide, direct, perform, approve and spend remains distinguishable.
• Segregation of duties and compensating controls are evaluated in the complete cross-company process.
• Audit evidence connects technical activity with business purpose, authority and result.
• Encryption, backup, recovery and historical access are designed as separate but coordinated controls.
• Analytics and artificial intelligence do not weaken confidentiality, authority or accountability.
• On-premises middleware is introduced only for a demonstrated hybrid or legacy requirement.

- Commercial availability, licensing and supported configurations are confirmed with Oracle before implementation commitment. 

- People, Ideas & Objects Intellectual Property ownership and permitted use are explicit, controlled, auditable and enforceable.

- The architecture is reviewed continuously as Oracle services and Synallagi requirements develop.

Current Oracle Direction

The Oracle product direction in this section is validated against Oracle documentation available in August 2026. At that time, the principal Oracle capabilities applicable to this architecture were:

• Oracle Cloud ERP
• Oracle Fusion Cloud Applications Security Console, application roles and data security;
• Oracle Fusion Cloud Applications identity domains and Oracle Cloud Infrastructure Identity and Access Management;
• Oracle Access Governance;
• Oracle Fusion Cloud Risk Management, including access requests, access certifications and advanced access controls;
• Oracle Fusion Cloud Procurement and Oracle Supplier Portal;
• Oracle Visual Builder Studio and Oracle Integration;
• Oracle Database encryption, Database Vault and Oracle Data Safe;
• Oracle Audit Vault and Database Firewall where hybrid monitoring is required;
• Oracle Database Autonomous Recovery Service; and
• current Oracle Identity and Access Management middleware for justified on-premises or hybrid requirements.
• Oracle's services will continue to change. Synallagi therefore treats these products as the present means of satisfying durable requirements, not as permanent substitutes for those requirements.
• Oracle Reference Material
• Oracle Fusion Cloud Applications Security Console
• Oracle Fusion Cloud Applications data access
• Oracle Fusion Cloud Applications identity domain for extensions
• Oracle Cloud Infrastructure Identity and Access Management identity domains
• Oracle identity-domain types
• Oracle Access Governance
• Oracle Access Governance integration with Fusion Cloud Applications
• Oracle Fusion Cloud Risk Management advanced controls
• Oracle Supplier Portal user provisioning
• Oracle Visual Builder Studio
• Oracle Integration
• Oracle Data Safe
• Oracle Data Safe activity auditing
• Oracle Transparent Data Encryption
• Oracle Data Redaction
• Oracle Database Vault
• Oracle Audit Vault and Database Firewall
• Oracle Database Autonomous Recovery Service
• Oracle Database Flashback technology