The Architecture of Decentralized Collaborative Artificial Intelligence: A Blueprint for NeuralWikis

Full report

On this page

Introduction to the Collaborative Artificial Intelligence Paradigm

The historical trajectory of artificial intelligence, particularly in the domain of large language models (LLMs) and foundational multimodal architectures, has been overwhelmingly characterized by centralization. Massive technology conglomerates, equipped with vast concentrations of computational resources and proprietary datasets, have dictated the pace and direction of machine learning innovation. However, a profound architectural and philosophical shift is currently underway, transitioning the industry from isolated, monolithic model development toward a decentralized, composable, and collaborative ecosystem. The theoretical construct of a "NeuralWiki"—a platform envisioned to allow distributed users to train artificial intelligence models on crowdsourced, specialized data and dynamically merge these specialized branches into a unified intelligence—represents the culmination of recent breakthroughs in weight-space model merging, parameter-efficient fine-tuning, distributed version control, and decentralized compute orchestration. The traditional paradigm of model development necessitates joint training, a process wherein a neural network is exposed to vast datasets simultaneously. This approach is computationally exorbitant and structurally rigid. As new domains, tasks, and linguistic nuances emerge progressively over time, static models rapidly degrade in relevance. Furthermore, customizing LLMs through conventional fine-tuning introduces severe inefficiencies; organizations routinely execute numerous hyperparameter optimization experiments that produce only a single viable model, discarding the computational resources and carbon footprint associated with the suboptimal variants.1 The collaborative NeuralWiki framework directly addresses these inherent inefficiencies by bypassing the need to retrain networks from scratch. Instead, it operates entirely within the weight space of pre-trained models. This methodology enables the mathematical blending of disparate models that have been fine-tuned independently on specialized data, producing a synthetic "frankenmodel" that retains the specialized strengths of its ancestors without incurring the prohibitive costs of additional GPU training cycles.2 Early iterations of projects bearing the "NeuralWiki" nomenclature focused on relatively basic implementations, such as localized retrieval-augmented generation (RAG) using models like Mistral and vector databases populated by user-uploaded documents.4 Other historical open-source efforts utilized the term to describe actor resolution models or specific translation splits, such as Transformer NeuralWiki-Split systems for semantic tasks.5 However, the modern conceptualization of a NeuralWiki fundamentally elevates this premise. It envisions a Git-like collaborative environment where a user can intuitively "point" their local foundational model at a highly specialized branch of knowledge curated by another user, seamlessly ingesting and merging that specialty into their own local instance. The materialization of this concept requires a highly orchestrated, multi-layered technology stack. It relies on advanced evolutionary merging algorithms capable of resolving parameter interference, decentralized version control systems specifically engineered for massive tensor arrays, cooperative multi-agent verification frameworks, robust economic models to incentivize data contribution, and stringent cryptographic security protocols to prevent adversarial data poisoning. Furthermore, the ecosystem must navigate an increasingly complex legal environment surrounding copyright infringement, fair use doctrines, and algorithmic rights to erasure. The following analysis exhaustively details the theoretical, technical, operational, and regulatory architectures necessary to construct and sustain a decentralized collaborative AI platform.

The Foundational Mechanics of Weight-Space Model Merging

At the absolute core of the collaborative NeuralWiki ecosystem is the ability to combine the intelligence of multiple specialized models without requiring access to their original training data. This mechanism, known as model merging, interpolates the weight matrices of multiple neural networks into a single, more capable architecture.1 The transition from gradient-based training to weight-space merging is revolutionary because it circumvents the catastrophic forgetting typically associated with sequential fine-tuning. By operating strictly in parameter space, developers can mathematically blend models that are already experts in distinct fields—such as logic-heavy reasoning and creative writing—yielding a unified model that frequently outperforms systems constructed by heavily funded centralized entities.2 The mathematical blending of model weights has evolved significantly from early, naive linear averaging approaches, heavily supported by open-source toolkits such as MergeKit, which boasts an extensive repository of supported algorithms and an out-of-core execution model allowing merges to run entirely on CPU or with as little as 8 GB of VRAM.3

