Structural 13
Rules over the context chain: owners, links, priorities, and lifecycle fields.
- Building on a discontinued foundationExplainer Active work still builds on an artifact above it that was abandoned, marked obsolete, or marked a duplicate.
- Stranded by a completed parent Open work sits under a parent that completed or migrated, so the artifact needs to close or move to an active parent.
- Two people working on the same thing Two in-flight artifacts under the same parent have different owners working on them at the same time.
- Lifecycle data inconsistency An artifact's status fields disagree with each other, such as a closed artifact with no closure reason or an open artifact with a closure reason.
- Duplicate singleton More than one open, unarchived artifact exists for a type that allows only one in the workspace, such as mission, vision, or strategy.
- No work addresses this yet An active persona or problem definition has no active project linked to it.
- Circular dependency A chain of depends_on links leads from an artifact back to itself, so the work has no valid order.
- In progress, but unassigned Work that is in progress or in review has no owner assigned.
- No shared top-level goal The workspace has several top-level goals or strategies with no shared parent above them, so work below them can point in competing directions.
- Not broken into tasks yet A mission, vision, strategy, goal, or domain model has children, but no projects or tickets beneath it.
- In progress with no priority set Work that is in progress or in review has no priority set, so you cannot rank it against other in-flight work.
- No owner A committed strategy or goal has no owner accountable for its outcome.
- Urgent, no owner A goal or strategy has urgent work beneath it, but no work under it has an owner assigned.