bimbOS: an open personal-OS starter framework

bimbOS is a persona-agnostic personal operating system you run in Obsidian and Claude Code. You get a structured vault, a pack of AI subagents, and slash commands. Clone it, open it in Claude Code, and run /onboard. It builds the OS around you: creator, founder, consultant, writer, or generic.

Free and open under GPLv3 (see LICENSE). A done-for-you build and orchestration service exists, but nothing here needs it. The whole framework is self-serve.

This README is what your OS shows you after onboarding. Welcome. This is your personal operating system: vault structure, AI agents, and slash commands tuned to your archetype.

Read in this order: SETUP.md (install, 30 min) → USAGE.md (daily/weekly/monthly mechanics) → PERSONAL-FIRST-WEEK.md (7-day onboarding) → CUSTOMIZE.md (extend it your way, after 30 days).

Bring your own mentors. Turn the mentors you admire into callable advisor personas your OS can think in. Start with identity/mentors/_build-guide.md.

Write freely. You do not have to remember the commands. Type a thought and your OS routes it to the right place. See .personal-os/write-router.md.

What this is

A working personal operating system built for you across:

Identity layer — who you are: principles, baseline self, relationships, wins, body
Operational layer — finances, content, network, todos, inbox, daily journal
Strategy layer — north-star, plan, bets, criteria, principles
Skills layer — slash commands + AI subagents in .claude/
Conventions layer — .personal-os/ (architecture, linking, metadata, log)
Mentor layer: your callable advisor personas, mentors you admire distilled into voices your OS can think in (/mentor)

How to use it

Open this folder in Obsidian (or your preferred markdown editor) — it's a vault.

Open this folder in Claude Code — .claude/commands/ and .claude/agents/ activate when you do. The slash commands and subagents are tuned to your archetype + your workflow.

Daily ritual: /morning-journal → do your work → /scratch thoughts as they come → /evening-journal.

Weekly ritual: /sunday review every Sunday. Non-negotiable.

Critical files (in order of how often you'll touch them)

File	What it does
`home.md`	Your daily landing — opens here every morning
`todos.md`	What's on your plate (Tasks plugin syntax)
`inbox.md`	Capture-anything; sweep weekly
`journal/daily/{YYYY-MM-DD}.md`	Today's entry — auto-created by `/morning-journal`
`plan.md`	Near-term route — this week / month / quarter
`north-star.md`	Your destination — the real why
`principles.md`	Beliefs you've earned (your library, you fill)
`bets.md`	Active bets with thesis + conviction + kill condition
`network.md`	Your leverage map (CRM-light)

Folder map

Path	What
`identity/`	Who-you-are layer — adn, principles, relationships, wins, body
`identity/mentors/`	Your callable advisor personas; build them with `/new-mentor` plus the build guide
`finances/`	revenue / burn / net-worth / payment-rails
`content/`	Voice, source-material, posts pipeline
`network/`	Per-person CRM cards
`journal/`	Daily notes + Body/Mind/Spirit/Vocation areas. Gitignored.
`inbox/`	Richer captures (attachments). Gitignored.
`drafts/`	Workshop folder for in-progress drafts
`_archive/`	Closed / superseded files
`templates/`	Cross-cutting scaffolds
`.claude/`	Slash commands + subagents (your skill pack)
`.personal-os/`	Conventions: architecture, linking, metadata, log

The 7 Growth Doctrine Rules

These are the disciplines that make the system work. You signed onto them at engagement. Re-read in low-energy moments.

Daily journaling is non-negotiable (/morning-journal 5+ days/week)
/sunday review every Sunday (60-min weekly synthesis)
Capture or lose it (/capture or /scratch within 60 seconds)
Money-first, art-second (every project decision passes through finances/burn)
One pillar per quarter (don't add new pillars; deepen one)
Body-floor gates every external commitment (no calls/launches/sprints below sleep + eat floor)
Public visibility compounds (output is structural, not optional)

Full doctrine: .personal-os/growth-doctrine.md (your version, customized at intake)

When you need help

Async support per your tier (Starter: email 48hr / Pro: 24hr / Studio: 4hr) — see your engagement letter
Cadence calls per your tier (Starter: monthly / Pro: bi-weekly / Studio: weekly)
Crisis triage available — message your operator if something's broken or you're drifting

What this is NOT

Not a Notion template you tweak in isolation
Not a productivity course
Not a magic productivity system

This is an operating system that requires daily use to compound. If you stop using it for 14 days, drift accumulates faster than the system can recover. The 7 doctrine rules exist for that exact reason.

The five docs that ship with this folder

File	When to read
`SETUP.md`	First — install Obsidian + Claude Code + Git, fill `[fill]` markers, 30 min
`USAGE.md`	Second — daily / weekly / monthly mechanics
`PERSONAL-FIRST-WEEK.md`	Third — your 7-day onboarding plan
`CUSTOMIZE.md`	After 30 days — write your own commands and agents
`HANDOFF.md`	Reference — what got built specifically for you

Customer-facing protocols live in docs/:

docs/growth-doctrine.md — the 7 rules (re-read at every /sunday)
docs/activation-gate.md — the first-14-days unlock mechanics
docs/re-engagement.md — what happens if you drift 30+ days
docs/support-slas.md — response times by tier
docs/refund-policy.md — refund terms

License

bimbOS is licensed under the GNU General Public License v3.0. See LICENSE.

Copyright (C) 2026 Sebastian Bimbi / Bimbi Digital. You are free to use, study, modify, and share it. A distributed modified version must also be GPLv3 with its source available. Commercial use is permitted under those terms.

Personal OS: the open, persona-agnostic starter framework by Bimbi Digital. Clone it, run /onboard, make it yours. An optional done-for-you build and orchestration service is available but never required.