Security & Access Control — Business and Technical Specifications

Note to Our User Community

This specification represents the beginning of the development process rather than its conclusion. It establishes the purposes, operating concepts, essential capabilities, responsibilities, controls, and architectural boundaries presently understood to be necessary for Synallagi. It does not contain every requirement that developers will eventually need, nor should it be interpreted as prescribing every design decision that will be made.

As custody of the specification passes from its originator to the Synallagi user community, responsibility for its continued development passes with it. Members of the community will be expected to test its assumptions against their experience, identify missing requirements, resolve ambiguities, and develop the operational detail needed to transform its concepts into a working product.

This transfer is not intended to constrain the community to the ideas presently documented. Members should feel free to propose new capabilities within the community, challenge existing assumptions, and pursue better ways of satisfying the purposes of Synallagi. They should build collaborative support for their ideas and support material proposals with detailed analysis of the business need, affected users, alternatives, benefits, costs, risks, dependencies, authorities, controls, and consequences involved.

Ideas should be welcomed while they are still forming. However, an idea should become a development requirement only after it’s been examined sufficiently to demonstrate that it addresses a genuine need, fits the wider product, and is supported by those whose work or responsibilities it will affect directly.

The community must avoid adding products, technologies, processes, controls, or complexity merely because they are available. Technical sophistication is not a benefit by itself. Every material addition should correspond to a defined business, operational, security, regulatory, or architectural requirement. The objective is to satisfy the needs of Synallagi completely and responsibly without burdening its users, developers, operators, or producers with unnecessary complexity and cost.

Under the Synallagi user community license, a qualified member may receive exclusive rights and corresponding responsibilities for a defined process domain that the member undertakes to manage on behalf of the oil & gas industry. These rights establish accountable stewardship. They are not merely permission to influence the product or control a body of functionality.

The Synallagi user community license establishes the following foundational principles of accountable stewardship and independent governance. These rights ensure that the community remains the primary driver of the product:

• • Exclusive authority to modify, develop, or create derivative works from the underlying intellectual property of Synallagi is reserved solely for licensed community members.  

  • People, Ideas & Objects developers maintain an exclusive focus on community-led requirements, remaining unresponsive to external influences that have not been reconciled through our user community.  

  • Members operate as independent business participants with autonomous budgetary control, ensuring their contributions represent genuine industry needs rather than the interests of external funding sources.

The license provides for the service-provider organization that the member will own and operate to implement, operate, maintain, support, and continue developing the processes within that domain. The member must therefore consider the complete life of the process, including:

• Maintaining its business and technical specifications.  

• Building informed and representative support for proposed requirements.  

• Defining the information, actions, authority, events, controls, and evidence required.  

• Reconciling competing user needs and documenting material decisions.  

• Coordinating requirements that affect other Synallagi process domains.  

• Working with architects and developers to produce compatible solutions.  

• Establishing testing, acceptance, security, service, operational, and maintenance requirements.  

• Providing the documentation, training, support, governance, and continuity necessary for dependable industry use.  

• Managing future changes without losing the purpose, integrity, compatibility, or accumulated knowledge of the process domain.

Exclusive stewardship does not create unlimited authority to expand a process domain, introduce unnecessary complexity, or make decisions affecting other domains without consultation. Every material addition must remain traceable to a demonstrated industry requirement. Changes crossing process-domain boundaries must be collaboratively developed and reconciled within the wider Synallagi specification.

The proficiency demonstrated by Elon Musk in executing scientific endeavors of immense scale and intricacy remains unrivaled. Central to his methodology is an "algorithm"—a set of principles he asserts are fundamental to his success. Within Synallagi, this framework serves as a vital conceptual cornerstone, guiding our user community in the meticulous development and delivery of their products. As detailed in Walter Isaacson's *Elon Musk*, this algorithm consists of five essential components. (Isaacson, 2023, pp. 282, 284–285)

1. Question every requirement.

All requirements should be attached to the name of the person who made it. Always question the requirements, no matter who made it, and then try to improve them. p. 284

People, Ideas & Objects will require each of our user community members and developers to digitally sign their contributions. This process offers two key benefits: it ensures accountability by identifying the responsible individual, and it helps allocate service provider organizations to specific processes within Synallagi. The allocation will be determined by an AI algorithm developed by our user community, with digital signatures assisting in the guiding of appropriate assignments.

2. Delete any part or process you can. 

You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. p. 284

Given the oil & gas industry's high rate of data distribution and duplication, this step challenges us to consider whether a single data source could eliminate redundancy. For further insight, refer to E.F. Codd’s *Relational Theory* in the bibliography. Where sharing the same data to different users who perceive the data differently. 

A key lesson from software development is that while adding features is simple, it often leads to feature bloat; true innovation lies in simplifying the interface by removing unnecessary elements—even if that removal faces resistance.

3. Simplify and optimize. 

This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. p. 284

Although straightforward, this step underscores the time constraints often imposed by quarterly requirements, which frequently force organizations to bypass this global perspective. In many ERP implementations, budgets dictate the elimination of the user committee is the first element skipped, making our prioritization of our user community a distinct competitive advantage, resulting in improved software quality.

4. Accelerate cycle time. 

Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. p. 284

5. Automate. 

That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. p. 285

“If conventional thinking makes your mission impossible,” Musk told him, “then unconventional thinking is necessary.” p. 282

