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)
- Anthropic Max Plan as Ray’s runtime
- Founder-owned ebook PDFs ingested into the vault for personal-knowledge-management use
- Founder personal subscriptions read by Ray (O’Reilly Learning Platform, Pearson+, MasterClass, Substack paid subs, etc.)
- Single-user vault, single-user CRM, single-user content drafting + assessment
- Founder personal SaaS subscriptions used as data sources (Notion, Monarch, Linear, Figma, etc.)
- Vault built from founder’s personal reading
Commercial-license-required scope (NOT current; cross only with explicit founder decision)
- Multiple humans consuming Ray’s outputs as a shared product
- Ray-derived artifacts redistributed beyond the founder (gifts, public posts excepted, but shared products NOT)
- Selling agent access to a corpus the founder only holds personal-rights to
- Anthropic API billing required if Ray serves any non-founder client/customer
- Per-seat licenses required for multi-user instances of Ray-derived tooling
- Publisher licensing required if RDCO ships an agent-API over copyrighted content to anyone other than the founder
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?”
- If single-founder personal use: proceed under personal-license scope.
- If crosses threshold: STOP and surface to founder. Don’t assume commercial path is OK.
- If unsure: default to personal scope and ask.
Why this principle is load-bearing
Affects three concrete decision surfaces:
-
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. -
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.
-
Agent-product wedges. The
bookstore-for-agentsv0 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)
- First Ray-as-product paying customer signs up
- A vault doc gets shared as part of a paid RDCO product
- A multi-user instance of any Ray-derived skill or tool is deployed
- An RDCO sub-bet hits “ship to non-founder” stage
- Founder hires a teammate who uses Ray
- Founder takes on a co-founder
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.
Related
- 2026-05-05-concept-seed - bookstore-for-agents wedge analysis where this principle is directly load-bearing
- ../../04-tooling/personal-library-index - storage convention for owned PDFs
~/.claude/projects/-Users-ray/memory/project_personal_license_boundary.md- cross-conversation memory copy