---
prompt_version: 1
layer: implementation
action: recertify
---

# Prompt: Recertify Implementation Summary

Review the selected implementation summary against its paired task definition, current repository behavior, changed files, validation evidence, and milestone reconciliation state. Decide whether the summary remains accurate as-is, needs correction, should be collapsed with or split from related implementation evidence, should be marked superseded, or should trigger follow-up planning or reconciliation cleanup.

## Instructions

- Command placeholder: Expand `<day-shift-cli>` to the resolved session invocation. Use `day-shift` for installed/user mode after verification, and use `node dist/cli/index.js` in repository development mode when compiled `dist` output is current.
- Use this prompt when an implementation summary may have become stale because additional commits landed, validation results changed, the paired task was revised, or reconciliation evidence no longer matches the implementation record.
- Treat recertification as implementation-evidence lifecycle hygiene, not as authorization to implement new changes, create follow-up tasks, or write milestone reconciliation.
- Compare the implementation summary against current repository evidence before deciding disposition:
  - paired task definition and parent milestone evidence
  - actual changed files, current code behavior, tests, and command output
  - validation commands and recorded results
  - milestone reconciliation and task-level reconciliation exception artifacts when present
  - current workflow, prompt, template, and command guidance
- Separate stale wording from stale implementation evidence. A summary can need correction even when the implementation remains valid.
- Do not report planned or desired behavior as completed implementation unless repository evidence supports it.
- If related implementation summaries duplicate or fragment one task result, recommend collapse or split cleanup and identify the affected summaries.
- If implementation evidence was replaced by newer work, recommend supersession while preserving historical traceability.
- If the summary is accurate but identifies unresolved follow-up work, keep the follow-up as evidence and do not create downstream artifacts unless separately requested.
- Identify required metadata, task-status, validation-evidence, changed-path, reconciliation, and follow-up cleanup if update, collapse, split, or supersession is recommended.
- Preserve historical traceability where useful, but keep active closeout evidence focused on current repository state.
- Keep the review read-only unless the user explicitly asks you to apply the recertification changes.
- Recertification, second-pass review, hardening, and improvement requests do not authorize new implementation or reconciliation writes. Stop after implementation-evidence hygiene recommendations unless the user explicitly asks for those writes.

## Disposition Options

Use one of these dispositions for each reviewed implementation summary:

- `accurate`: the summary remains current, accurate, and traceable to the paired task and repository evidence.
- `correct-summary`: the implementation remains valid, but summary wording, metadata, validation evidence, changed paths, or follow-up classification is stale.
- `collapse`: related implementation summaries should be merged into one accurate evidence record.
- `split`: the summary combines distinct implementation results that should be separated for traceability.
- `needs-revalidation`: recorded validation is missing, stale, or contradicted by current repository evidence.
- `superseded`: newer implementation evidence replaces this summary, but it should remain available for historical traceability.
- `closeout-ready`: implementation evidence is accurate and ready for milestone reconciliation or closeout, subject to the existing lifecycle gate.

## Required Output

Return findings grouped as:

- Recertification Scope
- Current Evidence Reviewed
- Disposition By Implementation Summary
- Accurate Evidence To Preserve
- Stale Or Contradicted Evidence To Correct
- Validation Evidence Needed
- Collapse Or Split Recommendations
- Metadata And Traceability Updates Needed
- Reconciliation Updates Needed
- Follow-Up Work Classification
- User Decisions Needed

For each disposition, state:

- the implementation summary path
- the paired task definition path
- the recommended disposition
- why that disposition follows from current evidence
- whether file edits are needed
- whether validation, task metadata, or reconciliation evidence must change
