Establishing a Higher Standard of Commercial Performance
Every industry develops a standard of performance that its participants come to accept. That standard can demand continuous improvement, disciplined capital allocation and demonstrable profitability. It can also become an accommodation among firms that congratulate one another while avoiding difficult questions. An industry that rewards participation should not be surprised when participation becomes its principal achievement.
Competition becomes more demanding when a firm raises its own performance threshold. Others must respond, and the competitive pressure builds. Those are the animal spirits that advance an industry. Too often in oil & gas, I see a comfortable acceptance of existing practices, with scientific and technical accomplishments treated as sufficient evidence of commercial success. The quarterly report shows earnings. Leadership is satisfied. Criticism is dismissed.
Science is indispensable to oil & gas. Its commercial application, however, must ultimately demonstrate that the resources committed to it have created value. An interesting idea does not become a sound investment simply because the people pursuing it find it compelling.
The loss of investor confidence that I have been discussing for more than a decade should have forced a fundamental reassessment. When investors lose confidence in management’s ability to allocate capital, the corporation’s financial foundation is compromised. Waiting for those investors to recognize how well the company believes it is performing does nothing to rebuild that foundation. Their confidence must be earned through results that withstand scrutiny.
People, Ideas & Objects’ assessment remains that the North American oil & gas industry, considered over at least four decades, has failed to generate the genuine economic profitability its reported results suggest. In our assessment, investor capital has too often sustained operations without creating enduring incremental value, while previously accumulated wealth has been consumed. Profitable quarters and favourable commodity cycles do not, by themselves, resolve that cumulative failure.
Cash flow is particularly capable of obscuring the problem. A capital-intensive business can generate substantial operating cash receipts for years while failing to recover the capital committed to its assets. Selling production from a depleting reserve converts part of that resource into cash. Whether the activity creates value depends on the full economics, including capital recovery. The persistence of cash flow can delay recognition of a commercial failure until the financial capacity to address it has deteriorated. Liquidating reserves to buy groceries is possibly not the intent.
I would place the industry’s commercial effectiveness, at best, at roughly one-quarter of the standard I believe it must achieve. That is my assessment of the distance between its capabilities and its performance. The industry possesses extraordinary scientific knowledge and technical competence. Its ability to organize those capabilities around sustained profitability remains profoundly inadequate.
When a strategy’s shortcomings become impossible to ignore, the response too often involves pursuing the next fashionable opportunity. Heavy oil, natural gas, steam-assisted gravity drainage, offshore, shale, clean energy, back to shale, then Venezuela or another international destination. The geography and technology change. The unresolved capital-allocation problem travels with them.
Moving capital can be justified. The failure occurs when a new direction substitutes for an honest assessment of the previous one. What caused the losses? Which assumptions failed? What can be remediated? Which assets can become commercially viable, and what must change before further capital is committed? “We have to be in this market” is an assertion of urgency. It provides no evidence of investment merit.
Responsibility rests with officers and directors. They establish strategy, approve capital allocation, determine incentives and define acceptable performance. They also establish whether criticism is examined or excluded. Engineers and geologists cannot remedy a governance failure merely by producing another technical achievement.
My criticism has been consistent for decades, as has my experience of being pushed to the margins for expressing it. An industry that treats an unwelcome argument as grounds for exclusion makes its own learning more difficult. The appropriate response is to examine the evidence, challenge the assumptions and demonstrate where the argument fails. Protecting leadership from criticism leaves the underlying commercial problems intact.
Two recurring objections illustrate the difficulty.
The first is the blanket claim that production cannot be shut in because doing so will damage the formation, an objection raised in response to my July 4, 2019 paper. Shut-in decisions require an assessment of the particular reservoir, well, facilities and duration involved. That requirement deserves serious engineering attention. A universal prohibition does not withstand the industry’s own operating practices. Offshore producers routinely shut in wells ahead of hurricanes; the Bureau of Safety and Environmental Enforcement describes this as a standard safety and environmental procedure. Bureau of Safety and Environmental Enforcement
The market disruption of 2020 also exposed the consequences of production becoming disconnected from demand and available storage. On April 20, the expiring May WTI futures contract settled at negative US$37.63 per barrel amid a collapse in consumption, storage constraints and trading pressures around expiry. CFTC For People, Ideas & Objects, that episode reinforced the commercial rationale behind our price maker strategy: production decisions must respond to economic conditions before financial distress forces the response.
The second objection concerns the relationship between natural gas and oil prices. The familiar ratio of approximately 6:1 reflects a comparison of energy content: a barrel of crude oil contains roughly six million British thermal units. This provides an energy-equivalence benchmark when oil is quoted per barrel and natural gas per million Btu. Actual market prices also reflect supply, demand, infrastructure and the ability of consumers to substitute one fuel for another. Energy equivalence does not establish a guaranteed trading relationship. U.S. Energy Information Administration (EIA)
The divergence nevertheless deserves examination. On February 20, 2024, WTI spot crude was US78.72 per barrel and Henry Hub natural gas was US1.50 per million Btu. Dividing those quoted prices produces a ratio of approximately 52.5:1. The Energy Information Administration identified high production, weak consumption and elevated inventories as contributors to the depressed natural gas price. St. Louis Fed
Our challenge concerns the producer’s commercial response to those conditions. Where production cannot recover its full costs, what action will restore profitability? Disputing a comparison with oil does not answer that question. Neither does continuing to produce while waiting for someone else to correct the market.
These issues return us to leadership. Officers and directors are accountable for the operating model through which scientific knowledge, capital and organizational resources are deployed. When that model repeatedly permits commercial failure to continue, its reform becomes a leadership obligation. Another corporate presentation or change in geographic emphasis is distraction and insufficient.
People, Ideas & Objects proposes that reform through Synallagi, our user community and their service provider organizations. Synallagi is being developed as an oil & gas ERP system with an operating model designed to make profitability visible, actionable and accountable at the Joint Operating Committee level. Its purpose is to establish the information, authority and coordination through which people can improve the economics of the assets entrusted to them.
Joint Operating Committee — Capabilities Deployment addresses a central weakness in that operating model: organizational latency. Too much time can pass between identifying a problem, understanding its financial consequences, assembling the necessary capabilities, securing authority and completing the work. During that interval, losses continue and opportunities deteriorate.
Engineers and geologists need access to the people, knowledge, resources and decision authority necessary to act. They also need a clear financial basis for choosing among alternatives. Synallagi is designed to connect their scientific judgment with actual, factual operating and accounting information, standardized monthly financial statements and pro-forma assessments of proposed changes. As new information becomes available, they should be able to distinguish measured results from projected outcomes and adjust their decisions accordingly.
Autonomous Asynchronous Transaction Orchestration supports this work by coordinating transactions, responsibilities and approvals within defined authority and audit controls. The objective is to shorten the interval between identifying a commercial problem and implementing an authorized response. Each completed intervention should then produce evidence that informs the next decision.
Under this discipline, unprofitable production is shut in through an appropriate technical plan, and the property enters an inventory of innovative projects requiring remediation. The commercial problem is made explicit, and the necessary capabilities are directed toward establishing a profitable basis for returning it to production. Success is demonstrated through improved economics and actual results.
This is the competitive standard we seek to establish. Scientific knowledge must translate into decisions; decisions must translate into timely action; and action must demonstrate the value it creates. Synallagi’s contribution is to make that progression an operating discipline that the industry can apply, measure and continually improve.
A New Discipline begins when the pursuit of value governs the work.
Part III — Technical Companion
1. Architecture and authority
The Engineers and Geologists interface presents the selected JOC or permitted research context. Business Operations Management supervises processes across sub-modules. Capability Deployment organizes engagements, while responsible components retain authoritative business decisions, calculations and records.
Autonomous Asynchronous Transaction Orchestration communicates defined tasks, results and exceptions among specialized service providers. A provider may perform one element of a larger process. Business responsibility must remain explicit even where several providers operate software or perform tasks on behalf of the same function.
The architecture should distinguish:
These are logical responsibilities, not a required number of applications, databases or service-provider companies. Vendor and deployment topology choices require a later architecture decision. This companion does not presume that a particular cloud or software product already implements them.
2. Transaction references and record relationships
T-01 — Maintain a connected, versioned business context
Each coordinated engagement should have a stable reference connecting its requirement, parties, applicable JOC or research context, approvals, agreements, deployment, evidence and results.
An authoritative reference should identify the responsible component, record identity and the version or effective basis used. Cached information should carry its source version and retrieval time. Where records have business-effective periods and later recording dates, retain both so that amendments can be interpreted correctly.
A common transaction view is not a second authoritative accounting ledger. It may assemble information from component records and retain the evidence needed to explain a decision.
T-02 — Preserve distinctions without fixing premature cardinalities
Work Order, Job Order, Episteme, AFE, Lease, Accounting Voucher and Material Balance Report must remain distinguishable. An engagement can connect applicable records without prescribing a universal containment hierarchy.
D5 must settle the permitted Work Order/Job Order references, scope checks, amendments and renewed authorization before production implementation. This companion does not specify one Work Order per Job Order, a mandatory Job Order for all research, or a Work Order parent for Episteme.
A proposed relationship record should express its purpose, source, target, governing agreement and effective version. Referential checks belong at the component boundary responsible for the relationship. Deletion or supersession of a source must not silently erase historical evidence.
3. Capability publication and deployment
T-03 — Enforce selective publication
Research & Capabilities retains the producer's capability information. Publication to Knowledge & Learning should explicitly identify the target JOC, permitted content, publisher's authority and source version. A publication operation must not default to all JOCs or the wider market.
The receiving view must enforce audience and purpose restrictions. Search indexes, cached results, notifications and logs must not reveal unpublished capabilities or confidential research subjects.
Changing or withdrawing a publication should affect future discovery according to an agreed policy. Historical records needed to explain an authorized engagement may require retention under restricted access. Retention and withdrawal rules must be specified together; withdrawal is not a promise that already disclosed information can be recalled.
T-04 — Separate discovery, reservation and commitment
Availability displays are advisory until the authoritative resource function accepts a reservation or commitment. Concurrent requests must not both succeed against the same remaining availability where the resource rules prohibit that outcome.
The component owning the relevant commitment should perform an atomic check and update, or an equivalent concurrency control, against its current position. Across independent components, use explicit pending states and acknowledgements rather than pretending there is one instantaneous global transaction.
Resource reservations and financial commitments are different constraints. Acceptance of one does not prove the other has succeeded. The supervisor should expose partial completion, identify what remains pending and follow an agreed release or escalation procedure.
Priority, expiry, reservation renewal and conflict resolution remain user-community decisions.
4. Specialized service-provider work
T-05 — Define an executable contract for each process element
Every service-provider element should specify:
- Business purpose and responsible function.
- Required authoritative inputs and acceptable versions or freshness.
- Authority required to request, approve and execute it.
- Preconditions and dependencies.
- Result, evidence and acceptance criteria.
- Permitted side effects, including whether it commits funds or posts accounting.
- Timeout, retry, dispute and escalation behavior.
- Information disclosure and retention rules.
The provider's identity and the authority under which it acts must remain visible. Replacing a provider must not change the business meaning of the task or silently expand its access.
Process definitions should be versioned. An in-flight engagement should retain its applicable process basis; adopting a new definition requires a specified migration or continuation decision.
T-06 — Keep requests, acknowledgements and results distinct
The following is a proposed message envelope, not a final API schema:
A transport acknowledgement means a message was received. An accepted request means its business preconditions were satisfied. A completed task means its declared result exists. Those distinctions must remain visible to the supervisor and user.
The envelope should carry references and only the information needed by the recipient. It must not become a mechanism for copying every participant's confidential records to every provider.
5. Asynchronous execution and recovery
T-07 — Make progress durable and delivery recoverable
Proposed reliability mechanisms include durable outgoing messages committed with the responsible local change, durable incoming-message receipts, duplicate detection and explicit processing outcomes. Equivalent designs are acceptable if they satisfy the same failure scenarios.
Delivery may occur more than once or arrive out of order. Duplicate delivery must not create a second commitment, charge, payment or posting. Deduplication should use the intended business operation and preserve the original accepted result. Reusing an operation key with materially different content should raise a conflict.
An out-of-order message must be held, rejected or reconciled under a defined rule. Arrival order alone must not determine the governing contract, rate or accounting period.
The system must not claim universal exactly-once effects across independent services. Where an external side effect succeeds but its acknowledgement is lost, reconcile with the authoritative external reference before retrying the effect.
T-08 — Recheck authority at execution
A queued request does not preserve unlimited authority. The executing component must validate the current actor or delegated service authority, permitted purpose, applicable agreement, remaining commitment position and any relevant expiry.
For a delayed action whose authority or business basis has changed, pause or reject it and refer the exception to the responsible function. Do not silently substitute a new budget, contract, beneficiary or rate to make the request succeed.
The design must define which actions can continue under existing approved commitments after a role change and which require renewed approval. That is a business policy decision supported by technical enforcement.
T-09 — Distinguish retry, amendment and corrective action
Transient delivery failures may be retried under bounded rules. Business rejections require corrected inputs or an authorized decision. A pending human approval is a business state, not a transport failure to be retried until it succeeds.
Cancellation must account for work already performed, financial obligations and participant rights. A compensating accounting entry is not a reversal of physical field work. The orchestrator must never issue an automatic contrary field instruction merely to restore a software state.
A failed or abandoned process requires an assigned owner, visible remaining obligations and a documented recovery path. Operational safety and physical authorization remain with the responsible operational functions.
6. Operational and research funding routes
T-10 — Implement operational Work Order controls
Operational deployment must link approved funding, purpose, beneficiary, assignments, commitments and accounting destinations through Work Order. The responsible function checks available authority before accepting further commitments.
Job Order processing separately verifies recognized Industrial Command & Control authority, applicable instruction and contractual scope. No request can use a Job Order to enlarge approved expenditure. Changed scope or budget must pass the relevant amendment and approval process.
Where the agreed process requires both financial readiness and a field instruction, orchestration may follow both prerequisites. Their detailed relationship remains D5; orchestration does not establish a universal record hierarchy.
T-11 — Preserve Episteme's complete research functioning
Episteme requires its own arrangement and contribution controls. Participant AFEs may provide independently approved funding. Eligible operating-cost contributions may be charged to Lease under separate spending approval, and producers may contribute internally generated resource charges under approved arrangements. Lease accepts no capital costs. An internal resource charge must be distinguished from a cash contribution and does not itself create spending authority. No mandatory separate Work Order is introduced.
The design should support two related views: the agreed distribution of research costs and benefits, and the funding or contributions supplied to satisfy the arrangement. Contributions can include cash, time, samples, data, facilities, software and computing resources.
For each contribution, retain contributor, agreed nature, valuation or treatment, quantity or amount where relevant, acceptance evidence, conditions, funding approval references, applicable account treatment and delivery or commitment status. These fields are proposals; their exact schema remains to be agreed.
A noncash contribution must not automatically trigger a cash payment. Its accounting consequence follows the accepted agreement and the responsible accounting treatment. Cash shortfalls cannot be hidden by treating any unvalued contribution as equivalent funding.
The research arrangement must retain budgets, approvals, commitments, allocations, charging and output rights inherited from the former research Work Order function. Independent participant approvals are not replaced by a fictional group-issued AFE.
Conditional contributions and withdrawal require explicit dependencies. Before affected work proceeds, the responsible functions must establish whether required conditions are satisfied and funding remains authorized. Detailed contingency rules remain open, not removed from scope.
An Episteme may combine contributions from several producers and individual researchers. Examples include independently approved capital contributions eligible for exploration treatment, including cash funding for those costs; valued historical data associated with a property or group of wells; and software, computing time and other overhead contributions treated as current-period expenses in the illustrated arrangement. Engineers' and geologists' time may contain both capital and expense elements. Each contribution retains its source, agreed valuation, beneficiary, approval and classification. Cash funding, the contributed resource and the resulting cost are different facts: classification follows the underlying activity and applicable treatment, not the label Episteme or the fact that cash changed hands. The lease contains no capital costs. Detailed classification and allocation rules remain with the responsible accounting functions and user community.
JOC AFE approval is attributable to its members under the applicable governing arrangements. Independently approved producer AFEs retain their own authority. Funding an eligible Work Order or Episteme contribution with an approved AFE is supported; neither deployment tool creates or extends the approval.
T-12 — Preserve accounting classification and discretionary features
Funding validation and accounting classification should be separate checks. Leases must reject capital charges; capital accounts must reject operating charges. Research classification must follow the nature and applicable treatment of the contribution, irrespective of an AFE funding reference.
Purchase Order functionality is discretionary and excluded from standard configuration. If enabled, it must connect contract acceptance, progress payments and holdbacks to the existing approval and coding structure.
Revenue Per Employee is also discretionary. If used, store or reference the authorized method version, factor period, grade, conversion basis, rate and units. Do not infer an hourly rate from an annual revenue figure without the approved conversion method. A new monthly factor must not silently reprice previously authorized work.
There is no producer-size eligibility threshold or special small-producer/start-up floor.
7. Accounting, period close and amendments
T-13 — Obtain authoritative accounting results
Accepted work, time, charges and contribution treatment should reach Accounting Voucher through defined accounting requests. Relevant participant allocation and Joint Account consequences belong to Partnership Accounting and the responsible allocation functions.
Provider acceptance, voucher creation, ledger posting, settlement and collection are distinct results. The supervisor should show their status through authoritative references and avoid interpreting a submitted invoice as a completed payment.
Producer pooled-resource cost recovery must be traceable through the Joint Account. This does not prescribe the same legal or payment arrangement for every supplier or research participant.
T-14 — Preserve monthly Material Balance Report integrity
Each JOC's monthly Material Balance Report must identify the reporting period, configuration, contracts, included wells and relevant allocation bases. Close or clearing must be prevented while required financial, material, system or partnership balances remain unresolved.
Estimates and accruals must remain distinguishable from confirmed evidence. The detailed design must carry forward the source's next-month reversal approach, with specified replacement, late-data and exception handling. It must prevent double counting when confirmed information arrives after an estimate has been reversed or replaced.
A revision should retain the original evidence and affected period, identify its cause, invoke the appropriate accounting amendments and follow dependent allocations and reports. Reprocessing an amendment must not duplicate its financial effects.
The downstream-allocation example's 90-day sequence is illustrative. It is not a universal deadline after which data becomes immutable. Connected reconciliations determine the outstanding work; an accounting balance alone does not establish physical measurement accuracy.
8. Commercial calculations and outcome evaluation
T-15 — Coordinate calculations without centralizing their ownership
The responsible calculation capability must define and version its method. The coordinating process should request a result using an identified scope and basis, including relevant wells, producer interests, period, currency, units, prices, actual costs, overhead, allocation basis, invested capital, additions and recovery contributions.
The result should identify method version, input references, assumptions, evidence status, calculation time and limitations needed for the decision. No fixed recovery period, return parameter or breakeven formula is adopted here.
Source amendments may require recalculation. Preserve the earlier assessment, the revised result and the affected decisions; do not erase the basis on which authorized work was originally undertaken.
Physical-production economics, financing or hedge effects, statutory reporting treatment and commercial recovery must remain distinguishable. Aggregated views should retain access to well details and shared allocations.
T-16 — Connect findings to authorized decisions and outcomes
A financial anomaly should create a reviewable finding with evidence and an assigned recipient. It must not automatically issue field instructions or infer a technical diagnosis.
An authorized response may include investigation, correction, preservation, shut-in or a return to production. The JOC continues its other responsibilities. Each response retains the applicable financial and operational authority.
Outcome evaluation should connect expected technical and financial results to observed evidence, accepted work, charges and collections. Identify changes in prices, allocation and concurrent work that could affect attribution. Detailed methods develop with the Targeting Framework; this companion specifies the evidence needed, not a completed causal model.
During suspension, production-dependent service provider tasks should cease when their triggering activity ceases. Preservation, investigation, amendments and other continuing obligations retain separate triggers. The technical design must not implement suspension as a blanket deletion of all charges.
9. Security, evidence and operations
T-17 — Preserve restricted research and JOC contexts
Enforce permissions at each authoritative service and data access boundary, including background tasks. A process identifier or message reference must not grant access by possession alone.
Research access must respect confidential formation, membership, approved additions and output rights. Non-rival output does not imply public disclosure. Knowledge & Learning publication requires separate permitted-use checks.
Audit records should identify requests, approvals, material state changes, versions and responsible actors without copying unnecessary confidential payloads. Define access, retention and export rules for those records before deployment.
T-18 — Make failure and recovery visible
The supervisory view should expose blocked dependencies, pending approvals, overdue tasks, conflicting versions, uncertain external effects, unresolved accounting balances and unaccepted outputs. Every exception needs a responsible recipient and a next permissible action.
Recovery design must cover interruption between local changes and delivery, provider unavailability, lost acknowledgements and restoration from backups. After restoration, reconcile process status with authoritative commitments, vouchers and external results before resuming work that could duplicate an effect.
Availability targets, recovery objectives, retention periods and monitoring thresholds remain to be agreed with the responsible functions. They are implementation gates, not invented service guarantees.
10. Specialist engagements, Intellectual Property and value
These requirements preserve the Security & Access Control model and define the engagement and evidence relationships required by Capability Deployment.
T-19 — Preserve each specialist's client and assignment context
Use one persistent personal identity with separately approved employment, consultancy, representation and JOC assignments. Every material request must identify the active assignment, represented party, beneficiary and relevant client/JOC. The user interface should make that context clear before consequential action.
Context separation must apply to searches, cached results, exports, notifications, background tasks and AI-assisted work as well as visible screens. Switching context must not reuse another client's permissions or restricted material. Ending one assignment revokes or reevaluates access derived from that assignment while preserving separately authorized work and required historical evidence.
Evaluate representation and segregation-of-duties conflicts when a specialist serves multiple parties. A permitted consultancy relationship does not waive conflicts on an individual approval or transaction.
Success requires engineers and geologists to have clear, complete and timely access to the information and functions needed for their approved work. Employment status must not become an artificial barrier to a client's information. Trust, as a developing Organizational Construct, must be incorporated with explicit representation, accountability, confidentiality and the producer's Intellectual Property rights. These arrangements protect IP and industrial secrets while enabling the work. The design must identify and resolve missing access that prevents success; it must also preserve the agreed client context and disclosure rights.
Access acceptance checks must demonstrate that an assigned specialist can obtain all information and functions required to complete the approved work. Record denied or missing necessary access as an engagement exception with a responsible owner and resolution path. Trust mechanisms are to be developed with the user community; they must operate together with the existing representation, confidentiality and IP-rights model.
T-20 — Connect Intellectual Property permission to use
Retain authoritative references identifying the relevant IP, rights holder or licensor, authorized user or organization, license or agreement, permitted work and beneficiary, effective period, restrictions and permitted treatment of results. These are proposed information requirements, not a legal interpretation of any particular license.
Check the applicable permission before protected material or methods are used, including by an AI workload or external service provider. Client access, professional qualification and ability to operate the software do not substitute for the IP permission. Do not infer permission to disclose, sublicense, copy or train an AI system from permission to perform the engagement.
A changed or expired license must trigger review of affected future work under the governing terms. Historical evidence and continuing rights require their own retention and access basis; neither blanket deletion nor indefinite unrestricted reuse is assumed.
When the intended work requires permission from an IP owner, Autonomous Asynchronous Transaction Orchestration coordinates the purpose-specific license process: identify the owner and intended use, obtain and record the agreed terms and authorized acceptance, establish the resulting permission, and then continue the protected work. It does not invent rights or treat a license request as a completed agreement. The responsible parties and functions retain authority over license terms, acceptance, charges and permitted use.
T-21 — Keep incremental value assessment and compensation distinct
Connect each value claim to its engagement, contribution, baseline, observations, assumptions, period, evaluation method/version and supporting records. Preserve the responsible evaluator and approval evidence. The Targeting Framework owns the agreed evaluation and distribution rules; Business Operations Management follows their use and outcomes.
Separately identify the hourly charge or salary arrangement and any agreed incremental-value compensation, including beneficiary, liable party, applicable terms and allocation basis. Acceptance of a technical result or publication of a performance statement must not itself create a payment entitlement.
Prevent duplicate recognition of the same incremental value across periods, engagements and contributor claims. Define reconciliation, disputes and recalculation when inputs change. Approved compensation reaches Accounting Voucher and relevant allocation processes through existing controls. Formulae, percentages and recognition rules remain for user-community development.
T-22 — Separate restricted evidence from public performance statements
Detailed evaluation evidence is available only to authorized participants and auditors. A public performance statement requires a separately approved release containing anonymized results. Keep a restricted provenance reference connecting the released statement to its evidence, method/version and approval.
Review proposed releases for identifying source information and indirect identification through combinations of client, location, timing, formation or small populations. If the permitted disclosure cannot be achieved, withhold or revise the release. The user community must establish the release and anonymization criteria.
Preserve versions of cumulative performance statements. A subsequent correction to underlying evidence must trigger review of dependent statements and an authorized correction process. A public statement must not expose the restricted provenance or imply that a value claim has been independently verified unless that verification occurred.
T-23 — Make Organizational Latency observable
Record the relevant times at which a finding or opportunity is recognized, reviewed, approved, made ready and acted upon. Identify waits for information, authority, resource availability, external dependencies and execution. Measures must distinguish stages and legitimate waiting conditions rather than rewarding bypass of required review.
Use these observations to improve the New Discipline with engineers, geologists and the user community. Targets and interpretation remain to be agreed; reduced elapsed time alone does not establish improved commercial performance or justify weaker authority checks.
11. Development sequence and review gates
Develop the component responsibility contracts and unresolved decisions first. Then build a representative operational path and an Episteme research path against controlled data. Include provider boundaries and failure recovery from the beginning.
Before production use, resolve D5; define funding and resource concurrency; approve research contingencies, classification and access rules; specify rates and calculations where enabled; establish amendment propagation; define specialist client contexts, IP permissions and value-evidence controls; and complete security and operational recovery review.
The Companion Review and Development Register supplies concrete scenarios and expected outcomes for that work. Passing a simulation demonstrates only the tested behavior under its stated assumptions. Operational readiness requires implemented component integrations, approved policies and evidence from the actual deployment environment.