The temporal dimension of model merging introduces unique complexities not addressed by static integration. The TIME (Temporal Integration of Model Expertise) framework defines temporal model merging across three specific axes: initialization, deployment, and merging technique.7 When a contributor pushes a new specialized branch to a collaborative platform, the orchestration engine must dynamically determine whether the new expert should commence training from the merged past experts or from the original foundational base model, and whether all models should be iteratively re-merged at each temporal step to prevent knowledge decay.7 Furthermore, the integration of these models is transitioning from deterministic formulas to evolutionary optimization. Evolutionary Model Merging, facilitated by frameworks such as Mergenetic and utilized in models like Sakana AI's EvoLLM-JP, utilizes genetic algorithms to discover optimal, non-obvious combinations of open-source models across diverse domains.9 By optimizing both the parameter space (weight integration) and the data flow space (inference pathing), evolutionary merging automates the discovery of novel neural architectures, successfully merging orthogonal domains—such as non-English language processing and advanced mathematics—in ways that human researchers would be unlikely to hypothesize manually.11 Because this search occurs entirely in parameter space without requiring active gradient calculation, evolutionary merging remains computationally feasible for decentralized nodes operating consumer-grade GPUs.9

Parameter-Efficient Architectures and the Modular Expert Ecosystem

While full-weight merging provides comprehensive integration, it is computationally heavy, memory-intensive, and structurally irreversible. A collaborative NeuralWiki platform functions optimally when contributions are lightweight, modular, and easily swappable at runtime. Low-Rank Adaptation (LoRA) has emerged as the definitive mechanism for parameter-efficient fine-tuning, facilitating the creation of hyper-specialized "experts" that can be dynamically attached to a frozen, generalized base model.13 LoRA operates by freezing the pre-trained weights of the foundational model and introducing two smaller, low-rank matrices into the neural architecture.14 During the fine-tuning process, only these smaller matrices are updated, drastically reducing the required compute power and memory overhead. These matrices effectively learn the "delta" between the generalized capabilities of the base model and the specific domain knowledge introduced by the user.13 Because LoRA adapters possess a minimal parameter footprint—often constituting mere megabytes compared to the tens of gigabytes required for a full base model—they function as highly portable "mods" or plugins within the collaborative ecosystem.15 This modularity enables the concept of a user "pointing at a specialty and merging with that branch." In a decentralized platform, users can browse repositories for specific adapters targeting style, task proficiency, or safety guardrails.15 Instead of downloading a massive new model, they pull the lightweight LoRA adapter. At the runtime and inference level, these LoRA weights can be loaded, stacked, and swapped dynamically.15 Advanced serving infrastructures, such as LoRAX (LoRA eXchange) and Predibase, utilize Dynamic Adapter Loading and Continuous Multi-Adapter Batching to serve hundreds of fine-tuned LLMs simultaneously.16 Unlike conventional serving infrastructure that preloads all model weights into GPU memory during initialization, these systems load only the pretrained base weights once, dynamically swapping the specific LoRA adapters just-in-time per individual user request.16 The collaborative potential expands further with multi-LoRA frameworks. Architectures such as LoraHub enable the purposive assembly of multiple LoRA modules trained on diverse tasks, combining them fluidly with just a few demonstration examples from a new task, entirely eliminating the need for human expertise in module selection.17 This data-driven composition requires neither additional parameters nor gradients during inference.17 However, forcing multiple tasks into a single fine-tuning pathway often creates gradient conflicts. The Collaborative Multi-LoRA Experts with Achievement-based Multi-Tasks Loss (C-LoRAE) framework mitigates this by extending the standard LoRA methodology to incorporate a "universal expert" that learns shared multimodal knowledge across tasks, alongside "task-specific experts" that isolate specialized instructional features.18 This sophisticated configuration enhances generalization while maintaining the strict independence of various domains, preventing catastrophic interference when a user attempts to merge highly disparate branches of knowledge.18

Distributed Version Control: The Git-ification of Machine Learning

For a collaborative AI platform to function akin to a wiki or a traditional software repository, it necessitates a robust version control system capable of managing the ingestion, branching, and merging of neural network weights. Traditional software development relies heavily on Git; however, Git was fundamentally designed for text-based source code and is wholly incompatible with the massive binary files associated with machine learning model checkpoints.19 Attempting to track gigabyte-scale tensors in standard Git repositories leads to immediate catastrophic repository bloat and systemic failure.19 While Git Large File Storage (Git LFS) and Data Version Control (DVC) provide foundational mechanisms by replacing large binary files with small text pointers within the Git tree, they still treat model checkpoints as opaque, atomic blobs.19 Under standard LFS, any modification to a model—even a microscopic parameter adjustment—requires duplicating and uploading the entire multi-gigabyte file, destroying bandwidth and rendering collaborative branching highly inefficient.19 Git-Theta represents a critical, paradigm-shifting evolution, providing a version control system specifically engineered for the unique structural properties of machine learning models.21 Git-Theta bypasses the limitations of LFS by viewing model checkpoints not as monolithic binary files, but as a structured collection of individual parameter group tensors.20 This granular perspective allows standard Git snapshot concepts—such as commits, diffs, and merges—to be applied directly at the parameter level.20 Git-Theta introduces several revolutionary mechanics that form the backbone of a collaborative NeuralWiki ecosystem:

1. Locality Sensitive Hashing (LSH) and Custom Diff Drivers: When a user executes a git diff command to compare two versions of a model checkpoint, standard byte-based hashing produces false mismatches due to minor numerical noise or hardware-induced floating-point variances. Git-Theta solves this by employing LSH, which maps highly similar parameter groups to identical hash values. This probabilistic bounding ensures that only actual, meaningful changes to the neural parameters are flagged for review.20
2. Parameter-Efficient Update Tracking: Git-Theta seamlessly tracks sparse updates, low-rank updates (such as LoRA), and dense updates via a modular update plug-in system.20 The plug-in compares the new values against the previous values to infer the exact mathematical change, isolating the absolute minimum information required to describe that update.20 This isolated update is then compressed using msgpack and tensor serialization tools, drastically reducing the bandwidth required to push or pull model branches.20
3. Interactive Merge Conflict Resolution: When independent branches modify the exact same parameter groups—for instance, two users optimizing the same attention layer for different tasks—Git-Theta’s custom merge driver intercepts the conflict. It bypasses Git's built-in text merge and provides an interactive resolution menu. Contributors can opt to accept the current branch, accept the incoming branch, revert to a common ancestor, or execute a mathematical parameter averaging strategy (like SLERP or TIES) directly within the version control workflow, outputting a successfully merged checkpoint ready for a Git commit.20

Major repository hosts are actively adapting their infrastructures to support these collaborative ML workflows. Hugging Face, for example, has streamlined collaborative mechanics by introducing model branching and Pull Requests (PRs) that utilize custom "refs" instead of requiring users to fork massive repositories.23 Contributors can push changes directly to a special reference branch on the source repository, allowing maintainers to run continuous integration (CI) tests on modular model files and seamlessly merge validated parameter updates or LoRA adapters into the primary collaborative trunk.23 This capability, when paired with the mechanics of Git-Theta, provides the exact infrastructure necessary for a distributed community to collaboratively cultivate a NeuralWiki.

Cooperative Multi-Agent Frameworks and Continuous Feedback

A collaborative intelligence platform must not only merge static weights but also foster active cooperation and self-improvement among the models themselves. The shift toward cooperative multi-agent systems ensures that when a user points their local model at a new specialty branch, the models can communicate, evaluate, and refine their outputs collaboratively. The Collaborative Reasoner (Coral) framework is designed to bridge the gap between problem-solving and social collaboration skills in language models.27 Current post-training processes often optimize models for single-turn, isolated interactions. Coral necessitates that agents actively disagree with incorrect solutions proposed by other agents, convince their partner of the mathematically or logically correct solution, and ultimately agree as a team to commit to a final output.27 By leveraging scalable multi-agent communication frameworks like Matrix, developers can synthesize supervised and preference-finetuning data based on these conversational turns, teaching the underlying foundation models how to collaborate effectively.27 This collaborative refinement is highly pertinent to complex domain simulations. General-purpose LLMs are frequently unreliable when tasked with niche social-science or domain-specific simulations. The Verifier-Reasoner-Refiner-Tuner (VR2T) multi-agent feedback framework addresses this by iteratively evaluating simulation outputs and fine-tuning the backbone LLMs dynamically.28 Within this architecture, a "verifier" agent assesses the correctness of a response, a "reasoner" provides an explanatory diagnosis of any hallucination, a "refiner" agent revises the low-scoring output, and a "tuner" conducts supervised fine-tuning (SFT) or direct preference optimization (DPO) based on the interaction.28 Operating in this manner, the collaborative platform acts as a continuous "gym," wherein models progressively acquire specialized intelligence through continuous simulation, peer-agent feedback, and automated fine-tuning, dramatically accelerating the speed at which a NeuralWiki can assimilate and perfect new branches of knowledge.28

Decentralized Orchestration, Compute Networks, and Economic Incentives

