Added a Guide Page Explaining Graph View Nodes, Connection Relationships, and Playback Controls
We added a dedicated Graph View guide page explaining how Pack, Saved, and Anchor are displayed as nodes and how to use Timelapse and exploration controls.
Graph View is not a screen that lays out AI conversation originals as is. It is a projection screen for visually exploring Pack formed by context boundaries, user-selected Saved, Anchor as reference points for resuming, and movement relationships between conversations. We added a dedicated guide page so that users encountering this structure for the first time do not confuse the roles of nodes and controls.
Graph View is not a screen that evaluates thoughts but a screen where the user directly explores already recorded thinking flow.
What Changed in This Update
- Explained the roles and display differences of Pack, Saved, and Anchor respectively.
- Noted that Raw is not a direct node in Graph View and that some Raw remaining outside Pack is normal.
- Summarized that Timelapse playback, pause, and time navigation are features for examining thinking flow in chronological order.
- Stated that node selection and screen movement are projection actions and do not automatically change memory importance or state.
- Explained the structure where Handoff through Anchor can be displayed as a movement relationship with a new conversation.
How to Verify
- Open the /graph page to check the overall structure.
- Distinguish node types and follow the connection flow between Packs.
- Use Timelapse controls to check the structure at a specific point in time.
- Select needed Saved or Anchor to check detailed context or prepare for reentry.
Example in Actual Usage Flow
For example, to verify this change, the user opens the /graph page to check the overall structure. They distinguish node types and follow the connection flow between Packs. Then they use Timelapse controls to check the structure at a specific point in time. Finally, they select needed Saved or Anchor to check detailed context or prepare for reentry. In this flow, the following conditions should also be checked. Graph View does not guide the user's judgment through auto-recommendation, importance display, or automatic camera movement. Therefore, this update is not just adding one more notice item but enabling the user to check the start, result, and limitations of the feature within the same flow.
Before and After the Change
Before the change, users had to guess this feature or notice from other screens or navigate across multiple pages. After this update, we added a dedicated Graph View guide page explaining how Pack, Saved, and Anchor are displayed as nodes and how to use Timelapse and exploration controls. However, items where public notices and actual account/runtime status may differ need to be checked separately, and notice text alone should not be interpreted as expanding permissions or availability.
Scope and Things to Note
- Graph View does not guide the user's judgment through auto-recommendation, importance display, or automatic camera movement.
- Opening a screen or clicking a node alone does not create a Saved or Anchor.
- Not all Raw is made into nodes, and not all conversations are forced into Pack.
- Current visual representation and interaction stability are continually improving, but screen improvements do not change the memory Core's criteria.
Why This Change Matters in the Overall 5BY.AI Structure
The dedicated guide page fixes both feature usage and product philosophy together. The core of this update is clearly explaining the boundary between screen and memory state so that Graph View's visual convenience does not replace the user's judgment and the Core is not subordinate to the UI.
Criteria for Verifying This Update
- The public screen title, summary, and actual provided feature should describe the same content.
- Adding a new feature should not arbitrarily change existing Saved, Anchor, Handoff, and account flows.
- Conditions that are in preparation or vary by account should be marked separately without exaggerating as fully available.