Give the frontline a progress phrase, attachments and a card worth showing

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '

src/data/demo-history.ts

@@ -210,6 +210,30 @@ const IN_PROGRESS_IN_FLIGHT: readonly string[] = [
  'Shift handover record — Line A',
 ];
 
+/**
+ * The progress phrase each in-flight owner has reported (#108).
+ *
+ * The "最新进展" column and the board card face are the point of that card, and
+ * a column that is empty on every row demonstrates nothing — so the in-flight
+ * population carries phrases, spread deterministically by position the same
+ * way every other variation in this fixture is.
+ *
+ * Two populations are deliberately left BLANK, and each blank says something:
+ *
+ * - **Stalled rows.** "Untouched since dispatch" and "the owner reported
+ * progress" are contradictory claims about the same row. A phrase here
+ * would undercut the one lens the product says is its most valuable.
+ * - **Done rows.** A completed task's report IS its status. Stamping
+ * `on_time` on 151 finished rows would also put a self-reported phrase
+ * beside `completed_late: true` wherever the drift ran over — a screen
+ * disagreeing with itself, and an invitation to read the phrase as the
+ * on-time verdict, which `task.object.ts` says in as many words it is not.
+ */
+const IN_FLIGHT_PROGRESS = ['in_hand', 'distributed', 'awaiting_feedback'] as const;
+
+/** What a late task that IS being chased says about itself. */
+const CHASED_PROGRESS = 'awaiting_feedback' as const;
+
 /** Notes, so a record detail view is not a wall of empty fields. */
 const NOTES: Readonly<Record<string, string>> = {
  'Emissions return — Northgate': 'Meter 3 was swapped mid-period — figures split across the two serials, both attached.',
@@ -236,6 +260,8 @@ export interface SeededTask extends Omit<TaskDraft, 'status'> {
  */
  skip_reason?: string;
  note?: string;
+ /** A preset phrase the owner picked (#108) — absent on stalled and done rows. */
+ progress?: (typeof IN_FLIGHT_PROGRESS)[number] | typeof CHASED_PROGRESS | 'on_time';
  /** Written by a SECOND seed pass — an insert can never carry it. See `task.seed.ts`. */
  last_update_at: string;
 }
@@ -322,6 +348,9 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  draft.duty === STALLED_LATE
  ? untouchedSinceDispatch
  : iso(new Date(NOW.getTime() - CHASED_DAYS_AGO[index % CHASED_DAYS_AGO.length]! * DAY)),
+ // The three that are being chased say so; the stalled one says nothing,
+ // which is the whole difference between the Late and Not-moving lenses.
+ ...(draft.duty === STALLED_LATE ? {} : { progress: CHASED_PROGRESS }),
  });
  }
  if (isMostRecentPast && draft.duty === SKIPPED_MOST_RECENT) {
@@ -362,6 +391,8 @@ const resolveDraft = (draft: TaskDraft, index: number): SeededTask => {
  ...draft,
  status: isInFlightHead && IN_PROGRESS_IN_FLIGHT.includes(draft.duty) ? 'in_progress' : 'open',
  last_update_at: stalled ? untouchedSinceDispatch : iso(new Date(NOW.getTime() - touchedDaysAgo(draft, dispatched, index) * DAY)),
+ // A stalled row has had nothing said about it — see IN_FLIGHT_PROGRESS.
+ ...(stalled ? {} : { progress: IN_FLIGHT_PROGRESS[index % IN_FLIGHT_PROGRESS.length]! }),
  });
 };
 

src/data/task.seed.ts

@@ -104,6 +104,12 @@ export const taskHistorySeed = defineSeed(Task, {
  // conclusion, which is the only way the demo and a live completion cannot
  // disagree.
  skip_reason: task.skip_reason,
+ // The preset phrase its owner reported (#108). Absent on the stalled and
+ // the done rows by design — `demo-history.ts` says why each blank is a
+ // blank. Carried on THIS pass and never on pass 3: `progress` is in the
+ // hook's `last_update_at` field list, so writing it in the backdating pass
+ // would re-stamp the clock that pass exists to set.
+ progress: task.progress,
  note: task.note,
  })),
 });
