files / vfs

vibestartup is a virtual filesystem under the hood. every entity — every part, every pcb, every customer, every agent, every run — is a real file at a real path in a real tree. this is the whole trick fr.

why

because llms read files. they dont read apis. they dont read databases. they read filesystems. if you want agents to work on your whole startup, your whole startup needs to look like a filesystem.

also because you already know how a filesystem works. there are no new concepts to learn. no new crud uis. no new apis. just read, write, mkdir, glob, mv, rm. same muscle memory you already have.

the layout

a default project looks like:

/
  .vibe/               settings + metadata
  parts/               *.part.md
  pcbs/                *.pcb.md
  ics/                 *.ic.md
  robots/              *.robot.md
  ais/                 *.model.md
  apps/                *.app.md
  products/            *.product.md
  marketing/           campaigns, posts, emails
  customers/           *.customer.md
  partners/            *.partner.md
  investors/           *.investor.md
  agents/              *.agent.md
  runs/                run history (generated)

you can rearrange this however you want. the tabs filter by file suffix, not by folder, so moving files doesnt break anything.

file formats

every domain file is markdown with typed frontmatter. example part.md:

---
kind: part
name: bracket-v2
material: aluminum-6061
mass_g: 42
geometry: bracket.step
---

# bracket v2

left-side mounting bracket for the arm. machined from 6061.

the frontmatter is typed per kind. the body is freeform markdown — you, agents, links, embeds, whatever.

how agents see it

agents get fs.read, fs.write, fs.glob, fs.mv, fs.rm, fs.stat as tools. they operate in a cwd you set in the .agent.md frontmatter. they see the same paths you see. no translation layer. no db behind your back. if you can see it in the file tree, the agent can too — and vice versa.

versions + history

every write is versioned. file@v3 gets you the third revision. file@2026-04-01 gets you a point-in-time read. history retention depends on your tier — see pricing.

this is the unlock

once everything is files, agents compose. scheduling composes. sharing composes. backups compose. you get 40 years of unix tooling as interop for free. ngl thats the whole memo.