Define the standards and framework alignment pass in the Implement stage

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

src/docs/Ways-of-Working/Workflow-Stages/Implement.md

@@ -47,7 +47,28 @@ When the plan is wrong, stop and document the conflict in a comment, then update
 1. Run the [Copilot review loop](../Contribution-Workflow.md#the-copilot-review-loop) until it reports a clean round.
 2. Triage each thread and CI failure per [Review Etiquette](../Review-Etiquette.md): fix in scope and propagate the same fix elsewhere; file a follow-up for out-of-scope; reply, then resolve.
 
-### 5. Finalize and hand off
+### 5. Standards and framework alignment pass
+
+Run this once per implementation session, when the change is otherwise complete and before the pull request is marked ready — not on every commit. Re-read the applicable guidance in precedence order and reconcile the whole diff against it:
+
+1. **Process** — the [Ways of Working](../index.md) pages that govern this stage, including [Commit Conventions](../Commit-Conventions.md), [PR Format](../PR-Format.md), and [Branching and Merging](../Branching-and-Merging.md).
+2. **Standards** — the [Coding Standards](../../Coding-Standards/index.md) chapters that apply to the languages and file types actually changed.
+3. **Framework and domain documentation** — the documentation the repository's framework or product owns, such as the module-framework documentation for a module repository or the action contract for an action repository.
+
+Process defines the method; standards and framework documentation define correctness details. Where the layers overlap, the narrower layer supplies the detail and the broader layer supplies the method — a framework page never overrides a process rule it does not own. Read the canonical pages instead of recalling them; that is what keeps guidance written once and referenced everywhere.
+
+Record the outcome as one row per changed surface:
+
+| Changed surface | Standards checked | Framework docs checked | Result |
+| --- | --- | --- | --- |
+| `src/functions/**` (PowerShell) | Naming, Functions, Error Handling | Module source layout | Aligned |
+| `.github/workflows/**` | GitHub Actions | Reusable workflow contract | Exception — Owner/Repo#123 |
+
+A result is `Aligned`, `Fixed in this PR`, or `Exception` with a link that justifies it. Carry the table into the pull request's Technical details block per [PR Format](../PR-Format.md), so [Review](Review.md) can verify the pass instead of guessing whether it happened.
+
+**Stop rule.** Fix what is in scope for the closing Task or Bug and small enough to keep the pull request reviewable. When a finding is out of scope, systemic across the repository, or would change the shape of the pull request, file a follow-up issue through [Define](Define.md), link it in the table as an exception, and leave the change as it is. The pass improves alignment; it does not turn into a second delivery.
+
+### 6. Finalize and hand off
 
 When the change meets the [Definition of Ready for Review](../Definition-of-Ready-and-Done.md):
 
@@ -60,11 +81,13 @@ When the change meets the [Definition of Ready for Review](../Definition-of-Read
 2. Progress is visible — the delivery issue is updated as plan steps complete, not in bulk.
 3. Draft pull request from the start; stay in the issue's scope.
 4. Mark ready only when the change meets the Definition of Ready for Review — never with open plan steps.
-5. Return unplanned work to [Define](Define.md) and hand review-ready work to [Review](Review.md).
+5. Run the standards and framework alignment pass once at session end, before marking the pull request ready, and record its result in the pull request.
+6. Return unplanned work to [Define](Define.md) and hand review-ready work to [Review](Review.md).
 
 ## Where this connects
 
 - [Contribution Workflow](../Contribution-Workflow.md) — the draft-first loop this runs.
+- [Coding Standards](../../Coding-Standards/index.md) — the standards layer the alignment pass reconciles against.
 - [Issue Lifecycle](../Issues/Process/Lifecycle.md) and [Issue Relationships](../Issues/Process/Relationships.md) — delivery-leaf eligibility and blockers.
 - [Definition of Ready and Done](../Definition-of-Ready-and-Done.md) — the gate this hands off at.
 - [PR Format](../PR-Format.md) and [Branching and Merging](../Branching-and-Merging.md) — packaging and landing.