GitHub Org Creation Before LLC Formation — Research Note

Status: research-only. This document does NOT constitute legal or tax advice. Before filing or acting, consult a business-formation attorney and CPA licensed in Pennsylvania (or your state of residence at the time of filing). Also consult the engaged IP/tech-transactions attorney (Matthew Crosby, per reference_attorneys.md) on the IP and ToS-authority questions specifically. Last updated: 2026-05-06. Sources as of that date — verify freshness before any action.

TL;DR (3 sentences)

On 2026-05-06, Kristerpher Henderson is creating a GitHub organization (raxx-app, plan: GitHub Team at $4/user/month) by attesting "I hereby accept the GitHub Customer Agreement on behalf of my organization and confirm that I have the authority to do so" — before any LLC or corporation named "Raxx" legally exists. California Business and Professions Code §17910 (primary source below) requires a fictitious business name (DBA) filing within 40 days whenever a sole proprietor transacts business under a name that does not include their legal surname — "Raxx" does not contain "Henderson," so DBA exposure may be triggered depending on where Kristerpher is resident and operating. The core open questions — authority attestation risk, IP chain of title, and DBA status — require resolution by Matthew Crosby (attorney) before the repo transfer from MooseQuest/TradeMasterAPI to raxx-app/TradeMasterAPI is treated as permanent.

Facts (with citations)

GitHub org creation facts