A truly collaborative AI framework cannot rely exclusively on the concentrated, proprietary computational power of centralized corporate data centers. It must aggressively harness the latent, globally distributed Graphics Processing Units (GPUs) possessed by individual contributors, research institutions, and independent data miners.29 Decentralized AI training effectively democratizes foundational model development, but it introduces profound architectural, communication, and economic challenges.29 The primary infrastructural bottleneck in decentralized training is communication overhead. Centralized data centers utilize highly specialized, heavily optimized physical interconnects to synchronize gradients across thousands of GPUs with near-zero latency. Conversely, decentralized networks must operate over standard internet infrastructure, suffering from severe latency and bandwidth constraints that render synchronous training nearly impossible.29 To bridge this critical gap, modern decentralized training stacks implement bandwidth-aware optimizers (such as DeMo and DisTrO) and asynchronous protocols. Architectures like the Incentivized Orchestration Training Architecture (IOTA) and high-performance frameworks such as OpenDiLoCo allow robust pre-training to occur on highly heterogeneous, unreliable, and permissionless hardware.29 Furthermore, Reinforcement Learning (RL) workflows are heavily favored in these distributed environments because their forward passes are asynchronously parallelizable; sub-tasks can be distributed globally and executed simultaneously with minimal requirement for high-frequency weight synchronization.29 To sustain a globally distributed compute and data contribution network, robust economic incentive layers must be embedded directly into the foundational architecture. Data monetization is expanding rapidly, with the global data monetization market projected to reach USD 14.4 billion by 2032, driven by enterprises seeking to extract tangible economic value from proprietary data products.30 In a NeuralWiki ecosystem, monetization occurs primarily through the distribution of highly specialized LoRA adapters and curated datasets within transactional marketplaces.15 Platforms deploy several distinct monetization models to incentivize collaboration:

However, the transition toward AI-centric data monetization creates significant contributor friction if mismanaged. A prime example is the evolution of commercial stock media platforms. As entities like Shutterstock pivoted to AI data licensing, they established opaque "Data Marketplaces" designed specifically to feed computer vision and machine learning models.37 Independent contributors noted that assets diverted to these automated data catalogs were abruptly removed from the traditional commercial market, resulting in heavily diluted payouts through collective "Contributor Funds" rather than direct, per-license royalties.39 This friction underscores a critical design requirement for a collaborative NeuralWiki: transparent, immutable attribution. To avoid alienating the user base that provides the foundational intelligence, the platform must implement granular, ledger-based tracking mechanisms that accurately attribute revenue to the specific datasets, parameter updates, and LoRA adapters that demonstrably drive the final model's utility.

Legal Frameworks: Copyright, Fair Use, and DMCA Safe Harbor

The ingestion of crowdsourced data and the subsequent merging of trained neural parameters introduces an immense and volatile matrix of legal liabilities. A decentralized platform acting as a conduit for collaborative AI training must continuously navigate evolving global copyright statutes, highly contested fair use doctrines, and emerging platform liability frameworks.41 The fundamental legality of utilizing copyrighted material for generative AI training remains the subject of intense global debate and high-stakes litigation. In 2025 and 2026, the judiciary began issuing the first substantive rulings shaping the consensus regarding algorithmic training.43 A landmark decision in Bartz v. Anthropic (2025) granted summary judgment in favor of the AI developer, determining that training an LLM on legally purchased copyrighted books constituted fair use.44 The judicial ruling explicitly emphasized that AI training is "quintessentially transformative," as the neural network does not reproduce the books but instead distills linguistic patterns and styles to generate novel, uncopyrighted content, akin to a human author learning from reading.44 However, this interpretation is not universally accepted. The United States Copyright Office (USCO) released a comprehensive report indicating that while some uses are transformative, instances where AI-generated outputs are substantially similar to the training inputs present a "strong argument" for direct infringement.45 The USCO noted that when a foundation model shares the commercial purpose of the original work—producing content that appeals to the exact same audience as the training data—the fair use defense is, at best, "modestly transformative" and highly tenuous.45 For collaborative platforms hosting user-contributed model weights and training datasets, the Digital Millennium Copyright Act (DMCA) Safe Harbor provision serves as a critical, yet fragile, legal shield.46 The DMCA Safe Harbor protects service providers from secondary liability for copyright infringement committed by their users, provided the platform meets strict compliance criteria, including prompt notice-and-takedown procedures.46 Crucially, to maintain this protection, the platform must operate as a passive, non-volitional intermediary, mirroring the precedent set in Religious Technology Center v. Netcom, which established that "passive, automatic acts" in handling user data do not constitute direct infringement.48 Generative AI radically complicates this paradigm. If a collaborative NeuralWiki platform actively merges user-uploaded LoRA adapters into a primary, provider-operated base model, creating a "black-box" content generator, courts may view the platform as an active content generator rather than a passive host.48 This volitional involvement could theoretically strip the platform of its Safe Harbor protections. Therefore, a collaborative platform must implement rigorous procedural boundaries, deploying AI-driven detection systems to flag potentially infringing training data upon upload, and ensuring that the ultimate integration of model weights remains explicitly directed by the end-users (via Git-Theta branching and merging) rather than automated indiscriminately by the platform host.46

