​

Folder system design

​

Prompt:

​

Response:

• Folders inside an instance
• Separate instructions / persona per folder
• Shared memory across the whole instance
• No extra whiteboard per folder (only at instance level)

​

1. Mental model: Instance → Folders → Chats

• Instance (aiConnected)
  • Has: global instructions, global tools, global memory, one whiteboard.
  • Example: “This instance is for the entire aiConnected platform.”
• Folders (sub-domains of the instance)
  • Example folders:
    • User Interface & UX
    • Hiring & Teams
    • Marketing & Positioning
    • Cognigraph Architecture
  • Each folder:
    • Has its own settings & instructions, like a mini-instance
    • Holds chats/threads
    • Does not have its own whiteboard
• Chats (threads)
  • Live inside a folder (or a “root” / uncategorized area).
  • Can also link to other chats across folders (your “linked conversations” concept).

aiConnected (instance) → “Hiring” (folder) → “Sales Team Tier Structure v2” (chat)

​

2. What a Folder Actually Is (Feature Set)

• name – e.g., “User Interface”
• description – optional, e.g., “All conversations related to chat UI, dashboard, and persona controls.”
• icon / color – for quick visual scanning in the sidebar
• Instructions / Persona profile
  • Folder-specific system prompt / rules
  • Default tone and priorities
• Default model / engine choices
  • e.g., “Use ‘UI Architect Persona’ by default in this folder”
• Default tools / integrations
  • e.g., UI folder can default to Figma / code-oriented tools
  • Hiring folder can default to HR templates, job description generator, etc.
• Access / collaborators (eventually)
  • You might want to share just the “Hiring” folder with HR staff but keep “Cognigraph” private.

​

3. Instruction & Context Inheritance (the important part)

“I can provide dedicated instructions or customizations for individual folders without tainting the information…”

​

Instruction layers

1. Global system / platform rules (safety, core behavior)
2. Instance-level instructions
   • Example: “You are working on aiConnected, an AI automation marketplace…”
3. Folder-level instructions
   • Example (UI folder):
     • “Prioritize UX clarity, React/Tailwind patterns, coherence of chat + dashboard.”
   • Example (Hiring folder):
     • “Focus on role definitions, compensation design, and scaling sales teams.”
4. Chat-level instructions
   • Example: “In this chat we are only working on the persona selection dropdown behaviors.”
5. Message-level modifiers
   • Temporary modes like: “Right now, think like a skeptical investor.”

​

How conflicts are handled

• Lower layer can extend or override higher layers on specific fields.
• Example:
  • Instance says: “Talk in warm, professional tone.”
  • Folder says: “In this folder, be more technical and concise.”
  • Result in that folder: technical + concise wins when there’s tension.

• A “Context Stack” panel showing:
  • ✅ Which instructions are active (Instance / Folder / Chat)
  • ✅ What’s being overridden (e.g., tone, priority, tools)

​

4. Memory & Retrieval Across Folders

“If I ask a question about something, it obviously can reference the other chats, not just in other folders, but just overall in the instance…”

• Organizational scope (folders)
• Cognitive scope (memory)

​

Retrieval logic

1. Prioritize:
   • Chats + artifacts in the current folder first.
2. Expand to instance:
   • If relevant info isn’t found, automatically widen to all folders within the same instance.
3. Mark the origin:
   • When citing past work, show where it came from:
     • “Found related spec in: aiConnected → Marketing → GTM Narrative v1”

• Folders don’t wall memory off.
• They just bias which memories get looked at first.

​

5. UI / UX: How This Feels in the App

​

Sidebar layout

• Top: Instance Selector
  • e.g., [aiConnected] [Cognigraph] [Oxford Pierpont Capital]
• Within the selected instance:
  aiConnected
    > Whiteboard
    > All Chats (view)
    > Folders
        - User Interface & UX
        - Hiring & Teams
        - Marketing & Sales
        - Cognigraph Architecture
    > Unsorted / Inbox
  
• Clicking a folder shows:
  • List of chats in that folder
  • A small panel summarizing folder-level instructions/persona.

​

Quick actions

• Right-click / kebab menu on a chat:
  • “Move to folder…”
  • “Link to other chat…”
  • “Add to whiteboard”
• Right-click on a folder:
  • “Edit folder settings”
  • “Duplicate folder settings to another folder”
  • “Create chat with these folder defaults”

​

Linked chats across folders

• From any chat, you can:
  • “Link existing chat…” → search any chat in the instance → link it.
• UI then surfaces:
  • “Linked: [Market Research – ICP] (Marketing folder)”
  • “Linked: [Persona State Machine Design] (Cognigraph folder)”

​

6. How Folders Interact with the Whiteboard

Folders have all instance config except the whiteboard.

​

Whiteboard filters

• origin_instance
• origin_folder
• origin_chat

• By folder:
  • Show only items from User Interface & UX
  • Show only items from Hiring & Teams
• Or mix:
  • Show all items tagged aiConnected regardless of folder.

