Federated-Learning

TL;DR for operators Federated LLM fine-tuning sounds attractive until someone asks the rude operational question: who is actually paying for the compute, memory, and communication on the devices? The paper behind DevFT proposes a useful answer: do not fine-tune the full model end-to-end from the first round. Start with a compact submodel, train it federatively, transfer the learned LoRA parameters forward, then expand the model in stages until it reaches the full target size.1 The authors call this Developmental Federated Tuning, and yes, the developmental psychology metaphor is a little enthusiastic. Fortunately, the mechanism is more interesting than the metaphor. ...

TL;DR for operators SpoQFL is a proposal for making quantum federated learning less fragile by teaching noisy clients when to speak and when to stay quiet.1 In ordinary federated learning, each client trains locally and sends model updates to a server. In quantum federated learning, those clients are quantum models running under noisy intermediate-scale quantum conditions, which means their updates can be corrupted by gate errors, measurement uncertainty, decoherence, and client-to-client hardware variation. ...

TL;DR for operators CoRAG is not “RAG, but with more documents.” It is a way to let multiple organizations train a shared retrieval-augmented model while keeping their labeled question-answer data local. That matters because labels are usually the expensive, sensitive, commercially revealing part. Market documents, manuals, policies, public reports, and technical references are often easier to share than the annotations that say which answer was correct, for whom, and under what business condition. Tiny distinction. Large legal bill avoided. ...