> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vegalake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contexts and environments

> Resolve VegaGraph facts through default, hierarchical, and environment-specific scopes.

# Contexts and environments

A context represents a named perspective in which graph facts can be resolved—for example, an environment or another hierarchical scope. Contexts belong to an organization and workspace and have stable fully qualified names.

## Default context

The default context provides the baseline when a caller does not select a more specific context. Confirm the default before comparing dashboard and API results.

## Context hierarchy

A context can have a parent. Resolution can combine inherited baseline facts with a more specific overlay. The hierarchy should express scope, not an arbitrary entity relationship; use graph edges for dependencies and entity hierarchy for structural containment.

## Environment projections

Environment resources can expose Entity 360 and runtime projections. An environment entity is still part of the typed graph, while the selected context controls which scoped facts are resolved.

## Working with contexts

1. List visible contexts in the active organization/workspace.
2. Resolve a known context by ID or fully qualified name.
3. Identify the default context.
4. Compare entity or search results with the intended context selected.
5. Grant collection or instance permissions only to readers and writers that require the context.

## Common mistakes

* Treating a context as a workspace boundary
* Assuming a child context duplicates every parent fact
* Confusing context hierarchy with lineage
* Writing secret values into context-scoped aspects; secret values must remain references