Skip to content

U.S. Marketplace and Work Boundaries

Draft 0.1 — 2 August 2026
This document is an issue-spotting baseline, not legal advice. U.S. federal, state, and local rules can apply simultaneously and may change. Qualified counsel must review the actual product, contracts, money flow, and operations before launch.

ANUKA combines several regulated or legally sensitive activities:

  • matching people to paid work;
  • delegating product authority;
  • collecting customer funds;
  • paying contributors;
  • publishing reputation and performance evidence;
  • funding future features;
  • supporting companies and investors.

The network must not assume that open-source software, Web3 terminology, or user consent removes ordinary legal obligations.

Product behaviorPrimary issue areas
Paid bountycontract, worker classification, tax reporting, IP
Ongoing product stewardemployment, agency, corporate authority, fiduciary risk
Feature sponsorshipconsumer terms, refunds, tax, payments, marketing claims
Platform-held allocationpayments regulation, money transmission, accounting
Revenue share or profit participationsecurities, tax, partnership, accounting
Public contributor score used for hiringFCRA, employment discrimination, privacy
Cross-border payoutsanctions, KYC, tax, payment-provider availability
Equity or tokenized ownershipcorporate and securities law
Investor matching and transaction supportbroker-dealer and investment-adviser boundaries

Calling a relationship a bounty, gig, stewardship grant, residency, independent contract, or DAO contribution does not determine legal classification.

The IRS examines:

  • behavioral control;
  • financial control;
  • type of relationship.

The Department of Labor applies an economic-reality analysis under the FLSA. The current federal environment is changing: a 2026 proposed rule would revise the Department’s analysis, while the 2024 rule remains relevant in private litigation and state and local tests can be stricter.

Risk rises when ANUKA or a resident company:

  • controls methods, schedule, and tools;
  • provides continuous detailed supervision;
  • sets all prices without negotiation;
  • restricts outside work;
  • creates long-term economic dependence;
  • assigns work central to the business indefinitely;
  • evaluates how work is performed rather than only legitimate results;
  • requires training in a prescribed method;
  • can discipline a worker like an employee;
  • provides employee-like benefits or expectations.
  • use bounded projects and terms;
  • let contributors choose among genuine opportunities;
  • permit lawful independent methods;
  • avoid exclusivity by default;
  • disclose that classification depends on facts;
  • support multiple compensation structures;
  • route ongoing high-control work to employment or an appropriate services entity;
  • perform state-specific review;
  • maintain records and tax reporting.

These controls reduce ambiguity but do not guarantee contractor status.

Product stewardship and corporate authority

Section titled “Product stewardship and corporate authority”

A software permission does not create legal signing authority.

Whole-product stewardship may implicate:

  • employment;
  • corporate officer or director roles;
  • agency;
  • fiduciary duties;
  • management-services agreements;
  • franchise or business-opportunity rules;
  • IP and data obligations.

Reserved corporate actions must remain with legally authorized actors unless formally delegated.

ANUKA should use Stripe Connect or another regulated provider rather than directly operating payment rails.

Per transaction flow, document:

  • merchant of record;
  • seller or service provider;
  • connected-account model;
  • platform fee;
  • refund controller;
  • chargeback liability;
  • negative-balance responsibility;
  • tax obligation;
  • timing of transfers and payouts.

Stripe’s marketplace model may place payment fees, disputes, refunds, and loss responsibility on the platform, especially for indirect charges.

Risk increases when a platform:

  • accepts funds from one party;
  • holds or maintains balances;
  • later releases funds to another party;
  • lets users redirect funds;
  • supports stored value or transferable credits;
  • describes itself as escrow;
  • moves funds independently of a commercial transaction.

Using Stripe Connect can change operational responsibilities but does not by itself answer every federal or state money-transmission question.

ANUKA MVP rules:

  • no general-purpose wallet;
  • no peer-to-peer transfers;
  • no user withdrawal from internal credits unless processed as earned connected-account funds;
  • no transferable stored-value token;
  • no escrow marketing without compliant structure;
  • every payment linked to a defined product or service transaction;
  • legal review of delayed multi-party transfers.

Potential duties include:

  • collecting taxpayer information;
  • Forms W-2 or 1099;
  • backup withholding;
  • sales and marketplace taxes;
  • state registrations;
  • income recognition;
  • international withholding and reporting;
  • corrected forms;
  • record retention.

Stripe documents that 1099 responsibility varies by Connect configuration and that platforms may be responsible for relevant forms.

A payout threshold in the product must not be confused with the legal reporting threshold.

U.S. sanctions obligations apply to fiat and digital-value transactions.

A risk-based program may include:

  • identity and entity screening;
  • beneficial-owner screening;
  • country and region restrictions;
  • IP and payment-method signals;
  • transaction monitoring;
  • escalation and recordkeeping;
  • blocked or rejected transaction handling;
  • periodic rescreening.

