01-projects / bookstore-for-agents

personal license boundary

Mon May 04 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·principle ·status: active
licensingcopyrightscoperdco-operating-modelbookstore-for-agents

Personal-license vs commercial-license boundary

Founder-articulated 2026-05-05 in Discord, in the thread following the first founder-owned PDF ingestion (Beck “TDD by Example”). Sets the default scope under which Ray operates and the trigger conditions for flipping that scope.

The principle (founder’s exact framing)

“It’s fine within copyright laws. It’s if Ray ever becomes useful to a whole company or multiple people that that line starts to blur. Same sort of line for using the Anthropic Max Plan vs API billing. This is all for personal knowledge management and application to my solo businesses. It’s not broad distribution of an individual license.”

Personal-license-OK scope (current default for ANY RDCO action)

Commercial-license-required scope (NOT current; cross only with explicit founder decision)

Decision rule for any new ingestion or runtime question

Ask: “is this single-founder personal use, or does it cross the multi-user / shared-product / external-distribution threshold?”

Why this principle is load-bearing

Affects three concrete decision surfaces:

  1. Book / content ingestion. Founder-owned PDFs go in ~/Documents/library/books/ (per ~/rdco-vault/04-tooling/personal-library-index.md). Ray reads, vault gets primary-source assessment. No publisher license needed. Crosses scope if RDCO ever shares those vault notes externally as a product.

  2. AI infrastructure billing. Anthropic Max Plan is a personal-use license. If Ray ever serves a paying RDCO customer or a multi-user Ray-as-product instance, billing must flip to API or per-seat commercial. The Max Plan covers Ray-as-personal-COO, not Ray-as-multi-tenant-SaaS.

  3. Agent-product wedges. The bookstore-for-agents v0 wedge (personal-library-RAG) is INSIDE this scope: each user runs it on their own owned library with their own credentials. Each user is a “single-founder personal use” instance from the licensing perspective. Scaling to “shared corpus across users” is exactly where publisher relations becomes mandatory.

Trigger events that should flip scope (and prompt founder review)

When any of these happen, Ray should pause and surface “we just crossed the personal-vs-commercial scope threshold; we need to re-license X, Y, Z” to the founder.