Zero to Graph in 5 Minutes

5 minutes

Create your first decision graph using Magic Paste.

Capture Your First Decision

Click + New Decision in the header, then select "From Text (Magic Paste)".

Paste any text about a technical decision. Arbtr extracts the structure automatically.

Example input:

"We're going with Postgres because MySQL doesn't have good JSON support and we need to store flexible metadata. DynamoDB was considered but the cost model doesn't work for our read patterns."

Arbtr extracts:

Title: Database choice for metadata storage
Positions: PostgreSQL, MySQL, DynamoDB
Arguments: JSON support (pro-Postgres), Cost model (anti-DynamoDB)
Outcome: PostgreSQL (if detected)

tip

Pro tip

The messier the input, the better. Magic Paste handles Slack conversations, email threads, and meeting notes. It extracts signal from noise.

Add a Related Decision

Repeat the process with another decision. This time, we'll link them.

Example input:

"We chose Supabase for backend because it gives us Postgres + Auth + Realtime in one service. Considered Firebase but we wanted SQL. Self-hosting was ruled out due to ops burden."

Now you have two decisions: "Database Choice" and "Backend Service".

Create the Relationship

Open the "Backend Service" decision and click Add Relationship.

Select:

Target: Database Choice (PostgreSQL)
Type: depends_on

PostgreSQL

Supabase

Supabase depends_on PostgreSQL

Why this matters: If you ever revisit the PostgreSQL decision, you'll immediately see that Supabase depends on it. No more "why can't we just switch to MongoDB?"—the dependency is explicit.

See the Graph

Click Graph in the navigation to see your decision network.

Your first Strategic Debt is now visible.

As you add more decisions and relationships, the graph reveals:

Dependency chains: What breaks if this changes?
Conflicts: Which decisions are mutually exclusive?
Domains: How decisions cluster by team or area
Anchor decisions: Which choices are load-bearing?

What's Next

Import Existing Decisions

Have legacy docs in Notion or Confluence? Import them in bulk.

Understand the Graph

Learn how to read and navigate the decision graph.

Relationship Types

Learn when to use depends_on vs conflicts_with vs supersedes.

See Arbtr's Architecture

Explore Arbtr's own decisions—dogfooding in action.

Ready to start?

Create your first decision now, or import your existing documentation.

Create Decision Import from Files

Getting Started

Core Concepts

Command Palette