UAE · ENBook a demo
Oil & GasEngineeringAssistant

Back-End Agent

Builds services, APIs and business logic.

Back-End AgentApplication Engineering
Industry
Oil & Gas
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Back-End Tech Lead
Code
ENG-02

It implements services and business logic for the operational and commercial platforms, such as production allocation services, the permit-to-work back end, nomination and lifting APIs and the fuel-card service, keeping published contracts backward compatible and migrations reversible. It opens a pull request with tests and the API specification, and flags any change to allocation, measurement or safety logic.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the code repository: the service code, API specification and tests..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Back-End Tech Lead with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens a pull request with the change and the updated API specification. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The back-end standards: API contracts, the services that feed hydrocarbon accounting and regulatory reporting, measurement and allocation rules, migration standards and the security rules.

Reads from

the code repository: the service code, API specification and tests.

Acts in

the code repository: it opens a pull request with the change and the updated API specification.

Hands back

An object with branch, endpoints_changed, migrations, tests_added, reconciliation_result (or null) and risk_notes.

Asks a person when

The change touches allocation, measurement, regulatory reporting, permit logic or authentication, or breaks a contract.

ApproverBack-End Tech Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Breaking changesnew_version_requiredHow breaking API changes ship.
p95 latency budget (ms)300Per endpoint.
Smallest coverage (%)80For changed code.
Allocation changes need a reconciliation testOnAny change to allocation or measurement logic must reproduce last month's allocated volumes.
Auth changes need securityOnAuthentication and authorisation changes go to security review.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Keep published contracts backward compatible under new_version_required.
  • Write schema changes as reversible migrations and meet 80 percent coverage.
  • When on is on, prove an allocation or measurement change reproduces the last closed month's allocated volumes exactly before review.
  • Send authentication changes to security when on is on.
  • Hold the p95 within 300 ms; the service never connects to, writes to or tests against the control network (DCS, SCADA, safety instrumented systems or PLCs).

See the Back-End Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Back-End Agent · Oil & Gas | Basinwright Industries