# Nimrod QRSPI Artifact Template

Use this template by copying the relevant phase sections into files under:

```text
tickets/artifacts/<ticket-id>/
```

## 00-context.md

```markdown
# Context: <title>

## Source Ticket

- `tickets/active/<ticket-id>.md`

## Goal

## Why

## Scope

Included:
- 

Not included:
- 

## Constraints

## Acceptance Criteria

## Notes
```

## 01-questions.md

```markdown
# Research Questions: <title>

## Phase Contract

Allowed reads:
- `tickets/active/<ticket-id>.md`
- `tickets/artifacts/<ticket-id>/00-context.md` if present

Will write:
- `tickets/artifacts/<ticket-id>/01-questions.md`

## Context for Research

Neutral description of the area to investigate. Do not include the intended solution if it would bias research.

## Questions

1. 
2. 
3. 

## Approval Notes

- 
```

## 02-research.md

```markdown
# Research Findings: <title>

## Phase Contract

Allowed reads:
- `tickets/artifacts/<ticket-id>/01-questions.md`
- files/systems/sources needed to answer those questions

Do not read:
- design or plan artifacts

Will write:
- `tickets/artifacts/<ticket-id>/02-research.md`

## Q1: <question>

### Findings

- 

## Q2: <question>

### Findings

- 

## Cross-Cutting Observations

- 

## Open Areas

- 
```

## 03-design.md

```markdown
# Design: <title>

## Phase Contract

Allowed reads:
- `tickets/active/<ticket-id>.md`
- `tickets/artifacts/<ticket-id>/00-context.md` if present
- `tickets/artifacts/<ticket-id>/01-questions.md`
- `tickets/artifacts/<ticket-id>/02-research.md`

Will write:
- `tickets/artifacts/<ticket-id>/03-design.md`

## User Judgment Questions

1. 
2. 
3. 

## Current State

## Desired End State

## Patterns / Constraints to Follow

## Design Decisions

1. **Decision**: choice — reason

## Not Doing

- 

## Risks

- 

## Acceptance Criteria

- 
```

## 04-structure.md

```markdown
# Structure: <title>

## Phase Contract

Allowed reads:
- `tickets/artifacts/<ticket-id>/02-research.md`
- `tickets/artifacts/<ticket-id>/03-design.md`

Will write:
- `tickets/artifacts/<ticket-id>/04-structure.md`

## Approach

## Phase 1: <vertical slice>

What this phase delivers end-to-end.

**Files:**
- 

**Key changes:**
- 

**Verify:**
- Automated: 
- Manual: 

## Phase 2: <vertical slice>

## Testing Checkpoints

- After Phase 1: 
- After Phase 2: 
```

## 05-plan.md

```markdown
# Implementation Plan: <title>

## Phase Contract

Allowed reads:
- `tickets/artifacts/<ticket-id>/02-research.md`
- `tickets/artifacts/<ticket-id>/03-design.md`
- `tickets/artifacts/<ticket-id>/04-structure.md`

Will write:
- `tickets/artifacts/<ticket-id>/05-plan.md`

## Overview

## Phase 1: <name>

### Changes

#### 1. <file/component>

**File:** `<path>`
**Action:** create / modify / delete

Details:
- 

### Verification

Automated:
- [ ] 

Manual:
- [ ] 

### Rollback

- 

## Phase 2: <name>

```

## 06-review.md

```markdown
# Review / Closeout: <title>

## Phase Contract

Allowed reads:
- `tickets/artifacts/<ticket-id>/03-design.md`
- `tickets/artifacts/<ticket-id>/05-plan.md`
- git diff / verification outputs

Will write:
- `tickets/artifacts/<ticket-id>/06-review.md`

## Summary

## Changes Made

## Verification

Automated:
- 

Manual:
- 

## Decisions / Deviations

## Risks / Follow-ups

## Rollback Notes

## Links

- Ticket: `tickets/active/<ticket-id>.md`
```