Discovery / Spike Report

Findings from a time-boxed investigation, including the dead ends.

The source

49 lines of Markdown, with nothing to install. Copy it, or open the template inside Gnomon and render it as it is.

# Spike Report: <Title>

- **Author:** <name>
- **Time-boxed to:** <N days>
- **Status:** In progress | Complete
- **Date:** YYYY-MM-DD

## Question

What are we trying to find out? State it as a question we can answer yes/no or
with a concrete recommendation.

> e.g. "Can we replace our in-house job scheduler with Temporal without exceeding
> our $X/month infra budget and with < 2 weeks of migration effort?"

## Approach

How we investigated. Keep this honest — what we did, not what an idealised plan
would have looked like.

- Read: <docs, papers, source>
- Built: <prototype, benchmark, POC>
- Measured: <what, how>
- Talked to: <teams, vendors>

## Findings

The actual data. Numbers, screenshots, links to the prototype branch.

- Finding 1: …
- Finding 2: …
- Finding 3: …

### What surprised us
- …

### What we couldn't determine
- …

## Recommendation

One of: **proceed**, **proceed with conditions**, **do not proceed**, **needs more investigation**.

Then 2–3 sentences on why, and what the next concrete step is (an RFC, a tech
spec, another spike, or shelving it).

## Appendix

Raw notes, benchmark scripts, diagrams.

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.

Get GnomonOpen the browser editor

Others in Architecture document templates