RaisinDB Branch Workflows

A branch is an isolated copy of both schema and content. Writes on one branch are invisible on another until you merge. Use branches to give an AI agent its own workspace and merge the result back, to stage schema/content changes before promoting to main, or to run parallel experiments without touching production.

Branches are scoped per {tenant, repo, branch} — every node, index, archetype, element type, and node type is keyed by branch.

1. Scope work to a branch — onBranch

db.onBranch(name) returns a branch-scoped database/workspace. The default branch is main.

const db = client.database('myapp');