Projections | Nebula Docs

NEBULA-CONCEPTS-PROJECTIONS(1)

Nebula Manual

NAMEprojections — GitHub, local Git, deployment platforms, and CI systems are outputs of policy-aware projection plans.

SOURCEnebula/docs/architecture.md

STATUSpre-alpha · protocol in design

Git as a projection

Git branches and pull requests are compatibility projections of the Nebula canonical graph. The export respects all policy decisions when generating Git-native objects.

output

Proposal + Environment + Actor + Policy
  -> Projection Plan (manifest)
  -> Git branch / commit / PR

Projection manifests

Every projection produces a manifest that classifies every path before generation begins. This ensures complete policy coverage before any file is written.

output

# Manifest structure
included_paths:  [src/**, tests/**, package.json]
redacted_paths:   [.env]
templated_paths:  [config.tpl]
omitted_paths:    [internal/**]
blocked_paths:   []  # Must be empty for valid export

Deployment projections

Different deployment targets may need different material. Nebula can produce separate projections for GitHub (public source) and Vercel (authorized build + env vars) from the same canonical graph.

output

# GitHub: public-safe source only
github -> safe_public_source

# Vercel: authorized build source + env
vercel -> authorized_build + environment_variables + short_lived_grant

Preview and export

Use the CLI to preview what a projection will include before executing it.

output

neb projection preview --environment production --target vercel
neb projection export --environment development --target local