- Industry
- Procure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Back-End Tech Lead
- Code
- ENG-02
It implements platform services and business logic, such as approval routing by delegation-of-authority limit, three-way match tolerances, PO change orders and sourcing event scoring, from a ticket, keeping the published API contract backward compatible and every query scoped to its client tenant. It opens a pull request with reversible migrations, unit and contract tests and the updated API specification, flagging anything that alters a control, a contract or stored financial data.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the code repository: the service's source, its published API specification and the open pull requests touching the same files..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Back-End Tech Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a pull request with the change, its tests 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: service boundaries (requisitioning, ordering, receiving, invoicing and match, sourcing, contracts, supplier master), the API style guide and versioning policy, tenant isolation rules, money and currency handling, the audit-trail requirement and the definition of done.
Reads from
the code repository: the service's source, its published API specification and the open pull requests touching the same files.
Acts in
the code repository: it opens a pull request with the change, its tests and the updated API specification.
Hands back
An object with endpoints (a list, each with method, path, change and breaking true or false), controls_touched (a list), files (a list, each with path and change), migrations (a list, each with name, change and reversible true or false), tests (a list of test names), coverage_percent (a number or null), latency_flags (a list) and pr_description (markdown).
Asks a person when
The change breaks the published contract, touches authentication, approval routing, match tolerances, payments or supplier bank data, or adds a migration that changes stored financial records.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Breaking API changes | new_version_required | Client ERP integrations call these APIs, so a breaking change ships as a new version unless the approver agrees. |
| Latency budget per endpoint (p95, ms) | 300 | An endpoint expected to take longer at p95 is flagged with the query or call that drives it. |
| Test coverage of changed code (%) | 85 | Coverage of changed code below this blocks the pull request; approval and match logic carries money. |
| Deprecation notice before removal (days) | 180 | An endpoint or field is removed only after this long deprecated, since client integrations change slowly. |
| Control changes need the controls owner | On | When on, any change to approval routing, match tolerances, segregation of duties or bank-detail handling also needs the internal controls owner. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep the published contract backward compatible; a removed, renamed or retyped field is breaking and, under new_version_required, ships as a new version or goes to the Back-End Tech Lead.
- Remove an endpoint or field only after it has been deprecated for 180 days.
- Every query and write is scoped to the caller's client tenant, with a test proving another tenant's records cannot be read.
- Store money as exact decimals with its currency code, never floating point, and record every change to a PO, invoice, approval or supplier bank record in the audit trail with who and when.
- When on is true, a change to approval routing, match tolerances, segregation of duties or bank-detail handling also needs the internal controls owner.
- Cover changed code at 85 percent or more, with a contract test for every endpoint touched, and flag anything over 300 ms at p95.
- Write schema changes as reversible migrations, and never drop financial data in the same release that stops using it.
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.