---
title: "Vision"
description: "The long-term direction for connected, user-controlled intelligence workflows."
canonical: https://y2.dev/docs/vision/
---

# Vision

The long-term direction for connected, user-controlled intelligence workflows.

Y2's vision is a workspace that preserves useful context for decisions. Users can understand changes and act without restarting their research.

Direction, not a release promise

This page explains the design direction of Y2. For current product availability, use [Plans and limits](https://y2.dev/docs/plans) and the [Changelog](https://y2.dev/docs/changelog).

## The intelligence loop

The goal is not a larger stream of information. New evidence updates shared context. Research produces a result that readers can inspect. Operator priorities shape the next cycle.

## Design direction

### Persistent rather than one-off

A question that matters today will often matter again tomorrow. Profiles and saved workspace context should make recurring monitoring easier than restarting the same search.

### Connected rather than isolated

Reports, events, entities, sources, and investigations should reinforce one another. Readers should be able to move from a summary to the evidence, relationships, and prior context behind it.

### Human-directed agents

AI should extend an analyst's reach while preserving user control. The operator defines the goal, reviews the evidence, and decides whether to act.

### Usable wherever decisions happen

Intelligence should work in the Y2 interface and through delivery channels, APIs, and interoperable contracts. A useful result should not be trapped in one screen.

### Compounding community knowledge

Reusable profiles and shared intelligence patterns can reduce duplicated work. Community knowledge becomes more valuable when its authorship, scope, and source context remain understandable.

## What remains constant

- Operators control the topics, workspace, and delivery paths that matter to them.
- Source context and limitations remain visible enough to support independent judgment.
- Product capabilities are documented as they exist, separately from long-term direction.
- Integrations use explicit contracts so teams can build without depending on hidden behavior.

## Continue exploring

[Read the mission](https://y2.dev/docs/mission): Understand the access and decision-support problem Y2 is designed to address.

[See current capabilities](https://y2.dev/docs/plans): Compare available workspace features and enforced limits.

[Review product changes](https://y2.dev/docs/changelog): Follow shipped improvements and current release notes.