@@ -131,8 +137,8 @@ export const taskAdHocSeed = defineSeed(Task, {
  * Pass 3 — backdate the dispatched series.
  *
  * Carries the external id (so the row can be found) and `last_update_at`, and
- * nothing else. Deliberately nothing else: adding `status`, `note` or
- * `skip_reason` here would put the hook's stamping leg back in play and
+ * nothing else. Deliberately nothing else: adding `status`, `progress`, `note`
+ * or `skip_reason` here would put the hook's stamping leg back in play and
  * overwrite the value this pass exists to set.
  */
 export const taskHistoryTouchSeed = defineSeed(Task, {

src/hooks/task.hook.ts

@@ -171,7 +171,7 @@ import type { Hook, HookContext } from '@objectstack/spec/data';
  *
  * ── The same path and `last_update_at`: write nothing, do not refuse ─────
  * The stagnation stamp is row-conditional too, in the other direction: it
- * fires when THIS row's `status`, `note` or `skip_reason` differs from THIS
+ * fires when THIS row's `status`, `progress`, `note` or `skip_reason` differs from THIS
  * row's pre-image. D3 applies unchanged — that value goes into the one shared
  * payload and is written to every matched row, so a single genuine edit inside
  * a 200-row bulk write refreshes all 200 clocks and the stalled list quietly
@@ -389,6 +389,23 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // radius; do it only for something a person changes BECAUSE they worked the
  // task.
  //
+ // `progress` (#108) is on the list for exactly that reason, and it is the
+ // clearest case of it: the column exists so that reporting progress is ONE
+ // TAP instead of a typed sentence, and the phrase a person picks is a person
+ // saying "I am on this". Leaving it off would have made the product's own
+ // headline gesture the one interaction that does not count as movement — a
+ // task nudged every week would keep drifting into "Not moving", which is the
+ // list a manager is supposed to trust. It is the same category as `note`
+ // beside it (a human sentence about the work) and NOT the category of
+ // `owner` or `due_date` (somebody administering the row).
+ //
+ // ⛔ `attachments` is deliberately NOT here, and the asymmetry is the point.
+ // A file arriving is real, but the column is optional by product invariant
+ // and nothing may make it feel otherwise; an upload that silently reset the
+ // stagnation clock would turn "attach something" into the cheapest way to
+ // look busy, which is one step from the evidence gate the invariant forbids.
+ // A person who attaches a file and means it has a phrase to pick beside it.
+ //
  // Compared against the pre-image rather than merely tested for presence: a
  // re-save carrying an unchanged `status` is not progress.
  // ── …and nothing at all on the shared-payload path ─────────────────────
@@ -407,7 +424,7 @@ const stampTaskLifecycle = (ctx: HookContext): void => {
  // in `test/bulk-stagnation-premise.test.ts`.
  if (ctx.dispatch?.mode === 'per-row') return;
 
- for (const field of ['status', 'note', 'skip_reason']) {
+ for (const field of ['status', 'progress', 'note', 'skip_reason']) {
  if (!(field in input)) continue;
  const next = input[field];
  const prior = previous[field];
@@ -428,7 +445,8 @@ export const TaskLifecycleHook: Hook = {
  description:
  'Server-owned columns on duly_task: completed_at and the completed_late verdict on the '
  + 'transition into and out of done, late_after filled at insert for the paths the '
- + 'dispatcher does not stamp, and last_update_at only when status, note or skip_reason '
+ + 'dispatcher does not stamp, and last_update_at only when status, progress, note or '
+ + 'skip_reason '
  + 'actually changed — never on an administrative write, which would reset the stagnation '
  + 'signal. Both lateness stamps are write-once: a later change to the duty\'s grace never '
  + 'moves them. On a predicate (bulk) write the row-conditional stamps are handled by '