Restructure .lattice/requirements per new lattice standard

[techygarg]

Summary

• Reorganizes .lattice/requirements/ to match the updated lattice requirement standard
• Adds epic docs (differentiators, platform-play, reduce-team-friction, remove-the-capability-ceiling, expand-the-use-case-surface)
• Updates feature docs and index to reflect new structure

Test plan

• Review restructured requirement docs for accuracy

[qodo-code-review]

PR Summary by Qodo

Restructure .lattice requirements into epic-based standard

📝 Documentation 🕐 20-40 Minutes

AI Description

• Add epic index pages under .lattice/requirements/epics/ with generated feature tables.
• Reassign feature frontmatter + links to the correct epic pages.
• Replace the old tier roadmap in index.md with the new requirements index + epic table.

Diagram

graph TD
  A["requirements/index.md"] --> B(("epics/")) --> C["epics/*.md"] --> D(("features/")) --> E["features/*.md"]
  E --> F{"Frontmatter (epic)"} --> C
  C --> G["Generated feature tables"]

  subgraph Legend
    direction LR
    _doc["Markdown doc"] ~~~ _dir(("Folder")) ~~~ _meta{"Metadata"}
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Single source-of-truth manifest (YAML/JSON) for epics + features

• ➕ Eliminates duplicated metadata across many feature files (epic names, summaries, statuses).
• ➕ Makes generation deterministic and avoids drift from inconsistent frontmatter edits.
• ➖ Introduces a new artifact and a generation workflow that must be maintained.
• ➖ Moves ownership away from the feature spec files themselves (less self-contained docs).

2. Keep tier-based `index.md` and add epics as secondary navigation

• ➕ Minimal churn for readers familiar with the old roadmap layout.
• ➕ Reduces link-update surface area across feature docs.
• ➖ Does not fully align with the new lattice epic standard.
• ➖ Encourages duplicate structures (tiers + epics) that can diverge.

Recommendation: The PR’s approach (epic pages + frontmatter-driven generated tables) is the best fit for the new lattice standard and keeps the feature specs largely self-contained. If doc drift becomes a recurring issue, consider moving to a dedicated manifest later; for now, the current structure is a good balance of clarity and maintainability.

Files changed (15) +166 / -86

Documentation (15) +166 / -86

differentiators.mdAdd Differentiators epic page with generated feature table +22/-0

Add Differentiators epic page with generated feature table

• Introduces a new epic page with frontmatter ('epic', 'status') and a generated table placeholder listing features in this epic.

.lattice/requirements/epics/differentiators.md

expand-the-use-case-surface.mdAdd Expand the Use Case Surface epic page +23/-0

Add Expand the Use Case Surface epic page

• Adds a new epic document defining the epic and a generated features table for roadmap items that broaden supported testing categories.

.lattice/requirements/epics/expand-the-use-case-surface.md

platform-play.mdAdd Platform Play epic page +23/-0

Add Platform Play epic page

• Creates the Platform Play epic page and a generated list of related cross-platform / ecosystem expansion features.

.lattice/requirements/epics/platform-play.md

reduce-team-friction.mdAdd Reduce Team Friction epic page and feature index +26/-0

Add Reduce Team Friction epic page and feature index

• Adds an epic page marked in-progress and includes a generated table referencing the set of friction-reducing features with corrected relative links.

.lattice/requirements/epics/reduce-team-friction.md

remove-the-capability-ceiling.mdAdd Remove the Capability Ceiling epic page +22/-0

Add Remove the Capability Ceiling epic page

• Adds an epic page describing the tier goal and a generated table of the core capability-unblocking features.

.lattice/requirements/epics/remove-the-capability-ceiling.md

assert-002-field-level-failure-output.mdUpdate Epic index link to new epic page path +1/-1

Update Epic index link to new epic page path

• Repoints the “Epic index” link from the old 'index.md' to the new epic-specific page under 'epics/'.

.lattice/requirements/features/assert-002-field-level-failure-output.md

dsl-002-yaml-support.mdUpdate Epic index link to Reduce Team Friction epic page +1/-1

Update Epic index link to Reduce Team Friction epic page

• Updates the “Epic index” backlink to target 'epics/reduce-team-friction.md' instead of the former shared index.

.lattice/requirements/features/dsl-002-yaml-support.md

env-001-declarative-auth-profiles.mdReassign ENV-001 epic and update epic backlink +2/-2

Reassign ENV-001 epic and update epic backlink

• Changes the feature frontmatter epic from “Environment Setup” to “Reduce Team Friction” and updates the epic index link accordingly.

.lattice/requirements/features/env-001-declarative-auth-profiles.md