• A single “God board” for the instance
• But with folder-aware filtering so you don’t drown in everything at once.

​

7. Real Examples Using Your aiConnected Work

​

Example Folder: User Interface & UX

• Folder instructions:
  • Focus on:
    • Interaction design, information architecture
    • React/Next.js + Tailwind + shadcn patterns
    • Keeping the Cognigraph mental model visible (instances → folders → chats → whiteboard)
  • Avoid:
    • Deep dives into sales comp models unless explicitly asked.
• Default tools:
  • Figma integration
  • Code snippets
  • Component library
• Typical chats:
  • “Design the Persona creation modal”
  • “Layout for the Conversation Reference panel”
  • “Folder sidebar interactions and animations”

​

Example Folder: Hiring & Teams

• Folder instructions:
  • Prioritize:
    • Role design, org charts, quotas, comp plans
    • Clear, policy-friendly language
  • Constraints:
    • Don’t drift into UI details; keep it people/process focused.
• Default tools:
  • Org chart generator
  • Offer letter templates
  • Commission plan calculators
• Typical chats:
  • “Tier 0–5 sales comp restructure”
  • “Onboarding flow for Tier 1 SDRs”
  • “KPIs & dashboards for VP of Sales”

​

8. Data / Architecture Sketch (for your dev brain)

• Instance
  • id
  • name
  • instructions
  • settings
• Folder
  • id
  • instance_id (FK)
  • name
  • description
  • instructions
  • settings (default model, default tools, etc.)
• Chat
  • id
  • instance_id (FK)
  • folder_id (FK, nullable for “Unsorted”)
  • title
  • custom_instructions (optional)
• ChatLink
  • id
  • chat_id
  • linked_chat_id
  • relationship_type (e.g., “continued-from”, “related-to”)

• Index all chats/messages at the instance level in Cognigraph / your vector store.
• Use folder_id as a boosting factor when scoring relevance.

• When answering inside a chat:
  • Load:
    • instance.instructions
    • folder.instructions (if any)
    • chat.custom_instructions (if any)
  • Merge them in the defined precedence order and send that as the system context.

​

9. What You Get Out of This

• You keep one unified cognition for aiConnected.
• You gain clean separation of concerns by domain (UI vs Hiring vs Marketing vs Cognigraph).
• You can tune the AI’s behavior per folder without polluting the rest of the instance.
• You maintain navigational sanity as projects get huge.
• You can still cross-reference anything, because memory is instance-wide.

• The exact folder settings UI (fields, toggles, and layout), or
• The instruction precedence spec written like an internal dev doc so your team can implement it 1:1.

​

Prompt:

​

Response:

​

1. Core Rule: Folders Are Optional

• You can have:
  • Only chats (no folders at all)
  • Only folders (every chat lives in some folder)
  • A mix (some chats in folders, some “loose” at the root)

​

2. Root-Level Chats (“No Folder”)

• Every chat has an optional folder_id.
  • If folder_id = null → that chat lives at the root of the instance.
  • If folder_id = some_id → that chat lives inside that folder.

aiConnected
  > Whiteboard
  > All Chats
  > No Folder
      - Chat: “Brainstorm engine pricing”
      - Chat: “Random idea dump”
  > Folders
      - User Interface & UX
      - Hiring & Teams
      - Marketing & Sales
      - Cognigraph Architecture

• “No Folder” = root-level chats.
• Users never have to create a folder. They can live in “No Folder” forever if they like.

​

3. Instruction Behavior for Root vs Folder

• Root-level chats:
  • Get instance-level instructions + chat-level instructions.
  • No additional folder instructions, because they’re not in one.
• Folder chats:
  • Get instance-level instructions + folder-level instructions + chat-level instructions.

• In a folder:
  Platform → Instance → Folder → Chat
• At root:
  Platform → Instance → Chat

• You can keep some things general-purpose at the instance level.
• You can constrain and specialize behavior only inside certain folders, without affecting everything else.

​

4. Moving In and Out of Folders

​

UX

• “Move to folder…”
• “Remove from folder (send to No Folder)”

​

Behavior

• When you move a chat into a folder:
  • Future turns in that chat now inherit the folder’s instructions.
• When you move it out of a folder:
  • Future turns lose the folder’s instructions and go back to instance-only.

​

5. Creation Flow (How Users Naturally End Up Using Folders or Not)

​

New chat button

• Either:
  • Start in the currently selected folder, or
  • Choose a location from a simple dropdown:
    • “No Folder”
    • “User Interface & UX”
    • “Hiring & Teams”
    • etc.

• Everything auto-creates under “No Folder”.
• You still get a clean, simple interface like “classic chat apps.”

​

6. Search, Whiteboard, and References Respect This Flexibility

• Search / Retrieval
  • Searches still run across all chats in the instance by default.
  • You can filter by:
    • Entire instance
    • Specific folder
    • “No Folder” only
• Whiteboard
  • Still one per instance.
  • Items can come from:
    • Folder chats
    • Root chats
  • You can filter whiteboard items by:
    • Origin folder
    • Or show everything.
