Back to Roles

Guide Origin: Official | ArcKit Version: [VERSION]

DDaT Role Family: Architecture Framework: UK Government DDaT Capability Framework

Overview

The Technical Architect translates high-level designs into implementable architecture. You own the detailed design, infrastructure patterns, and operational architecture — ensuring solutions can actually be built, deployed, and run.

Primary Commands

Command Purpose Guide
/arckit:diagram Create architecture diagrams (C4, sequence, dataflow) Guide
/arckit:hld-review Review High-Level Design against principles and requirements Guide
/arckit:dld-review Review Detailed Design for implementation readiness Guide
/arckit:devops Create DevOps strategy with CI/CD, IaC, and container orchestration Guide
/arckit:operationalize Create operational readiness pack — runbooks, DR/BCP, on-call, handover Guide

Secondary Commands

Command Your Involvement Guide
/arckit:requirements Review NFR requirements (performance, scalability, availability) Guide
/arckit:research Evaluate technology options and implementation feasibility Guide
/arckit:azure-research Deep-dive Azure infrastructure services Guide
/arckit:aws-research Deep-dive AWS infrastructure services Guide
/arckit:gcp-research Deep-dive GCP infrastructure services Guide
/arckit:adr Record infrastructure and technology decisions Guide
/arckit:servicenow Design ITSM integration (CMDB, incident, change) Guide
/arckit:mlops Design ML pipeline infrastructure (for AI projects) Guide
/arckit:finops Review cloud cost architecture Guide
/arckit:backlog Review backlog for technical feasibility and effort estimation Guide

Typical Workflow

requirements → research → cloud-research → adr → diagram →
hld-review → dld-review → devops → operationalize

Step-by-step

  1. Understand NFRs: Review performance, scalability, and availability requirements from /arckit:requirements
  2. Research options: Run /arckit:research and cloud-specific research for infrastructure choices
  3. Record decisions: Run /arckit:adr for technology stack, hosting, and infrastructure decisions
  4. Create diagrams: Run /arckit:diagram for container, deployment, and infrastructure diagrams
  5. Review HLD: Run /arckit:hld-review to validate the high-level architecture
  6. Detail the design: Author DLD, then run /arckit:dld-review for implementation readiness
  7. Design CI/CD: Run /arckit:devops for pipeline architecture, IaC, and deployment strategy
  8. Prepare operations: Run /arckit:operationalize for runbooks, DR/BCP, and handover docs

Key Artifacts You Own

  • ARC-{PID}-DIAG-{NUM}-v*.md — Architecture diagrams
  • ARC-{PID}-HLDR-v*.md — HLD review (co-owned with Solution Architect)
  • ARC-{PID}-DLDR-v*.md — DLD review
  • ARC-{PID}-DEVOPS-v*.md — DevOps strategy
  • ARC-{PID}-OPS-v*.md — Operational readiness pack