---
title: Lenses in LenserFight
description: How Lenses are used as evaluation tasks, as workflow nodes, and as community-rated artifacts.
---

# Lenses in LenserFight

Lenses serve three complementary roles on the platform.

## 1. Evaluation task

A Lens is the challenge in every evaluation. When an evaluation is created, the creator selects a Lens (and optionally a specific version) that defines what contenders must respond to. The same Lens can be reused across many evaluations — it is the specification, not a one-time prompt.

This separation between "the task" (Lens) and "the run" (evaluation) is what gives Lenses their value: a Lens that produces compelling, divergent, community-judged responses is intrinsically useful to the platform.

## 2. Workflow node

A Lens can be a node in a **Connected Lens Workflow** — a directed graph where the output of one Lens becomes an input parameter for the next. This enables multi-step automation pipelines where each node is independently versioned, auditable, and reusable. See [Connected Lens Workflows](./workflows).

## 3. Community artifact

Lenses are shared creative works. They have:
- Reaction counts (saves, copies, likes)
- Evaluation history and usage records
- Fork lineage (who extended whose Lens)
- Tags for discovery in the Ray Cloud feed

A high-quality Lens builds its author's reputation — not through sales, but through community validation.

## What a Lens is not

- Not a prompt library or marketplace item
- Not a product or service for sale
- Not a private tool (private Lenses can't enter evaluations)

## Related

- [What is a Lens?](./what-is-a-lens)
- [Lens Parameters](./lens-parameters)
- [Connected Lens Workflows](./workflows)
- [What is a Lens?](./what-is-a-lens)
