lens systemOrient item -> trace flow -> inspect dependencies -> confirm promise.An item needs a shape before it needs a status: why it matters, how it flows, what it touches, and who owns it.
experimental lenses
Terrain ScanScorelineSignal WeatherObservatoryStrata CutAttention Market
Items / Scoreline / alternate

What is the shape of this work, not just its status?

Read left to right through time. Teams and agents become instruments, not swim lanes.

flow recoveringcurrent read
26active items
Planning cadence, release rhythm, reviews, ceremonies, and recurring personal work.why this view exists
nownexthandoffclose
1
blocked by schemaNormalize lacrosse alert payload

Define source, urgency, destination, and confidence fields before ingest.

2
needs ownerPrototype critique capture

Turn review observations into decisions, not loose notes.

3
safeArchive stale field

Retire one unused ticket field after migration check.