Printable Artifact Templates
Purpose
Use these compact templates during study, architecture reviews, capstones, and portfolio preparation.
ADR template
# ADR: <Decision>
## Context
What problem, constraint, user outcome, and risk led to this decision?
## Decision
What are we choosing?
## Alternatives
| Alternative | Why rejected |
|---|---|
## Tradeoffs
| Benefit | Cost |
|---|---|
## Verification
What evidence proves this decision works?
## Rollback
How do we reverse or reduce blast radius?
## Follow-up
Owner, date, and signal.
Threat model template
# Threat Model: <Surface>
## Assets
| Asset | Risk |
|---|---|
## Trust boundaries
Browser, backend, third party, storage, user input, generated content.
## Threats and controls
| Threat | Example | Control |
|---|---|---|
## Sensitive data
Where can sensitive data appear? HTML, JS, storage, logs, analytics, tools.
## Verification
Tests, manual review, policy reports, incident drill.
## Residual risk
Accepted risk, owner, expiry.
Performance budget template
# Performance Budget: <Route>
## User cohort
Device, network, geography, route, release, experiment.
## Metrics
| Signal | Target | Block launch | Owner |
|---|---:|---:|---|
## Resource budgets
| Resource | Budget | Rule |
|---|---:|---|
## Third parties
| Script | Purpose | Load strategy | Owner | Kill switch |
|---|---|---|---|---|
## Verification
RUM, lab trace, profile, before/after evidence.
GenUI registry template
# GenUI Registry Contract
## Rules
Registry-only components, schema validation, no raw HTML, accessibility props required.
## Components
| Component | Purpose | Required props | Risk class |
|---|---|---|---|
## Validation failures
| Failure | Fallback |
|---|---|
## Observability
Component type, schema version, validation result, fallback reason, correction.
Eval matrix template
# Eval Matrix: <AI Feature>
## Categories
| Category | What it catches | Release threshold |
|---|---|---|
## Fixtures
| Case | Input condition | Expected behavior |
|---|---|---|
## Release decision
What blocks release, what can canary, what needs human review?
Architecture review template
# Architecture Review: <Change>
## Summary
Decision, risk level, reviewers, packet used.
## Intake
What is changing, why, and who is affected?
## Required artifacts
| Artifact | Status | Notes |
|---|---|---|
## Decision matrix
| Concern | Assessment | Required action |
|---|---|---|
## Blocking follow-ups
| Follow-up | Owner | Due |
|---|---|---|
## Final decision
Approved, approved with conditions, canary only, or rejected.
Review prompts
- Which template should become a completed artifact for the current decision?
- Does the completed artifact name owner, expiry, and verification?
- Which sections can be removed for low-risk changes?
- Which sections are mandatory for high-risk routes?
Source lens
Use these templates with the completed examples in Part XII and the capstone solution-pack map.