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 / Weave Field / alternate

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

Follow a strand to see what it touches, or pull a knot forward to reveal dependent commitments.

flow recoveringcurrent read
26active items
Dependency reasoning, agent-human handoffs, shared ownership, and seeing where one change tugs the system.why this view exists
26active items
blocked by schemaNormalize lacrosse alert payload

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

needs ownerPrototype critique capture

Turn review observations into decisions, not loose notes.

safeArchive stale field

Retire one unused ticket field after migration check.