Core concepts

Understand how selected source material becomes scoped, evidence-backed knowledge.

View as Markdown

Alpha is organized around a simple promise: the work you approve enters the right vault, becomes connected knowledge, and stays inside that boundary wherever you use it.

From source to answer

The first row decides what Alpha may read and where it belongs. The second row turns that approved material into evidence that can support search, answers, relationships, tasks, and artifacts.

Sources

A source is a meeting, email, Slack message, Teams conversation, or file available through a connected account. Connecting an account gives Alpha permission to list eligible source material. It does not import everything automatically.

Routing rules and selections

Mail and calendar can be routed with keywords, participant domains, required keyword groups, and exclusions. Drive, Slack, and Teams also use exact selections so you can approve the folders, files, channels, DMs, or conversations that belong in each vault.

Review routing rules and exact selections before starting ingestion. A vault name alone is not a routing rule.

Vaults

A vault is a controlled workspace for one client, project, or internal team. Every imported source, extracted entity, relationship, answer, task, and artifact carries a vaultId.

  • A member sees only vaults they can access.
  • A channel or conversation selected for one vault does not become searchable from another vault.
  • Cross-vault questions are possible only when the requesting person can access every selected vault.
  • Internal multi-client meetings stay in the internal vault. They are not copied into client vaults automatically.

Entities, relationships, and evidence

During processing, Alpha identifies useful entities such as people, organizations, systems, decisions, problems, and tasks. Relationships connect those entities to each other and to their source evidence.

The graph is a visual index of those connections. It is not a replacement for the source. Open a claim, relationship, or discovery to inspect where it came from before acting on it.

Answers and artifacts

Chat, Slack, email, MCP, and the API all use the same vault boundaries. Alpha should identify the relevant accessible vaults, search them deliberately, and label information when an answer uses more than one vault.

Artifacts are reusable outputs such as reports, briefs, diagrams, charts, and spreadsheets. They retain links to the underlying evidence so a reader can verify the work.

Personal and vault-wide rules

Rules added by a member apply to source material from that member’s connected accounts. Vault admins can review member additions and promote useful rules for everyone in the vault. This lets a person improve routing for their own inbox without silently changing what other members import.