• Org slug: raxx-app
• GitHub URL: https://github.com/raxx-app
• Account type selected: "A business or institution"
• Name of business or institution entered: "Raxx"
• Date of creation: 2026-05-06
• Plan: GitHub Team — $4/user/month (billed monthly or annually) Source: https://github.com/pricing
• Plan features relevant to PR #1202 context:
• Required reviewers on protected branches: included in Team plan
• Environment protection rules with deployment branches/secrets: Team plan includes environment deployment branches and secrets; full environment protection rules with required approvers may require GitHub Enterprise (verify at https://docs.github.com/en/actions/deployment/targeting-different-environments/managing-environments-for-deployment)
• Source: https://github.com/pricing

GitHub Customer Agreement — authority attestation

• GitHub's on-org-creation flow presents the attestation: "I hereby accept the GitHub Customer Agreement on behalf of my organization and confirm that I have the authority to do so."
• GitHub's Corporate Terms of Service defines "Customer" as "the company or organization that has entered into this Agreement with GitHub." It requires the signatory to be "an employee or agent of such Party with all necessary authority to bind such Party." Source: https://docs.github.com/en/site-policy/github-terms/github-corporate-terms-of-service
• The GitHub Customer Agreement (General Terms, March 2025) repeats the authority-to-bind representation. PDF available at: https://assets.ctfassets.net/8aevphvgewt8/luAPHjODK4vAYIpwisJfC/88a1961a9c7fcbb8d02a86d5d4635295/GCA_-_2025_03_-_GitHub_Customer_Agreement_General_Terms_-_FINAL_locked.pdf
• Customer agreements index: https://github.com/customer-terms
• Key tension: As of 2026-05-06, "Raxx" as an entity does not legally exist. The entity that GitHub's agreement names as Customer — "Raxx" — has no articles of organization or incorporation on file with any state. The signer (Kristerpher Henderson) is attesting authority to bind an entity that has no legal existence. Whether this creates contract-formation risk or personal-liability exposure is unsourced from primary sources — confirm with attorney (Matthew Crosby).

Repository transfer — technical facts

• Source repo: MooseQuest/TradeMasterAPI (current working repo)
• Target org: raxx-app/TradeMasterAPI (post-transfer)
• GitHub documents that on transfer: issues, pull requests, wiki, stars, and watchers transfer with the repo. Forks remain associated with the repo. Source: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
• Old URLs (github.com/MooseQuest/TradeMasterAPI/...) redirect automatically to new location. Creating a new repo at the old path permanently deletes those redirects. Source: same
• GitHub org ownership transfer (if Raxx LLC needs to later "own" the org) requires appointing a new owner and manually updating billing details; departure of the current owner does not auto-update payment information. Source: https://docs.github.com/en/organizations/managing-organization-settings/transferring-organization-ownership
• GitHub's transfer docs contain no IP-transfer or legal-entity language. The platform treats org ownership as an access-control matter, not a property-law matter. Confirm IP chain-of-title implications with attorney.

DBA / fictitious business name — California

• Operator residence: Kristerpher spends approximately 4 months/year in California (per questions-for-cpa.md §J4 noting CA nexus considerations). State of primary residence is Pennsylvania (per CPA questions referencing PA LLC, PA returns). Both states may be relevant depending on where business activity is deemed to occur.
• California rule: California Business and Professions Code §17910 requires any person who "regularly transacts business in this state for profit under a fictitious business name" to file a fictitious business name statement within 40 days of commencing such business. Source: https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC&sectionNum=17910.
• CalOSBA confirms: a sole proprietor must file a DBA if they operate under a name that "does not contain the owner's surname." Source: https://calosba.ca.gov/for-small-businesses-and-non-profits/set-up-your-business-in-california/
• "Raxx" does not contain "Henderson." If Kristerpher is deemed to be transacting business in California under the name "Raxx" (e.g., by entering it as the GH org's business name and using the org for commercial activity while present in CA), the 40-day filing window may begin on 2026-05-06.
• California DBA filing is at the county clerk level (not Secretary of State). After filing, publication in a newspaper of general circulation is required once a week for four successive weeks, with an affidavit of publication filed within 30 days of the last publication date. Source: https://calosba.ca.gov/for-small-businesses-and-non-profits/set-up-your-business-in-california/

• Relevant counties for Kristerpher's CA time: unsourced — confirm with attorney which county applies based on where CA activity occurs.

• Pennsylvania rule: Pennsylvania requires a fictitious name registration for any entity (including sole proprietor) doing business under a name other than its legal name. Filing is with the Pennsylvania Department of State. Primary source to verify: https://www.dos.pa.gov/BusinessCharities/Business/RegistrationForms/Pages/default.aspx (unsourced detail — confirm filing fee and publication requirement with formation attorney or CPA).

Trademark dovetail

• USPTO Reg. 7779396 covers "Raxx" (per project_matthew_crosby_email.md memory). The GH org business name "Raxx" and slug raxx-app align with that mark.
• USPTO trademark registrations record the owner of the mark as of the filing date. If the mark is currently registered in Kristerpher Henderson's personal name (or in MooseQuest's name), and the GH org names "Raxx" as the business, the public-facing record does not yet match the trademark owner. Source for TSDR lookup: https://tsdr.uspto.gov/
• When Raxx LLC is formed, a trademark assignment from the current owner of record to Raxx LLC must be recorded with the USPTO via the Electronic Trademark Assignment System (ETAS). Source: https://www.uspto.gov/trademarks/maintain/assignment (unsourced confirmation of ETAS fees — verify at USPTO site before filing)

Data processing terms

• GitHub's Corporate Terms treat private repository content as Customer's Confidential Information, protected under the agreement's confidentiality provisions. Source: https://docs.github.com/en/site-policy/github-terms/github-corporate-terms-of-service
• GitHub's Data Protection Agreement governs data processing: https://github.com/customer-terms/github-data-protection-agreement PDF (September 2023): https://assets.ctfassets.net/8aevphvgewt8/DaflLjyuIt6un69xg3n6W/9e51773d6687d4d5f4c29fc63c115d24/GITHUB-20230922-GitHubDataProtectionAgreement.pdf
• Raxx repos contain Raptor (backend, securities-execution-adjacent) and MQ-A (algo layer) code per project memory. The GitHub ToS does not contain securities-execution- specific clauses (per research above), but the DPA's data-controller vs. data-processor framing may interact with GDPR obligations if EU users are ever onboarded. Confirm with attorney and software-architect agent.
• GitHub's standard ToS (non-corporate) notes that GitHub may use content to train AI features. The Customer Agreement / Corporate Terms offer stronger confidentiality protections for private repos. Confirm which agreement tier applies to the Team plan at the point of org creation. Source: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service

Options compared

This table is for research framing only. Attorney input required before selecting any option.

Jurisdiction flags

Timing / deadlines

Questions for attorney (Matthew Crosby)

These questions are preparation material for the next attorney meeting. They are not answered here.

J — GitHub Org Pre-LLC Authority and IP (added 2026-05-06)

1. Authority attestation risk. On 2026-05-06, Kristerpher accepted GitHub's Customer Agreement attestation — "I hereby accept the GitHub Customer Agreement on behalf of my organization and confirm that I have the authority to do so" — entering "Raxx" as the business name, before any LLC or corporation named "Raxx" is filed with any state. Does this attestation create personal liability exposure for Kristerpher? Does it create a contract-formation problem (i.e., is the agreement unenforceable because one "party" has no legal existence)?

2. IP chain of title — org transfer mechanics. When Raxx LLC is formed, what is the cleanest documented path to: (a) transfer GitHub org ownership from Kristerpher's personal control to the LLC, and (b) ensure that the IP assignment to the LLC (covering code, designs, and trademarks) is properly recorded so that the GH org ownership change and the IP assignment are consistent? Is a formal IP assignment agreement + org ownership change sufficient, or is there a bill of sale or additional instrument needed?

3. DBA / fictitious name risk — California. Cal. BPC §17910 requires a DBA filing within 40 days when a sole proprietor transacts business under a name not containing their legal surname. By entering "Raxx" as the GitHub org's business name and using the org for commercial development activity (while spending ~4 months/year in CA), has Kristerpher triggered the CA fictitious business name requirement? If so, which county clerk is the correct filing jurisdiction, and what is the publication requirement?

4. DBA / fictitious name risk — Pennsylvania. Does the same scenario trigger a PA fictitious name registration requirement? What is the filing fee and process, and does it interact with or precede LLC formation?

5. Trademark owner matching. USPTO Reg. 7779396 records a specific owner. The GitHub org now names "Raxx" as the business. Once Raxx LLC is formed, should the ETAS trademark assignment from the current owner of record to Raxx LLC be executed before the LLC is publicly associated with the raxx-app GitHub org (e.g., on the product website), or is the sequence flexible? What is the risk of the LLC operating publicly under a mark whose ETAS assignment has not yet been recorded?

6. GitHub ToS interaction with securities-adjacent code. Raxx's private repos contain Raptor (backend) and MQ-A (algorithmic strategy layer), which are adjacent to securities-execution tooling. GitHub's ToS do not appear to contain securities-specific restrictions (per this research), but does the GitHub Data Protection Agreement's data-controller / data-processor framing create any obligation for Raxx as controller once the GH org houses production code that processes user trade data? Any ToS clause that would restrict housing such code on GitHub?

Priority for this consult: J1 and J2 are highest priority — they determine whether any corrective action is needed before the repo transfer is made permanent. J3 may have a 40-day hard deadline from 2026-05-06 (CA DBA, approx. 2026-06-15) — surface early.

Questions for CPA

M — GitHub Org Business Account — Tax and Schedule C treatment (added 2026-05-06)

1. GitHub Team plan — Schedule C vs. entity deduction. The GitHub Team plan is billed at $4/user/month under the raxx-app org, entering "Raxx" as the business name, before Raxx LLC is formed. Should this expense be treated as a Schedule C business expense for Kristerpher's sole proprietorship in 2026 (pre-formation), or does it become a pre-formation start-up cost under IRC §195 once Raxx LLC is formed? Apply the same convention being established under questions-for-cpa.md §L (pre- formation expense convention).

2. GitHub org named as "Raxx" — any tax consequence. Entering "Raxx" as the GitHub org business name (before entity formation) creates an implicit DBA situation for sole-proprietor tax purposes. Does this have any Schedule C reporting implication — e.g., should the business name on Schedule C match the DBA, and if so, does the GH org creation date function as the DBA commencement date?

Sources

Primary sources used in this document:

• GitHub pricing: https://github.com/pricing
• GitHub Corporate Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-corporate-terms-of-service
• GitHub Terms of Service (individual): https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
• GitHub Customer Agreement — General Terms (March 2025 PDF): https://assets.ctfassets.net/8aevphvgewt8/luAPHjODK4vAYIpwisJfC/88a1961a9c7fcbb8d02a86d5d4635295/GCA_-_2025_03_-_GitHub_Customer_Agreement_General_Terms_-_FINAL_locked.pdf
• GitHub Customer Agreement index: https://github.com/customer-terms
• GitHub Data Protection Agreement (September 2023): https://assets.ctfassets.net/8aevphvgewt8/DaflLjyuIt6un69xg3n6W/9e51773d6687d4d5f4c29fc63c115d24/GITHUB-20230922-GitHubDataProtectionAgreement.pdf
• GitHub — Transferring a repository: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
• GitHub — Transferring organization ownership: https://docs.github.com/en/organizations/managing-organization-settings/transferring-organization-ownership
• California Business and Professions Code §17910: https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC&sectionNum=17910.
• CalOSBA — Set Up Your Business in California: https://calosba.ca.gov/for-small-businesses-and-non-profits/set-up-your-business-in-california/
• USPTO TSDR (for Reg. 7779396 status lookup): https://tsdr.uspto.gov/
• USPTO trademark assignment (ETAS): https://www.uspto.gov/trademarks/maintain/assignment
• Pennsylvania DOS — Business Registration: https://www.dos.pa.gov/BusinessCharities/Business/RegistrationForms/Pages/default.aspx (unsourced detail — verify fees and process)

Before acting on any item in this document, consult Matthew Crosby (IP/tech-transactions attorney, already engaged per reference_attorneys.md) on questions J1–J6, and a CPA licensed in Pennsylvania on questions M1–M2. Formation counsel (in pipeline per reference_attorneys.md) should be looped in on entity timing and DBA filing before the 40-day CA window closes (approx. 2026-06-15 if trigger date is 2026-05-06).

Addendum — RAXX §2(d) Conflict Intersection (added 2026-05-06)

(This addendum cross-references Matthew Crosby's 2026-05-05 18:13 UTC reply re the cited RAXX trademark registration. Full conflict analysis: docs/legal/research/raxx-tm-conflict-analysis-2026-05-06.md.)

Crosby's signal

Crosby's 2026-05-05 letter confirms that the USPTO will analyze the cited registration's identification text — not the registrant's real-world commerce — when evaluating likelihood of confusion under §2(d). The cited RAXX registration (Reg. 7779396, Ramp Payment Solutions LLC, Class 36) covers broad payment-processing and financial-transaction services described in fourteen discrete service recitations, including "financial transaction services, namely, providing secure commercial transactions and payment options" and "payment processing of funds transferred through an online payment platform." The examiner may find these commercially related to options-trading software even across different international classes (Raxx is in Classes 9 and 42).

Governing authority: TMEP § 1207.01(a)(iii) — the USPTO relies on the identification, not the specimen, in §2(d) analysis. Source: https://tmep.uspto.gov/RDMS/TMEP/print?version=current&href=TMEP-1200d1e5044.html

Interaction with this document

The GitHub org creation (github.com/raxx-app, business name "Raxx," 2026-05-05 UTC) is relevant to the conflict analysis in two ways:

1. Pivot cost is rising. If Crosby ultimately advises a mark pivot (Option F in the conflict analysis doc), github.com/raxx-app must be renamed, all repositories relocated or re-referenced, CI/CD pipelines updated, and any external references to the org URL corrected. The repo is also being transferred from MooseQuest/TradeMasterAPI to raxx-app/TradeMasterAPI. Each committed repo push under the raxx-app org increases the cost of a future pivot.

2. GitHub org as a commercial-use date. The creation date (2026-05-05 UTC) is a documentable date of public commercial use of the RAXX mark in the software-technology channel. This is a favorable data point for a potential OA response (distinguishing Raxx software from Ramp Payment Solutions' bar/restaurant POS), but it does not establish priority over the cited registration's filing date. Crosby should assess whether documenting this date is useful for the OA response strategy.

3. Business name attestation. Entering "Raxx" as the GitHub org business name (accepted via the GitHub Customer Agreement) is a public record that Raxx is operating as a going business concern. This strengthens the channels-of-trade argument (Raxx = software company, not payment processor) but also commits the operator to the brand in a way that makes a pivot more disruptive and more visible.

Questions for Crosby surfaced by this intersection

These are staged in the new Section K of docs/business/questions-for-attorney.md:

• K1: §2(d) probability assessment given the full cited identification text
• K2: §14 cancellation vulnerability — pull file wrapper on Serial 97826727
• K3: Coexistence agreement feasibility with Ramp Payment Solutions LLC
• K4: OA cost and timeline if we file and receive a §2(d) refusal
• K5: Pivot-vs-fight threshold given current brand investment
• K6: Whether the GitHub org creation date is useful for OA response documentation