GraphJuly 23, 2026

How Nodes Connect in 5BY.AI Graph View: Pack, Saved, Anchor, and Handoff

To understand 5BY.AI Graph View, you first need to distinguish the roles of the elements that appear on screen.

Pack, Saved, and Anchor can all appear as nodes but do not have the same meaning. Handoff is not a node but represents movement between conversations.

Pack is a thought segment, Saved is a conversation to revisit, and Anchor is a coordinate for resuming. Handoff is the path moved from that coordinate to a new conversation.

Pack Is a Segment Where a Context Boundary Was Formed

Pack is not a folder that holds entire conversations.

It is a segment where a single problem definition and direction of thought formed during a conversation with AI. Even with the same topic, if the goal or judgment criteria change, a new Pack may be created.

Conversely, even if multiple technical terms appear, if it is the same flow solving a single problem, it can continue as one Pack.

Saved Is a User's Choice for a Specific Question and Answer

Saved is a single logical conversation pair that the user directly chose to revisit.

Saved is not limited to answers the user agreed with. Important counterarguments, risk warnings, and hypotheses to verify later can also be left as Saved.

Saved is not a sub-item of Pack or an importance badge. It is an independent user selection record.

Anchor Is a Reference Point for Continuing

Anchor is a high-density state node where you can re-confirm the goal up to that point, confirmed facts, chosen direction, conditions to maintain, and remaining problems.

Anchor is not a parent container that holds Pack and Saved. In Graph View, it exists at the same level as Pack and Saved.

The user can create an Anchor when a conversation has gotten long or when they want to move to a different AI.

Handoff Is a Movement Relationship, Not a Node

Handoff is the process of continuing context from an Anchor as the starting point to a new conversation in the same AI or a different supported AI.

Handoff itself does not become a new memory node.

The conceptual flow is as follows.

Anchor → Handoff → Start of new conversation → New Pack

Through this relationship, the user can see from which reference point they moved a conversation and what new thinking formed after the move.

Nodes Are Distinguished by Role, Not Hierarchy

If you understand it as a hierarchical structure where Anchor is above Pack and Saved is inside Pack, the role of 5BY.AI becomes blurred.

Pack is a context segment that can be formed automatically. Saved and Anchor are directly selected by the user. The three elements have different creation methods and purposes, so they are not merged into a single hierarchical structure.

Graph View shows their temporal and contextual relationships while maintaining this difference.

Raw Is Not a Direct Node

Raw is the basic conversation flow consisting of user questions and AI responses.

If every Raw is displayed as a node, short edits and repetitive explanations fill the screen. So Raw remains as the source from which Pack, Saved, and Anchor are created, and does not become a direct node in Graph View.

It is also normal for some Raw to exist outside of Pack.

A Real-World Flow

Suppose the user is reviewing the login structure of a product.

First, a Pack is formed for investigating error symptoms. An important log interpretation is left as Saved. After the cause is confirmed, the authentication principle to maintain is created as an Anchor.

Then, to delegate a security-focused review to another AI, Handoff is executed. A separate review Pack is formed in the new conversation.

In Graph View, you can see the following relationships that would not be visible from the result document alone.

From which problem did I start?
Which conversation did I choose as worth revisiting?
Where did I create a reference point?
To which conversation did I move?
How did the judgment differ after the move?

The Screen Shows Relationships But Does Not Judge

Opening Graph View does not create new Saved or Anchor. Nodes are not automatically promoted to more important thoughts because they have many connections.

Graph View's role is not to interpret the user's past thinking on their behalf but to show it so they can re-explore.

The reason for distinguishing Pack, Saved, Anchor, and Handoff is the same.

By not mixing the roles each element plays, the user can accurately distinguish past conversation records, important moments they directly selected, positions for resuming, and actual movement paths.