Skip to main content

Module tasks

Module tasks 

Source
Expand description

Task records: the shape a declared piece of live work takes as it crosses crate boundaries.

Re-exports§

use std::time::SystemTime; 🔒
use serde::Deserialize; 🔒
use serde::Deserialize; 🔒
use serde::Serialize; 🔒
use serde::Serialize; 🔒
use crate::SessionSlot; 🔒

Structs§

Attestation
A lead’s record of a look approval it witnessed, written when the lead completes a look wait on the user’s behalf. Only a lead attests, and only a look: a decision is the user’s to answer.
Estimate
A duration estimate: the words a reader sees (“2h”, “1d”) and the seconds the chase compares against worked time.
Task
One piece of live work in one project.
TaskChase
One fired chase: the row it was about (absent for a seat-level rung), the rung’s own subject where a row id does not identify it, and when.
TaskId
Identifies a task within its project.
TaskLink
One reference a row carries: the epic’s spec and plan, a task’s issues and PRs, anything else.
TaskTransition
One status transition, appended to the history the board’s worked time and the retro’s metrics are computed from.
Waiting
Why a row cannot proceed. kind is absent only for a row migrated from the old blocked spelling, which the board draws as an unstated wait.

Enums§

By
Who moved a row: the seat that called, the user from the board, or the core itself (a cleared dependency, the verify gate, archiving).
ChaseRung
A chase rung that fired. Each fires once per row (or seat) per threshold; the chase log is what makes that a fact rather than a hope.
LinkKind
What a link points at. Generic to any VCS: a GitHub pull request and a GitLab merge request are both Pr.
ReservedBy
Who reserved a row’s pick. The sweep leaves a reserved pick for the user rather than dispatching it.
TaskStatus
Where a task is in its life: waiting says what it waits on, and failed and canceled are terminal without being done.
Verify
Whether a row’s completion waits on the user’s look.
WaitingKind
What a waiting row waits on. A decision routes to the user; a dependency and a resource route to the lead.