The open framework

vibegraph.md

Your vibes, codified.

Your vibes: your personality, taste, voice, values, purpose, and aesthetic.

A vibegraph is the network of identity, context, knowledge, and memory that governs how AI thinks, writes, and acts for one person, and any businesses they own or operate. This is its file convention: a readable structure for who you are, your personal brand, and the business brands you own, portable to any AI tool you choose.

Read the specification → Browse the example →

Published specification: 2.0 · MIT (templates, schema, code) · CC-BY 4.0 (prose)

The definition.

Everyone who uses AI for real work already has a vibegraph, spread across a notes app, a folder, a few platform memories, and their own head. Two things turn that pile into a vibegraph: a human-authored identity core, and a root file with a fixed name that any agent reads first. Without them, it is context. With them, it is a graph any agent can walk, a permission model you can reason about, and an asset that moves unchanged when a better tool ships.

Memory layers remember what happened. A vibegraph defines who you are.

Three things, three roles

The web, HTML, a website builder.

Role	vibegraph	vibegraph.md	vibegraph.ai
What it is	The noun: the network that governs AI for one person and the businesses they own	The open framework: the root file, the link schema, scopes, areas, the handoff	The guided builder for the identity core and brands
Who owns it	Nobody. A common noun	Open. MIT and CC-BY 4.0	Raizen Labs, LLC
Analogy	the web	HTML and index.html	a website builder

What goes into a vibegraph

Make your identity readable.

Identity

Personality (the Big Five, the Enneagram, and any other instruments you bring), an integrated reading, and a four-pillar Ikigai. Small, stable, safe to share.

identity/<your-name>.md

Brands

One personal brand and any business brands you own, each with twelve Brand Context elements and eight Brand Visuals elements. Business brands add Aaker's dimensions, an archetype, and the Golden Circle.

brands/<slug>.brand.md

Areas and components

Areas are the domains you add when a use case demands one, each a folder with its own scope. Components are the tools that already hold parts of your graph, registered with a kind and a scope.

areas/<area>/index.md · components.md

Read first

VIBEGRAPH.md is the root file.

A fixed name at the root, capitalized to match AGENTS.md and CLAUDE.md. It names the owner, links every part of the graph with a kind, a scope, and a rule for when to read it, and states the read order. It is to a vibegraph what index.html is to a website.

- [Maya Okafor](identity/maya-okafor.md) · kind: identity · scope: public · when: always
- [Delivery OS](brands/delivery-os.brand.md) · kind: brand · type: business · scope: public · when: on-task (any Delivery OS writing, design, or publishing)
- [Finances](areas/finances/index.md) · kind: area · scope: private · when: on-grant

kind: identity · brand · area · source · memory · project · skill · agent scope: public · scoped · private when: always · on-task · on-grant

Nothing is exposed by omission.

Ten seconds to add

Send every agent to your vibegraph.

Put this in AGENTS.md, and the same text in CLAUDE.md, in any repository or workspace you work in. Codex, Cursor, Copilot, and Gemini CLI read AGENTS.md. Claude Code reads CLAUDE.md. Both files, same four lines.

## Who you emulate
Before starting, read `VIBEGRAPH.md` (in this repo, or at `~/vibegraph/VIBEGRAPH.md`).
It defines the person and brands this work belongs to. Follow its read order and scopes.
Do not read entries marked `scope: private` unless they have been granted for this session.

Start with the format

Open it. Read it. Make it yours.

Read the specification.

The layout, the root file, the link schema, scopes, the handoff, and how AI systems consume a vibegraph. Open SPEC.md ↗

Start from the example.

A complete vibegraph for a fictional owner, Maya Okafor, with a personal brand and a business brand. Clone it, replace her with you, and pass the paste test in under an hour. Browse the example ↗

Bring it to your tools.

Paste the root file, your identity file, and one brand file into any chat. Add the handoff to your repositories. Serve it over MCP if you want it live. Read the whitepaper ↗

Want a guided build with an AI coach? That is what vibegraph.ai is for.

The acceptance test.

Open a fresh session in any model. Paste VIBEGRAPH.md, your identity file, and one brand file. Ask for a piece of work you do often. The output should sound like you on the first generation. If it does not, the core is incomplete, not the tool.