Architecture review
An independent assessment of how your production software is structured, where it fails under load or organisational change, and which structural risks deserve attention before the next major initiative.
What you receive
- Executive summary (2–4 pages) suitable for non-engineering leadership
- Engineer annex with boundary diagrams, risk register ranked by likelihood and blast radius
- Evidence appendix: repo paths, sequence notes, observability screenshots where available
- 90-minute readout workshop with your architects and leads
- Four hours of office hours within 30 days for implementation questions
Explicitly excluded
- Writing production code or merging pull requests
- Penetration testing or formal compliance certification
- Unbounded systems outside the signed scope document
Who leads the work
A senior consultant from Vector Orbit with prior ownership of distributed systems in regulated or high-traffic environments. No handoff to a anonymous “review team.”
Process
Follows our standard engagement calendar: access and interviews in week one, deep repository read in week two, draft validation and readout in week three.
Preparation
Grant read-only VCS access, nominate interviewees who lived through the last two incidents, and share any architecture documents—even drafts marked obsolete.