Technical Architecture
Create a technical architecture plan for a new or evolving system from its requirements.
Sample result
How it works
What Technical Architecture does
Ranks quality attributes with measurable targets, sizes load and storage with back-of-envelope capacity math, sets system boundaries and data ownership, maps the context, containers, and data flows for key scenarios, designs APIs and data storage by access pattern, covers infrastructure, security trust boundaries, and failure modes, and records each major choice as a decision with options, criteria, reversibility, and a build sequence that proves the riskiest assumptions first.
Use it when
Someone asks to design a system architecture, choose between a monolith and services, plan data flow and APIs, size infrastructure, or document architecture decisions and tradeoffs.
Use something else for
Splitting a finished design into tickets, assessing an existing codebase, planning a move between systems, or writing infrastructure definitions.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Architecture plan, decision records, capacity estimate and data flow diagram
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Technical Architecture
Updated Oct 20, 2026.
What does Technical Architecture do?
Create a technical architecture plan for a new or evolving system from its requirements. Ranks quality attributes with measurable targets, sizes load and storage with back-of-envelope capacity math, sets system boundaries and data ownership, maps the context, containers, and data flows for key scenarios, designs APIs and data storage by access pattern, covers infrastructure, security trust boundaries, and failure modes, and records each major choice as a decision with options, criteria, reversibility, and a build sequence that proves the riskiest assumptions first. Use when someone asks to design a system architecture, choose between a monolith and services, plan data flow and APIs, size infrastructure, or document architecture decisions and tradeoffs. Do not use for splitting a finished design into tickets (use technical-requirements-splitter), assessing an existing codebase (use codebase-audit), planning a move between systems (use migration-plan), or writing infrastructure definitions (use iac-setup).
Who is Technical Architecture for?
It is designed for software architects, engineering leads, founders, technical product managers and senior engineers.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Technical Architecture produce?
Architecture plan, decision records, capacity estimate and data flow diagram. Results come back with their sources and any open questions for you to check before anything is used.
How much does Technical Architecture cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgtacw300aa…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Technical Architecture fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.