> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.alpha.openantares.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.alpha.openantares.com/_mcp/server.

# Knowledge graph

The knowledge graph turns extracted facts into connected operational context. Every node, relationship, and supporting source belongs to one vault.

![Northstar Fulfillment knowledge graph with visible entity connections](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/alpha-506400.docs.buildwithfern.com/e760c51fcb9ff989dcdab5ee5e6ed7bcee88500270d44f38766af54a16984afb/docs/assets/screenshots/knowledge-graph.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260903%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260903T012038Z&X-Amz-Expires=604800&X-Amz-Signature=3035527466cd25413f77e9f4c15cab684c3b4a5d488bab198238041696fd33c5&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Read the graph

A node represents an entity Alpha found in source material. An edge represents a relationship supported by one or more sources.

Common entity types include:

| Type                   | Examples                                                        |
| ---------------------- | --------------------------------------------------------------- |
| People and departments | Owners, decision makers, teams, and external contacts           |
| Processes              | Fulfillment, approval, onboarding, and escalation flows         |
| Systems                | CRMs, warehouse tools, data stores, and communication platforms |
| Problems               | Delays, bottlenecks, missing access, and unclear ownership      |
| Opportunities          | Automation ideas, improvements, and proposed next steps         |
| Measures               | KPIs, targets, thresholds, and observed results                 |

Connections describe relationships such as ownership, dependency, use, measurement, impact, or participation.

## Find the useful part

Use the controls at the top of the graph to reduce noise:

* Search for an entity or relationship name.
* Toggle entity types on or off.
* Increase **Minimum mentions** to emphasize recurring entities.
* Filter by department when the graph contains several teams.
* Use zoom and **Fit view** to reframe the current result.

Selecting one node highlights its immediate neighborhood and opens the detail panel. Background nodes stay available without competing for attention.

## Follow evidence

The graph is an index into evidence, not a replacement for it.

#### Open a node or connection

Read its description, type, mention count, and related entities.

#### Inspect the source list

Confirm the vault and the meetings, messages, mail, or files supporting the relationship.

#### Open the original source

Check who made the claim, its date, and the surrounding context.

#### Review disagreements

If another source conflicts with the claim, open the Review item before using it in a decision or artifact.

## Graph updates

The graph takes a fresh snapshot when the page loads. It does not continuously restart its layout while ingestion writes new entities and edges.

Reload the page when you want a newer snapshot. This keeps the graph stable while you inspect it and prevents flicker during a large import.

## Empty nodes or missing connections

If entities appear without meaningful edges:

1. Confirm the underlying meetings, mail, or files finished processing.
2. Open an entity and check whether any source evidence was extracted.
3. Review the ingestion status for partial failures.
4. Reload the graph after relationship extraction completes.

An imported file is not the same as a processed relationship. Large documents can appear in Files before their entities and connections finish.

## Vault boundaries

A vault graph contains only that vault's nodes and edges. The organization-level graph can place accessible vault subgraphs together, but it preserves the source vault for every entity and does not create cross-client edges merely because names look similar.

#### [Search and chat](/search-and-chat)

Ask a question about a person, process, or connection.

#### [Review evidence](/review-evidence)

Resolve conflicting claims before they become accepted knowledge.