Workspace Objects

Pantasso organizes imported content into structured workspace objects. These objects are the foundation of cited retrieval, agent context, and workspace health monitoring.

This page describes the hosted public beta. Files and Obsidian are the live first source. Slack, Google Drive and Docs, Telegram, and GitHub need a connection.

What are workspace objects?

When you connect a source, Pantasso does not store raw data as-is. It structures the content into typed objects that can be searched, cited, and tracked. Each object has:

Type: What kind of content it represents (document, decision, task, and later message objects after a conversation source is connected).
Source: Where it came from (an approved file, Obsidian note, or a later connected source).
Content: The text and metadata from the original source.
Provenance: When it was imported, when the source was last synced.

In the hosted public beta, those objects start as approved files and Obsidian notes. Connected sources can add more objects after a connection is in place.

Object types

Documents

Imported from uploaded files and Obsidian notes in the hosted public beta. Google Docs and Google Drive files become document objects after Drive is connected. Documents include the full text content and metadata.

Messages

Imported from Slack channels, Telegram groups, and similar conversation sources after those sources are connected. Messages are not a day-one object type in the hosted public beta. When present, they include the text, author, timestamp, and thread context.

Decisions

Extracted from documents, and from messages after a conversation source is connected, where a decision was recorded. Decisions capture what was decided, who was involved, and when.

Projects

Structured representations of ongoing work, including scope, status, and related objects.

Tasks

Individual work items connected to projects, decisions, or other workspace objects.

How objects are used

Cited retrieval

When you ask a question, Pantasso searches workspace objects and returns citations pointing to the specific objects that informed the answer. In the hosted public beta, those objects start as Files and Obsidian.

Agent context

AI assistants with agent profiles receive workspace objects as context when answering company-specific questions. The objects they can access depend on their profile scope and on which sources are connected.

Workspace health

The workspace dashboard shows object counts, source coverage, and freshness metrics so you can see how complete your workspace is.

Object lifecycle

Import: Content is imported from a connected source and structured into objects. Files and Obsidian are the live first source.
Index: Objects are indexed for retrieval.
Query: Objects are returned as cited context when relevant to a question.
Update: When sources re-sync, objects are updated to reflect changes.
Archive: Objects from disconnected sources can be archived but remain in workspace history.