Privacy Regulations and the Mechanics of Machine Unlearning

Beyond the complexities of copyright law, privacy regulations such as the European Union’s General Data Protection Regulation (GDPR) dictate that individuals possess an algorithmic "right to be forgotten" (RTBF) or right to erasure.50 In traditional relational databases, fulfilling an RTBF request requires a simple SQL deletion command. In the context of deep learning, excising an individual's personal data from a densely entangled matrix of billions of continuous neural parameters is extraordinarily complex.51 Machine unlearning has emerged as the requisite technical response to this legal mandate.50 Because retraining massive foundational models from scratch for every deletion request is computationally and economically prohibitive, unlearning techniques attempt to retroactively isolate and erase specific concepts, behaviors, or data points without destroying the model's generalized intelligence.52

Despite rapid advancements, unlearning techniques frequently suffer from unintended performance degradation, colloquially known as "forgetting too much," necessitating ongoing research into more precise unlearning metrics and standardized evaluation protocols across the industry.52

Security Infrastructure: Defending the Collaborative Ecosystem

The open, decentralized, and collaborative nature of a wiki-style AI platform simultaneously serves as its greatest strength and its most critical vulnerability. If any network participant can freely submit training data, parameter updates, or LoRA adapters, malicious actors can systematically execute attacks designed to subvert the model's behavior, introduce bias, or install latent backdoors.55 Targeted data poisoning occurs when adversarial inputs are intentionally introduced into the training pipeline to compromise the model's subsequent outputs.55 The threat is exceptionally potent; empirical studies analyzing healthcare AI architectures demonstrate that introducing as few as 100 to 500 poisoned samples into a federated learning environment can compromise critical diagnostic models with a success rate consistently exceeding 60%.56 In a decentralized ecosystem utilizing parameter merging, these vulnerabilities are amplified by Sybil attacks. In a Sybil attack, a single adversary forges thousands of fake node identities in a permissionless compute network, flooding the aggregation protocol with malicious gradient updates to force the acceptance of a poisoned model update.57 Furthermore, the proliferation of the AI Mod Store introduces severe supply chain risks, as compromised LoRA adapters published on open marketplaces can inject vulnerabilities directly into downstream enterprise applications that dynamically load the unverified weights.56 To defend the integrity of the collaborative ecosystem, platforms must transition beyond probabilistic anomaly detection and implement deterministic, cryptographically secure validation layers. The Trustworthy Blockchain-based Federated Learning (TBFL) framework demonstrates that anchoring network trust in cryptographic identity rather than behavioral patterns significantly mitigates poisoning risks.57 By integrating Self-Sovereign Identity (SSI) standards—specifically utilizing Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs)—the platform ensures that only authenticated, legally accountable entities are permitted to contribute to the global model trunk.57 Clinical studies testing TBFL architectures demonstrated the successful neutralization of 100% of attempted Sybil attacks while maintaining high predictive performance and introducing negligible computational overhead (less than 0.12%).57 Additionally, platforms must mandate holdout validation sets. Before any user-submitted parameter update or merged branch is committed to the primary trunk via Git-Theta, it must be automatically evaluated against a strictly quarantined, known-clean dataset to detect subtle performance degradation or anomalous statistical feature distributions.55 Finally, utilizing Proof-of-Stake consensus mechanisms, multiple independent network nodes can evaluate an incoming parameter update; the update is only merged if a cryptographic supermajority of validation nodes mathematically agree that the update improves the model against a shared benchmark, providing robust systemic resilience against highly coordinated poisoning campaigns.58

Synthesis: The Operationalization of the NeuralWiki Architecture

