Define the Task data model #66

New issue

Closed

opened 2026-09-07 20:37:17 +01:00 by liamjd · 0 comments

liamjd commented

2026-09-07 20:37:17 +01:00

Owner

Design:

Abstract Task extends Entity (RefCounted), with @abstract hooks the way Entity itself is declared
Fields: id (manager-assigned, never reused), priority (int, higher first), created_seq (creation order), status, parent, children, target_cell: Vector2i (where a pawn must stand to work it), required_role (for specialisation, see the later issue), assignee (pawn id or -1), work_remaining
Status enum: PENDING, CLAIMED, IN_PROGRESS, BLOCKED, COMPLETE, CANCELLED
Abstract hooks: can_start(ctx) -> bool (resources, reachability), work(ctx, ticks) -> void, on_complete(ctx), on_cancel(ctx)
ctx is a small context object handing the task what it may touch (Buildings registry, later resources) rather than tasks reaching for autoloads

AC:

Task cannot be instantiated directly; a stub subclass in the test suite can
Status transitions are validated (e.g. COMPLETE cannot go back to PENDING) and an invalid transition pushes an error
Unit tests for the transition table using a stub task

Adding a new task type must require only a new subclass, no changes to the manager.

Part of milestone #5. The generic base that every task type extends. Pure data plus abstract hooks, so it is headless-testable and serialisable, following the same record-is-the-truth pattern as `Building`. Design: - Abstract `Task extends Entity` (RefCounted), with `@abstract` hooks the way `Entity` itself is declared - Fields: `id` (manager-assigned, never reused), `priority` (int, higher first), `created_seq` (creation order), `status`, `parent`, `children`, `target_cell: Vector2i` (where a pawn must stand to work it), `required_role` (for specialisation, see the later issue), `assignee` (pawn id or -1), `work_remaining` - `Status` enum: PENDING, CLAIMED, IN_PROGRESS, BLOCKED, COMPLETE, CANCELLED - Abstract hooks: `can_start(ctx) -> bool` (resources, reachability), `work(ctx, ticks) -> void`, `on_complete(ctx)`, `on_cancel(ctx)` - `ctx` is a small context object handing the task what it may touch (Buildings registry, later resources) rather than tasks reaching for autoloads AC: - Task cannot be instantiated directly; a stub subclass in the test suite can - Status transitions are validated (e.g. COMPLETE cannot go back to PENDING) and an invalid transition pushes an error - Unit tests for the transition table using a stub task Adding a new task type must require only a new subclass, no changes to the manager.

liamjd added this to the Task management for pawns milestone

2026-09-07 20:37:17 +01:00

liamjd added the

enhancement

label

2026-09-07 20:37:17 +01:00

liamjd referenced this issue

2026-09-07 20:37:18 +01:00

TaskManager: queue, cancel, and next_for(pawn) selection #67

liamjd referenced this issue

2026-09-07 20:37:19 +01:00

Parent and child tasks: blocking and cascading cancel #68