---
artifact_schema_version: 1
artifact_type: implementation_summary
slice: "{{slice}}"
task: "{{task}}"
planning_depth: lightweight
workflow_provenance: "{{workflow_provenance}}"
workflow_cli_command: "{{workflow_cli_command}}"
workflow_manual_exception: "{{workflow_manual_exception}}"
execution_mode: "{{execution_mode}}"
implementation_status: pending
status: draft
upstream:
  specs:
    - id: "{{spec_id}}"
      depth: "{{spec_depth}}"
      ref: "{{spec_ref}}"
      source_type: "{{source_type}}"
  slice_overview: "{{slice_overview}}"
  task_definition: "{{task_definition}}"
---

# {{task_title}} Implementation Summary

## Summary

{{summary}}

## Changed Paths

{{changed_paths}}

## Acceptance Criteria Results

{{acceptance_criteria_results}}

## Validation Performed

{{validation_performed}}

## Validation Exceptions

{{validation_exceptions}}

Authoring guidance:
- Use this section only when planned validation could not run.
- Runtime and hybrid validation exceptions must record the planned command, blocker, substitute evidence, residual risk, and follow-up validation path.
- If there are no validation exceptions, use exactly `None.`

## Scope Classification

{{scope_classification}}

## Runtime Evidence Boundary

{{runtime_evidence_boundary}}

Authoring guidance:
- Contract summaries must not claim runtime implementation unless runtime files changed and executable evidence is recorded.
- Runtime and hybrid summaries must name non-documentation changed paths and executable validation evidence, or a structured validation exception for the validation gap only.
- Validation exceptions cannot substitute for missing runtime code changes.

## Deviations

{{deviations}}

## Risks and Follow-Ups

{{risks_and_follow_ups}}

## Open Questions

{{open_questions}}
