RELAY / AI AGENT OPERATIONS MANUAL DOC RLY-FM-02 · ISSUE 07 · PRODUCTION

Deployment is a recorded procedure.

Ship agents with a record you can sign.

Relay gives teams a controlled path from agent configuration to production deployment. Every evaluation, permission change, deployment action, observation, and approval becomes part of the operating record.

01 / Deployment record

REC / PRD / 2026-08-14 / 1842

Agent Research-04

Build RLY-1842

Environment PRODUCTION

State VERIFIED

Deployed 14:32

Rev 07

Operational sequence

Deployment procedure

Complete the release sequence in order. Relay records the state and local timestamp for every stage. A deployment is not signed off until all seven stages are present in the record.

Record 00 / 07 State OPEN Ref PROC-RLY-1842-A

Procedure open — validation required.

Completion record
Awaiting stage 01

Effective configuration

System specification

The running agent is described as a specification, not a set of dashboard metrics. Values shown here are the effective production configuration attached to revision 07.

Model ASTER-4.2 / REASONING CFG-01

Context 200,000 TOKENS CFG-02

Tools 12 APPROVED / 12 RESOLVED CFG-03

Memory PROJECT + RUN SCOPED CFG-04

Timeout 240 SECONDS CFG-05

Region US-CENTRAL-1 CFG-06

Version AGENT / 7.4.1 CFG-07

Operational inventory

Agent records

A structured record of currently managed agents and their latest effective revisions. States are explicit and dated so operational history does not disappear behind a generic status screen.

Agent	Rev	Task	Env	State	Updated
Research-04	07	Source synthesis and research	PROD	VERIFIED	14:32
Support-12	18	Customer issue triage	PROD	VERIFIED	13:48
Review-02	04	Policy and output review	STAGE	IN REVIEW	12:16
Catalog-09	11	Product normalization	PROD	VERIFIED	11:54
Ops-06	03	Deployment observation	PROD	ATTENTION	10:40
Draft-21	02	Document preparation	DEV	VALIDATING	09:28

Schedule / AGT-PRD-08 6 records shown / order by updated

Revision lineage

Change record

Production state is inseparable from revision history. Relay preserves what changed, the approval basis, and which revision superseded the previous operating state.

REV 05 SUPERSEDED

Tool permissions changed.

Write scope for the document connector was narrowed to the research workspace. External publishing remained disabled.

Recorded / 09:14
Approved / M. Ortiz
Ref / PERM-1178
State / superseded

REV 06 SUPERSEDED

Evaluation threshold updated.

Production acceptance threshold increased from 0.90 to 0.92 following evaluation-set revision EVAL-8921.

Recorded / 11:06
Approved / N. Chen
Ref / EVAL-8921
State / superseded

REV 07 CURRENT

Production deployment verified.

Configuration, tools, evaluation, permissions, deployment, initial observation, and operator sign-off completed for build RLY-1842.

Recorded / 14:32
Approved / N. Chen
Ref / RLY-1842
State / effective

Supporting instruction

Annotation

Supporting guidance belongs to the document, not in a floating tooltip. Reveal the annotation to attach its note directly to the operating context.

Production deployment requires a valid environment, resolved tools, approved permissions, and a recorded evaluation result.

Diagnostic procedure

Failure procedure

Failures are written as actionable operational records: observed symptom, probable cause, and the next controlled procedure.

Symptom

Tool execution unavailable.

Possible cause

Permission scope incomplete.

Procedure

01

Inspect configuration

02

Verify connector

03

Rerun validation

State / unresolved

No resolution recorded

What Relay does

Operational software for AI agents

The interface uses manual logic where that logic helps. The product itself can still be explained in ordinary language.

Deployments should leave evidence behind.

Relay is a deployment and operations platform for teams running AI agents in real environments. It brings configuration, evaluations, tool permissions, release procedures, production observation, and revision history into one controlled workflow.

Instead of reducing an agent to a green dot on a dashboard, Relay shows the operating record around it. Teams can see which configuration was evaluated, which permissions were approved, which build was deployed, what changed between revisions, and whether the release was actually verified.

That makes Relay useful after deployment too. When an agent fails, behaves differently, or needs to be changed, operators have a documented starting point rather than reconstructing the release from chat threads, logs, configuration files, and memory.

[ Run deployment procedure ] [ Review revision history ]