The conceptualization and operationalization of a decentralized, collaborative NeuralWiki ecosystem require the seamless synthesis of disparate, bleeding-edge technological domains. The foundational base models provide the generalized reasoning architecture, which is subsequently expanded and accelerated via decentralized compute networks operating asynchronously across highly heterogeneous global hardware.29 Individuals and enterprise contributors isolate specific niches, training parameter-efficient LoRA adapters that capture highly specialized, localized domain knowledge.13 These distinct, evolving branches of intelligence are systematically managed through specialized version control protocols like Git-Theta, which isolate updates at the microscopic parameter group level and enable sophisticated, LSH-based diffing to track the provenance of every weight adjustment.20 When community consensus or individual user preference dictates that a specialized branch should be integrated into a local instance or the primary intelligence trunk, advanced evolutionary algorithms and interference-resolving techniques like TIES and DARE seamlessly weave the weight spaces together without requiring computationally destructive retraining.1 Simultaneously, the overarching platform operates within a stringent, highly scrutinized regulatory environment. It utilizes advanced machine unlearning techniques to comply with international privacy mandates and employs immutable cryptographic verification protocols to defend against adversarial manipulation and data poisoning.50 Economic frameworks and smart contracts ensure that those who contribute the most valuable data, the most efficient compute, or the most effective architectural modifications are compensated transparently, mitigating the friction typically associated with data extraction.33 Ultimately, this architecture represents a fundamental departure from the static, monolithic, black-box AI models produced by centralized corporate entities. By enabling asynchronous, permissionless contributions that dynamically branch and merge directly in weight space, the NeuralWiki ecosystem functions as a living computational entity—continuously evolving, mathematically optimized by the collective intelligence of its global contributors, and democratizing the future trajectory of artificial intelligence.

Works cited

