Skip to main content

Core Concepts

Veoveo is built around a small set of concepts that appear throughout the app, API, and agent runtime.

Workspace​

A workspace is the operating boundary for a team or mission. It contains members, bots, tools, prompts, billing settings, artifacts, links, events, and search state. Most product and API routes start by selecting a workspace.

Artifact​

An artifact is a durable object in the workspace graph. Documents, images, recordings, scenes, datasets, locations, forms, prompts, tools, operations, rules, alerts, collections, and messages are all artifacts. Each kind has its own data, but all artifacts share common identity, metadata, visibility, links, blobs, and events.

Blob​

A blob is file-backed content attached to an artifact slot. A document might have an original file and rendered pages. A recording might have an original recording and a thumbnail. A dataset might have a CSV source and a rendered preview. Blob routes are how users and tools read or update those files.

A link is a relationship between two artifacts. Links let Veoveo represent evidence chains, related context, parent-child collections, generated outputs, and operational dependencies without burying relationships inside one-off metadata fields.

Event​

An event records what happened in the workspace or on a specific artifact. Events support timelines, audit trails, subscriptions, search, and operation history. They are useful when a team needs to answer: what changed, who or what changed it, and when did it happen?

Bot​

A bot is a workspace-owned agent identity. Bots can be connected to channels, receive prompts, inspect artifacts, use tools, and create operation history. A bot should be treated as a participant in the workspace, with its own permissions and traceable actions.

Tool​

A tool is a capability a bot or workflow can call. Tools can read artifacts, create links, analyze media, render documents, query datasets, forecast time series, call container-backed services, or project external MCP capabilities into Veoveo.

Operation​

An operation is the trace of multi-step bot or runtime work. It captures turns, tool calls, status changes, outputs, failures, and follow-up work. Operations make automation reviewable instead of opaque.

Media To Add​

  • Diagram: one artifact with attached blobs, outgoing links, and event timeline. It helps readers understand how the shared graph works. Source: artifact detail page for a sample workspace document.
  • Screenshot: workspace artifact list with kind filters visible. It helps readers connect the concept list to the actual app. Source: sample OSINT workspace artifact explorer.