AI ENGINEERING COMMAND CENTER

Know the code.
Change it safely.

NEW · VERIFIED FIX

From production failure
to verified change.

Give Relay a signal. Its engineering agents trace the root cause, reproduce the failure, prepare the smallest safe patch and prove the result.

Evidence, not guesses.Every conclusion links back to a log, line of code, test or command result.

Investigate an incident

Paste a stack trace, log excerpt or bug report.

GPT-5.6 SOL

RepositoryProduction signal

Project overview

acme/commerce-api

Event-driven commerce platform

⑂ maindemo From cache

Engineering score

89/100

Strong foundation. Address the focused findings to improve release confidence.

Executive summary · Heuristic fallback

A clean service boundary with three concentrated risks in authentication, database access, and release confidence.

100% eligible coverage24/24 files · 6 batches · 7 excluded

6Domains mapped3Priority findings6Agents completed

Recommended next step

Harden auth and order data access

3 proposed changes · 3 test additions

System architecture

How this codebase fits together

WEWeb App

APAPI Gateway

AUAuth

OROrders

PAPayments

POPostgres

Live architecture · 6 domains

Engineering scorecard

Quality by analyzed layer

100% eligible coverage

Architecture91

Security76

critical: Token verification accepts stale keys

Reliability92

Performance86

high: Order lookup can produce N+1 queries

Test quality92

medium: Payment adapter lacks contract tests

Maintainability90

Documentation94

Dependencies93

Priority findings

What deserves attention

critical

Token verification accepts stale keys

The auth path caches signing keys without a bounded TTL.

src/auth/verify.ts

high

Order lookup can produce N+1 queries

Line items are fetched inside the order iteration.

src/orders/service.ts

medium

Payment adapter lacks contract tests

Failure and retry semantics are not covered.

src/payments/adapter.ts