1 min lesson
The written artifact
Walk through each part of "The written artifact", then explain what each one does.
Step 1 of 2
The written artifact
Reviews that live only in a meeting evaporate. Produce a short recommendation document stakeholders can forward to their CISOChief Information Security Officer. The executive who owns security; usually the hardest and most important person to win over. Press Enter for the full definition. and CTO. It does not need to be long - it needs to be defensible.
- Current state
- One diagram-as-table of their SDLC/identity/network/CI today
- Requirements
- The constraints captured, in their words
- Target architecture
- The concrete Cursor configuration you recommend
- Risk register
- Each risk with owner and mitigation
- Phasing
- What ships now vs. what's deferred, with why
Do not present the ideal architecture as the only architecture. An org that cannot adopt PrivateLinkAn AWS connection Cursor uses for private Git provider and repository-origin traffic; it does not cover model-provider traffic. Press Enter for the full definition. this quarter still needs a safe path. Balance the target against what they can actually run now and phase the rest.
An unadoptable recommendation is a failed review, however elegant.
In the demo or scenario round, if asked to “walk us through how you'd run an architecture review,” lead with the structure (current state → constraints → integration → risk → target) and name the written artifact at the end. Ending on a circulatable document signals you understand the review is a means to an internal decision, not a meeting for its own sake.