Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Deliverable guide
System Architecture Design Document Source-Aware Guide
Defines source-aware system and solution architecture documentation, evidence handling, and action boundaries.
Read the fileOverview
System Architecture Design Document overview
Use this bundle to prepare source-aware system and solution architecture documentation analysis and a reviewable architecture design document.
Read the fileWorkflow
System Architecture Design Document source-aware triage
1. State the requested decision or artifact. 2. Inventory evidence: system purpose, scope, stakeholders, and concerns, functional and quality requirements, current and target context.
Read the fileQuality rubric
System Architecture Design Document source-awareness check
Check that responses: - answer directly using the required visible sections - name authoritative source categories and local evidence - separate verified, provided, assumed, and missing.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on System Architecture Design Document
- Teams working in Software, Information technology, Financial services
When to use it
- A System Architecture Design Document draft needs a clear purpose, audience, evidence base, structure, and approval path.
- An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.
What you need to provide
- The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
- Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.
Tasks and expected outputs
Questions it helps answer
- Prepare an architecture design document without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- architecture design document
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review System Architecture Design Document and return architecture design document with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with AWS Documentation — Architectural Decision Records / Adr Process, then confirm that the reference is current and applicable. Inspect System Architecture Design Document Source-Aware Guide before drafting.
Context path: bundles/deliverables/architecture-design-doc
What the bundle includes
Frameworks
- source-evidence matrix
- system and solution architecture documentation review matrix
- qualified-review gate
Evaluations
- System Architecture Design Document source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.
Known limitations
- Use the cited official, originator, standards, or professional sources for general system and solution architecture documentation context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for system purpose, scope, stakeholders, and concerns, functional and quality requirements, current and target context, components, dependencies, and trust boundaries, interfaces, contracts, data flows, storage, and lifecycle, capacity, availability, security, privacy, operability, cost, and constraints, and alternatives, decisions, consequences, risks, validation, ownership, and approval.
- Do not infer requirement, component behavior, interface contract, capacity, security posture, and architecture approval.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, and other sensitive data.
- Require explicit confirmation before committing architecture, interfaces, vendors, infrastructure, security controls, spend, or implementation without accountable technical and business review.
- Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to accountable reviewers.