---
prompt_version: 1
layer: reconciliation
action: recertify
---

# Prompt: Recertify Reconciliation Artifact

Review the selected reconciliation artifact against its parent milestone or task exception context, current repository behavior, implementation summaries, validation evidence, accepted residual work, and follow-up planning state. Decide whether the reconciliation remains accurate as-is, needs correction, should be split or collapsed, should be marked superseded, or should reopen follow-up planning recommendations.

## 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 reconciliation may have become stale because additional implementation landed, accepted residual work changed, follow-up work was completed elsewhere, validation results changed, or parent planning state no longer matches the reconciliation record.
- Treat recertification as reconciliation-evidence lifecycle hygiene, not as authorization to create follow-up planning artifacts, reopen implementation, or rewrite parent planning status.
- Compare the reconciliation artifact against current repository evidence before deciding disposition:
  - parent milestone or task exception context
  - task definitions and implementation summaries in scope
  - current code behavior, tests, validation output, and changed files
  - accepted residual work, discovered work, backlog work, and follow-up task references
  - current workflow, prompt, template, and command guidance
- Separate stale wording from stale reconciliation direction. A reconciliation artifact can need correction even when the milestone or task outcome remains accepted.
- Do not preserve accepted residual work as still accepted if current repository evidence shows it was fixed, invalidated, or promoted into active follow-up work.
- Do not report follow-up work as newly required if it has already been completed, superseded, or captured elsewhere.
- If related reconciliation artifacts duplicate or fragment one closeout decision, recommend collapse or split cleanup and identify affected artifacts.
- If reconciliation evidence was replaced by newer closeout direction, recommend supersession while preserving historical traceability.
- Identify required metadata, status, residual-work, follow-up-reference, validation-evidence, and parent-traceability cleanup if update, collapse, split, or supersession is recommended.
- Preserve historical traceability where useful, but keep active follow-up and residual-work records 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 follow-up artifact creation or implementation. Stop after reconciliation-evidence hygiene recommendations unless the user explicitly asks for those writes.

## Disposition Options

Use one of these dispositions for each reviewed reconciliation artifact:

- `accurate`: the reconciliation remains current, accurate, and traceable to parent planning and implementation evidence.
- `correct-reconciliation`: the outcome remains valid, but wording, metadata, validation evidence, residual-work classification, or follow-up references are stale.
- `collapse`: related reconciliation artifacts should be merged into one accurate closeout or exception record.
- `split`: the artifact combines distinct closeout or follow-up concerns that should be separated for traceability.
- `needs-revalidation`: recorded validation, acceptance, or residual-work evidence is missing, stale, or contradicted by current repository evidence.
- `superseded`: newer reconciliation or implementation evidence replaces this artifact, but it should remain available for historical traceability.
- `follow-up-ready`: the reconciliation accurately identifies follow-up work that can proceed only through a separate explicit planning lifecycle action.

## Required Output

Return findings grouped as:

- Recertification Scope
- Current Evidence Reviewed
- Disposition By Reconciliation Artifact
- Accepted Evidence To Preserve
- Stale Or Contradicted Evidence To Correct
- Residual Work And Follow-Up Classification
- Validation Evidence Needed
- Collapse Or Split Recommendations
- Metadata And Traceability Updates Needed
- Parent Planning Updates Needed
- User Decisions Needed

For each disposition, state:

- the reconciliation artifact path
- the parent milestone or task path
- the recommended disposition
- why that disposition follows from current evidence
- whether file edits are needed
- whether parent planning, follow-up references, or validation evidence must change
