EidralEngineering Engine
Chapter 03

The build: agents shipped inside your stack

5 agents, built against the baselines the audit measured and the exception categories it named. Each one runs on top of the systems you already own, through service accounts scoped to the actions it is allowed to take.

Agent roster
#AgentWhat it doesHrs/weekAnnual valueRatio
01Code ContextAnswers where something lives and why it was built that way, from the repository and its history.36$158k4:1
02PR ReviewerRuns the first pass on convention, test coverage and obvious defects before a human reads it.28$142k3:1
03Ticket TriageClassifies incoming issues, links duplicates and routes to the component owner.21$86k3:1
04Onboarding GuideAnswers the questions a new engineer would otherwise interrupt someone to ask.12$62k3:1
05Incident SummariserAssembles the incident timeline from logs, deploys and the thread that ran alongside.9$42k3:1

Ratio is automated steps to human steps within that agent's flow. The 5 agents return 106 hours a week between them, which is the annual figure in chapter 02 divided across a 46-week working year.

One agent, every step

PR Reviewer

Hours returned
28/wk
Annual value
$142k
Human gates
1
  1. 01Read the diff with the surrounding module and its history
    Automated
  2. 02Check convention, naming and test coverage against the repository's own patterns
    Automated
  3. 03Flag likely defects and missing error paths with the line referenced
    Automated
  4. 04Engineer accepts or dismisses each flag
    Reviewer input

    Dismissals retune what the agent raises on this repository

  5. 05Post the review with the mechanical findings resolved
    Automated
  6. 06A human approves anything touching auth, payments or migrations
    Human gate
  7. 07Link the merged change to its ticket and update the component owner map
    Automated

The gate is a step, not a promise made in prose. Where a correction appears it is marked, because the correction persisting as training signal is the difference between an agent that improves and one that repeats itself.

Operating complexity

7 steps → 2 touchpoints

What took 7 manual steps now needs a person at 2 of them.

Handoffs

3 → 1 queue

3 handoffs between people and systems collapse into one queue with the evidence already attached.

Modelled annual value, all agents
$490k
  • Cost reduction$310k63%
  • Revenue growth$96k20%
  • Risk mitigation$84k17%

The agent roster above sums to the same total: $490k across 5 agents. Cost reduction is hours at a fully loaded rate, discounted 25% for ramp.

Illustrative

These agents are specified, not running. The software is built for the client who commissions it, after their audit has named the thresholds and the exception categories it has to work against. What is fixed is the pattern: 1 human gate in this flow, every action logged with its inputs and its approver.