<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>可扩展监督 on 硅基 AGI · 智能体学习与测评</title><link>https://guijiagi.com/tags/%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9B%91%E7%9D%A3/</link><description>Recent content in 可扩展监督 on 硅基 AGI · 智能体学习与测评</description><generator>Hugo</generator><language>zh-cn</language><copyright>本站内容采用 CC BY-NC-SA 4.0 国际许可协议授权</copyright><lastBuildDate>Thu, 16 Jul 2026 10:23:00 +0800</lastBuildDate><atom:link href="https://guijiagi.com/tags/%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9B%91%E7%9D%A3/index.xml" rel="self" type="application/rss+xml"/><item><title>AI对齐的开放问题：可扩展监督、可解释性与可纠正性</title><link>https://guijiagi.com/posts/b2-f761472e/</link><pubDate>Thu, 16 Jul 2026 10:23:00 +0800</pubDate><guid>https://guijiagi.com/posts/b2-f761472e/</guid><description>探讨AGI时代AI对齐面临的核心开放问题，涵盖可扩展监督、机械可解释性与可纠正性挑战</description></item><item><title>AI对齐技术前沿：可扩展监督与AI反馈</title><link>https://guijiagi.com/posts/ai-alignment-frontier-scalable-oversight/</link><pubDate>Tue, 30 Jun 2026 11:25:00 +0800</pubDate><guid>https://guijiagi.com/posts/ai-alignment-frontier-scalable-oversight/</guid><description>深入探讨2026年AI对齐技术的前沿方向，包括可扩展监督、AI反馈（RLAIF）、辩论机制等，分析技术原理与实践挑战</description></item><item><title>AI对齐2026：从RLHF到Constitutional AI的演进</title><link>https://guijiagi.com/posts/ai-alignment-2026-rlhf-to-constitutional/</link><pubDate>Tue, 30 Jun 2026 10:15:00 +0800</pubDate><guid>https://guijiagi.com/posts/ai-alignment-2026-rlhf-to-constitutional/</guid><description>系统梳理2026年AI对齐技术的完整演进路径，从RLHF到Constitutional AI再到可扩展监督，分析各方案的优劣与适用场景</description></item><item><title>超级对齐：当 AI 超越人类智能时如何保持控制</title><link>https://guijiagi.com/posts/superalignment-2026-controlling-ai-beyond-human-intelligence/</link><pubDate>Sun, 28 Jun 2026 10:11:00 +0800</pubDate><guid>https://guijiagi.com/posts/superalignment-2026-controlling-ai-beyond-human-intelligence/</guid><description>2026 年超级对齐研究进展：从可扩展监督到机械可解释性，探讨当 AI 能力超越人类时的安全控制框架</description></item></channel></rss>