---
oat_status: in_progress
oat_ready_for: null
oat_blockers: []
oat_last_updated: null
oat_generated: false
oat_template: true
oat_template_name: summary
oat_summary_last_task: null
oat_summary_revision_count: 0
oat_summary_includes_revisions: []
---

# Summary: {Project Name}

<!-- Section omission rule: Omit sections with no meaningful content for this project.
     Do not leave empty sections or "N/A" placeholders.
     Minimum viable summary: Overview + What Was Implemented + Key Decisions.
     Target: under 200 lines total. -->

## Overview

{2-3 sentences: what the project was and why it existed. Ground in the problem statement, not the solution.}

## What Was Implemented

{Capability-level narrative of what shipped. Ground in implementation.md outcomes, not design.md plans.
Written for a reader who hasn't seen any other project artifact.}

## Key Decisions

{Design choices with rationale. Pull from design.md decisions and implementation.md notes
where decisions were made or changed during implementation.}

## Design Deltas

<!-- Omit this section if there were no deviations from the original design. -->

{Where the final result diverged from the original design and why.
Pull from implementation.md deviations table and review-received design drift notes.
Include accepted cases where shipped implementation became source of truth and a stale lifecycle artifact needs alignment or was explicitly deferred.}

## Notable Challenges

<!-- Omit this section if nothing was harder than expected. -->

{What was harder than expected and how it was resolved.
Pull from implementation.md task notes flagged as issues/blockers.}

## Tradeoffs Made

<!-- Omit this section if no explicit tradeoffs were made. -->

{Explicit tradeoffs with reasoning. Pull from implementation.md decisions and design.md tradeoff sections.}

## Integration Notes

<!-- Omit this section unless there are things other projects/developers need to know.
     For most projects, integration notes fold into What Was Implemented. -->

{Things other projects, developers, or agents need to know when working in areas this project touched.}

## Revision History

<!-- Omit this section if no post-PR revisions occurred.
     Cap each entry at 2-3 sentences. -->

{If revisions happened post-PR, what changed and why. One entry per revision round.}

## Autonomous Execution Learnings

<!-- CONDITIONAL: Include this entire section only when the project contains
     oat-execution-learnings.md with actionable entries. Otherwise remove the
     heading, category subheadings, and placeholders. Omit empty categories.
     Each recommendation needs a one-line rationale and a relative pointer to
     every supporting source entry (timestamp, category, and title). -->

### Agent-instruction updates

{Durable skill, agent-rule, or instruction recommendations.}

### Cloud-environment improvements

{Image, setup, credentials, provisioning, or environment-readiness recommendations.}

### Code follow-ups

{Concrete product or toolkit code recommendations not completed by this project.}

### Workflow issues

{Lifecycle, gate, review, dispatch, or orchestration recommendations.}

## Follow-up Items

<!-- Omit this section if there are no deferred items or known limitations. -->

{Deferred work, known limitations, spawned backlog items with refs.
Pull from implementation.md deferred findings and plan.md deferred items.}

## Associated Issues

<!-- Omit this section if no external issues are associated.
     For most projects, this folds into Follow-up Items. -->

{Which backlog items, Linear issues, or GitHub issues this project satisfied.
Pull from state.md associated_issues field.}