• Chat linking / references
  • You can link a root-level chat to a folder chat (e.g., “this loose brainstorm” ↔ “formal spec in UI folder”).
  • In the UI you’d see something like:
    • “Linked: [Initial brainstorm] (No Folder)”
    • “Linked: [UI State Machine Spec] (User Interface & UX)”

​

7. Explicit Design Principle (So Your Devs Don’t Misinterpret)

Folders are an optional organizational layer within an instance.

• Chats MAY be assigned to a folder, but are not required to be.
• Chats with no folder assignment are treated as root-level “No Folder” chats.
• All chats in an instance share the same memory space, regardless of folder, with retrieval optionally biased toward the current folder but never restricted to it.
• Folder-level instructions apply only to chats inside that folder and never to root chats.

​

Prompt:

​

Response:

​

1. Core Behavior: Multi-Select → Move → Existing or New Folder

1. Select multiple items
   • Each row (chat or file) has a checkbox.
   • You can:
     • Click individual checkboxes, or
     • Use Shift-click to select a range (desktop pattern).
2. Bulk action bar appears
   • Once at least one item is selected, a bar appears at the bottom or top:
     • Move
     • Link (for chats)
     • Delete (if supported)
     • Cancel Selection
3. Click “Move”
   • Opens a “Move items” modal:
     • Destination type:
       • Existing folder
       • New folder…
4. If “Existing folder” is chosen
   • Dropdown / list of folders:
     • “No Folder (root)”
     • “User Interface & UX”
     • “Hiring & Teams”
     • “Marketing & Sales”
     • etc.
   • Confirm → all selected items now belong to that destination folder (or root if “No Folder”).
5. If “New folder…” is chosen
   • Modal expands into “Create New Folder”:
     • Folder name
     • Optional description
     • Optional basic settings (you can keep advanced settings behind an “Advanced” toggle):
       • Default persona / instructions
       • Default model
     • [Create folder & move items] button
   • On submit:
     • New folder is created.
     • All selected items are moved into it in one operation.
     • User is optionally navigated straight into that folder to see the result.

​

2. Where This Lives in the UI

​

A. In the normal sidebar views

• Chats list view in an instance:
  • Button: Select / Manage
  • Tapping that switches the list into “selection mode”:
    • Checkboxes appear
    • Bulk action bar appears when something is selected
• Files view in an instance:
  • Same Select / Manage behavior.
  • Exactly the same move flow, but applied to files.

​

B. In a centralized “Content Manager” view (optional but powerful)

• Tabs or filters:
  • Chats
  • Files
• Filters:
  • Folder filter: All folders, specific folder, or No Folder (root).
• Multi-select with:
  • Move
  • Add to whiteboard (for chats or relevant file types)
  • Link (for chats)

​

3. Behavior Details & Edge Cases

​

Mixed folder origins

• That’s fine.
• The move operation just reassigns their folder_id to the chosen folder (or null for root).
• From the user’s POV: “Take all these scattered things and put them here.”

​

Root vs folders

• You can move:
  • From root → folder
  • From folder → root
  • From folder A → folder B
• This makes it easy to start totally unstructured, then later decide:

  “Okay, these 15 chats are all Cognigraph—group them now.”

​

Chats vs files

The user should also be able add multiple chats or files to a new folder…

• Bulk move chats in the Chat view.
• Bulk move files in the File view.

• Multi-select chats → Move to existing/new folder
• Multi-select files → Move to existing/new folder

​

Whiteboard metadata

• Does not remove those whiteboard items.
• Whiteboard items just keep their original origin_chat_id / origin_file_id.
• The whiteboard can still show the updated folder context if you want (e.g., “From: aiConnected → Hiring & Teams”).

​

4. Data / API View (Implementation-Level)

• POST /instances/{id}/chats/bulk-move
  • Payload: { chat_ids: [...], target_folder_id: "..." | null }
• POST /instances/{id}/files/bulk-move
  • Payload: { file_ids: [...], target_folder_id: "..." | null }

• Option 1: two calls
  1. POST /instances/{id}/folders → returns { folder_id }
  2. POST /instances/{id}/chats/bulk-move with that folder_id
• Option 2: single combined endpoint:
  • POST /instances/{id}/bulk-move-to-new-folder
    • { type: "chats" | "files", item_ids: [...], folder_name: "...", folder_settings: { ... } }

• Backend should treat:
  • “Create folder + move items” as one operation for the user.
  • If anything fails, either:
    • Folder isn’t created, or
    • Items are not partially moved without the folder.

​

5. UX Micro-Details That Will Feel Good

• After moving:
  • Show a toast like:
    • “Moved 7 chats to ‘Cognigraph Architecture’.”
    • Clicking it could jump straight into that folder.
• In the folder sidebar:
  • Brief animation / highlight to show the new folder or updated counts.
• Undo:
  • Optional “Undo” button in the toast that reverses the last bulk move.