Synallagi divides automation into two distinct areas. The first area encompasses the automation integrated with Oracle Cloud ERP, included upon discovery. The second area involves automating the processes within Synallagi itself, which has been deferred to the third phase of development. For further details, [please refer to our 2/10/2025 paper](https://bit.ly/IOE2-10-2025). Innovative Organization Excellence: How Elon Musk and Visionary Leaders Build High-Performance Enterprises.

Licensed members must preserve reasonable opportunities for affected users and producers, Joint Operating Committees and markets to contribute knowledge, question assumptions, propose alternatives, and participate in validation. Exclusive rights establish responsibility and accountability; they must not prevent the collaboration from which the quality and legitimacy of Synallagi will be derived.

The original specification provides the foundation. Our user community will transform that foundation into complete and testable requirements. Licensed process-domain stewards will establish and operate the service-provider organizations through which those requirements can be implemented, maintained, supported, and improved over time.

The quality of Synallagi ERP software will ultimately depend upon the quality of our user community and their stewardship.

Introduction

Joint Operating Committees are the key organizational construct of a dynamic, innovative, accountable and profitable oil & gas company. It is the interactions of many producers, service providers and suppliers who are involved in the day to day commercial and strategic concerns of that Joint Operating Committee that we need to concern ourselves with. The Security & Access Control module's focus is to ensure the right people have the right access to the right information with the right authority. This is at the right time at the right place and through the right device. 

Throughout Synallagi we discuss two of the most pressing operational issues in the oil & gas industry. Those being the demand for earth science & engineering effort is increasing with each barrel produced. This is best represented by the steep escalation of oil & gas exploration and production costs. At the same time, critical earth science & engineering resources are fixed and difficult to expand. And with the anticipated retirement of this brain trust in the next twenty years, the problem becomes critical. The second issue regards the manner in which the administrative and accounting resources are organized within the industry. With Synallagi the need for each producer to develop their own administrative and accounting capabilities internally is replaced by an overall industry capability. Then each producer can access those resources on a variable cost basis with direct charges to the Joint Operating Committee. This provides operational flexibility in how a producer approaches its strategic and tactical needs to their distinct competitive advantages. 

Business Specifications

Two Types of Data

When we talk about the various people within the producer firms affiliated with a Joint Operating Committee. And the number of Joint Operating Committees that a firm may have an interest in. And the number of people a firm employs. Access control becomes challenging. It becomes a challenge when we consider that people certainly should have the access required, but the level of trust they may have with respect to other partner organizations is probably not as strong. That is to say, does using the Joint Operating Committee as the key organizational construct of a dynamic, innovative, accountable and profitable oil & gas producer, open the producer firm to data loss? This is how People, Ideas & Objects deal with the access and trust issue in the Security & Access Control module.

3.10 Data entitlement

A data entitlement identifies the resources and records to which a privilege applies. Relevant scopes may include organization, business unit, ledger, Joint Operating Committee, property, well, agreement, partner, marketplace, wallet, blockchain address, work order, Authorization for Expenditure, voucher, settlement, or transaction.

Oracle AI Database 26ai or a later approved release is the intended principal data platform. Synallagi should therefore be treated in significant part as database-centred development, while access remains governed consistently through the application, policy, integration, and database layers.

When we concern ourselves with the data and information of the producer firm. We concern ourselves with the information cleared by the various Joint Operating Committees that the oil & gas producer’s interest is in. We can all agree that this information is proprietary and subject to each producer firm's internal policies. (Information such as reserves data, accounting information, internal reports and correspondence, strategy documents.) What we're concerned about is the information and data held in the Accounting Voucher module and the associated data common to the joint account. (well file, agreements, production data, capital and operating costs, revenue and royalties.) 

Close analysis of these two types of data and information held within the firm and the Joint Operating Committee falls within the proprietary and partnership domains. In Canada at least, most data and information regarding well operations can be freely obtained through various regulatory agencies. Nonetheless, the majority of the data is shared through the partnership who have an interest in the data and information. Which is not the case with the producer firm's data. Most of the information is kept close at hand and reported through filtered reserve report summaries and annual reports. Therefore keeping a handle on proprietary data, while operating the Joint Operating Committee as the key organizational construct of the innovative oil & gas producer, as proposed by People, Ideas & Objects, does not present any data leakage.

Access control can therefore be limited by restricting any company personnel from viewing other companies' files. Which is a given. While in People, Ideas & Objects access control is restricted to the firm's Joint Operating Committees and the firm's files only. To extend this further, we would limit access to the appropriate roles within the firm. Then it is up to our user community to define a standard set of generic roles in which access is required to certain data types. This would apply to the types of operations handled by that role, for example, read, insert, update, delete. These generic roles could then be assigned to each individual within the organization based on their needs. Assigning multiple roles for more complex access. Access to proprietary data would be restricted to company personnel only.

Industrial Command & Control (ICC)

Throughout Synallagi we've discussed our solution to one of the premier issues the oil & gas industry faces. That is the demand for earth science & engineering effort per barrel of oil increases with each barrel produced. This is best represented by the steep escalation of oil & gas exploration and production costs over time. At the same time, critical earth science & engineering resources are fixed and difficult to expand in the short or medium term. Add to that the anticipated retirement over the next twenty years of the current brain trust of the industry and the problem becomes a critical concern.

What is proposed through the People, Ideas & Objects software application modules ICC is that the producer's operational strategy avoids the “operator” concept. Instead, it pools these technical resources through each of their partnerships represented in their Joint Operating Committees. That way the inefficiencies that would have been present in the industry can be made available and used through industry wide, producer focused, advanced and advancing specialization and division of labor. Where many of the lower end processes are offloaded to service providers who specialize in that basic skill on behalf of many producers. This is done in a geographical area or other specialization. And each individual producer focuses on a specialized element of science as it develops and innovates upon that. 

People, Ideas & Objects believe producers will soon be unable to commercially support the full scale of engineering & earth science disciplines tasks and responsibilities as they have in house. This will be due to the shortages of resources, the cost escalation of these resources in the market due to their shortages, the expansion of demand from higher production volumes to achieve energy independence, the demands for more science in each incremental barrel of oil produced, the anticipated, substantial expansion of the sciences and the need to innovate upon that expanding science. For producers to maintain a broadened division of labor to deal with these issues and “operatorship” capabilities, it will extend them beyond any producer's commercial capacity.

What these concepts demand is what the Security & Access Control module is designed to provide through the ICC. The People, Ideas & Objects system must provide access to the right person at the right time and at the right place. This is with the right authority and the right information. With the ICC there will be a manner in which the technical and all the resources pooled from the producers, interact with the appropriate governance, compliance and industry standard chain of command.

Before the hierarch, a commercial development of the 20th century, only the military structure existed to organize large populations of individuals. The main difference between the two is subtle but significant. Military structures are broader and flatter than hierarchy. That is one of the ideals we are seeking, but the more significant feature is the ability for the chain of command to span multiple internal and external organizational structures and to move resources from different areas of the military through standardization.

The nature of people working through the industry-standard chain of command layered over the Joint Operating Committee will include all oil & gas disciplines. The contributions of staff, financial and technical resources will include all those employed by the industry today. I could foresee many office buildings being refurbished to accommodate the staff of a single Joint Operating Committee of a large property. There, staff from the different producers may be seconded to provide support for the Joint Operating Committee. They may work for a single Joint Operating Committee, not for any particular producer firm.

As background we should recall that each individual would have different access levels and authorizations to access to People, Ideas & Objects Synallagi. Assuming different roles and responsibilities, they would impose different access levels to data, information, processes and functionality. People, Ideas & Objects application modules rely on the Security & Access Control module to implement Industrial Command & Control. This structure, particularly in a Joint Operating Committee, would weave multiple producer firms under one industry standard chain of command. The interface ensures that all processes are monitored for compliance, governance, and overall completeness.

A principle of Synallagi is that North American oil & gas producers will earn the investment community’s support through competitive performance in capital markets—and through exceptional accountability, compliance, and governance.

Based on People, Ideas & Objects’ long-term observation and analysis of producer performance, the industry’s accountability, compliance and governance appear to operate at approximately one-quarter of the standard expected of a genuinely competitive industry. This is an informed analytical assessment rather than the result of a formal quantitative study.

For decades, the sector consumed capital while failing to deliver the fiduciary discipline investors should expect. It took the extraordinary endowment of shale—and destroyed it rather than creating any value.

After eleven years of raising these issues, their investors have seen little to no evidence of meaningful remediation. Investor trust must be earned through performance, accountability, and governance—not presumed. This begins with the Security & Access Control module. 

Access, Roles and Responsibilities

This topic discusses the way authorizations, roles and responsibilities are handled in the Security & Access Control module of Synallagi. We should discuss the topic of delegating authority and responsibility during absences, which can come up from time to time.

As background we should recall that each individual would have different access levels and authorizations in terms of access to the People, Ideas & Objects systems. Assuming various roles and responsibilities, they would impose different access levels to data, information, processes and functionality. In addition, Security & Access Control is the key module for implementing Industrial Command & Control across People, Ideas & Objects. This structure, particularly in a Joint Operating Committee, would weave multiple producer firms under one chain of command. To ensure compliance, governance, and overall process completeness, it will need to provide an interface to ensure all processes are monitored.

Throughout Synallagi there is the perception of a heightened role for technology in enabling authorization to conduct operations. Thus, the ability to do things and get things done depends on collaborating with partners and authorizing actions through processes managed by the systems. This participation dictates that the designation of the roles in the Security & Access Control module “means” more than just data access; it imposes authority and responsibility to undertake actions on behalf of Joint Operating Committees and / or producer firms.

It is necessary to assign this authority within the Security & Access Control module during any absence. If someone with authority and responsibility is away for whatever reason, they should be able to assign their authority to another person. This will enable them to fill that role while away. This will ensure that the process isn’t held up during their absence. Delegations of authority have been used for years in large firms and with a system that imposes authorizations and responsibilities on specific roles, the ability to temporarily move them down, across or up the chain of command is a necessity to keep the organization functioning.

Lastly we should talk about the interface that helps to identify missing elements in a process. It would simply show the command structure of the people assigned to a Joint Operating Committee or a process. It would show their related role, authorizations and responsibilities. If someone is away, it would indicate who took over their role. It would help to identify how they could impose a chain of command to fill any vacancies. This would be particularly helpful if the role or process needed to be documented for compliance purposes.

Business Specification Conclusion

It is important to remember that here in the Security & Access Control module of Synallagi. That the role and identity-based Industrial Command & Control (ICC) as conceived here has not been implemented, developed or conceived anywhere else before. We are taking role and identity-based management to the next level with the ICC. This is done through the usage of the Joint Operating Committee, through pooling and taking advantage of specialization and the division of labor in the oil & gas industry. 

Why are we bothering with the ICC and the Joint Operating Committee pooling of resources? The issue we are resolving is the finite number of earth science & engineering resources available to the industry. With the anticipated retirement levels in the next 20 years. With the time requirements to bring on increased levels of resources. And most importantly with the demands for more energy, and the demands for more earth science & engineering in each barrel of oil equivalent produced. We face long-term shortages of critical resources. The need to organize the industry, exploit [specialization and division of labor](https://bit.ly/HyperHarSpec), and [Professor Paul Romer's theory of non-rival costs](https://stanford.io/3zD01lx) is necessary to increase the output from the same number of resources. Doing this without pooling the resources in the Joint Operating Committee will cause the producer firm to broaden the scale of their earth science & engineering capabilities beyond what would be a commercially viable concern. Synallagi notes that we have contributions from earth scientists and engineers from multiple producers working together to meet the objectives of the Joint Operating Committee. Therefore we need a means to organize themselves and that is the Industrial Command & Control of the Security & Access Control module. 

How the ICC will be implemented will be determined by our user community. However, I can speculate that the Joint Operating Committee will have standard roles and identities used throughout the industry. Standardization provides many benefits and will be necessary in this instance to make technology work. One of the key benefits of standardization is enhanced innovation. The need to have the various areas "covered" regarding compliance and other requirements will require a standard template used by everyone. Everyone will know that that position is responsible for that role and responsibility. When Joint Operating Committees are small and have only a few people assigned, multiple roles can be assigned to one individual. 

There are security and access control issues associated with the service industry and particularly service providers accessing People, Ideas & Objects systems and data. Removing administrative and accounting resources from the producer firms and organizing them in their own service providers provides significant operational flexibility to the innovative and profitable oil & gas producer. The Security & Access Control module ties these disparate organizations into highly organized replacements for the current bureaucracy. Contributing substantially to People, Ideas & Objects' overall tangible portion of our value proposition.

With the natural division in the types of information held within a producer and Joint Operating Committee. Producers will know that Synallagi can deliver the right information to the right people at the right time. Leakage of proprietary information can be mitigated by isolating company data. This is due to its unique nature and Oracle Label Securities' ability to restrict access to database fields. 

Oracle’s products provide a strong layer of mission critical capabilities in the Security & Access Control module. Oracle provides comprehensive coverage of security, access control, audit, back up, recovery and roll management to name just a few of the highlights provided. Although this comes with additional costs, I am certain that no one will argue with the quality and peace of mind that these products bring.

Conceptual Model

Date: 2026-06-27

1. Design intent

Synallagi operates across organizational boundaries. A person may work for one producer, represent another party under contract, participate in several Joint Operating Committees, perform a specialized duty for a limited period, support a marketplace, and possess different authority in each context.

A conventional statement such as "assign the user a role" is therefore insufficient. Synallagi must determine who the person is, whom they represent, where and in which organizational construct they are acting, what duty they are performing, which information and transaction are involved, the limit of their authority, and whether the current circumstances provide sufficient assurance.

This need for context becomes more important as Synallagi advances hyper-specialization and the division of labor. A geologist may specialize in a formation or geophysical theory. An engineer may specialize in a particular form of hydraulic-fracturing design. An administrative or accounting specialist may manage one narrow process within the Material Balance Report. A single producer or Joint Operating Committee may not generate enough demand to sustain these capabilities within only one producer. Synallagi must enable specialists to work across many producers, Joint Operating Committees, markets, and assignments without receiving broad or permanent access to all of them.

Synallagi is ecosystem-informed, user community-led, service provider-enabled, and technologically supported. Producers participate in this environment, but they are not its exclusive or dominant source of operating knowledge. The relevant community includes service providers, engineers, geologists, accountants, administrators, contractors, service-industry firms, financial participants, technology providers, artificial intelligence specialists, cybersecurity specialists, and other disciplines required to rebuild oil & gas accounting, administration, operations, governance, and marketplaces.

Industrial Command and Control remains the business model through which authority, responsibility, coordination, and accountability are established. Security and Access Control is the policy system that faithfully enforces that model. Its practical objective is to enable the right person, with the right access, to the right information, at the right time, in the right place, on the right device, with the right authority, and through the right method of engagement.

2. Governing principles

1. Explicit representation: every consequential action identifies the organization, market, Joint Operating Committee, or other recognized construct on whose behalf it is performed.

2. No authority by implication: access to a function does not by itself grant authority to commit a party, approve expenditure, disclose information, publish market data, or direct work.

3. Contextual least privilege: access is restricted by duty, information, organizational construct, Joint Operating Committee, property, agreement, market, transaction, time, authority, and accountability.

4. Independent revocation: ending one assignment removes only the access derived from that assignment.

5. No permanent trust from network location: identity, policy, and current context determine access.

6. Foundational accountability: every material decision remains attributable to an authorized human or explicitly governed automated authority.

7. Complete evidence: Synallagi records the basis on which material access and authority decisions were made.

8. Safe failure: uncertainty about identity, representation, policy, scope, authority, cybersecurity condition, or accountability results in denial or controlled escalation.

9. Technology-independent requirements: Oracle capabilities implement the model but do not define Synallagi's organizational concepts.

10. Governed change: roles, policies, conflicts, authority templates, market rules, wallet rules, and artificial intelligence guardrails are versioned and reviewed like other critical product configuration.

3. Core objects

3.1 Identity

An identity is the persistent digital representation of a human, service, integration, device, wallet, or automated agent. Its purpose is to give Synallagi one reliable subject to which authentication, organizational relationships, assignments, actions, and accountability can be attached. A human identity normally remains the same while the person's employer, producer representation, Joint Operating Committee memberships, market participation, duties, and authority change around it.

An identity is not an employee record, Joint Operating Committee member, role, wallet, account, or market participant. Those are relationships or assignments attached to the identity.

Identity is broader than federated identity. Federation is one method by which Synallagi may trust another organization's authentication of an identity. It does not create Joint Operating Committee membership, market participation, wallet authority, or business authority.

Each identity consists of a unique identifier, type, status, authoritative source, assurance information, and lifecycle. Non-human identities must have a named human or organizational owner

3.2 Organization

An organization may be a producer, service company, supplier, regulator, auditor, financial participant, service provider, People, Ideas & Objects, or another recognized legal or commercial party. A market, Joint Operating Committee, user community, role, or wallet community may influence access but is modeled separately because it is not necessarily an organization.

3.3 Organizational relationship

This object establishes why an identity may represent an organization. Examples include employment, directorship, partnership representation, professional engagement, service contract, regulatory appointment, audit engagement, or approved marketplace participation.

The relationship represents an owner, sponsor, effective dates, status, and evidence. Ending it triggers review or revocation of all derived assignments.

3.4 Organizational construct

Synallagi's organizational constructs define, support, and constrain what the application, its participants, and its automated processes may do.

The nine organizational constructs currently identified are:

1. 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.

   9. Transactions.

An organizational construct is represented in security policy when it creates membership, authority, responsibility, information, process, market, technology, trust, or transaction boundaries. The constructs must not be reduced to technical roles. They are part of the institutional design that determines which relationships and actions Synallagi recognizes.

3.5 Joint Operating Committee

A Joint Operating Committee is the key organizational construct of Synallagi and a governed multi-party operating context. It has members, participating organizations, agreements, properties, decision rules, authority structures, information boundaries, effective dates, and accountability requirements.

The Joint Operating Committee is not merely a data-security segment. It is a domain object from which scoped authority and access may be derived.

3.6 Representation

Representation connects an identity, organization, and operating context. It answers: "For whom is this identity acting here?"

An identity may have more than one representation, including arrangements in which a small producer participates through another producer as a non-novated member. The active representation must be unambiguous when a material action occurs. Where dual representation creates a conflict, policy must prohibit the action or require declared mitigation.

3.7 Business role

A business role describes a recognizable position in an organization, Joint Operating Committee, market, user community, or service-provider process, such as working-interest representative, production engineer, controller, external auditor, formation specialist, transaction designer, wallet administrator, marketplace participant, or Material Balance Report reconciliation specialist.

A role groups duties but does not itself define all information access or authority.

3.8 Duty

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

Duties are the primary units used for least privilege, work rotation, segregation-of-duties analysis, and assignment of accountability.

3.9 Privilege

A privilege permits a system action such as view, create, amend, approve, post, export, administer, settle, tokenize, revoke, or invoke an application programming interface operation.

Privileges enable functions. They do not independently grant information access or business authority.

Synallagi application programming interfaces are private. Direct access is restricted 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.

Unauthorized release or use of private application programming interfaces is a license, security, and intellectual property concern. The specification should state Synallagi's product policy clearly without relying on legal interpretation inside this module.

3.11 Authority

Authority permits a subject to make or approve a business commitment. It may be constrained by monetary value, ownership interest, voting threshold, technical discipline, geographic area, property, transaction type, market, wallet, settlement instrument, or emergency condition.

Authority is granted by an accountable body and must have an effective period and evidence for accountability and auditability. The system must make the origin, exercise, result, and subsequent review of authority visible.

Responsibility and accountability

Responsibility identifies the party expected to perform or supervise work. Accountability identifies the party answerable for the outcome. Neither should be inferred solely from technical access.

Accountability must persist from the assignment of authority through the transaction, resulting records, financial statements, investor communication, performance evaluation, and audit evidence.

3.13 Delegation

A delegation temporarily transfers specified duties or authority. It identifies delegator, delegate, scope, reason, dates, approval, conflicts, and revocation state.

Delegation cannot create powers the delegator does not possess, evade segregation-of-duties policy, or silently transfer accountability. Synallagi should support innovative delegation patterns developed through our user community where they are needed to preserve organizational continuity.

3.14 Policy

A policy expresses the conditions under which a request is permitted, denied, or escalated. Policies may be global, organizational, Joint Operating Committee-specific, resource-specific, transaction-specific, market-specific, wallet-specific, or method-specific.

3.15 Audit event

An audit event records who or what acted, represented party, context, action, resource, before and after state, evaluated policy, decision, authority basis, time, assurance, result, accountability, and correlation identifiers.

Synallagi shall restore audit controls to a central operational role and demonstrate their value across distributed workforces, artificial intelligence-assisted processes, Joint Operating Committees, markets, service-provider activities, blockchain-supported transactions, and crypto-based asset participation.

In addition to audit controls, People, Ideas & Objects invites accounting firms to establish their own user-community members to actively participate in software development. The objective is to integrate higher levels of accountability, assist audit needs, and reduce the overall costs of annual audits and statutory reporting for the oil & gas industry.

4. Access-decision model

Every protected operation is evaluated as:

Subject plus representation plus operating context plus duty plus action plus resource plus information scope plus transaction state plus authority plus time plus session assurance plus cybersecurity condition plus applicable constraints plus accountability assignment.

The decision process should answer:

• Is the identity active and sufficiently authenticated?

• Is its authoritative relationship still valid?

• Which organization is it representing?

• Is that representation valid for this producer, Joint Operating Committee, agency, employment assignment, market, wallet, or other recognized context?

• Does the identity hold the required role and duty?

• Does the duty provide the required system privilege?

•  Does the data entitlement include this exact resource?

• Is the transaction in a state where this action is permitted?

• Does the identity possess sufficient business authority?

• Would the action create a segregation-of-duties or representation conflict?

• Are time, session, device, location, identity assurance, and cybersecurity conditions acceptable?

• Is additional approval, step-up authentication, or independent certification required?

• Is the accountable party identified?

The decision and its material inputs are retained as evidence for consequential actions.

5. Trust boundaries

Boundary A — home organization to Synallagi

The home organization may authenticate its people and assert selected attributes. Synallagi determines which issuers, authentication assurances, attributes, and lifecycle signals it accepts.

Boundary B — organization to Joint Operating Committee

Employment or authentication does not automatically confer Joint Operating Committee membership. A valid Joint Operating Committee representation and assignment are separately required.

Boundary C — Joint Operating Committee to producer-private information

Participation in a Joint Operating Committee grants no implicit access to a producer's strategy, reserves analysis, internal correspondence, unrelated properties, or other private information.

This boundary does not restrict information that is public by law or regulation. Production volumes, well configurations, drilling records, hydraulic-fracturing information, and other prescribed records may need to be disclosed in considerable detail.

Boundary D — Joint Operating Committee to marketplace

Information and authority used in a Joint Operating Committee are not automatically publishable or usable in a marketplace. Disclosure and commitment require separate privileges and authority, except where a defined public-disclosure obligation applies.

Boundary E — human to automated agent

An artificial intelligence system or automated service receives only explicitly delegated information and actions. The system records whether output is advisory, prepared for approval, or executed under governed automated authority.

People, Ideas & Objects' intellectual property and Targeting Framework are intended to define the objectives, permissions, constraints, and boundaries within which agents operate. These guardrails must be implemented as enforceable policy and monitored behaviour, not only as instructions to the model.

Boundary F — application to integration

Every application programming interface client and integration has its own identity, owner, credential lifecycle, permissions, information scope, and monitoring. Shared technical accounts are prohibited except under an approved transitional exception.

Boundary G — market to asset ownership

Market participation, wallet control, stablecoin payment capability, or blockchain address control does not automatically establish beneficial ownership, authority to sell, authority to pledge, authority to vote, or authority to receive Joint Operating Committee-level financial statements. Those rights must be separately represented, evidenced, and governed.

6. Assignment lifecycle

1. 1. Join

   2. Establish or federate identity.

   3. Verify organizational relationship and sponsor.

   4. Admit the organization and representative to the applicable context.

   5. Assign governed roles and duties.

   6. Define information scope and authority.

   7. Evaluate conflicts.

   8. Obtain required approvals.

   9. Provision and verify access.

   10. Record evidence and notify relevant owners.

Recurring transaction designs should be expressed as governed templates. A template defines the persistent, generic elements of a transaction type: roles, duties, workflow, information requirements, controls, authority patterns, and audit evidence. Each assignment supplies the people, organizations, Joint Operating Committees, properties, values, dates, and other context unique to that transaction.

Move

Changes in employer, contract, represented organization, Joint Operating Committee, property, duty, authority, ownership, pooling assignment, market status, wallet authority, or transaction template trigger reevaluation. New access is not simply added to old access. Obsolete derived access is removed.

Leave

Termination, contract expiry, Joint Operating Committee withdrawal, assignment, novation, farmout, farmin, subsequent joint venture, working-interest disposition, suspension, loss of qualification, market removal, wallet compromise, or termination of a pooling assignment causes prompt reevaluation or revocation.

Review

Access is certified periodically and after material events. Reviewers assess not only the assigned roles but Joint Operating Committee membership, information scope, authority, delegation, privileged access, market access, wallet authority, artificial intelligence access, and unresolved exceptions.

7. Segregation-of-duties model

Conflicts should be defined at three levels:

• Assignment conflict: incompatible duties are held concurrently.

• Transaction conflict: one person attempts incompatible actions on the same transaction.

• Representation conflict: one person represents parties with conflicting interests in the same decision.

A conflict may be prohibited, require a different actor, or proceed only with an approved mitigating control.

8. Illustrative decision scenarios

Authorization for Expenditure approval

A partner representative may approve an Authorization for Expenditure only for the represented partner and applicable Joint Operating Committee, within a valid assignment and monetary authority, after required authentication, provided the representative did not perform a prohibited conflicting duty.

8.a. Voucher review

A working-interest participant may view joint-account voucher information and supporting evidence to the extent established by the governing agreement and pooled Joint Operating Committee structure. Producer-private analysis, unrelated properties, and another participant's private annotations remain outside that entitlement.

Implementation within Synallagi is defined in the Accounting Voucher module. What is an accounting voucher is unique with particular characteristics for North American oil & gas and use of the Joint Operating Committee. A point of discussion is the Accounting Voucher can be saved as a template, added to as time passes and reused. When a template is deployed and is active within the accounting month it is then called a Synallagi. The Greek word for transaction, deal, business or exchange. 

Marketplace participation

A market participant may offer services, bid, negotiate, or accept an assignment only within an approved market role, qualification, representation, disclosure policy, and authority limit. Marketplace participation does not create access to unrelated producer-private or Joint Operating Committee-confidential information.

Crypto-based asset participation

A holder of a crypto-based oil & gas asset may receive financial statements or other disclosures only when identity, wallet control, beneficial ownership, asset rights, disclosure entitlement, and regulatory obligations have been established. Control of a wallet alone is not sufficient to establish every right in Synallagi.

Hyperspecialized Material Balance Report work

One service provider may capture industry-level balancing adjustments as controlled transactions. Another may analyze, verify, and reconcile the adjustments. Further specialists may support individual producers or Joint Operating Committees in validating their resulting records. Each specialist receives only the process, information partition, and evidence required for their duty.

Artificial intelligence preparation of a recommendation

An artificial intelligence agent may read approved information and prepare a recommendation under its own workload identity. It may not represent a partner or approve the decision unless a future policy explicitly establishes governed automated authority.

9. Oracle mapping principle

Oracle Cloud Enterprise Resource Planning can implement substantial portions of function and data security. Oracle security administration and risk-management capabilities can support role administration, analysis, access requests, segregation-of-duties controls, access certification, and audit reporting.

Synallagi should inherit and configure Oracle-delivered security where it meets the requirement, then use supported extension points to add Synallagi-specific capabilities while maintaining a consistent user experience.

Synallagi must own the domain objects and policy semantics unique to the product: Joint Operating Committee membership, representation, pooling relationships, agreement scope, working interest, transaction authority, delegation, marketplace participation, hyperspecialized service-provider work, wallet participation, crypto-based asset rights, cybersecurity policy, and cross-organizational conflicts.

10. Remaining decisions

The following matters remain open and should be developed with our user community and service providers:

1. A complete catalogue of standardized and hyper-specialized roles and duties.

2. The precise relationship among working-interest voting, monetary authority, technical authority, pooled capability assignments, market authority, and wallet authority.

3. The detailed information-classification rules for each Joint Operating Committee artifact and public disclosure obligation.

4. Actions requiring dual control, step-up authentication, independent technical certification, or Compliance and Governance review.

5. Required revocation and reevaluation timing for each lifecycle event.

6. The actions artificial intelligence systems may prepare, recommend, execute, or never perform.

7. The security consequences of the nine organizational constructs.

8. The detailed blockchain, stablecoin, and crypto-asset participation model.

9. The cybersecurity control model appropriate to Synallagi's cross-industry role.

10. The access rules for the Targeting Framework.

Architecture Brief

Date: 2026-06-27

This brief establishes the target direction for the Security & Access Control module and defines the architectural structure through which its business vision is to be implemented. The module is a central specification for trust, authority, accountability, cybersecurity, markets, transactions, artificial intelligence and cross-organizational participation in Synallagi.

Governing thesis

Security and Access Control in Synallagi is not only the administration of users, roles, passwords, or screens throughout North American oil & gas. It is the operating policy system that determines:

• who or what is acting;

• whom they represent;

• which organization, Joint Operating Committee, market, transaction, asset, or assignment is in scope;

• what duty they are performing;

• which information and functions they may use;

• what business authority they possess;

• what accountability attaches to the action;

• what evidence must be retained; and

• when access must be denied, escalated, reviewed, suspended, or revoked.

The intended outcome is to enable the right person, with the right access, to the right information, at the right time, in the right place, on the right device, with the right authority, and through the right method of engagement.

Design posture

Synallagi should pursue quality of architecture over quantity of prose. The module should be built in layers:

• Conceptual model.

• Target architecture brief.

• Technical companion specification.

• Section-by-section expansion.

• Traceability back to the original specification and related modules.

The immediate objective is not to finalize every rule. It is to establish a strong enough structure that later sections can be developed without repeatedly reopening the foundation.

There are few short-term solutions to the shortfall in geologists and engineers over the next twenty years. It takes the better part of that time to train them to operate in the industry. What we do know are several "things" being applied in the People, Ideas & Objects Synallagi. Many of these concepts are based on what we call Industrial Command and Control. Which is a method developed in the Security & Access Control module of imposing command and control over any and all Joint Operating Committees, working groups, producer firms, service providers or internal or external organizations the producer may need to add structure to. The concepts are the further hyper specialization and division of labor, and a reduction in the redundant building of capabilities within each oil & gas producer, or as we describe it, a pooling of resources in the Joint Operating Committee.

The first concept of specialization and division of labor is well known as a principle of economics that brings about greater economic productivity from the same volume of resources. Given that the volume of earth science & engineering resources is known for the foreseeable future. Specialization and the division of labor will provide industry with a tangible means to deal with oil & gas industry productivity. In today’s marketplace, approaching a heightened level of specialization and division of labor without software to define and support it would be unproductive.

The pooling concept is the solution to the current desire that each producer firm acquires the earth science & engineering capabilities necessary to deal with all the needs of their “operated” properties. This creates unneeded “just-in-time” capabilities for scarce scientific resources. When each producer within the industry pursues this same strategy substantial redundancies are built into the industry's capabilities. Redundancies that are left unused and unusable. What is proposed through the People, Ideas & Objects software application modules is that the producer's operational strategy avoids the “operator” concept. Instead, it pools their specialized technical resources through the Joint Operating Committee partnership. That way the redundancies that would have been present in the industry can be made available to the producers and used by the producers through hyper-specialization and division of labor.

These same principles are present in the second issue noted above. The administrative and accounting capabilities acquired through industry-wide capabilities provide the producer with the flexibility to address operational concerns. Issues such as today’s low natural gas prices can be addressed through this revised structure. By having administrative and accounting service providers charge their service fees directly to the Joint Operating Committee. The producer gains the ability to shut-in unprofitable production with only positive effects on their financial performance. Administrative, accounting, and production costs are eliminated during shut-in production. Providing the most profitable means of oil & gas operations when unprofitable properties no longer dilute profitable properties. Producers can save their reserves for the time when they can be produced profitably. Reserves costs don't have to carry additional losses if unprofitable production continues. Reserves can be seen as a low-cost solution to production and storage. Commodity prices will have less volatility due to producers removing marginal production from the marketplace. And petroleum reserves values are maximized when prices determine reserves value and the volume of commercial reserves available.

Domain position

Synallagi is ecosystem-informed, user community-led, service provider-enabled, and technologically supported. Producers are essential participants, but they are not the exclusive source of operating knowledge.

The Security and Access Control module must therefore support a larger operating community:

• producers;

• Joint Operating Committees;

• working-interest participants;

• service providers;

• suppliers;

• engineers;

• geologists;

• accountants;

• administrators;

• auditors;

• financial participants;

• market participants;

• technology providers;

• artificial intelligence specialists;

• cybersecurity specialists; and

• People, Ideas & Objects.

The module must preserve independence, information rights, authority limits, and accountability while allowing these parties to collaborate through common transactions, markets, infrastructure, and evidence.

Being able to provide service providers with access to and security during these day-to-day operations will be a unique situation for the oil & gas producer. Service providers will aggregate data industry wide. Although the data they access will be voluminous, unattributable to its owner and of a specialized nature. And there will be many service providers involved in providing administrative and accounting services to the producer firm and Joint Operating Committees. Consideration of the security, access control and proprietary nature of the information will be priorities for Synallagi. 

A quick note on mobility. People are provided with new devices that enable them to work anywhere. These phones and tablets, in addition to laptop computers, open up security and access control concerns for the innovative and profitable oil & gas producer. Some producers enable their staff with policies that allow them to bring their own devices to work. The fact is these devices provide enhanced productivity and are appropriate for an innovative and profitable oil & gas producer. People, Ideas & Objects Synallagi includes an understanding that these devices will be part of the day to day used in the oil & gas industry. 

What these concepts require is what the Security & Access Control module is designed to provide. The system must provide access to the right person at the right time and at the right place, on the right device with the right authority to the right information and through the right method of engagement. With the Industrial Command & Control there will be a manner in which the technical, and all the resources, that have been pooled from the producers, interact with an appropriate governance and chain of command.

Organizational constructs

The module shall align with the nine organizational constructs currently identified for Synallagi:

1. 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.

   9. Transactions.

These constructs are not merely labels. They define, support, and constrain what Synallagi recognizes as legitimate organization, work, information, authority, access, and accountability.

Architectural principles

Explicit representation

Every consequential action must identify the party, organization, Joint Operating Committee, market, transaction, or other construct on whose behalf the action is performed.

No authority by implication

Access to a function does not by itself grant authority to commit a party, approve an expenditure, publish information, disclose market data, direct work, or bind a Joint Operating Committee.

Contextual least privilege

Access must be limited by duty, transaction, information classification, organizational construct, Joint Operating Committee, property, agreement, market, working interest, authority, time, device, session assurance, and accountability.

Accountability as a product strength

Accountability, auditability, and evidence are competitive strengths of Synallagi. The module should help restore confidence in oil & gas administration, financial reporting, investor communication, and operating integrity. As is noted earlier in the Industrial Command & Control section of this specification.

Cybersecurity is integral

Cybersecurity is not a separate afterthought. Identity compromise, unauthorized access, malicious administration, data leakage, ransomware, integration abuse, artificial intelligence misuse, and market manipulation all belong within the scope of this module.

Markets and asset participation

Markets are first-class security contexts. Marketplace access, disclosure, offer authority, bid authority, settlement, investment participation, and asset securitization require explicit authorization and evidence.

Blockchain, stablecoins, and crypto-based participation

Where Synallagi supports blockchain records, stablecoin settlement, digital wallets, or crypto-based participation in oil & gas assets, the module must govern identity, wallet control, beneficial ownership, transaction authority, investor reporting, financial statement publication, disclosure, custody, settlement, revocation, and incident response.

Artificial intelligence under policy

Artificial intelligence systems may advise, prepare, reconcile, classify, monitor, or recommend. They may not infer representation, disclosure rights, or business authority. Any autonomous action requires explicit policy, accountable ownership, audit evidence, and enforceable guardrails.

Required conceptual separations

The module must keep the following concepts separate, even when an implementation platform combines parts of them:

• identity;

• authentication;

• organization;

• organizational relationship;

• represented party;

• Joint Operating Committee membership;

• market participation;

• wallet or payment instrument control;

• business role;

• duty;

• privilege;

• data entitlement;

• authority;

• responsibility;

• accountability;

• delegation;

• transaction state;

• information classification;

• cybersecurity risk;

• audit event; and

• policy decision.

This separation is necessary because a person may be authenticated but not authorized, employed but not assigned, assigned but not empowered, empowered but conflicted, or technically able to act without business authority.

• • Open design decisions

  • The following items should not be forced prematurely:

  • the detailed role and duty catalogue;

  • the detailed market participation model;

  • wallet identity and beneficial ownership rules;

  • stablecoin settlement and custody requirements;

  • blockchain record authority;

  • crypto-based asset securitization workflow;

  • investor reporting from the Joint Operating Committee level;

  • cybersecurity incident classifications;

  • artificial intelligence execution boundaries;

  • Targeting Framework access rules;

  • revocation timing by event type;

  • audit participation by accounting firms; and

  • exact Oracle implementation mapping.

*Only to Start the Ball Rolling for Our User Community*

These decisions should be developed through focused pages and later folded into the module.

People, Ideas & Objects and Oracle Corporation

Date: 2026-08-11

Purpose

Synallagi is based on Oracle Fusion 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, multifactor 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 Fusion 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 and 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 and 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 and 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 and 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:

1. Business authority is explicit and cannot be inferred solely from identity or organizational membership.  

2. Every material action is evaluated in the correct Joint Operating Committee, property, organizational and temporal context.  

3. Oracle-delivered controls are used before equivalent custom controls are developed.  

4. Synallagi extensions preserve rather than bypass Oracle application security.  

5. Identity information is separated from supplier, capability, contact and transaction information.  

6. Access is limited to the minimum information and functions required for an approved purpose.  

7. Temporary and delegated access has an owner, reason, effective period and automatic end condition.  

8. Authority to view, decide, direct, perform, approve and spend remains distinguishable.  

9. Segregation of duties and compensating controls are evaluated in the complete cross-company process.  

10. Audit evidence connects technical activity with business purpose, authority and result.  

11. Encryption, backup, recovery and historical access are designed as separate but coordinated controls.  

12. Analytics and artificial intelligence do not weaken confidentiality, authority or accountability.  

13. On-premises middleware is introduced only for a demonstrated hybrid or legacy requirement.  

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

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

16. 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 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 (https://docs.oracle.com/en/cloud/saas/applications-common/26c/facsa/overview-of-security-console.html)  

• Oracle Fusion Cloud Applications data access (https://docs.oracle.com/en/cloud/saas/applications-common/26c/facsa/data-access.html)  

• Oracle Fusion Cloud Applications identity domain for extensions (https://docs.oracle.com/en/cloud/saas/applications-common/26a/oaext/overview-of-using-oracle-fusion-cloud-applications-identity-domain-to-build-extensions.html)  

• Oracle Cloud Infrastructure Identity and Access Management identity domains](https://docs.oracle.com/en-us/iaas/Content/Identity/)  

• Oracle identity-domain types (https://docs.oracle.com/en-us/iaas/Content/Identity/sku/overview.html)  

• Oracle Access Governance (https://docs.oracle.com/en-us/iaas/Content/access-governance/access-governance-overview.html)  

• Oracle Access Governance integration with Fusion Cloud Applications](https://docs.oracle.com/en-us/iaas/Content/access-governance/integrate-with-fusion-cloud-applications.htm)  

• Oracle Fusion Cloud Risk Management advanced controls (https://docs.oracle.com/en/cloud/saas/risk-management-and-compliance/26c/faacm/using-advanced-controls.pdf)  

• Oracle Supplier Portal user provisioning (https://docs.oracle.com/en/cloud/saas/procurement/26a/oapro/how-supplier-user-provisioning-works.html)  

• Oracle Visual Builder Studio (https://docs.oracle.com/en/cloud/saas/applications-common/26c/oaext/overview-of-using-visual-builder-studio.html)  

• Oracle Integration (https://docs.oracle.com/en/cloud/paas/application-integration/integrations-user/integrations.html)  

• Oracle Data Safe (https://docs.oracle.com/en-us/iaas/data-safe/doc/oracle-data-safe-overview.html)  

• Oracle Data Safe activity auditing (https://docs.oracle.com/en-us/iaas/data-safe/doc/activity-auditing-overview.html)  

• Oracle Transparent Data Encryption (https://docs.oracle.com/en/database/oracle/oracle-database/26/dbtde/faq-tde.html)  

• Oracle Data Redaction (https://docs.oracle.com/en/database/oracle/oracle-database/26/dbred/what-is-oracle-data-redaction.html)  

• Oracle Database Vault (https://docs.oracle.com/en/database/oracle/oracle-database/26/dvadm/introduction-to-oracle-database-vault.html)  

• Oracle Audit Vault and Database Firewall (https://docs.oracle.com/en/database/oracle/audit-vault-database-firewall/20/index.html)  

• Oracle Database Autonomous Recovery Service (https://docs.oracle.com/en-us/iaas/recovery-service/index.html)  

• Oracle Database Flashback technology (https://docs.oracle.com/en/database/oracle/oracle-database/26/haovw/oracle-flashback-technology.html)

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's 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, hyperspecialized 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

Please see table at the end of the page.

Technical Specification Conclusion

Synallagi's 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, hyperspecialized 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.

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.