pub enum GoalRef {
Charter(String),
Task(String),
Setpoint(String),
}Expand description
What a piece of work serves.
Variants§
Charter(String)
A standing commitment from the charter (see crate::charter). The
id is a crate::charter::CharterLine’s own id.
Rank is the charter’s line order, and is deliberately not carried
here. Standing commitments conflict — protecting the owner against
not letting a colleague down — and value conflict is the measured cause
of goal drift, so the resolution has to be a total order rather than
weights: no quantity of a lower commitment outranks a higher one, which
is what makes “this is urgent for very many people” a non-argument.
Order in the file is that order, on TASK-AGENT-DESIGN.md R1’s rule
one noun over — priority derives from the record and is never a field
anybody maintains, because a second statement of urgency disagrees with
the first the moment either is edited.
Task(String)
A task on the GTD board, by the graph’s own uid.
Setpoint(String)
A homeostatic setpoint, by name. No store yet.
Implementations§
Trait Implementations§
impl Eq for GoalRef
Source§impl Serialize for GoalRef
Serialised as the same kind:id string the model writes, never as an
object.
impl Serialize for GoalRef
Serialised as the same kind:id string the model writes, never as an
object.
One spelling on every wire this type crosses. A derived impl would give a
stored record a second shape — {"Task": "01J8ZK"} — and then “what does a
goal reference look like” would have two answers depending on which file
you opened, which is how a reader written against one silently mis-reads
the other.