env-003-modern-test-host-initialization.mdReassign ENV-003 epic and update epic backlink +2/-2

Reassign ENV-003 epic and update epic backlink

• Moves the feature’s epic classification to “Reduce Team Friction” and updates the epic index backlink to the new epic page.

.lattice/requirements/features/env-003-modern-test-host-initialization.md

env-004-declarative-suite-bootstrap.mdReassign ENV-004 epic and update epic backlink +2/-2

Reassign ENV-004 epic and update epic backlink

• Updates the feature’s epic to “Reduce Team Friction” and adjusts the epic index link to the corresponding epic file.

.lattice/requirements/features/env-004-declarative-suite-bootstrap.md

env-005-app-launcher.mdReassign ENV-005 epic and update epic backlink +2/-2

Reassign ENV-005 epic and update epic backlink

• Changes the frontmatter epic to “Reduce Team Friction” and repoints the epic index backlink to 'epics/reduce-team-friction.md'.

.lattice/requirements/features/env-005-app-launcher.md

extraction-and-injection.mdAdd missing frontmatter + links section; update roadmap backlink +19/-1

Add missing frontmatter + links section; update roadmap backlink

• Adds standard lattice frontmatter (feature/epic/status/priority/personas) to the top of the doc, changes the “Back to Roadmap” link to '../index.md', and appends a Links section including design + epic index references.

.lattice/requirements/features/extraction-and-injection.md

flow-002-test-dependency-graph.mdUpdate Epic index link to Reduce Team Friction epic page +1/-1

Update Epic index link to Reduce Team Friction epic page

• Replaces the old epic index reference with a direct link to 'epics/reduce-team-friction.md'.

.lattice/requirements/features/flow-002-test-dependency-graph.md

semantic-matcher-library.mdReassign Semantic Matcher Library epic and update epic backlink +2/-2

Reassign Semantic Matcher Library epic and update epic backlink

• Changes the epic from “Response Assertion” to “Remove the Capability Ceiling” and updates the “Epic index” link to the new epic page.

.lattice/requirements/features/semantic-matcher-library.md

index.mdRewrite requirements index to epic-based standard + generated epic table +18/-72

Rewrite requirements index to epic-based standard + generated epic table

• Replaces the old tiered roadmap tables with a new index format including project frontmatter, definitions, ID format, and a generated Epics table linking to the new epic pages.

.lattice/requirements/index.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 17 rules

1. Broken design doc link 🐞 Bug ⚙ Maintainability

Description

flow-002-test-dependency-graph.md links its design doc via ../../.lattice/context/..., which
resolves to a non-existent .lattice/.lattice/context/... path from within
.lattice/requirements/features/. This breaks navigation to the design spec and makes the
requirement doc harder to use/maintain.

Code

.lattice/requirements/features/flow-002-test-dependency-graph.md[107]

- Design: [flow-002-test-dependency-graph.md](../../.lattice/context/flow-002-test-dependency-graph.md)
-- Epic index: [index.md](../index.md)

Evidence

The requirements doc currently uses ../../.lattice/context/... as the link target, but the actual
design doc is located at .lattice/context/... and other requirement docs use the correct
../../context/... pattern from the same directory depth.

.lattice/requirements/features/flow-002-test-dependency-graph.md[105-108]
.lattice/context/flow-002-test-dependency-graph.md[1-5]
.lattice/requirements/features/dsl-002-yaml-support.md[143-146]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The FLOW-002 requirements doc links to its design doc using an incorrect relative path (`../../.lattice/context/...`) that effectively points to `.lattice/.lattice/context/...`.

## Issue Context
Other requirement docs in the same folder link to design docs using `../../context/...`, and the FLOW-002 design doc exists at `.lattice/context/flow-002-test-dependency-graph.md`.

## Fix Focus Areas
- .lattice/requirements/features/flow-002-test-dependency-graph.md[105-108]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Broken design doc link 🐞 Bug ⚙ Maintainability

flow-002-test-dependency-graph.md links its design doc via ../../.lattice/context/..., which
resolves to a non-existent .lattice/.lattice/context/... path from within
.lattice/requirements/features/. This breaks navigation to the design spec and makes the
requirement doc harder to use/maintain.

Agent Prompt

## Issue description
The FLOW-002 requirements doc links to its design doc using an incorrect relative path (`../../.lattice/context/...`) that effectively points to `.lattice/.lattice/context/...`.

## Issue Context
Other requirement docs in the same folder link to design docs using `../../context/...`, and the FLOW-002 design doc exists at `.lattice/context/flow-002-test-dependency-graph.md`.

## Fix Focus Areas
- .lattice/requirements/features/flow-002-test-dependency-graph.md[105-108]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools