Prims Drive

prims.sh · drive · stub · multi-org · teams · agents

Prims Drive

A multi-org, teams cloud drive — first-class product for people who wear many hats and agents that need identity, scope, and audit across companies. .prim packs live on the drive plane; git, local, and legacy Drive stay under the hood. This is not Google Drive sync for Prim Desktop.

Multi-org Each company gets a tenant. Switch Eidos ↔ Greenmark ↔ side LLC without mixing stores.
Teams Folders, sharing, and roles at the team layer — not one flat personal bag bolted onto Shared Drives.
Cloud drive for agents Scoped connectors, cited read/write, versions agents can diff. Packs live here.

Why this exists

One OAuth identity / filing cabinet per email was never enough

Google Drive assumed most people have one Google account. Multi-hat founders do not. You run personal life, a company, and a side LLC — three emails, three Drives, three OAuth silos. Agents need identity + scope + audit across orgs; the market gave a filing cabinet per email and bolted Shared Drives on later. Prims Drive is built for that gap from day one.

filing cabinet per email

Connect ChatGPT or Claude to Drive and it binds one OAuth identity. Your company pack and your LLC evidence never share a plane — unless you crown one Gmail as mega-hub.

multi-hat founders

Morning: Eidos eng packs. Afternoon: Greenmark ops PDFs. Evening: personal tax folder. Same human, three tenants — Drive still asks “which account?” every time.

agents need scope

An agent that can cite what it read, write only where scoped, and leave an audit trail across orgs is not a Shared Drive checkbox. That is the product.

Problems (real-shaped)

Concrete friction — not abstract “collaboration challenges.” If you’ve lived three Google accounts and a half-migrated Maps folder, you already know these.

problem · oauth silo

Three Google accounts; ChatGPT connects only one

Personal Gmail, company Workspace, side LLC. You authorize ChatGPT once — ChatGPT connects only that one Drive root. Ask it about the LLC pack and it shrugs or hallucinates from the wrong cabinet.

you@gmail · you@eidos · you@llc
→ ChatGPT OAuth: you@gmail only
problem · wrong account

“Which Drive am I in?” · dumps like “From Other Drive”

Upload a contract while signed into the wrong account. Weeks later it’s in a junk folder named From Other Drive. Search fails. Ownership fights begin. Nobody knows which tenant owns the truth.

Contracts/Q3.pdf → filed under personal · tagged “From Other Drive”
problem · king fights

Mini packs vs Drive hub vs GitHub vs “make BV the king”

Everyone wants a source of truth. Mini packs claim locality. Drive claims the hub. GitHub claims history. Someone always proposes make BV the king — one root to rule them all — and the fight restarts next quarter.

pack://local ⚔ drive://hub ⚔ github://repo ⚔ “BV king”
problem · half-migrations

Maps / AI_MAP duplicated across mounts

Maps and AI_MAP copied to Desktop, Drive, and a USB “backup.” Half-migrations leave two maps that disagree. Agents cite both. Humans argue which mount is current.

~/Maps · Drive/Maps · /Volumes/…/AI_MAP — three ages, one name
problem · legacy takeout

Legacy account (Howjadoo-shaped) takeout cold, still in your head

Old Howjadoo-era Google still holds years of context. Takeout is a zip on a shelf — cold — but the mental model is still warm. Nothing indexes it into today’s orgs without crowning that old email again.

takeout-howjadoo-2019.zip · unread · still shaping how you search
problem · agents + cabinets

Agents need cited read/write + scope across orgs

Google gave a filing cabinet per email. Agents need to read with citations, write into a scoped folder, and leave versions across Eidos and Greenmark — without whole-root OAuth to one Gmail.

agent wants: cite · scope · audit · multi-org
Drive gives: one My Drive OAuth
problem · colliding centrals

Money packs vs PDF evidence colliding in the same “central” question

Finance wants the money pack as the hub. Legal wants PDF evidence as the hub. Both ask “what’s central?” in the same Drive tree. One folder cannot be both the ledger and the exhibit room without chaos — unless the plane separates orgs, packs, and permissions deliberately.

money.prim ⚔ exhibits/*.pdf — same “central Drive” argument, different jobs

Solutions (Prim Drive)

Pair each problem with a first-class answer — multi-org and teams by design, not Shared Drives bolted on.

solution · multi-org / teams

Multi-org / teams first-class (not bolted Shared Drives)

Tenants are the product. Switch orgs; teams own folders and packs. No more “which Drive am I in?” — the org switcher is the home screen.

solution · one plane

One drive plane; packs live on it

Backends (git / local / legacy Drive / Howjadoo takeout) stay under the hood. The story is one plane where .prim packs live — not crowning one Gmail as mega-hub.

solution · AI connectors

Web viewer + AI connectors with scoped access

ChatGPT, Claude, Cursor connect with scoped access — a pack, a team folder, an org — not whole-root OAuth to a single email’s My Drive.

solution · audit

Audit / versions agents can diff

Every agent write leaves a version. Humans and agents diff what changed, who (or what) wrote it, and under which org scope — cited read/write by default.

solution · thin curated context

Thin curated context for AI — without crowning one Gmail

Point connectors at curated packs and folders. Money packs and PDF evidence can both be “central” inside their orgs without collapsing into one personal Drive. Legacy takeouts attach as backends, not as the identity you live inside.

Screens walkthrough

CSS UI mock frames — denser story of org → teams → drive → viewer → share → AI connectors → activity. Soft stub; redrawn toward shipping chrome later.

01 · Org switcher / multi-org home

Org switcher

Pick a tenant. Files never leak across Eidos, Greenmark, and the LLC.

02 · Team directory + roles

Team directory + roles

People and agents get roles on folders and packs — invite, approve, revoke.

03 · Drive browser

Drive browser (folders / packs)

Browse the cloud drive. Packs live here; backends stay under the hood.

04 · Web viewer / preview

Web viewer / preview

Read packs and docs in the browser; hand off to Prim Desktop when you need depth.

05 · Share / permissions

Share / permissions

Teams and agents on one pack — permissions that match org boundaries.

06 · AI connectors

AI connectors (connect + scope)

ChatGPT / Claude / Cursor with scoped access — not whole-root OAuth to one Gmail.

07 · Activity / versions

Activity / versions

Humans and agents leave versions. Diff what changed under which org scope.

08 · Problem → solution storyboard

Before: three Drive icons + confused agent · After: one Prim Drive

Same human, many orgs — one plane with tenants, not three OAuth silos.

09 · Receive / sync status

Receive / sync status (secondary)

Sync is a feature of the plane — not the product name. Status stays visible, not central.

10 · Desktop teaser (optional)

Desktop teaser

Prims Desktop opens packs from Drive. Sync/share/backup are features — the drive is the product.

Stub / mockups only. Screens above are CSS UI frames for narrative. Under the hood, git / Google Drive / local / legacy takeout may still be backends — but the story is a multi-org teams cloud drive for agents, not “Drive sync for Desktop.” PNG gallery below is secondary reference chrome.

Gallery (secondary PNGs)

Earlier soft frames — keep as secondary until org/teams chrome ships.

Folder of Prim packs

Drive contents

Packs and files in the cloud drive — org-scoped, not a personal-only bag.

Share sheet for a pack

Share to teams

People and teams on one pack. Soft stub of drive sharing.

Desktop and Drive sync

Desktop ↔ Drive

Prims Desktop opens packs from the cloud drive. Sync is a feature, not the product name.

Cloud drive feel

Cloud-drive feel

Browse like a drive. Truth can still be the pack file — the plane is multi-org cloud.