Skip to content

SESSIONS — OPEN PANEL handoff log

Append-only session journal for zero-loss handoff. Newest session on top. Read CANON.md first (single source of truth); this file records how we got here, what was assumed, what’s unverified, and what to do next.


Session 001 — 2026-06-13 — Founding design package created

Section titled “Session 001 — 2026-06-13 — Founding design package created”

Operator: Christian (chris@todie.io). Agent: Claude Opus 4.8 (1M), background job. Repo created this session: /home/ctodie/projects/openpanel (standalone git repo, local only, no remote). First commit 8d998a6 (GPG-signed, good sig). This SESSIONS.md is a follow-up commit.

Draft specifications for mobile + web + desktop apps and a backend; design workstreams; architect foundational + operating contracts; develop base brand identity — for a comic book publishing company that:

  • makes comics available for free,
  • monetizes everything downstream — exclusive IP licenses for manufacturing merchandise, strategic partnerships, and licenses,
  • is a tax-exempt organization with revenue sharing for officers and strict reinvestment of residuals,
  • with a downstream for-profit sister org.

Then: “put this in a separate repo” → done (this repo). Then: “push all session context into a SESSIONS.md” → this file.

12 design docs (~3,500 lines) + README + this log. Map:

  • CANON.md — anchor / single source of truth (brand, stack, legal thesis, terminology, open decisions).
  • brand/BRAND_IDENTITY.md
  • business/BUSINESS_MODEL.md, business/LEGAL_STRUCTURE.md
  • product/PRODUCT_SPEC_OVERVIEW.md, product/SPEC_WEB.md, product/SPEC_MOBILE.md, product/SPEC_DESKTOP.md, product/SPEC_BACKEND.md
  • architecture/FOUNDATIONAL_CONTRACTS.md, architecture/OPERATING_CONTRACTS.md
  • delivery/WORKSTREAMS.md

How it was built (method, for reproducibility)

Section titled “How it was built (method, for reproducibility)”
  1. Wrote CANON.md by hand to lock all cross-cutting decisions FIRST (coherence anchor).
  2. Fanned out 11 parallel subagents, one per doc, each instructed to read CANON.md and conform. This keeps names/stack/legal-thesis consistent across docs.
  3. Assembled README.md index + verified signed commit.
  • Implication for next session: if you change a decision, change CANON.md first, then re-derive affected docs (optionally re-fan-out). Don’t edit downstream docs in isolation.

Key decisions locked this session (provisional, operator can override)

Section titled “Key decisions locked this session (provisional, operator can override)”
  • Brand (working): OPEN PANEL (umbrella) / OPEN PANEL FOUNDATION (501c3) / VARIANT (for-profit). Rationale: “open panel” = open-access + comic panel; “variant” = the premium collectible cover = the monetized layer on top of the free standard issue. Alternates parked: {INKWELL/INKWELL RIGHTS}, {LONGBOX/LONGBOX LICENSING}, {SPLASHPAGE/SPLASH}.
  • Jurisdiction ASSUMED: United States (501(c)(3) + Delaware C-corp). NOT confirmed by operator.
  • Stack: Next.js (web) · React Native/Expo (mobile) · Tauri/Rust (desktop) · shared @openpanel/reader TS engine · Supabase + Rust(axum) backend · Cloudflare R2+CDN · Stripe · Comic Package Format (CPF) as the open media manifest.
  • Entity relationship default: Option A (Foundation owns IP, licenses to an independently- owned VARIANT). Option B (wholly-owned taxable subsidiary) noted as conservative fallback.
  • Creator economics default: Hybrid (Foundation gets free-distribution license + first commercial option; creator co-owns + earns a % of net licensing). Placeholder share 50%.
Section titled “⚠️ The load-bearing legal finding (do NOT lose this)”

“Revenue sharing for officers” inside a 501(c)(3) is illegal — private inurement (IRC §501(c)(3)) + excess-benefit/intermediate sanctions (IRC §4958). Resolution baked into the design:

  1. Nonprofit officers → reasonable compensation only, via the §4958 rebuttable-presumption safe harbor (independent comp committee + comparability data + contemporaneous docs).
  2. Officer wealth-sharing lives in VARIANT (equity / profit interests) — legal on the for-profit side.
  3. Mandatory reinvestment of nonprofit residuals, codified as board policy.
  4. Bridge = arm’s-length IP license; royalties to the Foundation generally UBIT-exempt under §512(b)(2).
  • Sharpest open risk flagged for counsel: IRC §512(b)(13) attribution. If officers’ VARIANT equity is attributed back to the Foundation (control), the royalties could be taxed as UBIT and Option A’s protection erodes. Counsel must set the safe ownership/control ceiling.
  • This whole package is a DRAFT and is NOT legal/financial/tax advice. Requires qualified nonprofit/tax counsel before any filing. (Agent is not a lawyer.)

Open decisions carried forward (CANON §10 — still unanswered)

Section titled “Open decisions carried forward (CANON §10 — still unanswered)”
  1. Jurisdiction — confirm US, or correct (reshapes the entire legal doc).
  2. Brand name — approve OPEN PANEL/VARIANT or pick an alternate set.
  3. Entity relationship — Option A (license, default) vs Option B (owned sub).
  4. Creator economics — Model 1 / 2 / Hybrid (default) + the creator %.
  5. Depth/priority — which workstream to deepen into a build-ready spec first.

Assumptions & unverified items (honesty audit)

Section titled “Assumptions & unverified items (honesty audit)”
  • Jurisdiction = US: assumed, unverified. Everything legal/tax depends on it.
  • All IRC citations (§501(c)(3), §4958, §512(b)(2), §512(b)(13)) are drafting-level and must be confirmed by counsel — treat as direction, not authority.
  • Economics (P&Ls, creator %, unit economics) are illustrative placeholders, clearly labeled as such in the docs.
  • FOUNDATIONAL_CONTRACTS.md ran long (581 lines) by design — concrete schemas, not padding.
  • No remote was created and nothing was pushed externally (operator sign-off not given for that).
  • No code was written — this is a design/spec package only.
  • Repo: /home/ctodie/projects/openpanel, branch main (or default), 2 commits expected after this file (1: package, 2: SESSIONS.md). Local only, GPG-signed, no remote.
  • Nothing deployed, nothing filed in Linear (this venture is net-new and separate from the operator’s RINA/Reverie/Ops work).

Suggested next steps (agent’s recommendation)

Section titled “Suggested next steps (agent’s recommendation)”
  1. Run a quick decision interview on the 5 open decisions (jurisdiction first).
  2. If keeping: create a GitHub remote and push (operator sign-off needed — outward action).
  3. Deepen one workstream into a build-ready spec. Agent’s pick: WS6 Rights & Royalty Ledger — it is the bridge between product and money and gates all monetization.
  4. Engage nonprofit/tax counsel on the §512(b)(13) ceiling before any entity filing.