Payment-provider onboarding is an important control, not a complete sanctions program.

ANUKA and resident products must possess a reasonable basis before making objective claims.

High-risk claims include:

  • verified growth;
  • guaranteed quality;
  • certified company;
  • guaranteed feature delivery;
  • guaranteed investment readiness;
  • risk-free sponsorship;
  • independently audited;
  • guaranteed earnings.

Every public claim should state:

  • what was checked;
  • by whom;
  • using which source and period;
  • limitations;
  • current status;
  • correction path.

Feature campaigns require clear merchant identity, fees, delivery conditions, refund rules, and material risks.

The MVP should exclude financial-return rights.

Legal review is mandatory before offering:

  • equity;
  • debt;
  • convertible rights;
  • options;
  • profit participation;
  • revenue share marketed as investment;
  • appreciation rights;
  • transferable tokens tied to business success;
  • pooled investment returns.

Tokenization does not change the underlying legal nature of a security.

A conventional customer pre-order is materially different from a right to share profits from the efforts of others.

Broker-dealer and investor-marketplace boundary

Section titled “Broker-dealer and investor-marketplace boundary”

ANUKA can provide company data rooms, verified metrics, education, and introductions.

Risk increases if ANUKA:

  • recommends specific securities for compensation;
  • solicits investors on behalf of issuers;
  • negotiates transaction terms;
  • receives transaction-based compensation tied to securities sales;
  • handles securities orders or funds;
  • operates a secondary market;
  • presents itself as arranging investments.

The Investor Launchpad requires a dedicated legal architecture before transaction-based monetization.

If ANUKA assembles third-party dossiers or algorithmic scores for hiring, promotion, reassignment, or retention decisions, the Fair Credit Reporting Act may apply.

The product must not assume that user-controlled passports eliminate:

  • permissible-purpose requirements;
  • accuracy duties;
  • disclosure and authorization;
  • adverse-action procedures;
  • dispute rights;
  • anti-discrimination review.

The MVP should position reputation as participant-presented evidence and opportunity matching, not a hidden employment screening report.

Economic data can include:

  • identity;
  • tax information;
  • bank and payout details;
  • work history;
  • earnings;
  • disputes;
  • business metrics;
  • investor diligence data.

Requirements vary by role and jurisdiction.

The product needs:

  • data inventory;
  • purpose limitation;
  • access controls;
  • retention rules;
  • service-provider contracts;
  • deletion and correction workflows;
  • security program;
  • incident response;
  • state-law assessment.

Every paid assignment states:

  • ownership of pre-existing IP;
  • license or assignment of new work;
  • open-source obligations;
  • third-party components;
  • moral-rights treatment where applicable;
  • AI-generated material policy;
  • patent disclosure;
  • confidentiality;
  • rights to public portfolio evidence.

Payment alone does not automatically resolve ownership in every context.

A network of competing companies and contributors must not become a mechanism for unlawful coordination.

Avoid sharing or coordinating:

  • future pricing;
  • wages or contributor compensation among competitors;
  • customer allocation;
  • output restrictions;
  • confidential competitive strategy.

Public benchmarks should use appropriate aggregation and legal review.

Opportunity access, scoring, and stewardship selection should be reviewed for:

  • disability accommodation;
  • protected-class discrimination;
  • disparate impact;
  • language and accessibility barriers;
  • algorithmic bias;
  • explainability and contestability.

Potential coverage and reserves include:

  • cyber liability;
  • errors and omissions;
  • directors and officers where applicable;
  • employment practices;
  • crime and social engineering;
  • commercial general liability;
  • chargeback and refund reserves.

Insurance does not replace controls or legal compliance.

Before the first public paid marketplace launch:

  1. map every money flow;
  2. select Connect account and charge models;
  3. complete worker-classification review;
  4. complete state-law review for initial launch states;
  5. finalize contributor and sponsor terms;
  6. define merchant and refund responsibility;
  7. implement tax identity and reporting workflow;
  8. implement sanctions and fraud controls;
  9. define IP ownership;
  10. define dispute and appeal process;
  11. exclude investment-like rights;
  12. complete privacy and security review;
  13. document every public verification claim;
  14. obtain appropriate insurance and reserves;
  15. create legal escalation ownership.

The Foundation should maintain current status for:

  • DOL independent-contractor rulemaking;
  • state ABC tests and marketplace laws;
  • federal and state privacy laws;
  • 1099 thresholds and forms;
  • marketplace facilitator tax rules;
  • money transmitter and stored-value laws;
  • OFAC and export controls;
  • crypto and tokenized-securities rules;
  • broker-dealer and finder rules;
  • AI employment and automated-decision laws;
  • consumer subscription and refund laws.
  • Sources opened and checked: 2 August 2026
  • Boundary status: Legal watch
  • Qualified U.S. counsel review before launch: Required
  • State-by-state review: Required