m2ux · m2ux · Jul 12, 2026 · Jul 12, 2026
diff --git a/meta/techniques/workflow-engine/generate-summary.md b/meta/techniques/workflow-engine/generate-summary.md
@@ -26,6 +26,7 @@ Completed activities, checkpoint decisions, artifacts produced
 ## Protocol
 
 1. Draw from `{execution_trace}` to compose the summary sections: workflow id and title, start/completion timestamps, activities completed, key checkpoint decisions, artifacts with paths, outcomes satisfied vs. unmet, follow-up items. Return the assembled markdown as `{completion_summary}`.
+   > Obtain the execution trace through the `inspect_session` tool — `view: activities` for completed activities, `view: checkpoints` for checkpoint decisions, `view: history` for the event trace, or `view: summary` for all of it — rather than reading `session.json` directly.
 
 ## Rules
 

diff --git a/meta/techniques/workflow-engine/verify-outcomes.md b/meta/techniques/workflow-engine/verify-outcomes.md
@@ -26,3 +26,4 @@ Array of unsatisfied outcomes
 ## Protocol
 
 1. For each entry in `{outcomes}`, evaluate satisfaction against state variables, artifact presence in `planning_folder_path`, and the completed-activities trace; collect every unmet item into `{gaps}`.
+   > Read the state variables and completed-activities trace through the `inspect_session` tool (`view: variables` and `view: activities`, or `view: summary` for both) rather than reading `session.json` directly.
diff --git a/work-package/techniques/conduct-retrospective/retrospective.md b/work-package/techniques/conduct-retrospective/retrospective.md
@@ -32,6 +32,7 @@ Workflow [retrospective](../../resources/workflow-retrospective.md#output-sectio
 ### 1. Capture History
 
 - If metadata repository exists, capture session history.
+  > Obtain session state through the `inspect_session` tool (e.g. `view: history` for the event trace, `view: summary` for the full picture) rather than reading `session.json` directly.
 
 ### 2. Conduct Retrospective
 

diff --git a/work-package/techniques/conduct-retrospective/select-next.md b/work-package/techniques/conduct-retrospective/select-next.md
@@ -25,3 +25,4 @@ The identified next work package (when applicable) together with the context pre
 
 - Identify next work package if applicable.
 - Prepare context for transition.
+  > When carried context depends on the session's own record (variables, completed activities, checkpoint decisions), read it through the `inspect_session` tool (`view: summary`, or a narrower view) rather than reading `session.json` directly.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,3 +26,4 @@ Array of unsatisfied outcomes
		## Protocol

		1. For each entry in `{outcomes}`, evaluate satisfaction against state variables, artifact presence in `planning_folder_path`, and the completed-activities trace; collect every unmet item into `{gaps}`.
		> Read the state variables and completed-activities trace through the `inspect_session` tool (`view: variables` and `view: activities`, or `view: summary` for both) rather than reading `session.json` directly.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -25,3 +25,4 @@ The identified next work package (when applicable) together with the context pre

		- Identify next work package if applicable.
		- Prepare context for transition.
		> When carried context depends on the session's own record (variables, completed activities, checkpoint decisions), read it through the `inspect_session` tool (`view: summary`, or a narrower view) rather than reading `session.json` directly.