1. An Introduction to Model Merging for LLMs | NVIDIA Technical Blog, accessed May 24, 2026, https://developer.nvidia.com/blog/an-introduction-to-model-merging-for-llms/
2. Model Merging \- by Lince Mathew \- Medium, accessed May 24, 2026, https://medium.com/@linz07m/model-merging-ed094ae76923
3. arcee-ai/mergekit: Tools for merging pretrained large language models. \- GitHub, accessed May 24, 2026, https://github.com/arcee-ai/mergekit
4. sidjik/local-rag-ollama: Local llm app with rag answering as a university project \- GitHub, accessed May 24, 2026, https://github.com/sidjik/local-rag-ollama
5. Activity · ahalterman/NGEC · GitHub, accessed May 24, 2026, https://github.com/ahalterman/NGEC/activity
6. Semantic Structural Decomposition for Neural Machine Translation \- ACL Anthology, accessed May 24, 2026, https://aclanthology.org/2020.starsem-1.6.pdf
7. How to Merge Multimodal Models Over Time? \- Munich Center for Machine Learning, accessed May 24, 2026, https://mcml.ai/publications/dur+25/
8. Mergekit Model Merging | Guides \- Clore.ai, accessed May 24, 2026, https://docs.clore.ai/guides/training/mergekit
9. Hey r/LocalLLaMA\! We made evolutionary model merging feasible on consumer GPUs – meet Mergenetic \- Reddit, accessed May 24, 2026, https://www.reddit.com/r/LocalLLaMA/comments/1lqndyy/hey\_rlocalllama\_we\_made\_evolutionary\_model/
10. From Task-Specific Models to Unified Systems: A Review of Model Merging Approaches, accessed May 24, 2026, https://arxiv.org/html/2503.08998v1
11. Arcee's MergeKit: A Toolkit for Merging Large Language Models \- arXiv, accessed May 24, 2026, https://arxiv.org/html/2403.13257v3
12. Evolving New Foundation Models: Unleashing the Power of Automating Model Development \- Sakana AI, accessed May 24, 2026, https://sakana.ai/evolutionary-model-merge/
13. Parameter-Efficient Fine-Tuning with LoRA Using Custom Data | DigitalOcean, accessed May 24, 2026, https://www.digitalocean.com/community/tutorials/fine-tune-llms-with-lora-for-custom-domains
14. Efficient Fine-Tuning with LoRA: A Guide to Optimal Parameter Selection for Large Language Models \- Databricks, accessed May 24, 2026, https://www.databricks.com/blog/efficient-fine-tuning-lora-guide-llms
15. The AI Mod Store: Navigating the LoRA Models Marketplace for ..., accessed May 24, 2026, https://sider.ai/blog/ai-tools/the-ai-mod-store-navigating-the-lora-models-marketplace-for-custom-results
16. Serve 100+ Fine-Tuned LLMs with LoRA Exchange on One GPU | Rubrik, accessed May 24, 2026, https://www.rubrik.com/blog/ai/23/lora-exchange-lorax-serve-100s-of-fine-tuned-llms-for-the-cost-of-one
17. LoraHub: Efficient Cross-Task Generalization via Dynamic LoRA Composition, accessed May 24, 2026, https://openreview.net/forum?id=TrloAXEJ2B
18. Collaborative Multi-LoRA Experts with Achievement-based Multi-Tasks Loss for Unified Multimodal Information Extraction \- IJCAI, accessed May 24, 2026, https://www.ijcai.org/proceedings/2025/0772.pdf
19. Collaborative AI Development: Git Strategies for Model and Data Versioning, accessed May 24, 2026, https://blog.redlinesoft.net/posts/collaborative-ai-development-git-strategies
20. \[2306.04529\] Git-Theta: A Git Extension for Collaborative ..., accessed May 24, 2026, https://ar5iv.labs.arxiv.org/html/2306.04529
21. Git-Theta: Git for ML Models | ml-news – Weights & Biases \- Wandb, accessed May 24, 2026, https://wandb.ai/byyoung3/ml-news/reports/Git-Theta-Git-for-ML-Models--Vmlldzo0NjI0NzY1
22. r-three/git-theta: git extension for {collaborative, communal, continual} model development \- GitHub, accessed May 24, 2026, https://github.com/r-three/git-theta
23. Pull requests and Discussions \- Hugging Face, accessed May 24, 2026, https://huggingface.co/docs/hub/repositories-pull-requests-discussions
24. Introducing Pull Requests and Discussions \- Hugging Face, accessed May 24, 2026, https://huggingface.co/blog/community-update
25. Pull request checks \- Hugging Face, accessed May 24, 2026, https://huggingface.co/docs/transformers/pr\_checks
26. Contribute to Transformers \- Hugging Face, accessed May 24, 2026, https://huggingface.co/docs/transformers/en/contributing
27. Collaborative Reasoner: Self-improving Social Agents with Synthetic Conversations | Research \- AI at Meta, accessed May 24, 2026, https://ai.meta.com/research/publications/collaborative-reasoner-self-improving-social-agents-with-synthetic-conversations/
28. LLM Agents as Social Scientists: A Human–AI Collaborative Platform for Social Science Automation \- arXiv, accessed May 24, 2026, https://arxiv.org/html/2604.01520v1
29. Decentralized AI Training: How Crypto Can Power Open AI | Galaxy, accessed May 24, 2026, https://www.galaxy.com/insights/research/decentralized-ai-training
30. Data Monetization Strategy \- IBM, accessed May 24, 2026, https://www.ibm.com/think/insights/data-monetization-strategy
31. Intelligence at scale: Data monetization in the age of gen AI \- McKinsey, accessed May 24, 2026, https://www.mckinsey.com/capabilities/business-building/our-insights/intelligence-at-scale-data-monetization-in-the-age-of-gen-ai
32. Share and Monetize AI Models Securely on the AI Data Cloud \- Snowflake, accessed May 24, 2026, https://www.snowflake.com/en/blog/share-monetize-ai-models-snowflake/
33. What Are the Top 7 Monetization Models for AI Marketplace Platforms?, accessed May 24, 2026, https://www.getmonetizely.com/articles/what-are-the-top-7-monetization-models-for-ai-marketplace-platforms
34. The Economics of Data: Monetization Models for Modern Enterprises \- Medium, accessed May 24, 2026, https://medium.com/@eddamilare/the-economics-of-data-monetization-models-for-modern-enterprises-46aa837dad91
35. Best AI-Focused Blockchain Networks: 10 Projects Shaping Crypto's Future | Yellow.com, accessed May 24, 2026, https://yellow.com/research/best-ai-focused-blockchain-networks-10-projects-shaping-cryptos-future
36. 4 Decentralized AI Projects to Watch in 2024 \- Coinmetro, accessed May 24, 2026, https://www.coinmetro.com/learning-lab/4-decentralized-ai-projects-to-watch-in-2024
37. Recent Shutterstock experience : r/stockphotography \- Reddit, accessed May 24, 2026, https://www.reddit.com/r/stockphotography/comments/1qf7ew3/recent\_shutterstock\_experience/
38. All of a sudden 4/5 of all my uploads on Shutterstock are "Eligible for data licensing" \- Reddit, accessed May 24, 2026, https://www.reddit.com/r/stockphotography/comments/1m8vz7w/all\_of\_a\_sudden\_45\_of\_all\_my\_uploads\_on/
39. Shutterstock Data Licensing \- How does it work? : r/stockphotography \- Reddit, accessed May 24, 2026, https://www.reddit.com/r/stockphotography/comments/168ueq7/shutterstock\_data\_licensing\_how\_does\_it\_work/
40. Shutterstock \- Eligible for data licensing only : r/stockphotography \- Reddit, accessed May 24, 2026, https://www.reddit.com/r/stockphotography/comments/1nbsenc/shutterstock\_eligible\_for\_data\_licensing\_only/
41. Copyright and Artificial Intelligence | U.S. Copyright Office, accessed May 24, 2026, https://www.copyright.gov/ai/
42. Copyright and Artificial Intelligence, Part 3: Generative AI Training Pre-Publication Version, accessed May 24, 2026, https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-3-Generative-AI-Training-Report-Pre-Publication-Version.pdf
43. AI Trends for 2026 \- Copyright Litigation Shifts from Training Data to AI Outputs, accessed May 24, 2026, https://www.mofo.com/resources/insights/260210-ai-trends-for-2026-copyright-litigation
44. Green Light—For Now: First Set of Rulings Favoring AI Training on Copyrighted Content, accessed May 24, 2026, https://www.brookskushman.com/insights/green-light-for-now-first-set-of-rulings-favoring-ai-training-on-copyrighted-content/
45. Copyright Office Weighs In on AI Training and Fair Use | Skadden, Arps, Slate, Meagher & Flom LLP, accessed May 24, 2026, https://www.skadden.com/insights/publications/2025/05/copyright-office-report
46. DMCA Safe Harbor and the Rise of AI Content: What's Changing in 2025 | PatentPC, accessed May 24, 2026, https://patentpc.com/blog/dmca-safe-harbor-and-the-rise-of-ai-content-whats-changing-in-2025
47. DMCA Safe Harbor Rules and Their Application to AI Platforms | PatentPC, accessed May 24, 2026, https://patentpc.com/blog/dmca-safe-harbor-rules-and-their-application-to-ai-platforms
48. From safe harbours to AI harbours: reimagining DMCA immunity for the generative AI era | Journal of Intellectual Property Law & Practice | Oxford Academic, accessed May 24, 2026, https://academic.oup.com/jiplp/article/20/9/605/8221820
49. Reasonable Intelligence: How Should Platforms Be Held Accountable For AI-Assisted Copyright Infringement?, accessed May 24, 2026, https://jipel.law.nyu.edu/reasonable-intelligence/
50. Forget Me Not? Machine Unlearning's Implications for Privacy Law, accessed May 24, 2026, https://digitalcommons.law.uw.edu/cgi/viewcontent.cgi?article=2162\&context=faculty-articles
51. Machine Unlearning in 2024 | Ken Ziyu Liu \- Stanford Computer Science, accessed May 24, 2026, https://ai.stanford.edu/\~kzliu/blog/unlearning/
52. Teaching large language models to “forget” unwanted content | IBM, accessed May 24, 2026, https://www.ibm.com/think/insights/machine-unlearning
53. Machine unlearning for LLMs \- IBM Research, accessed May 24, 2026, https://research.ibm.com/blog/llm-unlearning
54. The Right to be Forgotten in Pruning: Unveil Machine Unlearning on Sparse Models \- arXiv, accessed May 24, 2026, https://arxiv.org/html/2507.18725v1
55. What Is Data Poisoning? \[Examples & Prevention\] \- Palo Alto Networks, accessed May 24, 2026, https://www.paloaltonetworks.com/cyberpedia/what-is-data-poisoning
56. Data Poisoning Vulnerabilities Across Health Care Artificial Intelligence Architectures: Analytical Security Framework and Defense Strategies \- Journal of Medical Internet Research, accessed May 24, 2026, https://www.jmir.org/2026/1/e87969/
57. Trustworthy Blockchain-based Federated Learning for Electronic Health Records: Securing Participant Identity with Decentralized Identifiers and Verifiable Credentials \- arXiv, accessed May 24, 2026, https://arxiv.org/html/2602.02629v1
58. A robust and verifiable federated learning framework for preventing data poisonous threats in e-health \- PMC, accessed May 24, 2026, https://pmc.ncbi.nlm.nih.gov/articles/PMC13036150/
59. A robust and verifiable federated learning framework for preventing data poisonous threats in e-health \- Frontiers, accessed May 24, 2026, https://www.frontiersin.org/journals/public-health/articles/10.3389/fpubh.2026.1762346/full