diff --git a/Codex Documentation/Current Software Plan/Task Pushing 01 - Past Task Push Controls/TASK_PUSHING_01_BLOCK_01_SCOPE_AND_DOMAIN_SEMANTICS.md b/Codex Documentation/Current Software Plan/Task Pushing 01 - Past Task Push Controls/TASK_PUSHING_01_BLOCK_01_SCOPE_AND_DOMAIN_SEMANTICS.md
index 4e5e24e..9501512 100644
--- a/Codex Documentation/Current Software Plan/Task Pushing 01 - Past Task Push Controls/TASK_PUSHING_01_BLOCK_01_SCOPE_AND_DOMAIN_SEMANTICS.md	
+++ b/Codex Documentation/Current Software Plan/Task Pushing 01 - Past Task Push Controls/TASK_PUSHING_01_BLOCK_01_SCOPE_AND_DOMAIN_SEMANTICS.md	
@@ -4,7 +4,7 @@
 
 # Task Pushing 01 Block 01 — Scope and Domain Semantics
 
-**Status:** Planned.
+**Status:** Complete.
 **Goal:** Confirm the exact pushable task scope and lock destination semantics
 before adding visible controls.
 
@@ -15,6 +15,21 @@ before adding visible controls.
 After this block, the implementation should know which cards can show `Push`,
 what `past` means, and what each destination must do.
 
+## Implementation notes
+
+1. Task Pushing 01 keeps V1 support limited to planned flexible tasks. Required,
+   locked, surprise, and free-slot cards must not show the full Push button.
+2. `past incomplete` is evaluated against owner-local current time. Historical
+   selected dates can make an incomplete scheduled task pushable, but future
+   selected dates do not make tasks pushable before their scheduled end.
+3. `Push to next` targets the next valid no-overlap slot after real current
+   owner-local time. Later-today placement is preferred when a fit exists.
+4. `Push to tomorrow` targets the owner-local day after real current time, not
+   the day after the selected review date.
+5. `Push to backlog` preserves `createdAt` and resets freshness through the
+   existing `backlogEnteredAt` persistence field, promoted into domain/read
+   behavior by this plan.
+
 ---
 
 ## Chunk 1.1 — Confirm prerequisites