Your agents ship fast. Do they ship the right thing?

Pure rules over the graph — owners, links, priorities, lifecycle fields.

• Stale Premise

  Active work still builds on a parent that was abandoned, made obsolete, or marked a duplicate — a live effort resting on a discontinued foundation.

• Stranded By Closure

  Open work left under a parent that already finished — every parent above it closed as completed or migrated, so the item needs a close, a new home, or an explicit carry-forward.

• Coordination Collision

  Two active items under the same parent are being worked by different people at the same time, risking duplicated effort or a clash.

• Lifecycle Contradiction

  An item's status fields disagree with each other — closed with no reason, a closure reason on something still open, or a priority where one doesn't belong.

• Duplicate Singleton

  More than one live instance of something that should exist only once — like two missions, visions, or strategies — competing to be the source of truth.

• Priority Inversion

  A child item is ranked more urgent than the parent it serves — high-priority work hanging off something that's been deprioritized.

• Owner Over-Allocation

  One person owns more in-flight work than they can reasonably move at once — a context-switching and throughput risk.

• Coverage Gap

  An active persona or problem has no live project, requirement, story, or descendant execution connected through SERVES or ADDRESSES.

• Execution Context Gap

  Live stories that share a project or requirement declaration point cannot be traced to both an active persona and an active problem. The detector groups the repair at that declaration point while retaining exact per-story evidence; infrastructure-only tickets remain exempt.

• Unowned Work In Flight

  Work that is actively in progress or in review has no owner — something is moving with nobody accountable for it.

• No Prime Goal

  The workspace has several top-level objectives with no shared apex above them, so the work below them can ladder up to competing directions.

• Decomposition Gap

  A mission, vision, strategy, or goal whose entire subtree never reaches doable work — intent that was stated but never broken down.

• Priority Vacuum

  Work that's actively in flight has no priority set, so it can't be ranked against everything else competing for the same capacity.

• Missing Accountable Owner

  A committed strategy or goal has no owner — a directional commitment with nobody accountable for whether it lands.

• Resource Misallocation

  An objective carries urgent work underneath it that nobody is staffed on — a high-priority outcome that's effectively understaffed.

Time-aware: staleness, review cadence, plans frozen against churn.

• Zombie Project

  An active project whose work is all finished and that hasn't been touched in a long time — consuming attention with no live momentum.

• Review Cadence Breach

  A committed item hasn't been reviewed within the cadence expected for its type — a mental model that may have quietly gone out of date.

• Plan-of-Record Staleness

  A strategy or goal whose own description has gone stale while the work beneath it keeps changing — the plan frozen against what's actually happening.

An AI reviewer judges a pair of items — contradiction or duplication.

• Semantic Contradiction

  Two related items pull in logically opposite directions — an AI reviewer judged their intents to be in conflict, not just differently worded.

• Redundant Overlap

  Two items in different parts of the graph say nearly the same thing — the same intent stated twice, eroding a single source of truth.

• Chain Contradiction

  A child's intent opposes the parent it descends from — strategic drift along the line from objective to execution.

• Copy-Paste Cascade

  A child simply restates its parent rather than breaking it into real work — an objective copied down the chain instead of decomposed.

Embedding geometry flags alignment outliers across the graph.

• Root Alignment Outlier

  A piece of execution work sits among the least connected, by embedding similarity, to its mission-root containment ancestor. SERVES/ADDRESSES completeness is measured separately by the structural demand checks.

• Horizontal Incoherence

  An objective's children scatter in meaning rather than cohering as one decomposition — vertically aligned but pulling apart sideways.

An AI reviewer judges a single item against its surrounding context.

• Presupposed Capability

  A plan assumes a capability the workspace has no artifact for — the work presupposes something that doesn't yet exist.

• Orphaned Metric

  A goal states a measurable target that none of its work actually moves — a metric nobody is working toward.

Matches intent against indexed code symbols: unbuilt work, stale implementations, drifted docs.

• Unrealized Commitment

  A committed piece of work has no resembling code in the connected repository — the intent is stated but nothing in the codebase looks like it.

• Stale Implementation

  Work whose intent changed after the code that implements it last did — the spec moved on and the code hasn't caught up.

• Signature–Doc Drift

  A public symbol whose doc-comment no longer matches its signature — the description and the contract have drifted apart.

• Duplicate Implementation

  Two public symbols in different files are near-identical — duplicated logic or a missing shared abstraction.

A workspace-wide aggregate signal, not a single-item conflict.

• Portfolio Distribution Anomaly

  The work under a parent is lopsided along one dimension — nearly all critical, one priority flat, or one branch carrying the bulk — so that dimension stops distinguishing what actually matters.