Kickoff: Ingesting Knowledge into Seed Hypermedia

Topic: UX Design — Importing External Knowledge and Systems of Record Participants: Product, Design, Engineering Goal: Define a coherent user experience for bringing external information into Seed, from simple document imports to autonomous agent-driven integrations. 1. Context Seed Hypermedia enables knowledge communities to collaboratively organize, connect, and evolve information. However, most organizational knowledge already exists elsewhere: in documents, websites, databases, and enterprise software. We need to make it easy to bring this information into Seed while preserving its meaning, structure, provenance, and relationships. Our challenge is not simply to import files. It is to transform external information into persistent, interconnected, and collaborative knowledge objects. We should support several levels of complexity: The UX should make these capabilities accessible without exposing unnecessary technical complexity. 2. Key Concepts 2.1 Source The external location from which information originates. Examples: Questions: 2.2 Connection An authorized relationship between Seed and an external system. A connection may provide access to information through an API, authentication mechanism, or external tool. Examples include enterprise document repositories, CRM systems, and research databases. Questions: 2.3 Importer A mechanism that retrieves information from a source and transforms it into Seed objects. Different importers may perform different operations: Questions: 2.4 Agent Importer An agent that orchestrates one or more tools to perform an import. For example, an agent might: Unlike a conventional importer, an agent can make decisions, ask questions, and adapt its behavior. Questions: 2.5 Import Job A specific execution of an import process. An import job may be instantaneous or run for hours, depending on its complexity. Possible states: Configured → Running → Needs Attention → Review → Completed With additional states for paused, failed, or cancelled jobs. Questions: 2.6 Imported Knowledge The result of transforming external information into Seed’s document and object model. Imported content may include: Questions: 2.7 Provenance and Synchronization Imported information should remain traceable to its origin. Importing also raises the question of whether the resulting Seed objects represent a one-time copy or an ongoing relationship with the source. Questions: 3. Main User Journeys We should design around four representative journeys. Journey A: Import a PDF Scenario: A researcher wants to import a scientific paper. Design challenge: Make a simple import almost effortless while allowing advanced extraction and structural preservation. Journey B: Import a Website Scenario: A knowledge organizer wants to import a collection of online publications. Design challenge: How do we communicate scope, hierarchy, and relationships before importing hundreds of pages? Journey C: Connect an Enterprise System Scenario: An organization wants to bring information from its existing system of record into Seed. Design challenge: How do we make enterprise integrations understandable without forcing users to understand APIs, schemas, and authentication details? Journey D: Delegate an Import to an Agent Scenario: A user wants to build a knowledge base from a large collection of documents. The user tells an agent: “Import all the environmental reports from this repository, organize them by topic, preserve their citations, and identify relationships between the projects.” The agent: Design challenge: How do we combine natural-language interaction with predictable, inspectable, and controllable operations? 4. Central UX Question: Chat or Dedicated Interface? This is probably the most important design decision of the workshop. Option A: Chat-Based Import The user interacts with an agent through conversation. Advantages Limitations Option B: Dedicated Import Interface A structured interface guides the user through source selection, configuration, execution, and review. Advantages Limitations Option C: Hybrid Interface Working hypothesis: Use conversation for intent and structured interfaces for configuration, control, and inspection. For example: The user tells an agent: “Import these 500 PDFs and organize them by project.” The agent responds with a proposed plan. Seed presents a structured interface containing: The user approves the plan and monitors execution through an import dashboard. The agent remains available to explain results, resolve exceptions, and modify the plan. Questions for the workshop 5. Important Product Decisions 5.1 Import vs. Sync We need to distinguish between: Import: Create Seed objects from an external source. Sync: Maintain a relationship between external information and Seed objects over time. Questions: 5.2 Copy vs. Reference Not every external resource needs to be copied into Seed. Sometimes maintaining a reference is sufficient. Questions: 5.3 Transformation vs. Preservation An importer may preserve the original document or reorganize it into a new structure. Questions: 5.4 Permissions and Trust External information may contain confidential or restricted content. Questions: 5.5 Reusability An import may be a one-time operation or a recurring organizational process. Questions: 6. Proposed Conceptual Model A possible model for discussion: Source → Connection → Importer → Import Job → Seed Objects An agent can orchestrate this process: Agent → Tools → Import Jobs → Seed Objects The distinction matters: Not every import requires every component. For example, importing a local PDF might not require a persistent connection or an agent. An enterprise integration might require all of them. Workshop question: Is this the right conceptual model, or are we introducing unnecessary abstractions? 7. Workshop Activities Suggested duration: 2 hours Activity 1 — Align on the Mental Model (20 minutes) Review the key concepts. Ask participants to describe how they understand the relationship between sources, connections, tools, importers, agents, and jobs. Output: Shared terminology and an initial conceptual model. Activity 2 — Map User Journeys (30 minutes) Divide into groups and map the four journeys: For each journey, identify: Output: Four user journey maps. Activity 3 — Explore Interaction Models (30 minutes) Sketch three alternatives: Compare the approaches using the same scenario: importing a large collection of documents through an agent. Output: Alternative UX concepts and their trade-offs. Activity 4 — Define the Import Lifecycle (20 minutes) Design how users: Output: Initial import lifecycle and interaction requirements. Activity 5 — Decisions and Next Steps (20 minutes) Agree on: Output: Design decisions, open questions, and prototype assignments. 8. Expected Workshop Outcomes By the end of the workshop, we should have: 9. Guiding Design Principle Importing information into Seed should feel less like transferring files and more like extending a knowledge network. Users should not have to understand extraction pipelines, APIs, or agent orchestration. They should be able to express what information they need, understand what Seed proposes to do, retain control over the process, and immediately begin working with the resulting knowledge. The ultimate objective is not merely to ingest information. It is to make existing knowledge available for collaboration, interpretation, and continuous improvement. My suggestion for the workshop I would make one question the centerpiece of the session: Is importing knowledge an operation performed by the user, or a task delegated to an agent? This distinction has major consequences for Seed’s UX architecture. Rather than designing a separate agent-import experience, I would explore whether an Import Job is a first-class Seed object that both humans and agents can create, inspect, and control. That would allow Seed to offer a simple PDF import button, a sophisticated enterprise integration interface, and an agent conversation—all operating on the same underlying model. It also fits Seed’s broader philosophy: agents and humans should operate on shared objects rather than inhabit separate applications.