Agent-managed knowledge

Proposal — not built yet. This is a behavior-alignment document for Vee and Turbo. The wireframe uses fictional pages and local simulation only; it does not read or change workspace knowledge. The PRD and stories hold the full proposed scope.

This document covers the sidebar, page preview and right details panel in separate sections. The sidebar demo focuses on the shared hierarchy; the page demo below it focuses on reading, breadcrumb navigation and supporting details.

What the sidebar is for

Browse the team's knowledge in its own structure: Customers → Acme → Overview, or Operations → Expense policy. Every entry is a page. A page can hold its own note and subpages. There is no required type or separate folder concept.

The agent creates and organizes knowledge. People open pages and expand branches here; they ask for creation, corrections, moves or deletion in chat.

Try the sidebar

Hover a parent icon, click its chevron, then click its title. Try a leaf such as Overview. The two Overview pages belong to different parents and open different notes.

The controls outside the wireframe replay agent work. Create a subpage, then replay an already-approved move. They are demonstration controls, not proposed manual page actions. Reset returns the fictional example to its initial state.

A row has two jobs

Open the page: click its title. The selected row is highlighted; opening a page does not toggle its children. Long titles stay on one line, with the full title available on hover.

Browse its children: on desktop, hovering a parent's icon replaces it with a chevron. Click the chevron to expand or collapse. The note currently being read stays open. Subpages appear indented beneath the parent and can have their own subpages.

No children: keep the page icon. No chevron and no “No pages inside” expansion.

On mobile, the page icon stays before the title and a separate chevron appears after the title. Tap the title to open the page; tap the chevron to expand or collapse its children. The Mobile preview demonstrates this arrangement. Keyboard focus also exposes the desktop expansion control. Leaf pages still have no expansion action.

One hierarchy, two views

The parent note contains its subpage references. The sidebar shows those same children as a tree; it does not maintain another independently managed list.

When the agent creates a subpage, creation completes with the page, its reference in the parent note, and its sidebar entry together. No manual refresh or separate agent sidebar-update step. If the parent is collapsed, the new child is there when it is expanded.

A normal link to a page elsewhere does not create a sidebar child. In the example, Acme links to Scallops' Overview, but that Overview stays under Scallops.

Subpage and cross-page references are inline: text may appear before and after the link in the same paragraph. They do not reserve an entire line. Acme’s example shows both kinds in sentences.

In notes, a child reference has a prefix page icon. A cross-page reference has the page icon with a small arrow overlay. External links use a website favicon. Sidebar children use their page icon and indentation, not the cross-page marker.

When the agent changes organization

Create: the new child becomes available in both the parent's note and sidebar together.

Move: after user approval, the page appears under its new parent, or at top level. Its old parent loses the subpage designation; any useful reference left there is an ordinary link. The page keeps its identity, content and history. The replay illustrates the arrow-overlay change.

Delete: after confirmation, remove the page and affected subpages from the parent note and sidebar. This is soft deletion; regular users cannot open the deleted pages. Workspace admins retain inspection/recovery access. Deleted pages never become top-level pages automatically.

Ordinary note edits must not move or delete children without approval. Safe retries must not duplicate pages or report completed creation with a missing child entry. Turbo chooses how to implement the shared hierarchy and coordinated updates.

Included, optional and still to decide

Included: icons and page titles, nested subpages, independent expand/open actions, selection, and a sidebar that agrees with the parent note. Duplicate titles are allowed under different parents, but not among siblings or at the workspace top level.

Nice to have: Recent or Favorites for quick access. These would be personal shortcuts to the same pages, visually separate from the tree; they are not part of this required sidebar wireframe.

Still proposed: sibling order follows the first appearance of each subpage in the note, with repeated references shown once. The demo uses that ordering so we can inspect it. Opening a cross-page reference reveals its target in the sidebar by expanding its ancestors and highlights that exact page. For example, Acme's reference to Scallops' Overview opens and selects Scallops' Overview, even when Scallops was collapsed. Other expanded branches stay open; the target's own children are not automatically expanded. Remembering branch state across visits remains a design detail to settle.

Page preview

Open a page in the main workspace reading area. The note uses the available space with a readable text width (the wireframe caps the note at 76ch and centers it), without a surrounding content card or separate preview modal. The frame below represents the application window, not a box around the note. No expansion/fullscreen control is needed.

Read: the title leads into the Markdown note. Headings, lists, emphasis and links retain their formatting. Subpage and cross-page references stay inline with their distinct prefix icons. Opening either reference navigates to that exact page; the sidebar reveals and selects its row.

Navigate: the breadcrumb shows the page’s current ancestry. Click an ancestor to open it; the final title identifies the current page. A cross-page link uses the target’s own ancestry, not the path of the page containing the link. Moves and renames update the displayed path without changing page identity. The wireframe demonstrates Customers → Acme → Overview and a different Overview under Scallops. Every accessible ancestor is navigable.

Manage: the note is read-only in v1. Ask the agent in chat to create, update, organize, move or delete pages. No manual editor or rename controls. Page emoji editing remains optional.

Unavailable: if a page is deleted or access is withdrawn while open, stop displaying live content and offer navigation back to accessible knowledge. A missing page or failed load gets a clear unavailable/retry state; it must not show a blank page as successfully loaded. These states are requirements in the PRD, not simulated by this wireframe.

Optional ideas: page-local chat could let a person ask about or manage the current page without switching channels. Its context, conversation continuity and placement remain open; it is not a required v1 control. Image embeds remain nice to have; the baseline renders image URLs as links. The generic web icon in this demo illustrates a favicon fallback, not a new favicon requirement.

Right details panel

Supporting information lives beside the note in a drawer using the channel-details layout and interaction pattern. Open or close it with Details. Closing it gives the note more reading space; it does not change the selected page. Switching pages updates both note and details to the same target. The selected details section can remain selected while browsing.

The wireframe above includes three sections. Their grouping and labels are a layout proposal:

• Properties: built-in title, parent, stable ID, creator/editor attribution and timestamps. No custom database fields, preset type, cover or public publishing. Timestamp labels say what changed; unknown legacy attribution stays unknown. A stable page address remains available in the product; the fictional demo IDs are not real workspace URLs.
• Links: outgoing note references and incoming backlinks, kept in separate groups, using the same icon-and-title rows without timestamps, types or linking-sentence previews. Click a page title to open that target. Following a page link closes the details panel on both desktop and mobile so the target note is immediately visible. Child references retain the page icon; cross-page references retain the arrow overlay. Backlinks derive from actual note references and do not recreate retired typed relationships. Parent references count once, not once per hierarchy projection.
• History: a read-only record of changes and truthful actor attribution. Inspect a prior revision and its recorded source evidence without changing the current note. The demo shows an illustrative revision summary. Corrections and undo are requested through the agent; no manual restore control in v1.

Empty sections explain that there are no visible entries. Unavailable or restricted evidence must not leak titles, excerpts or historical content. Failed loading offers retry while preserving navigation; access and deleted-page rules apply to the drawer as well as the note.

Mobile proposal: details occupy the reading area as a full-width panel, with a clear close control returning to the note. This mirrors the channel-details mobile destination rather than squeezing a narrow drawer beside the note. Try Mobile, close details, open a page reference, and reopen details. The exact mobile transition is still open for design alignment.

Component reuse: the wireframe uses Woodstock’s Markdown renderer and the same metadata Field/PanelSection components used by its existing properties panel. The drawer composition follows ChannelDetails; its channel-specific content is not reused. The fictional navigation, references and section content are local preview code. No additional component library was needed.