Solution One-Pager
A solution summary for people who will not read the HLD.
- Format.md
- Length58 lines
- Includesnone
The source
58 lines of Markdown, with nothing to install. Copy it, or open the template inside Gnomon and render it as it is.
# <Solution name>
> The thing you actually send upward. One page. No more.
## Executive Summary
3–4 sentences. The problem, what we want to do, what it costs, when it lands.
If the reader stops here they should know enough to say yes, no, or "tell me more".
## Problem
What's broken or missing today, and what it costs us to leave it that way.
Numbers if you have them; concrete user pain if you don't.
## Approach
The proposed solution in plain language. One paragraph.
Link out to the [RFC](./rfc.md) / [HLD](./hld.md) for the engineering detail.
### What we will do
- …
- …
- …
### What we will not do
- …
- …
## Cost
| Category | Estimate |
|-----------------|---------------------------------------|
| Engineering | <N people × M weeks> |
| Infrastructure | $<…>/month ongoing, $<…> one-off |
| Vendor / SaaS | $<…>/year |
| Opportunity | <what we won't ship instead> |
## Timeline
| Milestone | Date |
|-----------------------------|------------|
| Decision | YYYY-MM-DD |
| Kickoff | YYYY-MM-DD |
| Internal alpha | YYYY-MM-DD |
| Limited release (10%) | YYYY-MM-DD |
| GA | YYYY-MM-DD |
## Risks
| Risk | Likelihood | Impact | Mitigation |
|--------------------------------|------------|--------|------------------------------|
| <e.g. dependency slips> | Medium | High | Parallel track on <…> |
| <e.g. adoption lower than forecast> | Low | Medium | Co-design with 2 design partners |
## Decision Requested
What you need from the reader: approval, budget, headcount, a tie-break on
option A vs B. Be explicit.Render this offline
This template ships in Gnomon and renders on your machine, with no account and nothing sent to a server. The browser editor is free and needs no install.
Others in Architecture document templates
- ADR — Architecture Decision RecordContext, decision, consequences. The alternatives section is the valuable one.
- RFC — Request for CommentsFor proposing a change and inviting disagreement before building.
- HLD — High-Level DesignHigh-level design: the shape, the constraints, the risks.
- Tech Spec / LLDLow-level design. What an implementer needs that the HLD does not say.
- NFR CatalogueThe requirements that get discovered late and expensively.
- RunbookWhat to do at 3am. Written for someone tired and unfamiliar.
- Discovery / Spike ReportFindings from a time-boxed investigation, including the dead ends.
- Post-Mortem / Incident ReviewBlameless incident review. Timeline first, conclusions second.