Back-End Engineering

TechnologyPhase 1

Lead: Back-End Orchestrator Agent

api-gatewayArbitrium: In Progress

4 agents4 planned

Linear: HB-BACK

13 permissions (0 write)Prompt Chaining+ Evaluator-Optimizer

Architecture Pattern

API changes follow a strict chain: schema design → implementation → testing → deployment. Database migrations use evaluator-optimizer to validate before applying.

Evaluation

3 metrics defined

Error Handling

3 scenarios covered

Self-Improvement

2 human checkpoints

Phase 1: Foundation

Foundation. Back-end services and APIs underpin every other agent's ability to read/write data.

Tools

Back Office APILinear

Goals

Build and maintain APIs and servicesEnsure reliability

Agent Sizing Rationale

5 agents: 1 orchestrator + 3 service specialists (odd for architecture voting) + 1 data. Critical architecture decisions use 3-agent consensus.

Services (3-agent architecture panel)

AgentDescriptionComplexityRolesStatusActions

API & Microservices AgentDesigns and builds REST/GraphQL APIs, manages service boundaries and contracts.medium

generator

Auth & Security AgentManages authentication, authorization, session management, and API security.medium

guardian

Infrastructure & Messaging AgentManages message queues, caching layers, and service-to-service communication.medium

communicator

Data & Orchestration

AgentDescriptionComplexityRolesStatusActions

Database & Data AgentDesigns schemas, writes migrations, optimizes queries, and manages data integrity.medium

generator

Agents Used From Other Departments

These agents from other departments feed data into or are called by this department's agents.

Front-End EngineeringExternal

Front-End Orchestrator Agent

Front-end requirements define API contracts and data shapes.

DevOps & InfrastructureExternal

CI/CD Pipeline AgentInfrastructure Agent

DevOps deploys and scales back-end services.

SecurityExternal

Application Security Agent

Security agents audit back-end code for vulnerabilities.