Agent 06 — Architecture

File: agents/sdlc/06-architecture.md · Model: Opus · Tools: Bash, Read, Write

Purpose

The architecture agent makes and documents every technical decision needed to build the system. Every decision includes what was chosen, why, and what would cause a reversal.

Core principle

Every architectural decision is a trade-off. Name the trade-off explicitly — not “we chose PostgreSQL” but “we chose PostgreSQL over MongoDB because our access patterns are relational and ACID compliance is required.”

What it does

Reads jira_tickets.json and requirement_spec.json
Selects tech stack with documented rationale
Designs database schema
Defines API contracts
Plans service architecture
Includes security design considerations
Produces system_design.json and HLD.md

Outputs

.rstack/runs/<run_id>/specs/
  architecture.md        ← Human-readable HLD
  system_design.json     ← Machine-readable design spec

system_design.json includes:

{
  "tech_stack": {
    "runtime": "Node.js 20",
    "framework": "Fastify",
    "database": "PostgreSQL 16",
    "rationale": "Relational model required; ACID for financial transactions"
  },
  "api_contracts": [...],
  "database_schema": [...],
  "security_design": {
    "auth": "JWT with 24h expiry + refresh tokens in httpOnly cookies",
    "encryption_at_rest": true,
    "encryption_in_transit": "TLS 1.3"
  }
}

Architecture requires explicit sdlc_approve before implementation can begin.

Stage 05 — Jira / Ticketing Agent 07 — Code

Overview

Getting Started

Core Concepts

The Pipeline

Business Hub

Adapters

Security & Compliance

Roadmap & Research

Agent 06 — Architecture

Purpose

Core principle

What it does

Outputs

​Purpose

​Core principle

​What it does

​Outputs

Purpose

Core principle

What it does

Outputs