eva/focus-flow
6
0
Fork 1
Code Issues 14 Pull requests 1 Projects Releases Packages Wiki Activity Actions 1

docs: record task pushing scope

Browse source
This commit is contained in:
Ashley Venn 2026-07-02 12:30:35 -07:00
parent e20863108e
commit d4c85494c0
1 changed files with 16 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
Codex Documentation/Current Software Plan/Task Pushing 01 - Past Task Push Controls/TASK_PUSHING_01_BLOCK_01_SCOPE_AND_DOMAIN_SEMANTICS.md
View file

@ -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