---
id: STORY-TEST-V20
title: Legacy v2.0 illustrative example
epic: EPIC-TEST
sprint: Sprint-Legacy
status: Backlog
points: 3
priority: Medium
assigned_to: Test
created: 2025-11-01
format_version: "2.0"
---

# Story: Legacy v2.0 Illustrative Example

> **Reference example** for `template-version-validation.md` Worked Example 1. Pre-Provenance era story showing markdown AC, no `## Provenance`, `## Workflow Status` instead of `## Change Log`, and informal "Depends on STORY-044" prose. Expected detection: ~25 `template/*` findings.

## Description

**As a** developer,
**I want** a deliberately old-format story,
**so that** the template-upgrade validator can detect drift comprehensively.

## Acceptance Criteria

### AC1: First criterion

**Given** an input is provided,
**When** processing happens,
**Then** an output is produced.

### AC2: Second criterion

**Given** another input,
**When** other processing occurs,
**Then** other output is produced.

### AC3: Third criterion

**Given** yet another input,
**When** yet other processing occurs,
**Then** yet other output is produced.

## Workflow Status

- 2025-11-01: Created
- 2025-11-02: Reviewed
- 2025-11-03: Backlogged pending architecture

## Notes

Depends on STORY-044 informally mentioned here. This dependency is not in the frontmatter `depends_on` array because v2.0 stories did not have that field.

This file is illustrative — not part of the live story corpus. Do not run /dev against it.
