AI Intelligence Center — An AI-Powered Global Newsfeed

RPS (Reversed Plasticity SFT) is a novel LLM post-training methodology inspired by neuroplasticity, mimicking the human cognitive trajectory from high-plasticity childhood learning (basic skills) to low-plasticity adulthood (specialized expertise) to enhance the reliability of Qwen3-8b in complex program synthesis. ▶ Paradigm Shift: RPS upends traditional SFT by mapping learning rates to "model plasticity." It employs a two-stage schedule—high LR for foundational data followed by a 90% reduction in LR for complex data—ensuring deep knowledge integration without structural degradation. ▶ Empirical Gains: Preliminary benchmarks on Qwen3-8b demonstrate that RPS mitigates the logic breakdown often seen in high-complexity coding tasks, yielding higher consistency and execution accuracy. Bagua Insight The emergence of RPS signals a shift from brute-force data ingestion to sophisticated "cognitive stage management" in LLM fine-tuning. Its brilliance lies in addressing the tension between catastrophic forgetting and overfitting. By treating the second stage of training as a "fine-tuning scalpel" rather than a sledgehammer, RPS allows models to acquire niche domain expertise while anchoring their foundational reasoning. For teams operating with constrained compute but high-performance requirements in vertical domains, RPS offers a blueprint for achieving "expert-level" output from mid-sized models. It proves that biological heuristics still hold significant untapped potential for optimizing AI training efficiency. Actionable Advice Developers focused on code generation, mathematical reasoning, or specialized sectors like legal/med-tech should immediately pilot the RPS strategy. The key is to rigorously categorize datasets by "difficulty gradients" and synchronize learning rate decays with data complexity rather than simple step counts. Furthermore, since RPS shows exceptional promise in 8B-class models, it should be prioritized as a cost-effective strategy for enhancing the logical robustness of edge-deployed or specialized LLMs.

Event Core Meta’s legal department has officially issued a legal notice (likely a Cease and Desist) to the creator of the Heretic project. This move, targeting a tool within the LocalLLaMA ecosystem, centers on alleged violations of Meta’s Llama Community License and trademark policies, signaling a shift in how the tech giant polices its "Open Weights" territory. ▶ Trademark Enforcement: Meta is aggressively asserting control over the "Llama" brand, targeting any project that risks brand dilution or implies an unsanctioned official endorsement. ▶ The "Open" Paradox: This incident underscores that Llama is not "Open Source" by OSI standards; it is a proprietary asset under a restrictive license that Meta is now weaponizing to prune its ecosystem. ▶ Strategic Pivot: The legal pressure on Heretic suggests Meta is moving from a phase of rapid ecosystem seeding to one of strict regulatory and brand consolidation. Bagua Insight Meta’s strategy with Llama has always been a tactical moat-building exercise rather than pure altruism. By serving Heretic, Meta is drawing a hard line in the sand: you can build on Llama, but you cannot build over it or around its branding. This is a classic Big Tech maneuver—subsidize the ecosystem with "free" tech to kill competition, then enforce strict governance once the industry is hooked. For the decentralized AI community, this is a wake-up call. The "Open Weights" movement remains fragile and beholden to the legal whims of Menlo Park. Heretic is likely just the first of many projects to be "rationalized" as Meta seeks to sanitize the Llama ecosystem for enterprise-grade optics. Actionable Advice 1. Adopt "Clean Room" Naming: Developers should pivot away from using "Llama" as a prefix or suffix. Use vendor-neutral branding and relegate model compatibility to the technical documentation to mitigate trademark infringement risks.2. License Due Diligence: Any startup leveraging Llama weights must conduct a rigorous legal audit of their distribution mechanisms, especially if they involve modified weights or bypass Meta’s standard access gates.3. Hedge with True Open Source: To avoid platform risk, maintain architectural flexibility to swap Llama for truly open models (e.g., Mistral or Apache 2.0 licensed models) should Meta further tighten the screws on its community license.