[{"data":1,"prerenderedAt":4282},["ShallowReactive",2],{"site-settings":3,"all-writing":83},{"id":4,"title":5,"currentFocus":6,"description":7,"extension":8,"footer":9,"headline":12,"home":14,"introduction":7,"location":28,"meta":29,"name":5,"pages":30,"services":49,"stem":72,"theme":73,"writingTopics":75,"__hash__":82},"site\u002Fsettings\u002Fsite.yml","Quilibra","正在上班当牛马。","这是我自己部署的个人主页，用于记录我的一些事情并维护我的一些服务。","yml",{"icp":10,"credit":11},"皖ICP备2026023522号","DESIGNED & BUILT BY GPT-5.6 IN CODEX",{"prefix":13,"emphasis":5},"你好，这里是",{"kicker":15,"systemsLabel":16,"latestWriting":17,"modules":23,"dock":24},"个人主页 \u002F 持续施工中","SYSTEMS",{"enabled":18,"title":19,"linkLabel":20,"emptyLabel":21,"limit":22},true,"最近写下","全部文章","暂无文章",3,{"services":18,"rgbAssembly":18},{"writing":25,"services":26,"about":27},"文章","服务","关于","China · UTC+8",{},{"writing":31,"services":35,"about":43},{"intro":32,"seoDescription":33,"emptyLabel":34},"随笔、学习、交易，以及对日常变化的观察。","随笔、学习、交易与观察。","没有找到匹配的文章。",{"intro":36,"seoDescription":37,"accessTitle":38,"accessNotes":39},"统一入口，分别运行。尚未开放的服务会在域名和登录保护完成后上线。","开发环境、相册、NAS 和运行状态。","访问说明",[40,41,42],"公开入口由 VPS 上的 Nginx 提供 HTTPS 与反向代理。","家中服务通过 Tailscale 连接，不直接暴露 NAS 或路由器端口。","开发环境、相册与影音库仍需各自完成身份验证。",{"seoDescription":44,"focusLabel":45,"topicsLabel":46,"contactLabel":47,"contactCopy":48},"一些基本信息，以及这个网站目前用来做什么。","正在做的事","关注的主题","联系","不是，你联系我干嘛？",[50,56,61,66],{"name":51,"description":52,"href":53,"state":54,"icon":55,"showOnHome":18},"Code","浏览器里的开发环境","https:\u002F\u002Fcode.example.com","soon","code",{"name":57,"description":58,"href":59,"state":54,"icon":60,"showOnHome":18},"Photos","照片备份和浏览","https:\u002F\u002Fphotos.example.com","image",{"name":62,"description":63,"href":64,"state":54,"icon":65,"showOnHome":18},"NAS","文件与存储管理","https:\u002F\u002Fnas.example.com","hard-drive",{"name":67,"description":68,"href":69,"state":70,"icon":71,"showOnHome":18},"Status","服务可用性与故障记录","https:\u002F\u002Fstatus.example.com","online","activity","settings\u002Fsite",{"defaultAccent":74},"#006eff",[76,77,78,79,80,81],"看盘看线","捣鼓电脑","折腾NAS","踢踢野球","看看科普","玩币练胆","rzNwl0NJTHNz-9N0akkaLLep7T3BRIkBtg-HrZ3RTZ8",[84,149,192,291,395,3371,3543,3762,3961,4140],{"id":85,"title":86,"body":87,"category":131,"date":132,"description":133,"extension":134,"meta":135,"navigation":18,"path":136,"publishedAt":137,"seo":138,"slug":139,"stem":140,"tags":141,"updated":147,"__hash__":148},"writing\u002Fwriting\u002F2026-07-27-intp-sbti-personality-review.md","INTP的执行折扣：从SBTI测试到性格复盘",{"type":88,"value":89,"toc":124},"minimark",[90,94,97,100,105,108,112,115,118,121],[91,92,93],"p",{},"做了个 SBTI 测试，结果 THAN-K（感恩者），匹配度 73%，15 个维度命中 8 个。SBTI 本身是娱乐向的东西，B 站起源，讽刺行为类型指标，不用太当真。但测试维度里有些数据值得看看。",[91,95,96],{},"我的关键维度：S1 自尊自信偏低（3），S2 自我清晰度高（5），E1 依恋安全感高（6）。低自信 + 高自我清晰度，意思是知道自己是什么样的人，但对自己的评价偏低。73% 匹配度本身说明测试只照到了对外包容的那一面，没照到对内自我批判的那一面。",[91,98,99],{},"我的 MBTI 是 INTP。两个东西不是同一赛道--MBTI 有荣格理论背书，SBTI 是纯娱乐传播工具。但 INTP + THAN-K 的组合有内在逻辑：INTP 是冷的逻辑解构内核，THAN-K 是温和包容的外壳，两者分层而非矛盾。S1 低自信 + S2 高自我清晰度是典型的 INTP 内耗特征。",[101,102,104],"h2",{"id":103},"intp-的优势","INTP 的优势",[91,106,107],{},"逻辑强、系统思维、不受框架约束。看问题习惯拆到底层逻辑，不会被表面叙事带着走。这些东西在之前的交易认知讨论里已经验证过--看到量化系统会去拆合成期货的机制，看到抖音观点会自动分析信息源动机和逻辑链条。",[101,109,111],{"id":110},"intp-的核心缺陷","INTP 的核心缺陷",[91,113,114],{},"执行折扣。完美主义卡在启动条件上，想清楚了但做的时候摩擦极高。情感处理滞后，不是没有感受，是感受排在逻辑后面，等逻辑处理完了情绪才冒出来，有时候已经晚了。",[91,116,117],{},"THAN-K 的包容性其实是在给 INTP 的高标准兜底--对自己要求高，但对外表现温和，这是一种自我保护机制。整体来说是工具箱强但使用说明书烂，上限高但实现率取决于能不能跨越执行折扣。",[101,119,120],{"id":120},"回到测试本身",[91,122,123],{},"THAN-K 实际占比 7.76%，不算真正罕见。这类测试的价值不在于结果准不准，而在于给了个外部视角看自己。73% 匹配度恰好说明了一个人格标签装不下完整的自我，剩下 27% 的不匹配可能比匹配的部分更有信息量。",{"title":125,"searchDepth":126,"depth":126,"links":127},"",2,[128,129,130],{"id":103,"depth":126,"text":104},{"id":110,"depth":126,"text":111},{"id":120,"depth":126,"text":120},"随笔","2026-07-27","做了SBTI测试得到THAN-K，结合MBTI的INTP，梳理理性内核与温和外壳的组合以及执行摩擦的根源。","md",{},"\u002Fwriting\u002F2026-07-27-intp-sbti-personality-review","2026-07-27T00:26:15+08:00",{"title":86,"description":133},"intp-sbti-personality-review","writing\u002F2026-07-27-intp-sbti-personality-review",[142,143,144,145,146],"MBTI","SBTI","INTP","性格","认知",null,"gd3Zm2yODzA0PcysBaNZOxUUS_CkxThxsq0Fdri1SSY",{"id":150,"title":151,"body":152,"category":131,"date":132,"description":180,"extension":134,"meta":181,"navigation":18,"path":182,"publishedAt":183,"seo":184,"slug":185,"stem":186,"tags":187,"updated":147,"__hash__":191},"writing\u002Fwriting\u002F2026-07-27-transition-meaninglessness.md","悬空期：什么都没意思的时候",{"type":88,"value":153,"toc":178},[154,157,160,163,166,169,172,175],[91,155,156],{},"感到迷茫。人活着要么劳碌要么做自己的事，但没有产出。不工作就没收入，工作了就是出卖劳动力。上班是牛马，不上班又该干嘛？",[91,158,159],{},"不是找不到具体的事做，是什么都没意思。项目做好了也就几个 star，打游戏、做项目都感觉在虚度。有钱没钱又怎样？钱够花就行，就算有 10 亿也就是有底气，但实际又怎样？金钱、名誉、权力，似乎都无所谓。",[91,161,162],{},"不是不想活。活着挺好的，只是不知道做什么有意义，意义是什么。",[91,164,165],{},"想了一圈，最后落到的结论很朴素：人活着就行了，该做什么做什么，尽量多元化，保证好身体。给自己立一条底线：保证身体，做项目时多站站走走。",[91,167,168],{},"但现在这些都做不到。懒。",[91,170,171],{},"不想被安慰，想听客观理性的。直说就是：状态是执行摩擦高 + 外部锚点少。论文还没交、还没去合肥、项目没成型，处在一个悬空期，目标完成后的锚点缺失加上输入输出失衡，空洞感是这个阶段的正常产物。",[91,173,174],{},"悬空期不适合想大问题。两个实际的事：一是久坐不动会加剧懒和无意义感，每天走 30 分钟有数据支撑，不是鸡汤；二是启动成本问题，目标要小到可笑，不要一上来就规划宏大计划。项目短期给不了意义感，但能给具体感--有具体的事做，至少不会整天想\"意义是什么\"这种没有答案的问题。",[91,176,177],{},"等落地了节奏自然会起来。现在能做的最小动作是什么，比想清楚人生意义重要得多。",{"title":125,"searchDepth":126,"depth":126,"links":179},[],"一段找不到意义感的时期，关于劳碌、回报和执行摩擦的诚实记录。",{},"\u002Fwriting\u002F2026-07-27-transition-meaninglessness","2026-07-27T00:21:58+08:00",{"title":151,"description":180},"transition-meaninglessness","writing\u002F2026-07-27-transition-meaninglessness",[188,189,190],"迷茫","意义","状态","t7T4SfZ_rtsAVrgWujfPWgj8LfEq3D_dAaWMtlfCxQ8",{"id":193,"title":194,"body":195,"category":279,"date":132,"description":280,"extension":134,"meta":281,"navigation":18,"path":282,"publishedAt":283,"seo":284,"slug":285,"stem":286,"tags":287,"updated":147,"__hash__":290},"writing\u002Fwriting\u002F2026-07-27-crypto-40u-experiment.md","40U学费：从负和博弈到跨市场认知",{"type":88,"value":196,"toc":271},[197,200,203,206,209,213,216,219,223,226,229,232,236,239,242,246,249,252,255,258,262,265,268],[101,198,199],{"id":199},"永续合约是负和博弈",[91,201,202],{},"抖音上有一段对话：我说永续合约是散户对定价没有意义的负和博弈，靠这个发财基本不可能；作者回的是任何行业顶端才能赚钱；我又说自己只是普通人，稳定赚钱只有量化套利，但那需要工程和数学能力，主观交易做不到。",[91,204,205],{},"永续合约负和博弈的判断是准确的，散户无定价权也是事实。之前看到一个爆仓博主 3k 做到几百万 U 再爆仓，大概率是高杠杆顺势重仓，运气成分大于能力。作者那句\"顶端才能赚钱\"是正确的废话。",[91,207,208],{},"但\"只有量化套利\"这句话，我说的时候不是在指路，是一种无奈的总结。我知道答案在那里，但那条路跟我没关系--期权、滑点、费率是什么都要从头研究，根本不懂套利，也不愿意投入时间去尝试。",[101,210,212],{"id":211},"_40u当学费","40U当学费",[91,214,215],{},"我只有 40U，考虑用永续合约当赌场，目的是了解这个生态、DEX、去中心化交易所、加密货币逻辑、衍生品交易是什么。不考虑靠这个赚钱。",[91,217,218],{},"这个框架是合理的。40U 当学费做实操学习，比看文章有效得多，亏完也就 40U，但获得的是真实系统认知。唯一要提前做的是在心里把这 40U 标记为已花出去的学费，不要因为小赚了就开始加仓--那是体验性操作滑向真实赌博最常见的节点。",[101,220,222],{"id":221},"区块链被ai抢了梦","区块链被AI抢了梦？",[91,224,225],{},"刷到一个叫 Danielli 的视频，说 AI 好像把区块链的梦抢走了，区块链十几年发展远不如 AI 两年影响大，现在只剩投机资产和交易所收割流动性。",[91,227,228],{},"论点有观察基础但逻辑跳跃。AI 和区块链解决的不是同一类问题，拿改变日常生活的速度来比较是错误框架。评论区多数是噪音，少数有效观点比如\"全球支付是真实用例\"、\"AI 是科技升级、区块链是金融升级\"。",[91,230,231],{},"我在评论区说了区块链牛逼的是去中心化可编程智能合约，未来作为数字支付基础设施、跨国转账、大宗商品定价都大有所为，加了个 🌝。",[101,233,235],{"id":234},"的社交防御","🌝 的社交防御",[91,237,238],{},"在抖音评论区这种环境里，凭啥要和这帮人认真讨论？要么骗流量要么情绪化。加 🌝 是主动压低信噪比，预防别人觉得我懂得多喜欢装然后骂我。这是理性的社交防御策略，不是不自信。认真展开论证的成本远大于收益。",[91,240,241],{},"唯一要注意的是这个习惯用久了可能迁移到不该用的场合，在真正值得认真讨论的地方也习惯性给观点加保护性包装。",[101,243,245],{"id":244},"加密市场能给a股投资者提供什么","加密市场能给A股投资者提供什么",[91,247,248],{},"突然想到，我现在主战场是 A 股，加密货币市场不就相当于给我提供了一个对冲的方法吗？",[91,250,251],{},"严格说，\"对冲 A 股\"这个表述不准确。对冲成立的前提是两资产之间有稳定相关性，但加密和 A 股的相关性不稳定。更现实的问题是 40U 和 A 股仓位规模差距悬殊，对冲不了任何波动。",[91,253,254],{},"但换一个角度看，BTC\u002FETH 走势和美国流动性、通胀、美股走势高度相关，A 股有自己的政策逻辑，和美股加密的分离有时是真实存在的。链上永续合约平台还能交易股票永续合约等其他品种，相当于一个低成本的跨市场观察窗口。",[91,256,257],{},"所以 40U 的战略意义不只是学费，也是扩展市场认知边界的实验仓。跨市场配置降低单一市场风险敞口，这个思维框架本身是成熟的。",[101,259,261],{"id":260},"从40u到1w-usdt","从40U到1w USDT",[91,263,264],{},"之后可能有 1w USDT，可以考虑试一试。",[91,266,267],{},"1w USDT 规模下对冲逻辑开始有实际意义。但前提是 40U 阶段要真的学到东西：搞清楚资金费率机制、爆仓逻辑、链上平台的清算机制和中心化交易所的区别、自己的操作纪律能否和 A 股一样有框架。40U 如果只是随便玩没有形成结构性认知，1w USDT 进去大概率重复散户路径。",[91,269,270],{},"等 40U 跑完一个周期再说，到时候自己会知道准没准备好。",{"title":125,"searchDepth":126,"depth":126,"links":272},[273,274,275,276,277,278],{"id":199,"depth":126,"text":199},{"id":211,"depth":126,"text":212},{"id":221,"depth":126,"text":222},{"id":234,"depth":126,"text":235},{"id":244,"depth":126,"text":245},{"id":260,"depth":126,"text":261},"交易","从一段抖音评论出发，梳理永续合约、区块链价值和加密市场作为A股投资者认知补充的实际意义。",{},"\u002Fwriting\u002F2026-07-27-crypto-40u-experiment","2026-07-27T00:18:24+08:00",{"title":194,"description":280},"crypto-40u-experiment","writing\u002F2026-07-27-crypto-40u-experiment",[279,288,289,146],"加密货币","区块链","OjTLJ5ZBfXbUP2-ux-98zAUFVtqDclQ6IfelwXfjUnM",{"id":292,"title":293,"body":294,"category":279,"date":382,"description":383,"extension":134,"meta":384,"navigation":18,"path":385,"publishedAt":386,"seo":387,"slug":388,"stem":389,"tags":390,"updated":147,"__hash__":394},"writing\u002Fwriting\u002F2026-07-26-market-strategy-exploration-price-route.md","从非农数据到价格路线：一段市场策略探索的复盘",{"type":88,"value":295,"toc":373},[296,300,303,306,310,313,316,320,323,326,329,332,335,339,342,345,348,351,355,358,361,364,367,370],[101,297,299],{"id":298},"非农数据与黄金这不是统计套利","非农数据与黄金：这不是统计套利",[91,301,302],{},"非农就业数据弱 -> 黄金上涨 -> 次日继续上涨，这个现象看起来像可以利用的统计套利。但仔细想，这不算真正的统计套利，因为有方向暴露--你在赌一个特定方向，而不是对冲掉方向只赚价差。",[91,304,305],{},"更关键的问题是样本量。非农一个月才一次，几十年历史也就几百次，难以做统计显著性检验。即使这个 post-announcement drift 效应真实存在，也早被机构交易了，edge 很薄。执行容量不是瓶颈，edge 太薄才是真正的问题。当作研究练习或者辅助过滤条件可以，单独开策略不值得。",[101,307,309],{"id":308},"个人能靠容量小机构看不上获利吗","个人能靠\"容量小、机构看不上\"获利吗",[91,311,312],{},"逻辑方向是对的。机构受监管约束、有容量天花板、策略需要可标准化，这些结构性门槛留出了一些空间。比如小盘股流动性缺口、可转债条款博弈、打新、低流动性 LOF 折溢价。",[91,314,315],{},"但要注意，这块地已经有游资和量化工作室在挖了。竞争对手从机构换成了游资，不等于没竞争。",[101,317,319],{"id":318},"景气度投资有启发但不是我的方向","景气度投资：有启发但不是我的方向",[91,321,322],{},"看到一个基金经理的访谈思路：从申万一级行业中找成长性好的行业，挑龙头公司，买在基本面右侧、卖在行业周期走完。",[91,324,325],{},"这是主流的\"景气度投资\"框架，不是独创。\"买基本面右侧、不买股价右侧\"这个核心洞察确实有价值，和我自己的均线系统是正交的。但判断行业成长性和周期拐点本质是主观判断力，不可回测、有后视镜偏差。而且标的多为大市值龙头，容量大，机构挤满，和\"容量小、机构看不上\"的思路完全相反。",[91,327,328],{},"同时接触量化研究和主观判断型方法论两条路，注意力是零和的。新内容可以当认知输入，但要警惕把它变成新的主线分走注意力。",[101,330,331],{"id":331},"为什么选择先走量化路线",[91,333,334],{},"更系统化、止损清晰有预期、不会亏大钱。机构能扛判断错误，我扛不住。以后系统成熟了可以考虑拓展，但拓展的触发条件要具体化--回测引擎完成、多周期验证执行纪律、资金曲线连续达标，而不是凭模糊感觉判断\"时候到了\"。",[101,336,338],{"id":337},"创新药etf与横截面动量","创新药ETF与横截面动量",[91,340,341],{},"抖音上看到关于创新药 ETF 的评论：赢家通吃导致个股难选，不如买 ETF，\"别自己选啊，市场资金帮你选了\"。结合盘面观察，强势股跌得少、弱势股跌停。",[91,343,344],{},"这个逻辑其实是自洽的：用价格的相对强度（横截面动量）代替基本面判断。赢家通吃 -> 个股难选 -> 价格显示资金持续认可的方向 -> 跟着价格走等于间接跟着选股结果走。和我自己的技术分析哲学同源，是对现有时间序列动量系统的维度补充。",[91,346,347],{},"这里有一个重要的区分：用价格代替基本面（创新药案例的逻辑，价格永远替代基本面，不是过渡）和\"价格系统化后转向基本面研究\"（实质是走向已经拒绝的主观投资路线）是两条不同的路。不要在心态上悄悄开后门。",[91,349,350],{},"最终收敛很清楚：研究价格而非行业。价格路线可以在时间序列（GARCH、协整）和横截面（相对强度）两个维度做深，始终不涉及需要主观基本面判断力的领域。这是风险收益比更优的深化路径，不是能力局限。",[101,352,354],{"id":353},"btc与流动性相关性没那么简单","BTC与流动性：相关性没那么简单",[91,356,357],{},"\"BTC 和流动性高度相关\"--机制方向合理：流动性宽松 -> 资金溢出到高 beta 资产。但\"高度相关\"的说法有问题：相关性随周期不稳定，因果方向常被倒因为果，短视频叙事是事后归因。要用于策略得自己做滚动窗口回测验证，不能直接采信定性描述。",[91,359,360],{},"币圈反应快不等于定价效率高。反应快是 24\u002F7 交易 + 高频算法 + 高杠杆踩踏造成的基础设施结果，不代表信息处理效率高。真正的效率要看有没有超调后的回吐纠偏--如果存在，说明第一反应含大量噪音。这类品种更适合\"事后确认 + 右侧进场\"，而不是追第一时间反应。",[101,362,363],{"id":363},"抖音网赌小作文",[91,365,366],{},"刷到抖音上一个网赌小作文：女生从基金到黄金到股票充值游戏、期货爆仓、最终网赌。叙事很流畅，但流畅度和真实性成反比--风险递增顺序过于工整、时间线被压缩、多案例拼凑嫌疑、有变现动机。",[91,368,369],{},"不过每一步单独看的心理机制是真实的。追损升级（escalation of commitment）有实证支持：现实版本不会是直线堕落，而是反复横跳、时间跨度以年计。真正压垮人的往往是为掩盖亏损产生的借贷和欺骗行为。",[91,371,372],{},"止损纪律本质上就是在结构上拦截追损心理。这也呼应了我自己量化系统的价值--系统替你做理性认同但情绪会动摇的决定。",{"title":125,"searchDepth":126,"depth":126,"links":374},[375,376,377,378,379,380,381],{"id":298,"depth":126,"text":299},{"id":308,"depth":126,"text":309},{"id":318,"depth":126,"text":319},{"id":331,"depth":126,"text":331},{"id":337,"depth":126,"text":338},{"id":353,"depth":126,"text":354},{"id":363,"depth":126,"text":363},"2026-07-26","围绕统计套利、容量空间、景气度投资、横截面动量和赌博心理的讨论，最终收敛到以价格为核心的量化路线。",{},"\u002Fwriting\u002F2026-07-26-market-strategy-exploration-price-route","2026-07-26T23:57:58+08:00",{"title":293,"description":383},"market-strategy-exploration-price-route","writing\u002F2026-07-26-market-strategy-exploration-price-route",[279,391,392,393,146],"量化","策略","动量","yIF9k9yKby26JobCZKCuXjRT7JUAa9HK-7dFEovl0Nk",{"id":396,"title":397,"body":398,"category":3358,"date":382,"description":3359,"extension":134,"meta":3360,"navigation":18,"path":3361,"publishedAt":3362,"seo":3363,"slug":147,"stem":3364,"tags":3365,"updated":147,"__hash__":3370},"writing\u002Fwriting\u002F2026-07-26-quilibra-complete-technical-handbook.md","Quilibra 个人主页完整技术手册：从页面架构到内容发布与生产部署",{"type":88,"value":399,"toc":3291},[400,403,406,410,413,416,425,440,443,447,450,472,475,478,482,485,585,588,594,600,614,618,621,627,630,664,678,682,688,722,740,751,757,793,800,804,809,835,852,859,896,909,913,919,951,969,1011,1014,1025,1029,1032,1055,1074,1093,1096,1100,1103,1131,1134,1138,1145,1202,1213,1216,1243,1246,1252,1258,1262,1273,1279,1286,1296,1315,1319,1329,1332,1352,1355,1395,1401,1405,1412,1415,1418,1432,1453,1459,1491,1502,1506,1517,1520,1547,1558,1561,1576,1580,1583,1599,1602,1608,1622,1629,1647,1651,1657,1664,1667,1681,1695,1702,1706,1717,1720,1728,1734,1741,1745,1748,1823,1826,1832,1852,1875,1884,1894,1898,1907,1910,1929,1932,1940,1943,1950,1957,1963,1966,1970,1977,1980,2003,2022,2025,2029,2036,2042,2051,2064,2068,2071,2078,2081,2087,2090,2096,2099,2105,2122,2126,2132,2138,2151,2168,2177,2180,2186,2190,2213,2278,2284,2291,2295,2345,2352,2358,2362,2369,2411,2422,2433,2437,2440,2444,2450,2476,2480,2486,2505,2509,2515,2550,2553,2556,2560,2563,2580,2583,2586,2626,2631,2635,2638,2645,2662,2665,2669,2673,2679,2682,2691,2694,2703,2706,2716,2719,2733,2736,2743,2746,2760,2763,2769,2773,2777,2804,2809,2813,2889,2894,2897,2956,2961,2964,2967,2995,3006,3010,3013,3022,3026,3037,3040,3048,3051,3057,3061,3071,3075,3084,3088,3091,3095,3098,3104,3107,3113,3124,3128,3131,3134,3137,3140,3143,3146,3150,3153,3201,3204,3221,3224,3227,3287],[91,401,402],{},"这是一份面向未来自己的项目说明书。它不再复述网站是怎样一轮轮改成现在这个样子的，而是以 2026 年 7 月 26 日的实际代码为准，从浏览器里看到的页面一直追到内容文件、构建产物、静态服务器和生产 release。以后忘了某段代码为什么存在、主页颜色为什么能保存、文章为什么保存后还没有上线，或者 3000、3100、3101 三个端口分别在做什么，可以从这里重新建立完整认识。",[91,404,405],{},"本文记录的是一个具体版本的实现，不是一套永远不变的规范。最可靠的事实来源始终是仓库中的代码；本文的作用，是把分散在 Vue、CSS、YAML、脚本和运维文件里的设计意图串起来。",[101,407,409],{"id":408},"一先用一句话理解整个网站","一、先用一句话理解整个网站",[91,411,412],{},"Quilibra 是一个由 Nuxt 生成的静态个人网站：页面结构写在 Vue 中，主页设置写在 YAML 中，文章写在 Markdown 中；发布时把这些源文件编译成普通 HTML、CSS、JavaScript 和图片，再由一个很小的 Node 静态服务器提供给浏览器。",[91,414,415],{},"它的核心链路是：",[417,418,423],"pre",{"className":419,"code":421,"language":422,"meta":125},[420],"language-text","Vue \u002F CSS \u002F YAML \u002F Markdown\n           |\n           | Nuxt generate\n           v\n     .output\u002Fpublic\n           |\n           | 复制到带时间戳的 release\n           v\n  releases\u002F\u003Crelease-id>\n           |\n           | 原子切换 current 符号链接\n           v\n      current -> 当前 release\n           |\n           | Node 静态服务器 :3000\n           v\n        浏览器 \u002F 反向代理\n","text",[55,424,421],{"__ignoreMap":125},[91,426,427,428],{},"这里最重要的边界是：",[429,430,431,432,435,436,439],"strong",{},"仓库中的源码是长期事实，",[55,433,434],{},".output\u002Fpublic"," 是可重新生成的临时产物，",[55,437,438],{},"current"," 指向的 release 才是生产网站当前真正提供的版本。",[91,441,442],{},"因此，修改 Markdown 或 YAML 只改变源码；只有重新生成并切换 release，线上页面才会改变。网站没有生产数据库，也没有在访问文章时临时渲染 Markdown。",[101,444,446],{"id":445},"二为什么选择静态优先","二、为什么选择静态优先",[91,448,449],{},"个人主页的读取远多于写入，而且文章、简介和服务入口都不需要按访客实时计算。静态生成正好适合这种负载：",[451,452,453,457,460,463,466,469],"ul",{},[454,455,456],"li",{},"访问时不查询数据库，也不运行 Vue 服务端渲染逻辑；",[454,458,459],{},"HTML 已经在发布阶段生成，首屏可以直接返回完整内容；",[454,461,462],{},"生产服务只需要读取文件，故障面比常驻 Nuxt 服务小；",[454,464,465],{},"每个 release 都是一份独立、完整、可回滚的目录；",[454,467,468],{},"Markdown 和 YAML 都在 Git 中，内容、配置和代码可以一起审查与恢复；",[454,470,471],{},"CMS 只是源码编辑器，不会成为网站运行时依赖。",[91,473,474],{},"代价也很明确：每次内容变化都要重新生成站点；文章越多，生成时间越长；需要登录、评论、实时状态或用户数据时，必须接入独立服务，而不能假装静态文件可以承担动态业务。",[91,476,477],{},"当前项目主动接受这个取舍，因为稳定、透明和容易备份比“保存后数据库立刻生效”更重要。",[101,479,481],{"id":480},"三技术栈与各自职责","三、技术栈与各自职责",[91,483,484],{},"当前主要依赖如下：",[486,487,488,501],"table",{},[489,490,491],"thead",{},[492,493,494,498],"tr",{},[495,496,497],"th",{},"技术",[495,499,500],{},"当前职责",[502,503,504,513,521,529,537,545,553,561,569,577],"tbody",{},[492,505,506,510],{},[507,508,509],"td",{},"Nuxt 4",[507,511,512],{},"应用框架、路由、预渲染、页面头信息和构建产物",[492,514,515,518],{},[507,516,517],{},"Vue 3",[507,519,520],{},"组件、响应式状态、生命周期和浏览器交互",[492,522,523,526],{},[507,524,525],{},"TypeScript",[507,527,528],{},"页面、组件、配置、内容脚本和测试的静态类型检查",[492,530,531,534],{},[507,532,533],{},"Nuxt Content 3",[507,535,536],{},"读取 YAML\u002FMarkdown、建立集合、查询文章并渲染正文",[492,538,539,542],{},[507,540,541],{},"Zod",[507,543,544],{},"约束站点设置与文章字段",[492,546,547,550],{},[507,548,549],{},"Lucide Vue",[507,551,552],{},"返回、搜索、服务、调色等界面图标",[492,554,555,558],{},[507,556,557],{},"原生 CSS",[507,559,560],{},"全部视觉、响应式布局、悬浮反馈和字标动画",[492,562,563,566],{},[507,564,565],{},"Sveltia CMS",[507,567,568],{},"在浏览器中编辑仓库里的 YAML、Markdown 和上传资源",[492,570,571,574],{},[507,572,573],{},"Playwright",[507,575,576],{},"真实浏览器中的交互、布局、响应式和回归测试",[492,578,579,582],{},[507,580,581],{},"Node.js",[507,583,584],{},"内容工具、release 脚本和生产静态服务器",[91,586,587],{},"没有引入 Tailwind、组件库、动画框架、运行时数据库或外部字体。页面使用系统无衬线字体和系统等宽字体回退，这减少了字体请求，也避免了字体加载完成时重新排版。",[91,589,590,593],{},[55,591,592],{},"package.json"," 中最常用的入口是：",[417,595,598],{"className":596,"code":597,"language":422,"meta":125},[420],"npm run dev              开发服务，默认对外监听 0.0.0.0\nnpm run generate         生成静态站点\nnpm run typecheck        Nuxt\u002FVue TypeScript 检查\nnpm run content:validate 校验全部文章与站点设置\nnpm run test:content     内容校验器与受限 writer 的单元测试\nnpm run test:release     release 工具的单元测试\nnpm run test:e2e         Playwright 浏览器测试\nnpm run publish          发布未提交的受管内容\nnpm run deploy           部署已经提交且工作区干净的代码版本\nnpm run rollback         切换回指定历史 release\n",[55,599,597],{"__ignoreMap":125},[91,601,602,605,606,609,610,613],{},[55,603,604],{},"build"," 与 ",[55,607,608],{},"preview"," 仍是 Nuxt 的常规命令，但当前生产链路以 ",[55,611,612],{},"generate"," 和自有静态服务器为准。",[101,615,617],{"id":616},"四目录结构与所有权边界","四、目录结构与所有权边界",[91,619,620],{},"理解这个项目，先要知道“改什么就去哪里”。",[417,622,625],{"className":623,"code":624,"language":422,"meta":125},[420],"personal-site\u002F\n├── app\u002F\n│   ├── app.vue                         全站外壳、主题初始化、动态 favicon\n│   ├── assets\u002Fcss\u002Fmain.css             全站视觉与响应式规则\n│   ├── components\u002F\n│   │   ├── HandwrittenWordmark.vue     Quilibra 字标加载与重播控制\n│   │   ├── RgbAssembly.vue             RGB 滑杆、预设与重置\n│   │   ├── ServiceIcon.vue             服务图标名称到 Lucide 的映射\n│   │   └── ServiceStatusDot.vue        服务状态点\n│   ├── composables\u002F\n│   │   ├── useAccentTheme.ts           主题色状态、混色、对比色与持久化\n│   │   ├── useSiteSettings.ts          读取唯一一份站点设置\n│   │   └── useWordmarkAnimation.ts     跨组件字标重播信号\n│   ├── config\u002F                         文章分类、服务状态和图标枚举\n│   ├── pages\u002F                          首页、文章、服务、关于页面\n│   └── error.vue                       错误页面\n├── content\u002F\n│   ├── settings\u002Fsite.yml               主页与栏目内容的唯一数据源\n│   └── writing\u002F*.md                    正式文章\n├── public\u002F\n│   ├── admin\u002F                          Sveltia CMS 入口与字段配置\n│   ├── brand\u002F                          字标位图资源\n│   ├── uploads\u002F                        文章上传资源\n│   └── favicon.svg                     静态 favicon 回退\n├── scripts\u002F\n│   ├── content\u002Fvalidate.ts             内容结构校验\n│   ├── content\u002Fwrite.ts                受限文章写入、更新与删除\n│   ├── release.ts                      测试、生成、提交、发布和回滚\n│   └── static-server.mjs               生产静态文件服务器\n├── tests\u002F                              单元、发布和浏览器测试\n├── ops\u002F\n│   ├── openclaw\u002F...\u002FSKILL.md           OpenClaw 文章发布 Skill\n│   └── systemd\u002Fpersonal-site.service   用户级生产服务定义\n├── content.config.ts                   Nuxt Content 集合\n├── content.schema.ts                   站点设置 Schema\n├── nuxt.config.ts                      Nuxt 与静态预渲染配置\n└── playwright.config.ts                E2E 临时服务与浏览器配置\n",[55,626,624],{"__ignoreMap":125},[91,628,629],{},"可以把这些文件分成四层：",[631,632,633,639,645,654],"ol",{},[454,634,635,638],{},[55,636,637],{},"content\u002F"," 是可频繁修改的数据层。",[454,640,641,644],{},[55,642,643],{},"app\u002F"," 是页面表现和交互层。",[454,646,647,605,650,653],{},[55,648,649],{},"scripts\u002F",[55,651,652],{},"ops\u002F"," 是发布和运行层。",[454,655,656,659,660,663],{},[55,657,658],{},".output\u002F","、",[55,661,662],{},".nuxt*"," 是构建缓存或产物，不是手工维护的源码。",[91,665,666,667,659,670,673,674,677],{},"CMS 默认只管理 ",[55,668,669],{},"content\u002Fsettings\u002Fsite.yml",[55,671,672],{},"content\u002Fwriting\u002F"," 和 ",[55,675,676],{},"public\u002Fuploads\u002F","。Vue、CSS、CMS 配置、脚本或测试发生变化时，应当视为代码变更，走完整代码部署流程。",[101,679,681],{"id":680},"五nuxt-配置与构建数据库","五、Nuxt 配置与构建数据库",[91,683,684,687],{},[55,685,686],{},"nuxt.config.ts"," 做了几件关键的事：",[451,689,690,697,703,706,709,716,719],{},[454,691,692,693,696],{},"加载 ",[55,694,695],{},"@nuxt\u002Fcontent","；",[454,698,699,700,696],{},"全局引入 ",[55,701,702],{},"app\u002Fassets\u002Fcss\u002Fmain.css",[454,704,705],{},"关闭开发工具；",[454,707,708],{},"设置中文页面语言和移动端 viewport；",[454,710,711,712,715],{},"使用 ",[55,713,714],{},"out-in"," 页面切换过渡；",[454,717,718],{},"允许 Nitro 爬取内部链接并预渲染，遇到错误时直接让构建失败；",[454,720,721],{},"把 Nuxt Content 的本地数据库放到与构建目录对应的位置。",[91,723,724,725,673,728,731,732,735,736,739],{},"Nuxt Content 3 在构建过程中会建立 SQLite 内容索引。开发环境默认使用 ",[55,726,727],{},".nuxt",[55,729,730],{},".data\u002Fcontent\u002Fcontents.sqlite","；release 构建传入 ",[55,733,734],{},"NUXT_BUILD_DIR=.nuxt-release","，E2E 使用 ",[55,737,738],{},".nuxt-e2e","。把三种构建目录分开，是为了避免开发服务器、正式生成和 Playwright 同时读写同一个内容缓存。",[91,741,742,743,746,747,750],{},"这里的 SQLite 是",[429,744,745],{},"构建时索引","，不是生产文章数据库。它帮助 Nuxt Content 查询 Markdown；静态页面生成完成后，生产服务器只负责输出构建结果。遇到 ",[55,748,749],{},"no such table: _content_writing"," 时，通常是本地 Nuxt Content 缓存被并发构建或中断破坏，不代表文章源文件丢失。",[91,752,753,756],{},[55,754,755],{},"content.config.ts"," 定义了两个集合：",[451,758,759,772],{},[454,760,761,764,765,768,769,696],{},[55,762,763],{},"site","：",[55,766,767],{},"data"," 类型，只读取 ",[55,770,771],{},"settings\u002Fsite.yml",[454,773,774,764,777,780,781,784,785,788,789,792],{},[55,775,776],{},"writing",[55,778,779],{},"page"," 类型，读取 ",[55,782,783],{},"writing\u002F**\u002F*.md","，因此每篇文章会拥有可路由的 ",[55,786,787],{},"path"," 和可供 ",[55,790,791],{},"ContentRenderer"," 使用的正文。",[91,794,795,796,799],{},"E2E 测试通过 ",[55,797,798],{},"NUXT_CONTENT_CWD=tests\u002Ffixtures\u002Fcontent"," 把文章集合切换到固定 fixture，测试不会依赖真实文章的标题和数量，也不会改动生产内容。",[101,801,803],{"id":802},"六站点设置一份-yaml-如何驱动多个页面","六、站点设置：一份 YAML 如何驱动多个页面",[91,805,806,808],{},[55,807,669],{}," 是主页和栏目文本的中心配置。它包含：",[451,810,811,814,817,820,823,826,829,832],{},[454,812,813],{},"站点名称、浏览器标题、描述、位置；",[454,815,816],{},"首页介绍、当前状态、关注主题；",[454,818,819],{},"首页标题前缀与强调字标文字；",[454,821,822],{},"默认主题色；",[454,824,825],{},"最新文章、服务矩阵、RGB 模块和底部入口的开关与文案；",[454,827,828],{},"服务名称、说明、URL、状态、图标和是否显示在主页；",[454,830,831],{},"文章、服务、关于三个页面的介绍与 SEO 文案；",[454,833,834],{},"ICP、公安备案和署名。",[91,836,837,840,841,844,845,847,848,851],{},[55,838,839],{},"useSiteSettings()"," 使用固定的异步数据键 ",[55,842,843],{},"site-settings"," 查询 ",[55,846,763],{}," 集合的第一条记录。固定键让多个页面共享同一份 Nuxt 数据；如果设置缺失，它立即抛出 500，而不是让各组件在大量 ",[55,849,850],{},"undefined"," 判断中带病运行。",[91,853,854,855,858],{},"配置不是任意 YAML。",[55,856,857],{},"content.schema.ts"," 用严格 Schema 规定每个字段的类型和范围，例如：",[451,860,861,867,870,873,883,886,893],{},[454,862,863,864,696],{},"默认强调色必须是 ",[55,865,866],{},"#RRGGBB",[454,868,869],{},"最新文章数量只能是 1 到 3；",[454,871,872],{},"服务数量只能是 1 到 12；",[454,874,875,876,659,878,659,881,696],{},"服务状态只能是 ",[55,877,70],{},[55,879,880],{},"private",[55,882,54],{},[454,884,885],{},"图标只能使用代码中已有的枚举；",[454,887,888,889,892],{},"服务链接只能是 ",[55,890,891],{},"#"," 或完整的 HTTPS URL；",[454,894,895],{},"对象使用严格模式，拼错字段不会被静默忽略。",[91,897,898,901,902,904,905,908],{},[55,899,900],{},"public\u002Fadmin\u002Fconfig.yml"," 的表单选项、",[55,903,857],{}," 的运行时约束、",[55,906,907],{},"app\u002Fconfig\u002Fsite.ts"," 的 TypeScript 枚举应该同步修改。只改 CMS 下拉框，不改 Schema，保存后会校验失败；只改 Schema，不改组件映射，界面可能没有正确图标。",[101,910,912],{"id":911},"七全站外壳与水合边界","七、全站外壳与水合边界",[91,914,915,918],{},[55,916,917],{},"app\u002Fapp.vue"," 是每个路由外面的共同外壳。它负责：",[451,920,921,924,927,930,936,939,945,948],{},[454,922,923],{},"在页面加载时取得站点设置；",[454,925,926],{},"判断当前是否为主页；",[454,928,929],{},"初始化和恢复主题色；",[454,931,932,933,696],{},"把主题 CSS 变量挂到 ",[55,934,935],{},".site-shell",[454,937,938],{},"为非主页显示“返回”按钮与主题预设切换按钮；",[454,940,941,942,696],{},"设置标题模板、站点描述、Open Graph 信息和 ",[55,943,944],{},"theme-color",[454,946,947],{},"根据当前强调色实时生成 data URL favicon；",[454,949,950],{},"显示 Nuxt 页面加载进度条。",[91,952,953,956,957,960,961,964,965,968],{},[55,954,955],{},"hydrated"," 初始为 ",[55,958,959],{},"false","，在 ",[55,962,963],{},"onMounted"," 完成主题恢复和本地监听注册后变成 ",[55,966,967],{},"true","，最终反映为：",[417,970,974],{"className":971,"code":972,"language":973,"meta":125,"style":125},"language-html shiki shiki-themes github-light github-dark","\u003Cdiv class=\"site-shell\" data-hydrated=\"true\">\n","html",[55,975,976],{"__ignoreMap":125},[977,978,981,985,989,993,996,1000,1003,1005,1008],"span",{"class":979,"line":980},"line",1,[977,982,984],{"class":983},"sVt8B","\u003C",[977,986,988],{"class":987},"s9eBZ","div",[977,990,992],{"class":991},"sScJk"," class",[977,994,995],{"class":983},"=",[977,997,999],{"class":998},"sZZnC","\"site-shell\"",[977,1001,1002],{"class":991}," data-hydrated",[977,1004,995],{"class":983},[977,1006,1007],{"class":998},"\"true\"",[977,1009,1010],{"class":983},">\n",[91,1012,1013],{},"这个属性既是测试可观察的“客户端已经接管页面”标志，也是字标动画的播放闸门。CSS 动画先建立，但在页面完成水合前保持暂停，防止服务端 HTML 刚显示就消耗掉一段动画，等 JavaScript 接管时只剩最终帧。",[91,1015,1016,1017,1020,1021,1024],{},"非主页的全局返回入口固定回到 ",[55,1018,1019],{},"\u002F","，文本只有“返回”，图标和 ",[55,1022,1023],{},"aria-label"," 补充了方向与完整语义。它与文章正文中的“返回文章”属于不同层级：前者返回网站主页，后者返回文章列表。",[101,1026,1028],{"id":1027},"八主页是一张单屏工作台","八、主页是一张单屏工作台",[91,1030,1031],{},"主页不是按多个营销区块向下滚动，而是一张固定在一个视口高度内的工作台。核心区域包括：",[451,1033,1034,1037,1040,1043,1046,1049,1052],{},[454,1035,1036],{},"顶部站点标识、上海时区时钟、指针坐标和主题按钮；",[454,1038,1039],{},"左上介绍、普通标题前缀与 Quilibra 字标；",[454,1041,1042],{},"右上服务矩阵；",[454,1044,1045],{},"左下最近三篇文章；",[454,1047,1048],{},"右下 RGB 调色器；",[454,1050,1051],{},"底部中央文章、服务、关于三个入口；",[454,1053,1054],{},"两侧备案与署名。",[91,1056,1057,1058,1061,1062,1065,1066,1069,1070,1073],{},"首页在 ",[55,1059,1060],{},"setup"," 阶段并行取得站点设置和最近文章。文章查询按 ",[55,1063,1064],{},"date DESC"," 排序，再按 YAML 中的 ",[55,1067,1068],{},"limit"," 截取。服务矩阵先筛选 ",[55,1071,1072],{},"showOnHome: true","，按 YAML 顺序最多取四个；服务页仍然展示完整列表。",[91,1075,1076,1077,1080,1081,1084,1085,1088,1089,1092],{},"顶部时钟通过 ",[55,1078,1079],{},"Intl.DateTimeFormat"," 固定使用 ",[55,1082,1083],{},"Asia\u002FShanghai","，每 30 秒更新一次。指针坐标不是每次 ",[55,1086,1087],{},"pointermove"," 都直接改 DOM：事件只保存最新坐标，然后在下一帧 ",[55,1090,1091],{},"requestAnimationFrame"," 中统一计算。元素边界在挂载与窗口缩放时缓存，触摸指针被忽略。这样可以减少高频事件中的布局读取和响应式更新。",[91,1094,1095],{},"工作台没有为了装饰引入 canvas 或 WebGL。网格、面板、条纹、阴影和入场效果全部由 CSS 完成，浏览器可以直接合成绝大多数变换。",[101,1097,1099],{"id":1098},"九响应式布局为何不只是按比例缩小","九、响应式布局为何不只是“按比例缩小”",[91,1101,1102],{},"主页有大量绝对定位元素，因此响应式的目标不是把桌面页面机械缩成手机版，而是维护清晰的空间约束：",[451,1104,1105,1112,1115,1118,1121,1128],{},[454,1106,1107,1108,1111],{},"桌面端通过 ",[55,1109,1110],{},"clamp()","、视口高度和稳定的面板高度控制上下关系；",[454,1113,1114],{},"最近文章与 RGB 面板在宽桌面上对齐顶部和底部；",[454,1116,1117],{},"小屏笔记本缩小间距和模块尺寸，仍避免重叠；",[454,1119,1120],{},"768 像素附近的紧凑布局隐藏无法舒适操作的 RGB 面板；",[454,1122,1123,1124,1127],{},"手机端重新排列主页元素，并使用 ",[55,1125,1126],{},"overflow: clip"," 防止装饰或过渡产生横向滚动；",[454,1129,1130],{},"固定格式组件使用明确的 grid 列、最小宽度和高度，标题悬浮时不会重新计算可用宽度。",[91,1132,1133],{},"Playwright 会在 768×1024、1024×768、1440×900 和 3440×1440 上读取真实元素几何信息，验证介绍不压住服务矩阵、上方面板不压住底部导航、RGB 与最近文章对齐、页面没有横向溢出。这里测试的是关系，而不是容易因一个像素改动就失效的整页截图。",[101,1135,1137],{"id":1136},"十主题色从一个-rgb-值扩展成整套界面","十、主题色从一个 RGB 值扩展成整套界面",[91,1139,1140,1141,1144],{},"主题逻辑集中在 ",[55,1142,1143],{},"useAccentTheme.ts","。唯一的核心状态是：",[417,1146,1150],{"className":1147,"code":1148,"language":1149,"meta":125,"style":125},"language-ts shiki shiki-themes github-light github-dark","interface RgbColor {\n  r: number\n  g: number\n  b: number\n}\n","ts",[55,1151,1152,1164,1177,1186,1196],{"__ignoreMap":125},[977,1153,1154,1158,1161],{"class":979,"line":980},[977,1155,1157],{"class":1156},"szBVR","interface",[977,1159,1160],{"class":991}," RgbColor",[977,1162,1163],{"class":983}," {\n",[977,1165,1166,1170,1173],{"class":979,"line":126},[977,1167,1169],{"class":1168},"s4XuR","  r",[977,1171,1172],{"class":1156},":",[977,1174,1176],{"class":1175},"sj4cs"," number\n",[977,1178,1179,1182,1184],{"class":979,"line":22},[977,1180,1181],{"class":1168},"  g",[977,1183,1172],{"class":1156},[977,1185,1176],{"class":1175},[977,1187,1189,1192,1194],{"class":979,"line":1188},4,[977,1190,1191],{"class":1168},"  b",[977,1193,1172],{"class":1156},[977,1195,1176],{"class":1175},[977,1197,1199],{"class":979,"line":1198},5,[977,1200,1201],{"class":983},"}\n",[91,1203,1204,1205,1208,1209,1212],{},"三个内置预设是红、绿、蓝。站点设置里的 ",[55,1206,1207],{},"theme.defaultAccent"," 可以是任意合法十六进制颜色，并不要求与预设一致。当前颜色存放在 Nuxt ",[55,1210,1211],{},"useState"," 中，因此同一客户端的页面切换不会创建互相冲突的主题实例。",[91,1214,1215],{},"主题计算分为几步：",[631,1217,1218,1221,1231,1234,1240],{},[454,1219,1220],{},"把每个通道四舍五入并限制在 0 到 255。",[454,1222,1223,1224,1227,1228,1230],{},"生成 CSS ",[55,1225,1226],{},"rgb(r g b)"," 与大写 ",[55,1229,866],{},"。",[454,1232,1233],{},"把强调色分别与白色、画布色和黑色混合，得到 soft、faint、canvas、grid、strong 等衍生色。",[454,1235,1236,1237,1230],{},"计算 sRGB 相对亮度，对比黑白文字的对比度，自动选择更清晰的 ",[55,1238,1239],{},"--accent-ink",[454,1241,1242],{},"把结果以 CSS 变量挂到站点外壳，按钮、悬浮底色、网格、字标和 favicon 共同消费这些变量。",[91,1244,1245],{},"主题变量的意义大致如下：",[417,1247,1250],{"className":1248,"code":1249,"language":422,"meta":125},[420],"--accent          原始强调色\n--accent-ink      强调色背景上的黑或白文字\n--accent-soft     大面积悬浮反馈\n--accent-faint    更浅的面板背景\n--accent-canvas   轻微带主题倾向的页面画布\n--accent-grid     网格与线条色\n--accent-strong   向黑色混合后的强调色\n",[55,1251,1249],{"__ignoreMap":125},[91,1253,1254,1255,1257],{},"这样做比在 CSS 中到处硬编码“红色按钮、浅红背景、深红边框”更可靠。换成极亮或极暗的自定义颜色时，文字对比度仍会自动调整。E2E 会直接把颜色调到纯白和纯黑，验证 ",[55,1256,1239],{}," 分别变成深色和白色。",[101,1259,1261],{"id":1260},"十一主题持久化与旧黄色迁移","十一、主题持久化与旧黄色迁移",[91,1263,1264,1265,1268,1269,1272],{},"客户端挂载时，",[55,1266,1267],{},"restoreSavedAccent()"," 从 ",[55,1270,1271],{},"localStorage"," 读取：",[417,1274,1277],{"className":1275,"code":1276,"language":422,"meta":125},[420],"site-accent-rgb   完整 RGB 对象\nsite-accent       red \u002F green \u002F blue \u002F custom 等名称\n",[55,1278,1276],{"__ignoreMap":125},[91,1280,1281,1282,1285],{},"恢复后，深度监听 ",[55,1283,1284],{},"accentRgb","，后续每次变化都会重新保存。由于服务端无法读取浏览器存储，静态 HTML 首先使用 YAML 中的默认颜色；客户端挂载后再恢复访客上次的选择。",[91,1287,1288,1289,605,1292,1295],{},"旧版本曾使用黄色默认主题。为了避免已经访问过网站的浏览器永远被旧缓存锁在黄色，恢复逻辑专门识别 ",[55,1290,1291],{},"{255,255,2}",[55,1293,1294],{},"yellow"," 的组合，删除这两个旧值并回到当前 YAML 默认色。这是一次小型数据迁移：不是清空所有人的自定义配色，只清除能够明确识别的旧默认值。",[91,1297,1298,1299,1302,1303,1306,1307,1310,1311,1314],{},"动态 favicon 也跟随主题。",[55,1300,1301],{},"app.vue"," 在内存中生成一个含背景色和 Q 图形的 SVG，再编码为 ",[55,1304,1305],{},"data:image\u002Fsvg+xml","。因此标签页图标和 ",[55,1308,1309],{},"meta[name=theme-color]"," 会与 RGB 面板同步；",[55,1312,1313],{},"public\u002Ffavicon.svg"," 只负责 JavaScript 接管前或不支持动态图标时的回退。",[101,1316,1318],{"id":1317},"十二rgb-调色器的交互细节","十二、RGB 调色器的交互细节",[91,1320,1321,1324,1325,1328],{},[55,1322,1323],{},"RgbAssembly.vue"," 不是独立维护另一份颜色，它调用同一个 ",[55,1326,1327],{},"useAccentTheme()","，因此滑杆、预设按钮、页面按钮和 favicon 始终共享状态。",[91,1330,1331],{},"三个 range input 分别控制 R、G、B：",[451,1333,1334,1340,1343,1346,1349],{},[454,1335,1336,1339],{},[55,1337,1338],{},"input"," 事件实时更新颜色，拖动时页面连续渐变；",[454,1341,1342],{},"每条轨道通过 CSS 变量计算已填充百分比；",[454,1344,1345],{},"输出区显示十六进制、十进制通道值，并采用自动对比文字；",[454,1347,1348],{},"点击 RED、GREEN、BLUE 立即加载预设；",[454,1350,1351],{},"重置按钮恢复 YAML 中的默认颜色，而不是写死某个预设。",[91,1353,1354],{},"字标动画不能在滑杆的每一个像素变化时重播，否则会不断重建动画并显得卡顿。组件因此区分“预览变化”和“提交变化”：",[451,1356,1357,1364,1370,1380,1387],{},[454,1358,1359,1360,1363],{},"指针按下后标记 ",[55,1361,1362],{},"pointerActive","，并捕获当前 pointer；",[454,1365,1366,1367,1369],{},"拖动中的 ",[55,1368,1338],{}," 只改变颜色；",[454,1371,1372,1375,1376,1379],{},[55,1373,1374],{},"pointerup"," 或 ",[55,1377,1378],{},"pointercancel"," 才请求重播一次字标；",[454,1381,1382,1383,1386],{},"键盘调整 range 时由 ",[55,1384,1385],{},"change"," 请求重播；",[454,1388,1389,1390,673,1392,1394],{},"一个零延时抑制标志防止同一次鼠标提交同时触发 ",[55,1391,1374],{},[55,1393,1385],{},"，造成双播。",[91,1396,1397,1398],{},"预设与重置属于离散操作，所以点击时立即换色并重播。这个模型可以概括为：",[429,1399,1400],{},"连续操作实时预览、松手提交动画；离散操作立即提交。",[101,1402,1404],{"id":1403},"十三quilibra-字标并不是逐笔书写动画","十三、Quilibra 字标并不是逐笔书写动画",[91,1406,1407,1408,1411],{},"当前字标资源是 ",[55,1409,1410],{},"public\u002Fbrand\u002Fquilibra-handwritten.png","，尺寸比例为 1127:293，文件约 30 KB。页面不会直接显示这张 PNG，而是把它作为 CSS mask：图片只定义哪些像素可见，真正填充的颜色由 CSS 决定。因此同一份手写轮廓可以跟随任意主题色。",[91,1413,1414],{},"最终采用的是“RGB 套色从偏移到合拢”的动画，而不是模拟笔尖沿路径逐笔书写。原因是位图没有天然的笔画顺序；从位图自动推断真实书写路径成本高、结果也容易机械。套色动画更符合现有 RGB 工作台语言，同时实现稳定。",[91,1416,1417],{},"字标由四层相同 mask 组成：",[451,1419,1420,1423,1426,1429],{},[454,1421,1422],{},"红层从左下附近偏移进入；",[454,1424,1425],{},"绿层从上方偏移进入；",[454,1427,1428],{},"蓝层从右下附近偏移进入；",[454,1430,1431],{},"最终层使用当前主题色并带极轻的阴影。",[91,1433,1434,1435,1438,1439,659,1442,673,1445,1448,1449,1452],{},"前三层使用 ",[55,1436,1437],{},"mix-blend-mode: multiply","、动态模糊、透明度和不同位移。动画前段保留可见错版，中段快速靠近，后段降低彩色层透明度并让最终主题层聚焦。四层都只改变 ",[55,1440,1441],{},"opacity",[55,1443,1444],{},"transform",[55,1446,1447],{},"filter","，播放时临时声明 ",[55,1450,1451],{},"will-change","，结束后不长期占用合成资源。",[91,1454,1455,1458],{},[55,1456,1457],{},"HandwrittenWordmark.vue"," 的加载控制解决了“首次打开没有动画”的问题：",[631,1460,1461,1468,1475,1485,1488],{},[454,1462,1463,1464,1467],{},"首页用 ",[55,1465,1466],{},"\u003Clink rel=\"preload\" as=\"image\">"," 提前请求 mask。",[454,1469,1470,1471,1474],{},"组件创建一次共享的 ",[55,1472,1473],{},"wordmarkReady"," Promise。",[454,1476,1477,1480,1481,1484],{},[55,1478,1479],{},"Image"," 加载后调用 ",[55,1482,1483],{},"decode()","，等待图片真正可用于绘制。",[454,1486,1487],{},"只有资源就绪、组件仍存活、页面可见且请求仍是最新时才开始播放。",[454,1489,1490],{},"图片失败时显示文字 fallback；开启减少动态效果时直接展示最终状态。",[91,1492,1493,1494,1497,1498,1501],{},"每次重播都会增加 ",[55,1495,1496],{},"animationRun","，并把它放进四层的 Vue ",[55,1499,1500],{},"key","。这会让浏览器得到新的动画元素，可靠地从第 0 帧开始，而不是依赖移除 class 后强制读取布局。",[101,1503,1505],{"id":1504},"十四字标在什么时候重播","十四、字标在什么时候重播",[91,1507,1508,1509,1512,1513,1516],{},"全局 ",[55,1510,1511],{},"useWordmarkAnimation()"," 只维护一个数字信号。任何组件调用 ",[55,1514,1515],{},"requestReplay()","，数字加一；字标组件 watch 到变化后重播。这个很小的事件通道避免 RGB 组件直接引用字标 DOM。",[91,1518,1519],{},"当前重播场景包括：",[451,1521,1522,1525,1528,1531,1534,1537,1540],{},[454,1523,1524],{},"首次进入主页并且 mask 解码完成；",[454,1526,1527],{},"点击主题预设或重置；",[454,1529,1530],{},"RGB 滑杆松手或键盘提交；",[454,1532,1533],{},"从文章、服务、关于页面返回主页，主页组件重新挂载；",[454,1535,1536],{},"浏览器标签页从隐藏变为可见；",[454,1538,1539],{},"窗口重新获得焦点；",[454,1541,1542,1543,1546],{},"浏览器的 ",[55,1544,1545],{},"pageshow","，包括可能来自往返缓存的恢复。",[91,1548,1549,659,1552,673,1555,1557],{},[55,1550,1551],{},"visibilitychange",[55,1553,1554],{},"focus",[55,1556,1545],{}," 可能在同一次切回中连续到达。组件使用一个 animation frame 合并激活请求，并设置 200ms 的最小间隔，防止一次切回连续播两三遍。页面变为隐藏时会取消待播放帧、使旧异步请求失效并结束当前播放。",[91,1559,1560],{},"这里还有两个无障碍与容错原则：",[451,1562,1563,1569],{},[454,1564,1565,1568],{},[55,1566,1567],{},"prefers-reduced-motion: reduce"," 时不播放套色，直接显示最终字标；",[454,1570,1571,1572,1575],{},"可读文字仍存在于 ",[55,1573,1574],{},"sr-only"," 中，视觉 mask 不承担标题语义。",[101,1577,1579],{"id":1578},"十五服务矩阵图标与状态点","十五、服务矩阵、图标与状态点",[91,1581,1582],{},"每个服务在 YAML 中有六个字段：名称、说明、链接、状态、图标、是否显示在主页。",[91,1584,1585,1588,1589,605,1591,1594,1595,1598],{},[55,1586,1587],{},"ServiceIcon.vue"," 把业务名称映射到 Lucide 图标。NAS 使用独立的 ",[55,1590,65],{},[55,1592,1593],{},"HardDrive","，不会复用影音播放图标。未知值虽然有 ",[55,1596,1597],{},"Server"," 回退，但正常内容会在 Schema 阶段被拒绝，因此回退只是组件级防御。",[91,1600,1601],{},"状态共有三种：",[417,1603,1606],{"className":1604,"code":1605,"language":422,"meta":125},[420],"online   在线\nprivate  仅限本人\nsoon     准备中\n",[55,1607,1605],{"__ignoreMap":125},[91,1609,1610,1613,1614,1617,1618,1621],{},[55,1611,1612],{},"ServiceStatusDot.vue"," 把状态写入 ",[55,1615,1616],{},"data-state","，CSS 用属性选择器决定颜色，",[55,1619,1620],{},"title"," 提供文字说明。主页和服务页都复用这个组件，因此 CMS 修改 YAML 状态后，重新构建的两个页面会同步变化，不需要分别维护配色。",[91,1623,1624,1625,1628],{},"状态点表达的是",[429,1626,1627],{},"人工配置的展示状态","，不是实时健康检查。它不会主动请求 Code、Photos、NAS 或 Status，也不会自动从监控系统同步。如果未来需要实时状态，应由独立状态 API 提供可信结果，再决定是在客户端请求还是构建前抓取；不能仅把绿色小点误解为自动监控。",[91,1630,1631,1632,1634,1635,1638,1639,1642,1643,1646],{},"链接为 ",[55,1633,891],{}," 时，主页服务节点转到 ",[55,1636,1637],{},"\u002Fservices","，服务页显示为不可点击行；完整 HTTPS 链接则在新标签页打开，并带 ",[55,1640,1641],{},"noopener noreferrer","。Schema 禁止 ",[55,1644,1645],{},"javascript:"," 和非 HTTPS 外部地址，避免 CMS 字段直接变成危险链接。",[101,1648,1650],{"id":1649},"十六文章列表筛选与搜索","十六、文章列表、筛选与搜索",[91,1652,1653,1656],{},[55,1654,1655],{},"\u002Fwriting"," 在构建阶段查询全部文章，并按日期倒序排列。浏览器端只对已经加载的数组做筛选，不需要为每个关键词请求服务器。",[91,1658,1659,1660,1663],{},"分类来自共享常量：随笔、学习、交易、观察。列表额外添加“全部”。搜索会把标题、摘要和标签拼成小写字符串，再做简单的 ",[55,1661,1662],{},"includes"," 匹配。这适合当前文章规模，特点是实现透明、中文可用、没有索引服务；但它不是分词搜索，也不会搜索正文。",[91,1665,1666],{},"文章行显示日期、标题、摘要、分类和箭头。悬浮一篇时：",[451,1668,1669,1672,1675,1678],{},[454,1670,1671],{},"只给当前行增加浅主题色背景；",[454,1673,1674],{},"日期与正文整体平移 8px；",[454,1676,1677],{},"箭头向右上轻移；",[454,1679,1680],{},"其他文章保持完全不变。",[91,1682,1683,1684,659,1687,1690,1691,1694],{},"标题容器的 grid 列不会在 hover 时改变，所以长标题不会因为悬浮突然获得更小宽度而换行。主页“最近写下”的标题使用 ",[55,1685,1686],{},"minmax(0,1fr)",[55,1688,1689],{},"overflow:hidden","、省略号和 ",[55,1692,1693],{},"white-space:nowrap","，确保固定高度面板不被长标题撑开。",[91,1696,1697,1698,1701],{},"搜索结果区使用 ",[55,1699,1700],{},"aria-live=\"polite\"","，筛选后的篇数和空状态可以被辅助技术感知。",[101,1703,1705],{"id":1704},"十七文章详情与相邻导航","十七、文章详情与相邻导航",[91,1707,1708,1709,1712,1713,1716],{},"动态路由文件是 ",[55,1710,1711],{},"app\u002Fpages\u002Fwriting\u002F[...slug].vue","。它使用当前 ",[55,1714,1715],{},"route.path"," 查询对应文章；找不到时立即抛出带中文说明的 404。",[91,1718,1719],{},"详情页同时取得按日期倒序排列的全部文章，用当前文章的数组位置计算：",[451,1721,1722,1725],{},[454,1723,1724],{},"数组中下一项是时间上更旧的“上一篇”；",[454,1726,1727],{},"数组中上一项是时间上更新的“下一篇”。",[91,1729,1730,1731,1733],{},"页面展示分类、发布日期、可选的更新日期、标题、摘要、标签与正文。正文由 Nuxt Content 的 ",[55,1732,791],{}," 生成。SEO 标题使用全站模板变成“文章标题 · Quilibra”，描述来自 frontmatter，Open Graph 类型设为 article。",[91,1735,1736,1737,1740],{},"正文样式集中在 ",[55,1738,1739],{},".article-prose","：限制阅读宽度、提高行高、分级处理标题、列表、引用、代码、链接和图片。文章页面可以自由使用 Markdown，不需要为每篇文章编写 Vue 模板。",[101,1742,1744],{"id":1743},"十八文章-frontmatter-合约","十八、文章 frontmatter 合约",[91,1746,1747],{},"一篇新文章最小结构如下：",[417,1749,1753],{"className":1750,"code":1751,"language":1752,"meta":125,"style":125},"language-yaml shiki shiki-themes github-light github-dark","---\ntitle: 清楚的文章标题\ndescription: 一句话说明文章实际记录了什么。\ndate: 2026-07-26\ncategory: 学习\ntags:\n  - Nuxt\n---\n","yaml",[55,1754,1755,1760,1770,1780,1790,1800,1809,1818],{"__ignoreMap":125},[977,1756,1757],{"class":979,"line":980},[977,1758,1759],{"class":991},"---\n",[977,1761,1762,1764,1767],{"class":979,"line":126},[977,1763,1620],{"class":987},[977,1765,1766],{"class":983},": ",[977,1768,1769],{"class":998},"清楚的文章标题\n",[977,1771,1772,1775,1777],{"class":979,"line":22},[977,1773,1774],{"class":987},"description",[977,1776,1766],{"class":983},[977,1778,1779],{"class":998},"一句话说明文章实际记录了什么。\n",[977,1781,1782,1785,1787],{"class":979,"line":1188},[977,1783,1784],{"class":987},"date",[977,1786,1766],{"class":983},[977,1788,1789],{"class":1175},"2026-07-26\n",[977,1791,1792,1795,1797],{"class":979,"line":1198},[977,1793,1794],{"class":987},"category",[977,1796,1766],{"class":983},[977,1798,1799],{"class":998},"学习\n",[977,1801,1803,1806],{"class":979,"line":1802},6,[977,1804,1805],{"class":987},"tags",[977,1807,1808],{"class":983},":\n",[977,1810,1812,1815],{"class":979,"line":1811},7,[977,1813,1814],{"class":983},"  - ",[977,1816,1817],{"class":998},"Nuxt\n",[977,1819,1821],{"class":979,"line":1820},8,[977,1822,1759],{"class":991},[91,1824,1825],{},"文件名必须是：",[417,1827,1830],{"className":1828,"code":1829,"language":422,"meta":125},[420],"YYYY-MM-DD-english-kebab.md\n",[55,1831,1829],{"__ignoreMap":125},[91,1833,1834,1835,659,1837,659,1839,659,1841,659,1844,659,1847,659,1849,1851],{},"允许字段只有 ",[55,1836,1620],{},[55,1838,1774],{},[55,1840,1784],{},[55,1842,1843],{},"updated",[55,1845,1846],{},"slug",[55,1848,1794],{},[55,1850,1805],{},"。发布新文章时：",[451,1853,1854,1859,1865,1870],{},[454,1855,1856,1858],{},[55,1857,1784],{}," 必须是中国时区当天；",[454,1860,1861,1862,1864],{},"文件名日期必须与 ",[55,1863,1784],{}," 一致；",[454,1866,1867,1868,696],{},"不能包含 ",[55,1869,1843],{},[454,1871,1872,1874],{},[55,1873,1846],{}," 如果存在，必须与文件名后半段一致。",[91,1876,1877,1878,1880,1881,1883],{},"修订文章时保留原文件名和 ",[55,1879,1784],{},"，把 ",[55,1882,1843],{}," 设置为中国时区当天。正文结构是自由的，但不能为空。若使用二级标题“来源与延伸阅读”，该节必须至少有一个 HTTP 或 HTTPS 链接。",[91,1885,1886,1889,1890,1893],{},[55,1887,1888],{},"scripts\u002Fcontent\u002Fvalidate.ts"," 使用 ",[55,1891,1892],{},"gray-matter"," 和 YAML 解析 frontmatter，再用 Markdown AST 检查正文与来源节。使用结构化解析而不是正则扫描全文，可以区分标题、链接与普通文本，并给出确定的错误。",[101,1895,1897],{"id":1896},"十九sveltia-cms-到底是什么","十九、Sveltia CMS 到底是什么",[91,1899,1900,1903,1904,1906],{},[55,1901,1902],{},"\u002Fadmin\u002Findex.html"," 只加载 Sveltia CMS 的前端脚本，",[55,1905,900],{}," 描述后台字段。它不是另一个网站后端，也不存文章副本。",[91,1908,1909],{},"后台能维护：",[451,1911,1912,1915,1918,1921,1924],{},[454,1913,1914],{},"站点、首页与栏目文案；",[454,1916,1917],{},"默认强调色和主页模块开关；",[454,1919,1920],{},"服务的增删、顺序、URL、状态、图标和主页显示；",[454,1922,1923],{},"文章的新建、搜索、筛选、修改和删除；",[454,1925,1926,1928],{},[55,1927,676],{}," 中的文章资源。",[91,1930,1931],{},"CMS 有两种工作方式：",[631,1933,1934,1937],{},[454,1935,1936],{},"本地仓库模式：Chromium 通过 File System Access API 直接编辑本机选择的仓库。",[454,1938,1939],{},"GitHub 模式：用户经 GitHub 登录后，CMS 根据配置向私有仓库提交内容。",[91,1941,1942],{},"无论哪种模式，“保存”都只意味着源文件或远程仓库出现改动。它不会神奇地更新正在运行的静态 release。要让网站变化，仍需要一台部署机取得新提交，运行校验与生成，再切换 release。",[91,1944,1945,1946,1949],{},"GitHub OAuth 控制“谁能通过 CMS 读写仓库”，GitHub Actions 控制“仓库收到提交后执行什么自动任务”。两者不是同一个东西。私人仓库存放网站源码、文章、公开图片和不含密钥的配置；OAuth secret、访问令牌、部署 SSH key、OpenClaw 会话和 ",[55,1947,1948],{},".env"," 不应进入仓库。",[91,1951,1952,1953,1956],{},"目前 CMS 配置指向 ",[55,1954,1955],{},"master"," 分支。若未来启用自动部署，一个典型链路是：",[417,1958,1961],{"className":1959,"code":1960,"language":422,"meta":125},[420],"浏览器登录 GitHub -> CMS 提交 Markdown\u002FYAML -> 私有仓库 master 更新\n       -> GitHub Actions 触发 -> 部署机拉取指定提交\n       -> npm ci \u002F 校验 \u002F npm run deploy -> 新 release 上线\n",[55,1962,1960],{"__ignoreMap":125},[91,1964,1965],{},"域名是否已经备案、网站是否已有公网 HTTPS，与“先把代码推到私人仓库”没有冲突。远程 CMS 登录通常需要 HTTPS 回调，但仓库和 Actions 可以先配置好。",[101,1967,1969],{"id":1968},"二十受限-writer-为什么存在","二十、受限 writer 为什么存在",[91,1971,1972,1973,1976],{},"普通编辑器可以修改仓库中的任何文件，但自动化发布工具不应该拥有同样宽的写入自由。",[55,1974,1975],{},"scripts\u002Fcontent\u002Fwrite.ts"," 把 OpenClaw 的写入范围压缩为三个明确操作：create、update、delete。",[91,1978,1979],{},"新建流程只接受草稿目录中的一个普通 Markdown 文件名和一个无日期 slug。writer 会检查：",[451,1981,1982,1985,1988,1991,1994,1997,2000],{},[454,1983,1984],{},"草稿名不能包含目录或路径穿越；",[454,1986,1987],{},"草稿必须是普通文件，不能是符号链接；",[454,1989,1990],{},"草稿不超过 1 MiB；",[454,1992,1993],{},"slug 必须是小写英文、数字和连字符；",[454,1995,1996],{},"frontmatter 与正文必须通过完整校验；",[454,1998,1999],{},"日期必须是中国时区当天；",[454,2001,2002],{},"目标文章不能已经存在。",[91,2004,2005,2006,2009,2010,2013,2014,2017,2018,2021],{},"写入时先以 ",[55,2007,2008],{},"wx"," 模式建立权限为 ",[55,2011,2012],{},"0640"," 的随机临时文件并 ",[55,2015,2016],{},"fsync","，再用硬链接创建最终文件，利用文件系统的 ",[55,2019,2020],{},"EEXIST"," 保证不会覆盖已有新文章。更新时先验证现有文件和发布日期，再用 rename 原子替换。删除只接受精确的完整 dated slug，并拒绝目录、符号链接和不存在的目标。",[91,2023,2024],{},"这不是为了让日常写作变复杂，而是为了让“从聊天自动发布”仍有可审计的硬边界。Skill 中的文字规则可能被模型误解，writer 的路径、日期和文件类型检查则由操作系统与代码强制执行。",[101,2026,2028],{"id":2027},"二十一openclaw-发布-skill-的实际状态机","二十一、OpenClaw 发布 Skill 的实际状态机",[91,2030,2031,2032,2035],{},"仓库只维护一个 ",[55,2033,2034],{},"personal-site-publisher"," Skill。它先读取文章合约，再按以下过程工作：",[417,2037,2040],{"className":2038,"code":2039,"language":422,"meta":125},[420],"链接或素材\n   |\n   v\n确定标题、摘要、日期、slug、分类、标签\n   |\n   v\n在私聊中返回完整草稿，不写仓库\n   |\n   +-- 修改：... --> 修改内存草稿\n   +-- 放弃 ------> 清除内存草稿\n   +-- 发布 ------> 保存到受限草稿目录\n                         |\n                         v\n                   content:write\n                         |\n                         v\n                     npm publish\n                         |\n                         v\n              返回文章 URL、commit、release\n",[55,2041,2039],{"__ignoreMap":125},[91,2043,2044,2047,2048,1230],{},[55,2045,2046],{},"直接发布"," 只跳过人工预览，不跳过 writer、内容校验和静态生成。更新文章必须保留 dated URL；删除必须先展示目标信息，再收到完全匹配的 ",[55,2049,2050],{},"确认删除 \u003Cdated-slug>",[91,2052,2053,2054,659,2057,1375,2060,2063],{},"发布 Skill 还规定：只接受所有者私聊中的发布命令；把网页、对话和搜索结果视为不可信内容；不把 API key、cookie、账号信息、私人对话细节和精确私人资产写入文章；不能用任意编辑器、",[55,2055,2056],{},"rm",[55,2058,2059],{},"git add",[55,2061,2062],{},"git commit"," 绕过 writer 和 release 脚本。",[101,2065,2067],{"id":2066},"二十二publish-与-deploy-是两条不同入口","二十二、publish 与 deploy 是两条不同入口",[91,2069,2070],{},"这两个命令最终都会生成静态站并切换 release，但权限和检查强度不同。",[2072,2073,2075],"h3",{"id":2074},"npm-run-publish",[55,2076,2077],{},"npm run publish",[91,2079,2080],{},"用于尚未提交的内容改动。它只允许以下路径：",[417,2082,2085],{"className":2083,"code":2084,"language":422,"meta":125},[420],"content\u002Fsettings\u002Fsite.yml\ncontent\u002Fwriting\u002F**\npublic\u002Fuploads\u002F**\n",[55,2086,2084],{"__ignoreMap":125},[91,2088,2089],{},"它验证内容、生成静态站、自动创建本地 Git commit、复制 release 并切换生产。若工作区混入 Vue、CSS、脚本、CMS 配置或文档改动，会拒绝执行。内容发布不重复跑全部代码 E2E，因为代码版本没有变化。",[2072,2091,2093],{"id":2092},"npm-run-deploy",[55,2094,2095],{},"npm run deploy",[91,2097,2098],{},"用于已经提交的代码版本。它要求工作区完全干净，不创建 commit，并依次运行：",[417,2100,2103],{"className":2101,"code":2102,"language":422,"meta":125},[420],"类型检查\n内容与 writer 单元测试\nrelease 单元测试\n静态生成\n浏览器 E2E\n创建 release\n原子切换 current\n清理过旧 release\n",[55,2104,2102],{"__ignoreMap":125},[91,2106,2107,2108,2111,2112,2115,2116,2118,2119,2121],{},"因此，修改本文这样的文章后，正常下一步是 ",[55,2109,2110],{},"publish","；修改 Vue\u002FCSS 并已经提交后，使用 ",[55,2113,2114],{},"deploy","。不要用 ",[55,2117,2110],{}," 偷渡代码，也不要让 ",[55,2120,2114],{}," 带着未提交文件上线。",[101,2123,2125],{"id":2124},"二十三静态-release-如何做到切换时不中断","二十三、静态 release 如何做到切换时不中断",[91,2127,2128,2131],{},[55,2129,2130],{},"scripts\u002Frelease.ts"," 用 UTC 时间生成 release 名称，例如：",[417,2133,2136],{"className":2134,"code":2135,"language":422,"meta":125},[420],"20260726T144914-134Z\n",[55,2137,2135],{"__ignoreMap":125},[91,2139,2140,2141,2143,2144,2147,2148,2150],{},"生成结束后，把 ",[55,2142,434],{}," 递归复制到 ",[55,2145,2146],{},"releases\u002F\u003Cid>","。激活时不是先删 ",[55,2149,438],{}," 再新建，而是：",[631,2152,2153,2156,2159],{},[454,2154,2155],{},"创建一个带进程号的临时符号链接；",[454,2157,2158],{},"让临时链接指向新 release；",[454,2160,2161,2162,2165,2166,1230],{},"用 ",[55,2163,2164],{},"rename"," 把临时链接原子替换成 ",[55,2167,438],{},[91,2169,2170,2171,2173,2174,2176],{},"对访问者来说，某个请求要么读取旧 release，要么读取新 release，不会遇到 ",[55,2172,438],{}," 暂时不存在的中间状态。生产 Node 进程也不需要重启，因为它每次请求都从 ",[55,2175,438],{}," 路径解析文件。",[91,2178,2179],{},"脚本默认保留最近五个 release，并额外保证当前激活版本不被删掉。由于当前版本有可能是手工回滚到的较旧目录，保留“当前版本”比单纯保留时间最新的五个更重要。",[91,2181,2182,2183,2185],{},"回滚只调用同一个原子激活函数，把 ",[55,2184,438],{}," 指回已存在的 release。它不修改 Git、不重新构建、不删除较新的版本，也不重启生产服务。",[101,2187,2189],{"id":2188},"二十四生产静态服务器做了哪些事","二十四、生产静态服务器做了哪些事",[91,2191,2192,2195,2196,659,2199,659,2202,673,2205,2208,2209,2212],{},[55,2193,2194],{},"scripts\u002Fstatic-server.mjs"," 使用 Node 自带的 ",[55,2197,2198],{},"http",[55,2200,2201],{},"fs",[55,2203,2204],{},"stream",[55,2206,2207],{},"zlib","，默认监听 ",[55,2210,2211],{},"0.0.0.0:3000","。它没有框架中间件，职责非常窄：",[451,2214,2215,2218,2231,2237,2244,2247,2250,2253,2256,2259,2266,2272,2275],{},[454,2216,2217],{},"只接受 GET 和 HEAD，其他方法返回 405；",[454,2219,2220,2221,605,2224,2227,2228,2230],{},"解码 URL 后用 ",[55,2222,2223],{},"resolve",[55,2225,2226],{},"relative"," 检查目标仍在 ",[55,2229,438],{}," 内，阻止目录穿越；",[454,2232,2233,2234,696],{},"请求目录时返回该目录的 ",[55,2235,2236],{},"index.html",[454,2238,2239,2240,2243],{},"找不到文件时返回预生成的 ",[55,2241,2242],{},"404.html"," 和 404 状态；",[454,2245,2246],{},"根据扩展名发送正确的 Content-Type；",[454,2248,2249],{},"对大于等于 1 KiB 的文本资源协商 Brotli 或 gzip；",[454,2251,2252],{},"Brotli 使用质量 4，gzip 使用级别 6，在 CPU 与体积间取中间值；",[454,2254,2255],{},"使用读取流和 pipeline，不把大文件一次性读进内存；",[454,2257,2258],{},"根据文件大小和修改时间生成弱 ETag；",[454,2260,2261,2262,2265],{},"命中 ",[55,2263,2264],{},"If-None-Match"," 时返回 304；",[454,2267,2268,2271],{},[55,2269,2270],{},"_nuxt\u002F"," 哈希资源缓存一年并标记 immutable；",[454,2273,2274],{},"HTML、图片等非哈希路径使用 no-cache，确保 release 切换后会重新验证；",[454,2276,2277],{},"收到 SIGINT 或 SIGTERM 时停止接受新连接并正常退出。",[91,2279,2280,2281,2283],{},"如果 ",[55,2282,438],{}," 不可用，服务器返回 503，而不是把文件系统错误暴露给访问者。若响应流已经开始后出错，则销毁连接，避免发送一半文件后再拼接错误文本。",[91,2285,2286,2287,2290],{},"它不会处理 TLS、OAuth 或反向代理。公网 HTTPS 一般由 Nginx、Caddy、访问代理或隧道层终止，再转发到本机 3000。把服务监听改成 ",[55,2288,2289],{},"0.0.0.0"," 只代表网络接口可达，不会自动获得 HTTPS，也不会自动建立访问控制。",[101,2292,2294],{"id":2293},"二十五300031003101-分别是什么","二十五、3000、3100、3101 分别是什么",[486,2296,2297,2310],{},[489,2298,2299],{},[492,2300,2301,2304,2307],{},[495,2302,2303],{},"端口",[495,2305,2306],{},"用途",[495,2308,2309],{},"生命周期",[502,2311,2312,2323,2334],{},[492,2313,2314,2317,2320],{},[507,2315,2316],{},"3000",[507,2318,2319],{},"当前生产静态 release",[507,2321,2322],{},"systemd 长期运行",[492,2324,2325,2328,2331],{},[507,2326,2327],{},"3100",[507,2329,2330],{},"远程开发或稳定预览",[507,2332,2333],{},"人工启动，需要时运行",[492,2335,2336,2339,2342],{},[507,2337,2338],{},"3101",[507,2340,2341],{},"Playwright 隔离测试服务",[507,2343,2344],{},"测试自动启动并结束",[91,2346,2347,2348,2351],{},"开发命令使用 ",[55,2349,2350],{},"--host 0.0.0.0"," 后，可以从远程电脑访问 VPS 的 3100，但还必须满足防火墙、Tailscale\u002F内网路由和浏览器安全策略。Sveltia 的本地仓库模式依赖 Chromium File System Access API；通过普通 HTTP 远程访问时，浏览器可能因为不是安全上下文而拒绝文件系统权限。解决方向是通过 HTTPS 访问后台，或在实际拥有仓库文件的电脑上用 localhost 打开，而不是继续扩大 3100 的公网暴露。",[91,2353,2354,2355,2357],{},"3101 使用独立内容 fixture 和 ",[55,2356,738],{},"，不能拿它当日常预览端口。生产 3000、开发 3100 和测试 3101 可以同时存在，因为缓存目录和端口都隔离。",[101,2359,2361],{"id":2360},"二十六systemd-用户服务","二十六、systemd 用户服务",[91,2363,2364,2365,2368],{},"生产服务由 ",[55,2366,2367],{},"ops\u002Fsystemd\u002Fpersonal-site.service"," 描述。它的关键设置包括：",[451,2370,2371,2377,2383,2389,2395,2404],{},[454,2372,2373,2376],{},[55,2374,2375],{},"Type=simple","：Node 进程本身就是主进程；",[454,2378,2379,2382],{},[55,2380,2381],{},"After\u002FWants=network-online.target","：网络就绪后启动；",[454,2384,2385,2388],{},[55,2386,2387],{},"Restart=on-failure"," 与 5 秒延迟：异常退出后自动恢复；",[454,2390,2391,2394],{},[55,2392,2393],{},"KillSignal=SIGINT","：与静态服务器的优雅关闭逻辑对应；",[454,2396,2397,659,2400,2403],{},[55,2398,2399],{},"NoNewPrivileges=true",[55,2401,2402],{},"PrivateTmp=true","：缩小运行时权限；",[454,2405,2406,2407,2410],{},"安装到用户级 ",[55,2408,2409],{},"default.target","，不要求整个服务以 root 运行。",[91,2412,2413,2414,2417,2418,2421],{},"unit 当前把 Node 可执行文件写成 NVM 下的明确路径。升级 Node 或切换 NVM 版本后，shell 中的 ",[55,2415,2416],{},"node"," 可能已经变化，但 systemd 仍引用旧路径，这是需要主动检查的运维陷阱。修改 unit 后必须 ",[55,2419,2420],{},"daemon-reload","，而普通文章或页面 release 不需要重启服务。",[91,2423,2424,2425,2428,2429,2432],{},"用户级服务要在 VPS 重启且用户未登录时自动启动，需要为运行网站的 Linux 用户启用 linger。管理它时应使用相同用户的 ",[55,2426,2427],{},"systemctl --user","，不应使用 ",[55,2430,2431],{},"sudo systemctl --user"," 去连接 root 的用户总线。",[101,2434,2436],{"id":2435},"二十七测试体系究竟覆盖什么","二十七、测试体系究竟覆盖什么",[91,2438,2439],{},"测试按风险边界分成三组。",[2072,2441,2443],{"id":2442},"内容和-writer-单元测试","内容和 writer 单元测试",[91,2445,2446,2449],{},[55,2447,2448],{},"test:content"," 检查：",[451,2451,2452,2455,2458,2461,2464,2467,2470,2473],{},[454,2453,2454],{},"合法文章和四种分类可以通过；",[454,2456,2457],{},"非法日期、分类、文件名、重复标签和空正文会失败；",[454,2459,2460],{},"来源节必须包含公共 HTTP(S) 链接；",[454,2462,2463],{},"CMS 可选 slug 必须与文件名一致；",[454,2465,2466],{},"站点 YAML 满足 Schema；",[454,2468,2469],{},"writer 拒绝覆盖、穿越、符号链接和错误修订日期；",[454,2471,2472],{},"更新保留发布日期；",[454,2474,2475],{},"删除只接受精确存在的 dated slug。",[2072,2477,2479],{"id":2478},"release-单元测试","release 单元测试",[91,2481,2482,2485],{},[55,2483,2484],{},"test:release"," 在临时目录中检查：",[451,2487,2488,2493,2496,2499,2502],{},[454,2489,2490,2492],{},[55,2491,438],{}," 能原子切换；",[454,2494,2495],{},"清理历史版本时保留激活 release；",[454,2497,2498],{},"release 名称不能路径穿越；",[454,2500,2501],{},"受管内容路径不会扩大到应用代码；",[454,2503,2504],{},"子命令失败时错误信息保留退出码。",[2072,2506,2508],{"id":2507},"playwright-浏览器测试","Playwright 浏览器测试",[91,2510,2511,2514],{},[55,2512,2513],{},"test:e2e"," 在 Chromium 中检查：",[451,2516,2517,2520,2523,2526,2529,2532,2535,2538,2541,2544,2547],{},[454,2518,2519],{},"首页成功水合且没有控制台错误；",[454,2521,2522],{},"动态 favicon、theme-color 和 RGB 输出同步；",[454,2524,2525],{},"自定义主题在纯黑纯白下仍可读；",[454,2527,2528],{},"旧黄色缓存会迁移；",[454,2530,2531],{},"mask 没加载完时字标不偷跑，加载后正常播放；",[454,2533,2534],{},"标签页激活、窗口 focus、换色、滑杆松手和返回主页会重播；",[454,2536,2537],{},"拖动期间不会反复播放；",[454,2539,2540],{},"服务状态、NAS 图标、最近文章、文章详情和更新日期正确；",[454,2542,2543],{},"文章悬浮只影响当前行，长标题宽度不跳变；",[454,2545,2546],{},"手机页面无横向溢出，RGB 在小屏隐藏；",[454,2548,2549],{},"多种桌面尺寸下关键模块互不重叠。",[91,2551,2552],{},"Playwright 配置允许一次重试，等待时间 10 秒，临时 Nuxt 服务启动最长等待 120 秒。响应式几何测试启用 reduced motion，避免入场动画中的瞬时位置影响布局判断。",[91,2554,2555],{},"测试不是越多越好。这里保留的是曾经真实出错、或者一旦回归就很难靠类型系统发现的行为；字体文件数量、每个 CSS 颜色和每一段正文不需要分别写测试。",[101,2557,2559],{"id":2558},"二十八当前性能画像与做过的优化","二十八、当前性能画像与做过的优化",[91,2561,2562],{},"在当前版本的一次本机测量中：",[451,2564,2565,2568,2571,2574,2577],{},[454,2566,2567],{},"主 CSS 约 31.1 KB，gzip 后约 6.9 KB；",[454,2569,2570],{},"外部或本地字体文件由 98 个减少到 0；",[454,2572,2573],{},"首页一次传输约 252 KB；",[454,2575,2576],{},"模拟 4G 和 4 倍 CPU 降速时，LCP 约 0.75 秒，完整 load 约 1.37 秒；",[454,2578,2579],{},"CLS 为 0。",[91,2581,2582],{},"这些数字是环境相关快照，不是永久承诺。浏览器缓存、网络、CPU、文章数量和依赖升级都会改变结果。",[91,2584,2585],{},"当前主要性能措施包括：",[451,2587,2588,2591,2594,2597,2603,2608,2611,2614,2617,2620,2623],{},[454,2589,2590],{},"静态预渲染，HTML 首次响应包含页面内容；",[454,2592,2593],{},"移除大批字体资源，改用系统字体；",[454,2595,2596],{},"只预加载首屏真正依赖的 30 KB 字标 mask；",[454,2598,2599,2600,2602],{},"字标等待 ",[55,2601,1483],{},"，避免资源未准备好时动画丢失；",[454,2604,2605,2607],{},[55,2606,1091],{}," 合并高频指针更新；",[454,2609,2610],{},"缓存元素边界，避免每次 pointermove 读取布局；",[454,2612,2613],{},"连续调色只改颜色，松手才重播动画；",[454,2615,2616],{},"用 transform\u002Fopacity 处理大多数动效；",[454,2618,2619],{},"生产服务器流式响应并支持 Brotli、gzip、ETag 和长期哈希缓存；",[454,2621,2622],{},"固定组件尺寸，避免动态文本造成布局偏移；",[454,2624,2625],{},"分离开发、release 和 E2E 的 Nuxt Content 数据库。",[91,2627,2628,2630],{},[55,2629,434],{}," 整体约 5.4 MB，其中包括 Nuxt Content 的客户端 SQLite\u002FWASM 相关资源；这不等于每个访客首屏都会下载整个目录。分析性能时应看浏览器实际请求和传输体积，不应把产物目录大小直接当作首页流量。",[101,2632,2634],{"id":2633},"二十九为什么首次交互偶尔会过一会儿才正常","二十九、为什么首次交互偶尔会“过一会儿才正常”",[91,2636,2637],{},"这个问题曾同时表现为字标不播放和 RGB 滑杆暂时失灵，根因方向不是滑杆 CSS 本身，而是客户端水合尚未完成或开发服务器仍在编译。静态 HTML 可以先显示，但 Vue 事件只有在 JavaScript 加载、执行并成功水合后才生效。",[91,2639,2640,2641,2644],{},"判断方法是观察 ",[55,2642,2643],{},".site-shell[data-hydrated=\"true\"]","。如果页面已经显示但该属性迟迟没有变成 true，应检查：",[451,2646,2647,2650,2653,2656,2659],{},[454,2648,2649],{},"浏览器控制台是否有 JavaScript 错误；",[454,2651,2652],{},"Nuxt 开发服务器是否还在首次编译；",[454,2654,2655],{},"内容 SQLite 缓存是否损坏；",[454,2657,2658],{},"大型依赖或资源是否阻塞客户端入口；",[454,2660,2661],{},"当前访问的是 3100 开发服务，还是已经生成的生产静态站。",[91,2663,2664],{},"目前通过移除字体、减轻入口资源、预加载 mask、分离内容数据库和明确动画水合闸门改善了这个过程。生产静态站通常比第一次启动的开发服务器稳定，因为它不需要边访问边编译。",[101,2666,2668],{"id":2667},"三十常见修改应该改哪里","三十、常见修改应该改哪里",[2072,2670,2672],{"id":2671},"修改个人介绍栏目文案或服务","修改个人介绍、栏目文案或服务",[91,2674,2675,2676,2678],{},"优先通过 CMS 或编辑 ",[55,2677,669],{},"。若新增服务状态或图标类型，还要同步修改 Schema、配置枚举、CMS 选项、组件映射、CSS 和测试。",[2072,2680,2681],{"id":2681},"修改默认颜色",[91,2683,2684,2685,2687,2688,2690],{},"修改 ",[55,2686,1207],{},"。它可以是任意 ",[55,2689,866],{},"。已有访客若保存过自定义颜色，会继续看到自己的选择；要做全体迁移，需要像旧黄色迁移一样明确识别并处理旧值，不能无条件清空 localStorage。",[2072,2692,2693],{"id":2693},"修改红绿蓝预设",[91,2695,2684,2696,2698,2699,2702],{},[55,2697,1143],{}," 的 ",[55,2700,2701],{},"accentPresets","。RGB 面板和非主页调色按钮都复用它。修改后应测试纯黑纯白对比、localStorage 恢复和字标重播。",[2072,2704,2705],{"id":2705},"修改字标图",[91,2707,2708,2709,2711,2712,2715],{},"替换 ",[55,2710,1410],{},"，尽量保留透明背景和接近 1127:293 的宽高比；若比例改变，同步修改 CSS ",[55,2713,2714],{},"aspect-ratio","。检查 preload 路径、CSS mask 路径和组件资源路径三者一致。",[2072,2717,2718],{"id":2718},"修改字标动画",[91,2720,2721,2722,2724,2725,2728,2729,2732],{},"播放条件在 ",[55,2723,1457],{},"，跨组件触发在 ",[55,2726,2727],{},"useWordmarkAnimation.ts","，视觉关键帧在 ",[55,2730,2731],{},"main.css","。不要把三者混成一个大组件：资源状态、事件状态和视觉时间线是不同责任。",[2072,2734,2735],{"id":2735},"修改文章分类",[91,2737,2738,2739,2742],{},"至少同步 ",[55,2740,2741],{},"app\u002Fconfig\u002Farticles.ts","、Nuxt Content Schema、CMS 选项、校验器测试与界面测试。文章中的旧分类是否迁移，需要单独决定。",[2072,2744,2745],{"id":2745},"修改文章样式",[91,2747,2748,2749,2752,2753,2755,2756,2759],{},"文章列表看 ",[55,2750,2751],{},".article-row","，正文看 ",[55,2754,1739],{},"，详情头部看 ",[55,2757,2758],{},".article-hero","。长标题、手机宽度、hover 前后几何和其他文章 opacity 是必须复查的回归点。",[2072,2761,2762],{"id":2762},"修改生产服务",[91,2764,2765,2766,2768],{},"静态响应逻辑改 ",[55,2767,2194],{},"；启动用户、Node 路径、重启策略改 systemd unit。只有这两类变化需要重启服务本身，普通 release 切换不需要。",[101,2770,2772],{"id":2771},"三十一日常发布配方","三十一、日常发布配方",[2072,2774,2776],{"id":2775},"只发布文章或-yaml-内容","只发布文章或 YAML 内容",[417,2778,2782],{"className":2779,"code":2780,"language":2781,"meta":125,"style":125},"language-bash shiki shiki-themes github-light github-dark","npm run content:validate\nnpm run publish\n","bash",[55,2783,2784,2795],{"__ignoreMap":125},[977,2785,2786,2789,2792],{"class":979,"line":980},[977,2787,2788],{"class":991},"npm",[977,2790,2791],{"class":998}," run",[977,2793,2794],{"class":998}," content:validate\n",[977,2796,2797,2799,2801],{"class":979,"line":126},[977,2798,2788],{"class":991},[977,2800,2791],{"class":998},[977,2802,2803],{"class":998}," publish\n",[91,2805,2806,2808],{},[55,2807,2110],{}," 成功后会输出 commit、release 和 current 路径。它创建的是本地提交；是否推送 GitHub 是另一项操作。",[2072,2810,2812],{"id":2811},"发布-vuecss脚本或配置代码","发布 Vue、CSS、脚本或配置代码",[417,2814,2816],{"className":2779,"code":2815,"language":2781,"meta":125,"style":125},"npm run typecheck\nnpm run test:content\nnpm run test:release\nnpm run test:e2e\nnpm run generate\ngit diff --check\n# 明确检查并提交本次文件\nnpm run deploy\n",[55,2817,2818,2827,2836,2845,2854,2863,2874,2880],{"__ignoreMap":125},[977,2819,2820,2822,2824],{"class":979,"line":980},[977,2821,2788],{"class":991},[977,2823,2791],{"class":998},[977,2825,2826],{"class":998}," typecheck\n",[977,2828,2829,2831,2833],{"class":979,"line":126},[977,2830,2788],{"class":991},[977,2832,2791],{"class":998},[977,2834,2835],{"class":998}," test:content\n",[977,2837,2838,2840,2842],{"class":979,"line":22},[977,2839,2788],{"class":991},[977,2841,2791],{"class":998},[977,2843,2844],{"class":998}," test:release\n",[977,2846,2847,2849,2851],{"class":979,"line":1188},[977,2848,2788],{"class":991},[977,2850,2791],{"class":998},[977,2852,2853],{"class":998}," test:e2e\n",[977,2855,2856,2858,2860],{"class":979,"line":1198},[977,2857,2788],{"class":991},[977,2859,2791],{"class":998},[977,2861,2862],{"class":998}," generate\n",[977,2864,2865,2868,2871],{"class":979,"line":1802},[977,2866,2867],{"class":991},"git",[977,2869,2870],{"class":998}," diff",[977,2872,2873],{"class":1175}," --check\n",[977,2875,2876],{"class":979,"line":1811},[977,2877,2879],{"class":2878},"sJ8bj","# 明确检查并提交本次文件\n",[977,2881,2882,2884,2886],{"class":979,"line":1820},[977,2883,2788],{"class":991},[977,2885,2791],{"class":998},[977,2887,2888],{"class":998}," deploy\n",[91,2890,2891,2893],{},[55,2892,2114],{}," 自身也会执行完整检查，前面的命令适合在提交前尽早发现问题。工作区不干净时它会拒绝上线。",[2072,2895,2896],{"id":2896},"查看当前生产状态",[417,2898,2900],{"className":2779,"code":2899,"language":2781,"meta":125,"style":125},"systemctl --user is-active personal-site.service\nreadlink -f \"$SITE_DATA\u002Fcurrent\"\ncurl -fsS -o \u002Fdev\u002Fnull -w '%{http_code} %{content_type}\\n' http:\u002F\u002F127.0.0.1:3000\u002F\n",[55,2901,2902,2916,2933],{"__ignoreMap":125},[977,2903,2904,2907,2910,2913],{"class":979,"line":980},[977,2905,2906],{"class":991},"systemctl",[977,2908,2909],{"class":1175}," --user",[977,2911,2912],{"class":998}," is-active",[977,2914,2915],{"class":998}," personal-site.service\n",[977,2917,2918,2921,2924,2927,2930],{"class":979,"line":126},[977,2919,2920],{"class":991},"readlink",[977,2922,2923],{"class":1175}," -f",[977,2925,2926],{"class":998}," \"",[977,2928,2929],{"class":983},"$SITE_DATA",[977,2931,2932],{"class":998},"\u002Fcurrent\"\n",[977,2934,2935,2938,2941,2944,2947,2950,2953],{"class":979,"line":22},[977,2936,2937],{"class":991},"curl",[977,2939,2940],{"class":1175}," -fsS",[977,2942,2943],{"class":1175}," -o",[977,2945,2946],{"class":998}," \u002Fdev\u002Fnull",[977,2948,2949],{"class":1175}," -w",[977,2951,2952],{"class":998}," '%{http_code} %{content_type}\\n'",[977,2954,2955],{"class":998}," http:\u002F\u002F127.0.0.1:3000\u002F\n",[91,2957,2958,2960],{},[55,2959,2929],{}," 应指向个人站点的 release 数据目录，不要把示例变量直接用于删除命令。",[2072,2962,2963],{"id":2963},"回滚",[91,2965,2966],{},"先列出确实存在的 release，再执行：",[417,2968,2970],{"className":2779,"code":2969,"language":2781,"meta":125,"style":125},"npm run rollback -- \u003Cexact-release-id>\n",[55,2971,2972],{"__ignoreMap":125},[977,2973,2974,2976,2978,2981,2984,2987,2990,2993],{"class":979,"line":980},[977,2975,2788],{"class":991},[977,2977,2791],{"class":998},[977,2979,2980],{"class":998}," rollback",[977,2982,2983],{"class":1175}," --",[977,2985,2986],{"class":1156}," \u003C",[977,2988,2989],{"class":998},"exact-release-i",[977,2991,2992],{"class":983},"d",[977,2994,1010],{"class":1156},[91,2996,2997,2998,3000,3001,3003,3004,1230],{},"回滚后再次检查 ",[55,2999,438],{}," 和 3000 返回值。不要手动删除 ",[55,3002,438],{},"，也不要把它指向仓库的 ",[55,3005,434],{},[101,3007,3009],{"id":3008},"三十二故障排查顺序","三十二、故障排查顺序",[2072,3011,3012],{"id":3012},"文章已保存但网站看不到",[91,3014,3015,3016,3018,3019,3021],{},"依次确认：文章是否在 ",[55,3017,672],{},"、校验是否通过、是否执行 publish\u002Fdeploy、",[55,3020,438],{}," 是否指向新 release、3000 返回的 HTML 是否包含新标题。CMS 保存和 Git push 本身都不等于部署完成。",[2072,3023,3025],{"id":3024},"rgb-不能拖按钮不能点动画不播放","RGB 不能拖、按钮不能点、动画不播放",[91,3027,3028,3029,3032,3033,3036],{},"先看 ",[55,3030,3031],{},"data-hydrated","，再看控制台错误和网络请求。若只发生在 Nuxt 第一次开发编译，等待编译完成后重载；若持续发生，停止开发服务，运行 ",[55,3034,3035],{},"npx nuxt cleanup","，再启动 3100。不要为此停止生产 3000。",[2072,3038,3039],{"id":3039},"切回标签页没有动画",[91,3041,3042,3043,659,3045,3047],{},"检查浏览器是否启用 reduced motion、mask 图片是否加载失败，以及 ",[55,3044,1551],{},[55,3046,1554],{}," 是否触发。一次切回只播一次是正常防抖，不应去掉 200ms 合并后让三个事件连续触发。",[2072,3049,3050],{"id":3050},"换色先闪回旧颜色",[91,3052,3053,3054,3056],{},"检查静态默认色、Nuxt ",[55,3055,1211],{}," 初始值和 localStorage 恢复顺序。服务端 HTML无法知道客户端保存颜色，完全避免首帧差异需要在页面渲染前执行极小的内联主题恢复脚本；当前实现选择保持静态生成简单，在水合时恢复。",[2072,3058,3060],{"id":3059},"服务状态点不随-cms-变化","服务状态点不随 CMS 变化",[91,3062,3063,3064,3067,3068,3070],{},"确认 YAML 中 ",[55,3065,3066],{},"state"," 已保存、值属于三个枚举、已经重新生成 release，并检查 DOM 的 ",[55,3069,1616],{},"。如果属性已变而颜色没变，检查 CSS 状态选择器；如果属性没变，检查当前访问的 release 是否仍是旧版本。",[2072,3072,3074],{"id":3073},"_3000-无法访问","3000 无法访问",[91,3076,3077,3078,3080,3081,3083],{},"检查用户级 systemd 状态、日志、Node 固定路径、端口占用和 ",[55,3079,438],{}," 链接。服务器进程存在但 ",[55,3082,438],{}," 失效时会返回 503。不要在未确认进程归属前直接杀端口进程。",[2072,3085,3087],{"id":3086},"管理页面提示只允许-https","管理页面提示只允许 HTTPS",[91,3089,3090],{},"这通常来自浏览器安全上下文要求，而不是 Git remote 配错。Git remote 只决定仓库同步地址，不会给 HTTP 页面增加 HTTPS。使用 localhost、本机仓库模式，或为远程后台配置可信 HTTPS 和 Git OAuth；同时把后台放在 Tailscale或访问控制后面，因为后台路径本身不是权限系统。",[101,3092,3094],{"id":3093},"三十三安全与备份边界","三十三、安全与备份边界",[91,3096,3097],{},"至少要区分三类数据：",[417,3099,3102],{"className":3100,"code":3101,"language":422,"meta":125},[420],"Git 仓库       源码、文章、站点设置、公开静态资源\nOpenClaw 目录  Skill、草稿、会话和本地配置\nrelease 目录   当前及历史静态构建结果\n",[55,3103,3101],{"__ignoreMap":125},[91,3105,3106],{},"Git 提交是版本历史，不是异地备份。私人远程仓库可以备份源码与文章，但 OpenClaw 配置和 release 数据需要单独备份到受控存储。",[91,3108,3109,3110,3112],{},"永远不要提交或写入公开文章的内容包括：API key、OAuth secret、部署私钥、QQ token、cookie、扫码状态、",[55,3111,1948],{},"、私人服务密码、内部地址清单和不适合公开的资产信息。",[91,3114,3115,3116,3119,3120,3123],{},"CMS 的 ",[55,3117,3118],{},"\u002Fadmin\u002F"," 路径和 ",[55,3121,3122],{},"noindex"," 只能减少搜索引擎收录，不能阻止陌生人访问。真正的保护来自 Git 登录、HTTPS、网络访问范围和最小权限部署凭据。",[101,3125,3127],{"id":3126},"三十四维护这套代码时应坚持的原则","三十四、维护这套代码时应坚持的原则",[91,3129,3130],{},"第一，内容、表现和发布边界分开。能在 YAML 解决的文案不要硬编码进 Vue；能由共享组件表达的状态不要在两个页面复制；生产切换不要混进页面代码。",[91,3132,3133],{},"第二，把浏览器状态当成显式状态。主题色、资源是否解码、页面是否可见、指针是否仍按下、水合是否完成，都应有清楚的变量和生命周期，而不是靠延时猜测。",[91,3135,3136],{},"第三，动画必须有静态最终状态。资源失败、JavaScript 失败或用户减少动态效果时，标题仍要可读，布局仍要成立。",[91,3138,3139],{},"第四，自动化写入必须比人工编辑权限更窄。Skill 负责工作流，writer 负责硬边界，validator 负责内容合约，release 负责上线，四者不能互相冒充。",[91,3141,3142],{},"第五，生产部署应该是“生成一个完整新版本，然后切换”，而不是在访问者正在读取的目录里逐个覆盖文件。原子 release 是这个小网站最值得长期保留的工程设计之一。",[91,3144,3145],{},"第六，测试真实的关系和历史 bug。主题对比、滑杆松手、标签页重播、长标题 hover、服务状态同步和多视口不重叠，都来自实际使用中的问题，比为了提高数字而堆大量脆弱测试更有价值。",[101,3147,3149],{"id":3148},"三十五重新上手时的最短阅读路径","三十五、重新上手时的最短阅读路径",[91,3151,3152],{},"如果未来很久没有维护这个项目，按下面顺序读，可以最快恢复上下文：",[631,3154,3155,3161,3169,3178,3184,3189,3198],{},[454,3156,3157,3158,3160],{},"看 ",[55,3159,669],{},"，知道网站当前展示什么。",[454,3162,3157,3163,673,3166,3168],{},[55,3164,3165],{},"app\u002Fpages\u002Findex.vue",[55,3167,2731],{}," 的主页部分，理解首屏结构。",[454,3170,3157,3171,659,3173,659,3175,3177],{},[55,3172,1143],{},[55,3174,1323],{},[55,3176,1457],{},"，理解最复杂的交互。",[454,3179,3180,3181,3183],{},"看两个 writing 页面和 ",[55,3182,755],{},"，理解文章查询与渲染。",[454,3185,3157,3186,3188],{},[55,3187,857],{},"、validator 和 writer，理解内容边界。",[454,3190,3157,3191,659,3194,3197],{},[55,3192,3193],{},"release.ts",[55,3195,3196],{},"static-server.mjs"," 和 systemd unit，理解生产链路。",[454,3199,3200],{},"最后看测试，把“哪些行为不能再坏”快速过一遍。",[91,3202,3203],{},"只要能重新回答下面五个问题，就已经掌握了这个项目：",[451,3205,3206,3209,3212,3215,3218],{},[454,3207,3208],{},"当前页面内容的唯一来源在哪里？",[454,3210,3211],{},"浏览器中的主题色如何从 RGB 状态传到 CSS、字标和 favicon？",[454,3213,3214],{},"为什么 CMS 保存后线上不会立刻变化？",[454,3216,3217],{},"publish 和 deploy 的权限、检查与 Git 行为有什么不同？",[454,3219,3220],{},"一个新 release 如何在不重启 3000 的情况下接管生产请求？",[91,3222,3223],{},"这五条就是 Quilibra 当前技术架构的骨架。",[101,3225,3226],{"id":3226},"来源与延伸阅读",[451,3228,3229,3238,3245,3252,3259,3266,3273,3280],{},[454,3230,3231],{},[3232,3233,3237],"a",{"href":3234,"rel":3235},"https:\u002F\u002Fnuxt.com\u002Fdocs",[3236],"nofollow","Nuxt 文档",[454,3239,3240],{},[3232,3241,3244],{"href":3242,"rel":3243},"https:\u002F\u002Fcontent.nuxt.com\u002F",[3236],"Nuxt Content 文档",[454,3246,3247],{},[3232,3248,3251],{"href":3249,"rel":3250},"https:\u002F\u002Fvuejs.org\u002Fguide\u002Fextras\u002Fcomposition-api-faq.html",[3236],"Vue Composition API",[454,3253,3254],{},[3232,3255,3258],{"href":3256,"rel":3257},"https:\u002F\u002Fplaywright.dev\u002Fdocs\u002Fintro",[3236],"Playwright 文档",[454,3260,3261],{},[3232,3262,3265],{"href":3263,"rel":3264},"https:\u002F\u002Fgithub.com\u002Fsveltia\u002Fsveltia-cms",[3236],"Sveltia CMS 文档",[454,3267,3268],{},[3232,3269,3272],{"href":3270,"rel":3271},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FCSS\u002Fmask",[3236],"MDN：CSS mask",[454,3274,3275],{},[3232,3276,3279],{"href":3277,"rel":3278},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FPage_Visibility_API",[3236],"MDN：Page Visibility API",[454,3281,3282],{},[3232,3283,3286],{"href":3284,"rel":3285},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FCaching",[3236],"MDN：HTTP 缓存",[3288,3289,3290],"style",{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}",{"title":125,"searchDepth":126,"depth":126,"links":3292},[3293,3294,3295,3296,3297,3298,3299,3300,3301,3302,3303,3304,3305,3306,3307,3308,3309,3310,3311,3312,3313,3314,3318,3319,3320,3321,3322,3327,3328,3329,3339,3345,3354,3355,3356,3357],{"id":408,"depth":126,"text":409},{"id":445,"depth":126,"text":446},{"id":480,"depth":126,"text":481},{"id":616,"depth":126,"text":617},{"id":680,"depth":126,"text":681},{"id":802,"depth":126,"text":803},{"id":911,"depth":126,"text":912},{"id":1027,"depth":126,"text":1028},{"id":1098,"depth":126,"text":1099},{"id":1136,"depth":126,"text":1137},{"id":1260,"depth":126,"text":1261},{"id":1317,"depth":126,"text":1318},{"id":1403,"depth":126,"text":1404},{"id":1504,"depth":126,"text":1505},{"id":1578,"depth":126,"text":1579},{"id":1649,"depth":126,"text":1650},{"id":1704,"depth":126,"text":1705},{"id":1743,"depth":126,"text":1744},{"id":1896,"depth":126,"text":1897},{"id":1968,"depth":126,"text":1969},{"id":2027,"depth":126,"text":2028},{"id":2066,"depth":126,"text":2067,"children":3315},[3316,3317],{"id":2074,"depth":22,"text":2077},{"id":2092,"depth":22,"text":2095},{"id":2124,"depth":126,"text":2125},{"id":2188,"depth":126,"text":2189},{"id":2293,"depth":126,"text":2294},{"id":2360,"depth":126,"text":2361},{"id":2435,"depth":126,"text":2436,"children":3323},[3324,3325,3326],{"id":2442,"depth":22,"text":2443},{"id":2478,"depth":22,"text":2479},{"id":2507,"depth":22,"text":2508},{"id":2558,"depth":126,"text":2559},{"id":2633,"depth":126,"text":2634},{"id":2667,"depth":126,"text":2668,"children":3330},[3331,3332,3333,3334,3335,3336,3337,3338],{"id":2671,"depth":22,"text":2672},{"id":2681,"depth":22,"text":2681},{"id":2693,"depth":22,"text":2693},{"id":2705,"depth":22,"text":2705},{"id":2718,"depth":22,"text":2718},{"id":2735,"depth":22,"text":2735},{"id":2745,"depth":22,"text":2745},{"id":2762,"depth":22,"text":2762},{"id":2771,"depth":126,"text":2772,"children":3340},[3341,3342,3343,3344],{"id":2775,"depth":22,"text":2776},{"id":2811,"depth":22,"text":2812},{"id":2896,"depth":22,"text":2896},{"id":2963,"depth":22,"text":2963},{"id":3008,"depth":126,"text":3009,"children":3346},[3347,3348,3349,3350,3351,3352,3353],{"id":3012,"depth":22,"text":3012},{"id":3024,"depth":22,"text":3025},{"id":3039,"depth":22,"text":3039},{"id":3050,"depth":22,"text":3050},{"id":3059,"depth":22,"text":3060},{"id":3073,"depth":22,"text":3074},{"id":3086,"depth":22,"text":3087},{"id":3093,"depth":126,"text":3094},{"id":3126,"depth":126,"text":3127},{"id":3148,"depth":126,"text":3149},{"id":3226,"depth":126,"text":3226},"学习","完整记录 Quilibra 个人主页当前版本的技术选型、页面架构、内容系统、主题动画、测试体系、发布流程和日常维护方法。",{},"\u002Fwriting\u002F2026-07-26-quilibra-complete-technical-handbook","2026-07-26T23:46:23+08:00",{"title":397,"description":3359},"writing\u002F2026-07-26-quilibra-complete-technical-handbook",[3366,3367,525,3368,573,565,3369],"Nuxt","Vue","Nuxt Content","静态部署","ZT33YZq1D8x6VIr-hI2qE15LFS3Qlkr_dV3lsgBWpcw",{"id":3372,"title":3373,"body":3374,"category":279,"date":382,"description":3533,"extension":134,"meta":3534,"navigation":18,"path":3535,"publishedAt":3362,"seo":3536,"slug":3537,"stem":3538,"tags":3539,"updated":382,"__hash__":3542},"writing\u002Fwriting\u002F2026-07-26-trading-cognition-and-compound-reality.md","交易是为了赚钱还是验证认知：从量化门槛到复利现实",{"type":88,"value":3375,"toc":3522},[3376,3379,3383,3386,3389,3393,3396,3399,3402,3405,3408,3411,3414,3418,3421,3441,3444,3464,3467,3470,3484,3487,3490,3493,3496,3499,3503,3506,3509,3513,3516,3519],[91,3377,3378],{},"刷到一个清华博士的视频，说想赚钱就去量化。但普通人的门槛是不是太高？就算跨过去了，市场容量真的够赚到钱吗？带着这些问题和 AI 聊了一圈，从量化门槛一路聊到\"你到底为什么做交易\"，把思路理了一遍。",[101,3380,3382],{"id":3381},"机构量化-vs-系统化交易","机构量化 vs 系统化交易",[91,3384,3385],{},"机构量化（幻方、九坤级别）的门槛确实很高：博士学历、海量 tick 数据、专用算力、上亿起步资金，而且赛道内卷、alpha 衰减快、容量有限。",[91,3387,3388],{},"但普通人能做的是\"系统化交易\"而非机构量化。20 日均线 + 严格止损 + 行业 ETF，这套逻辑本质就是量化思维。真正的问题不是门槛，是把博士生的参照系错误地套用在自己身上。这类建议对清北学生可操作，对大多数人是废话，因为它省略了关键前提：清北学生的起点已经过滤掉 90% 的竞争。",[101,3390,3392],{"id":3391},"只是为了赚钱可能是对自己的贬低","\"只是为了赚钱\"可能是对自己的贬低",[91,3394,3395],{},"我说做交易只是为了赚钱。但仔细想想，我对系统和机制本身一直有探究欲--止损逻辑、Hyperliquid 架构、自己项目的技术选型会追求优雅和性能。真正纯粹为钱的人不会纠结止损后策略逻辑对不对。",[91,3397,3398],{},"如果账户明天清零，还会不会继续研究这套系统？会的。因为做交易挣不挣钱是对我认知是否正确的检验，猜对了奖励，猜错了亏钱。我在市场里的目的是验证认知，想知道自己是怎样的人。",[91,3400,3401],{},"核心驱动不是钱，是\"认知闭环\"--市场是不会说谎的裁判，钱只是计分板。",[101,3403,3404],{"id":3404},"一个需要警惕的特质",[91,3406,3407],{},"对\"是否正确\"极度敏感的人，容易把坚持系统等同于坚持自我，把止损等同于承认\"我是错的\"。如果哪天开始扛单不是因为信号而是无法接受\"我看错了\"，这个特质就从优势变成风险。",[91,3409,3410],{},"关键区分：把\"验证认知\"和\"验证自我价值\"分开。市场说这笔交易错了，不等于整个判断体系错了。我相信市场大部分时间是对的，应该是我往市场靠去检验自己，而不是市场错的时候坚持自己。但空仓时说这话容易，真正重仓浮亏 5%、系统说止损但脑子里说\"只是短期波动\"的那一刻，这套认知还在不在才是真考验。",[91,3412,3413],{},"止损系统的价值不只是风控，更是强制执行那些理性认同但情绪会动摇的信念。",[101,3415,3417],{"id":3416},"_10-万到几百万数学可行执行淘汰大多数人","10 万到几百万：数学可行，执行淘汰大多数人",[91,3419,3420],{},"市场容量直接排除--A 股日均成交额 8000 亿到 1.2 万亿，几十万到几百万对市场影响约等于零。真实难度分三段：",[451,3422,3423,3429,3435],{},[454,3424,3425,3428],{},[429,3426,3427],{},"10 万到 100 万","：拼策略稳定性和纪律一致性",[454,3430,3431,3434],{},[429,3432,3433],{},"100 万到 500 万","：拼复利需要时间，以及账户变大后心态是否变化（100 万亏 10% 是 10 万，感受和 10 万亏 10% 完全不同）",[454,3436,3437,3440],{},[429,3438,3439],{},"500 万以上","：拼市场风格切换时系统能否不变形",[91,3442,3443],{},"参照现有系统严格执行，年化 15%-30% 的历史区间成立。三种情景的复利推算：",[451,3445,3446,3452,3458],{},[454,3447,3448,3451],{},[429,3449,3450],{},"保守 15%","：10 万到 100 万约 17 年，到 500 万约 39 年",[454,3453,3454,3457],{},[429,3455,3456],{},"中性 20%","：10 万到 100 万约 13 年，到 500 万约 21 年",[454,3459,3460,3463],{},[429,3461,3462],{},"乐观 25%","：10 万到 100 万约 11 年，到 500 万约 15 年",[91,3465,3466],{},"数学上可行，但\"10 年严格执行\"淘汰的人比策略本身多。年化均值背后有巨大的方差，最大风险不是策略本身，而是震荡市连续止损后大多数人会改变规则。",[101,3468,3469],{"id":3469},"人群中能走到哪",[451,3471,3472,3475,3478,3481],{},[454,3473,3474],{},"能长期跑赢通胀：前 20%",[454,3476,3477],{},"年化 15%+ 持续 5 年以上：前 5%",[454,3479,3480],{},"系统化策略 10 年不变形：前 2-3%",[454,3482,3483],{},"10 万做到 500 万：前 1-2%",[91,3485,3486],{},"这个门槛不是天才门槛，而是纪律和时间门槛。输给认知的少，输给自己的多。",[101,3488,3489],{"id":3489},"交易不是生活的全部",[91,3491,3492],{},"正常认真上班拿现金流，有足球羽毛球爱好，偶尔玩游戏，继续交易探索市场和世界。每个部分各司其职：工作管现金流，运动游戏管切换放松，交易是认知战场。",[91,3494,3495],{},"这个心态本身是优势。很多人把交易当生活全部，盯盘过度、情绪放大、决策变差。有工作提供现金流、有运动游戏切换状态，交易在这个结构里心理压力更小，压力小反而更容易执行系统。",[91,3497,3498],{},"但有一个前提：执行密度。想清楚和做到之间有 gap，关键不是今天想通了，而是明天还在做。",[101,3500,3502],{"id":3501},"一个佩服的-up-主","一个佩服的 UP 主",[91,3504,3505],{},"关注过一个 UP 主，清华毕业三十多岁，提过资产千万级。他的操作和认知确实让人佩服：航运信息差套利抓住了真正的机会，暴跌那天开中证 500 期权多单判断准确，科技股暴跌后判断主线仍是科技股也对。盘中分享的想法很准，6 月 8 号中证 500 那波多单是实打实的。他还分享打新可转债信息、股东福利等内容，后来发现可转债确实是一个很好的盈利来源。",[91,3507,3508],{},"他的宏观判断和产业理解思路值得学，具体操作和套利思路也有参考价值。没有实盘记录这点确实无法验证，但判断质量摆在那里，佩服是真诚的。",[101,3510,3512],{"id":3511},"a-股打新现状","A 股打新现状",[91,3514,3515],{},"查了一下 A 股打新的数据：2024 年新股首日平均涨幅 253%，单签平均收益约 2 万元；2025 年至 6 月，45 只新股无一破发。但主板网上中签率仅 0.03% 左右，参与人数超 1100 万户，普通人中签概率极低，更像是彩票。网下机构打新年化约 4.5%，但门槛是亿级资金账户。",[101,3517,3518],{"id":3518},"止损永远是最重要的",[91,3520,3521],{},"20 日均线太死板，套到很多个股上买点太高了。但不管用什么方式入场，止损永远是第一位的。买点可以慢慢校准，进场理由可以有很多种，但止损必须进场前定好，而且不能因为浮亏就移动它。止损一旦守不住，什么策略都白搭。",{"title":125,"searchDepth":126,"depth":126,"links":3523},[3524,3525,3526,3527,3528,3529,3530,3531,3532],{"id":3381,"depth":126,"text":3382},{"id":3391,"depth":126,"text":3392},{"id":3404,"depth":126,"text":3404},{"id":3416,"depth":126,"text":3417},{"id":3469,"depth":126,"text":3469},{"id":3489,"depth":126,"text":3489},{"id":3501,"depth":126,"text":3502},{"id":3511,"depth":126,"text":3512},{"id":3518,"depth":126,"text":3518},"从清华博士的量化建议出发，梳理普通人做系统化交易的现实路径、人群比例和自我认知驱动。",{},"\u002Fwriting\u002F2026-07-26-trading-cognition-and-compound-reality",{"title":3373,"description":3533},"trading-cognition-and-compound-reality","writing\u002F2026-07-26-trading-cognition-and-compound-reality",[279,391,146,3540,3541],"复利","系统化交易","f82123ri2o8FqCPfH3G_9GEp8qqGeTztyTnd_1TzBhA",{"id":3544,"title":3545,"body":3546,"category":3747,"date":382,"description":3748,"extension":134,"meta":3749,"navigation":18,"path":3750,"publishedAt":3751,"seo":3752,"slug":3753,"stem":3754,"tags":3755,"updated":382,"__hash__":3761},"writing\u002Fwriting\u002F2026-07-26-fields-medal-claiming-connections.md","【转载】我反感菲尔兹奖成功后，一群人到处认领关系",{"type":88,"value":3547,"toc":3741},[3548,3564,3568,3571,3574,3577,3580,3583,3586,3589,3592,3595,3598,3601,3604,3607,3610,3613,3616,3619,3622,3625,3628,3631,3634,3641,3644,3647,3650,3653,3656,3659,3662,3665,3668,3671,3674,3677,3680,3683,3686,3689,3692,3695,3698,3701,3704,3707,3710,3713,3716,3719,3722,3725,3728,3731,3733],[3549,3550,3551],"blockquote",{},[91,3552,3553,3554,3559,3560,1230],{},"转载自B站专栏 ",[3232,3555,3558],{"href":3556,"rel":3557},"https:\u002F\u002Fwww.bilibili.com\u002Fopus\u002F1229213047382343689",[3236],"@漫士沉思录","，",[3232,3561,3563],{"href":3556,"rel":3562},[3236],"原文链接",[101,3565,3567],{"id":3566},"当时无人看见成名后都是故交","当时无人看见，成名后都是故交",[91,3569,3570],{},"最近，王虹和邓煜获得菲尔兹奖，这是一个非常让人兴奋的消息。这是中国数学史上真正重要的时刻。一个解决了三维挂谷猜想，一个与合作者完成了从微观粒子系统推导玻尔兹曼方程的重大突破。无论从数学史、科学史，还是朴素的民族情感来说，这都值得中国人感到自豪。我非常兴奋，迅速研究了两人的工作一个多星期，熬了好几个夜，在第一时间做了科普视频。还烧了几千块的AI额度。",[91,3572,3573],{},"这次中国一下子有了两个菲尔兹奖，最让人兴奋和自豪的地方在于，中国扎实的基础教育确实构成了他们成长中重要的一部分。中国教育能够让大量普通家庭的孩子，在相对有限的资源下，获得系统而高强度的数学训练。从代数、几何到分析和组合，一整套成熟的课程、考试和竞赛体系，训练了学生的计算能力、抽象能力和逻辑能力。邓煜接受过完整的竞赛训练，获得国际奥数金牌，进入北大学习；王虹虽然不是竞赛明星，也同样受益于扎实的本科课程和同学之间的讨论。这是中国基础教育的成绩，也是值得认真总结和珍惜的财富。",[91,3575,3576],{},"但这场兴奋中，也混杂着一种令人不适的刻奇。",[91,3578,3579],{},"很多人似乎并不真正关心两位数学家究竟解决了什么问题，也不关心他们怎样一步步成长为今天的数学家。大家更关心他们是哪所中学毕业的，在哪所大学待过，上过哪位教授的课，和哪个老师说过话，能不能把他们请回来。甚至是戴什么手环、玩什么手办、穿什么名牌。",[91,3581,3582],{},"仿佛一个人一旦获得世界级成就，他人生中接触过的每个机构、每门课程、每位老师，都突然变成了奖牌的共同缔造者。",[91,3584,3585],{},"尤其是王虹，当年根本不引人注意，现在人人都在她成功之后开始沾亲带故、认领关系。",[101,3587,3588],{"id":3588},"弹冠相庆",[91,3590,3591],{},"获奖消息公布后，有一场由北大数院老领导、相关领域教授和获奖者导师参与的直播。整场气氛当然非常热烈。中国数学等了这么多年，终于迎来两位中国籍菲尔兹奖得主，兴奋完全可以理解。",[91,3593,3594],{},"但直播越往后，越显得空洞。谈到王虹和邓煜，反复出现的是\"调和分析领域好起来了\"\"邓煜当年选过我的课，考得很好\"\"希望他们以后回北大带带学生\"。然而当主持人追问三维挂谷问题究竟难在哪里，王虹的证明跨越了什么障碍，邓煜的工作为什么能够连接微观可逆的粒子运动与宏观不可逆的玻尔兹曼方程时，回答迅速变得含混，或者干脆顾左右而言他。又变成了\"我认识那个谁谁谁……\"",[91,3596,3597],{},"问人工智能会怎样改变数学研究，回答是\"没有人能预测未来\"，或者忽然跳到\"AI比人聪明太多，人类会遭到毁灭性打击\"。主持人请教授给年轻观众一些寄语，几个教授领导最后仍然落回\"希望两位回来，帮助北大培养学生\"。",[91,3599,3600],{},"至于王虹当年在北大读书时为何没有受到注意，回答倒十分坦率：\"从来没有注意到。毕业论文选的确实比较难。\"说到邓煜时说，\"当时都说是邓神，我们当时就觉得，这种人才应该尽快到国际上跟真正的大师学习，我们别耽误他。\"",[91,3602,3603],{},"这两句话反而成了整场直播中最真实的话。",[91,3605,3606],{},"在整场直播和舆论场中，数学工作、研究道路几乎从来没有被认真讨论，他曾经面对的困境也无人关心。可是一旦奖项公布，所有人立刻开始翻阅旧名单、追溯选课记录、确认师承关系。数学本身退到背景，关系和归属占据舞台中央。祝贺变成了攀亲，学术变成了族谱。我后来想明白，这不是哪个人的问题。在那个场域里，唯一可以流通的货币就是关系和归属：谁教过、谁认识、谁哪一年注意到过、谁的课他考得好、哪个学院哪个学科该记这一笔。数学本身不是货币，因为它换不来任何东西。",[101,3608,3609],{"id":3609},"除非能得菲尔兹奖",[91,3611,3612],{},"中国教育的功劳不需要否认，问题在于，一套擅长提供基础训练的体系，未必同样擅长识别、容纳和培养真正的原创研究者。会做题不等于会做研究。快速掌握前人已经整理好的知识，也不等于能够在没有标准答案的荒野里发现问题、发明工具，并忍受漫长的失败。",[91,3614,3615],{},"考试面对的是确定性：题目一定有答案，方法大致存在，时间有限，做得越快越好。研究面对的却是不确定性：问题可能根本是错的，方法可能不存在，做了几年什么也得不到，甚至连\"应该往哪里走\"都无人知道。",[91,3617,3618],{},"前一种能力，中国教育极其擅长训练。而后一种能力，却需要完全不同的土壤：允许迟疑，允许绕路，允许犯错，允许一个暂时没有成果的人长时间追随自己的好奇，甚至能在学生困顿时告诉他也许怎么做会有转机和进展。",[91,3620,3621],{},"王虹的经历恰好体现了这种断裂。她最初进入北大地球与空间科学学院，后来转入数学系。为了转系，她需要同时应付原专业课程和数学课程，还要自学部分受选课限制无法直接修读的内容。进入数学系以后，周围是大量竞赛高手和奥赛金牌得主。她并不是最耀眼的学生，本科阶段始终处在一种艰难追赶的状态。",[91,3623,3624],{},"这种环境并非全无价值。同学组织的讨论班、扎实的课程训练和高水平同侪，都给了她重要帮助。但它也有另一面：当周围人都在炫技、刷题、比较成绩时，一个不以竞赛速度见长、需要慢慢形成数学品味的人，很容易不断怀疑自己是否适合数学。",[91,3626,3627],{},"后来她去了法国。巴黎综合理工允许学生自由选择课程，她去学习建筑、绘画，也曾认真考虑自己究竟要不要继续做数学。在许多高度标准化的培养体系中，这样的经历大概会被评价为\"不够专注\"\"路线不清晰\"或者\"浪费时间\"。但正是这种绕路，让她有机会重新确认自己真正想做的事情。",[91,3629,3630],{},"再后来，她到了MIT，遇见导师Larry Guth。当她的想法模糊、混乱，甚至很可能不成立时，导师不会立刻打断，也不会急于给出一个正确答案，而是耐心听她把想法讲完，让她逐渐学会怎样深入一个思路，怎样判断什么值得继续，哪里出了问题。",[91,3632,3633],{},"导师的价值，不是随时证明自己比学生聪明，而是帮助学生长出独立判断的能力。王虹在采访中说，\"那是第一次我感受到自己不必独自解决所有问题。\"",[91,3635,3636],{},[3637,3638],"img",{"alt":3639,"src":3640},"Documentary Interview in a Sunlit Garden","\u002Fuploads\u002Ffields-medal-garden.png",[91,3642,3643],{},"很多人习惯于把这总结成\"轻松教育\"和\"刻苦教育\"的区别，但其实太扁平了。这背后的核心，是把学生当作正在形成的研究者，还是把学生当作等待验收的标准化产品之间的区别。",[91,3645,3646],{},"邓煜的道路有所不同。他是典型的竞赛天才，国际奥数金牌，进入北大后成绩优异，却在大二转学MIT。北大的前两年为他打下了扎实的数学基础，到了MIT以后，他迅速接触前沿研究报告，在教师帮助下开始处理具体的随机初值偏微分方程问题。相比之下，MIT的师生关系更加松弛，学生更早接近研究前沿，交流方式也更平等随意。",[91,3648,3649],{},"所以，坦诚的说：中国的基础教育和北大本科训练的确提供了坚实起点；而法国和美国的学术环境提供了更大的探索空间、更靠近前沿的问题和不同方式的导师支持；最后真正把难题做出来的，是他们自己长期的思考和合作者共同完成的工作。",[91,3651,3652],{},"没有必要把一个人的全部成功据为己有。承认教育体系的长处，也承认别的环境提供过关键帮助，并不会损害中国教育的尊严。",[91,3654,3655],{},"更令人侧目的，是一种反复出现的模式。当初人在这里的时候，成绩不够耀眼，没有足够资源，没有人注意，只能自己想办法在压抑的环境里生存。等到去了法国、MIT、普林斯顿，做出世界级成果，所有人忽然开始翻通讯录：她是我们学院的，他上过我的课，我们早就知道他很优秀，欢迎回来建设母校。",[91,3657,3658],{},"一个年轻人尚未成功时，系统要求他不断证明自己配得上资源；等他终于不再需要这些资源时，系统又要求他回来证明这个系统的成功。",[91,3660,3661],{},"这很难称为培养，更像是收割。",[91,3663,3664],{},"\"希望他们回来带学生\"尤其耐人寻味。为什么第一反应总是让成功者回来\"带一带\"现有体系？为什么不是先问，今天的学生得到了足够的指导吗？年轻教师有稳定研究长期问题的空间吗？那些暂时没有论文、没有基金、成绩不够漂亮，却真正喜欢数学的人，有没有可能被看见？",[91,3666,3667],{},"仿佛体系本身从来不需要改变，只缺少几个世界冠军回来输血。",[91,3669,3670],{},"每当一个华人在海外获得巨大成就，国内舆论总会条件反射地追问\"什么时候回来\"。这背后仍是一种资源逻辑：把顶尖学者看作可以引进、争抢、挂牌的稀缺资产。似乎只要把人请回来，建一个中心，给一个头衔，再招一批学生，世界一流的学术文化就会自动生成。",[91,3672,3673],{},"但一个人为什么能够成为王虹？不仅因为她聪明、努力，也因为当她的想法尚且混乱时，有人愿意认真听她讲完。一个人为什么能够成为邓煜？不仅因为他是奥数金牌，也因为他在本科阶段就有机会进入研究前沿，得到具体问题，并沿着真正感兴趣的方向深入下去。",[91,3675,3676],{},"真正值得追问的，不是怎样让已经成功的王虹回来，而是怎样让下一个尚未成功、成绩并不耀眼、暂时做不出结果的王虹，在这里就能获得耐心、尊重和机会。不是怎样让邓煜回来带学生，而是怎样让一个有潜力的本科生，不必先成为标准化考试中的冠军，也能接触真正的研究。",[91,3678,3679],{},"读博期间最深切的感受，是许多研究从一开始就不是由问题驱动，而是由风口、项目、政策和履历驱动。",[91,3681,3682],{},"这个方向最近比较热，看看能不能做一个A+B；这个概念现在很多人关注，赶紧跟上；这个方向政策在推，容易申请项目和基金；这个题目适合创业，方便获得横向经费。",[91,3684,3685],{},"这些考虑并非全无道理。科研需要资源，学者也要生活，国家投入资金当然会有战略方向，应用研究也应回应现实需求。但当所有人都按照同一套风口和考核表选择问题，得到的通常不是伟大的创新，而是一群训练有素的人在同一个狭窄区域里重复施工。",[91,3687,3688],{},"真正原创的工作，在开始时经常显得没有用、不热门、不保险，甚至有些荒唐。三维挂谷猜想并不是某个年度指南里的热门任务，从微观粒子严格推导玻尔兹曼方程也不是一个容易结项的项目。吸引数学家投入多年时间的，首先是问题本身：它重要，它困难，它让人无法停止思考。",[91,3690,3691],{},"而短周期、强考核、零容错的制度，会系统性地消灭这种选择。探索失败的代价由年轻人承担，探索成功的功劳却可以由导师、学院、学校乃至整个体系共同认领。在这样的收益结构下，最理性的选择不是冒险，而是跟随；不是追问真正重要的问题，而是在热门方向上快速制造一个可以发表的差异。",[91,3693,3694],{},"久而久之，科研只剩下亦步亦趋的平庸、包装精致的空洞和围绕权力关系形成的利益链条。真正的学术能力退居其次，最重要的是项目、头衔、行政资源和技术官僚身份。",[91,3696,3697],{},"有些老师把博士生当作自己的低成本项目执行人员。学生需要打卡上班，替老师完成横向项目、写材料、跑报销、接待、演示，维护各种与自身研究无关的系统。项目拿到大量经费，真正做事的学生却只能得到象征性的补贴。学生承担了雇员的工作，却没有雇员的工资、合同和边界，同时还要接受\"老师是在培养你\"的道德规训。",[91,3699,3700],{},"另一种极端则是完全放养。没有稳定讨论，没有具体指导，不帮助学生寻找问题，也不关心学生陷入什么困境。学生如果自己长出来了，便成了导师和学校培养有方；如果没有长出来，就是学生能力不足、不够努力。",[91,3702,3703],{},"一种把学生当工具，另一种把学生当彩票。看似相反，本质上都没有把学生当作一个需要被认真培养、逐渐独立的人。真正的指导既不是把学生攥在手里，让他替自己完成任务，也不是把人扔进荒野，等待幸存者回来报喜。",[91,3705,3706],{},"还有一种更加隐蔽的情形：那些像韦东奕一样极其纯粹、极具天赋，却不擅长经营关系和适应行政秩序的人，会被当成一种特殊符号。但一旦有了成果，又会立刻被包装成学校精神和培养成绩的一部分。",[91,3708,3709],{},"人在其中时，感受到的是放养、压抑、内卷和无聊的应制。等到做出成绩，外界看到的却只剩下一张可以宣传的天才名片。",[91,3711,3712],{},"王虹和邓煜获得菲尔兹奖，中国人当然可以自豪。可以为中国基础教育所提供的扎实训练自豪，可以为普通家庭的孩子依靠教育走向世界前沿自豪，也可以为中国学者已经有能力参与乃至领导最核心的数学问题自豪。",[91,3714,3715],{},"但成熟的自豪不应害怕承认缺陷。一个真正自信的教育体系，应该能够坦然地说：这里有我们提供的基础，那里有别人提供的环境；这个地方做得很好，那个地方曾经没有看见她；这些经验值得继承，那些问题必须改变。",[91,3717,3718],{},"最廉价的爱国，是成功以后把一个人搬回族谱。最廉价的学术庆祝，是翻出选课记录，证明自己曾经与菲尔兹奖有过一面之缘。最廉价的反思，则是再次高喊\"把人才请回来\"，却不改变那些迫使人才离开的结构。",[91,3720,3721],{},"真正的庆祝，应该是认真理解他们究竟做了什么，认真理解伟大研究需要怎样的好奇、自由、耐心和容错，然后回头看看那些仍然坐在教室和实验室里，成绩不够漂亮，论文尚未发表，想法听起来有些古怪，甚至正在怀疑自己究竟适不适合科研的年轻人。",[91,3723,3724],{},"基础教育可以教会一个人怎样解决已有的问题，但一个文明能否产生真正伟大的学术，最终取决于它是否允许人提出无人要求的问题，追寻暂时无用的答案，走一条没有人保证正确的道路。",[91,3726,3727],{},"真正值得骄傲的一天，不是一个人在外面成名以后，所有人终于认出了他。",[91,3729,3730],{},"而是当他还只是一个小透明，还在挣扎，还在犯错，还无法证明自己将会成功时，这个体系就愿意认真地看见他。",[101,3732,3226],{"id":3226},[451,3734,3735],{},[454,3736,3737],{},[3232,3738,3740],{"href":3556,"rel":3739},[3236],"原文 - 哔哩哔哩专栏",{"title":125,"searchDepth":126,"depth":126,"links":3742},[3743,3744,3745,3746],{"id":3566,"depth":126,"text":3567},{"id":3588,"depth":126,"text":3588},{"id":3609,"depth":126,"text":3609},{"id":3226,"depth":126,"text":3226},"观察","王虹和邓煜获菲尔兹奖后，国内学术圈纷纷攀亲认关系，本文反思中国教育体系在培养原创研究者方面的缺失。",{},"\u002Fwriting\u002F2026-07-26-fields-medal-claiming-connections","2026-07-26T13:56:35+08:00",{"title":3545,"description":3748},"fields-medal-claiming-connections","writing\u002F2026-07-26-fields-medal-claiming-connections",[3756,3757,3758,3759,3760],"菲尔兹奖","王虹","邓煜","中国教育","学术反思","jwvp054ZJWI_LrptvQv7qj9iqxK_5lwHWCWDsb_ORGI",{"id":3763,"title":3764,"body":3765,"category":279,"date":382,"description":3946,"extension":134,"meta":3947,"navigation":18,"path":3948,"publishedAt":3949,"seo":3950,"slug":3951,"stem":3952,"tags":3953,"updated":147,"__hash__":3960},"writing\u002Fwriting\u002F2026-07-26-btc-synthetic-futures-arbitrage.md","BTC期权合成期货套利：用定价偏差锁定无风险利润",{"type":88,"value":3766,"toc":3937},[3767,3770,3774,3777,3780,3784,3790,3798,3801,3804,3807,3813,3819,3822,3826,3829,3832,3836,3843,3849,3852,3855,3869,3874,3882,3888,3893,3907,3912,3924,3927,3931,3934],[91,3768,3769],{},"看到一套量化交易系统看板：年化 197%、极低回撤、多平仓少持仓。核心策略是利用 Deribit 期权市场合成的虚拟期货价格与 Binance 永续合约价格之间的定价偏差进行对冲套利。当时对着看板追问了 AI 几轮，才把这套合成期货套利的逻辑理清楚。这篇文章是给自己留的复盘笔记。",[101,3771,3773],{"id":3772},"deribit-是什么","Deribit 是什么",[91,3775,3776],{},"Deribit 是目前加密货币期权交易量最大的交易所，总部在巴拿马，2016 年上线。BTC 和 ETH 期权的主流流动性都在这里，行权价、到期日覆盖范围广，机构参与度高。它的期权以币本位结算（BTC 期权用 BTC 结算），也支持永续合约和交割期货。",[91,3778,3779],{},"正因为 Deribit 在期权市场的深度优势，它的期权定价成为合成期货策略的基础端。另一端选 Binance 永续合约，是因为 Binance 流动性最好、API 稳定、支持开空，适合做对冲腿。",[101,3781,3783],{"id":3782},"核心概念合成期货","核心概念：合成期货",[91,3785,3786,3787,1230],{},"期权平价公式告诉我们：",[429,3788,3789],{},"买入 Call + 卖出 Put = 合成期货多头",[451,3791,3792,3795],{},[454,3793,3794],{},"买入 Call（看涨期权）：涨了赚，跌了不亏",[454,3796,3797],{},"卖出 Put（看跌期权）：涨了没事，跌了亏",[91,3799,3800],{},"两者组合后的盈亏轨迹，与直接持有 BTC 现货或期货完全一致——涨了赚、跌了亏。这就是\"合成期货\"。",[101,3802,3803],{"id":3803},"两种套利方向",[91,3805,3806],{},"关键在于：Deribit 期权合成的期货价格，和 Binance 永续合约的价格，经常不一致。",[91,3808,3809,3812],{},[429,3810,3811],{},"转换套利（Conversion \u002F SF+BS）","：当合成期货价格 > Binance 期货价格时，在 Deribit 卖出合成期货（卖出 Call + 买入 Put），同时在 Binance 买入永续合约。",[91,3814,3815,3818],{},[429,3816,3817],{},"反转套利（Reversal \u002F BF+SS）","：当合成期货价格 \u003C Binance 期货价格时，在 Deribit 买入合成期货（买入 Call + 卖出 Put），同时在 Binance 卖出永续合约。",[91,3820,3821],{},"本质上就是\"哪边便宜哪边买，哪边贵了哪边卖\"。",[101,3823,3825],{"id":3824},"对冲机制为什么涨跌都不怕","对冲机制：为什么涨跌都不怕",[91,3827,3828],{},"币安端永远做与 Deribit 完全相反的动作。Deribit 开合成多头，Binance 必开永续空头。BTC 暴涨暴跌时，两端的盈亏完全抵消，行情风险归零。",[91,3830,3831],{},"利润不来自方向判断，而是开仓瞬间两端的定价差。期权到期结算时，合成价格强制回归现货价，基差收敛完成无风险落袋。",[101,3833,3835],{"id":3834},"一个关键区分行权价-现价","一个关键区分：行权价 ≠ 现价",[91,3837,3838,3839,3842],{},"看板中的合约代码 ",[55,3840,3841],{},"BTC-10JUN26-62000","，62000 是行权价，不是当时的市场现价。当时 Binance 的标记价约为 62,991 美元。因为现价高于行权价，看涨期权呈浮盈状态，看跌期权的权利金已被吃满。",[91,3844,3845,3846,1230],{},"比对套利机会时，标的不是行权价本身，而是",[429,3847,3848],{},"合成总成本 = 行权价 + 买Call权利金 - 卖Put权利金",[101,3850,3851],{"id":3851},"完整数值演练",[91,3853,3854],{},"设定场景：",[451,3856,3857,3860,3863],{},[454,3858,3859],{},"Binance 现价：$63,000",[454,3861,3862],{},"Deribit 行权价 $62,000 的期权：Call 权利金 $1,500，Put 权利金 $300",[454,3864,3865,3866],{},"合成空头总成本：$62,000 + $1,500 - $300 = ",[429,3867,3868],{},"$63,200",[91,3870,3871],{},[429,3872,3873],{},"开仓动作：",[451,3875,3876,3879],{},[454,3877,3878],{},"Binance 开多，$63,000",[454,3880,3881],{},"Deribit 合成空头（卖 Call + 买 Put），$63,200",[91,3883,3884,3885],{},"开仓瞬间锁定利润：$63,200 - $63,000 = ",[429,3886,3887],{},"$200",[91,3889,3890],{},[429,3891,3892],{},"极端行情 A - 暴涨至 $80,000：",[451,3894,3895,3898,3901],{},[454,3896,3897],{},"Binance 多头盈利：+$17,000",[454,3899,3900],{},"Deribit 合成空头亏损：-$16,800",[454,3902,3903,3904],{},"合计：",[429,3905,3906],{},"+$200",[91,3908,3909],{},[429,3910,3911],{},"极端行情 B - 暴跌至 $40,000：",[451,3913,3914,3917,3920],{},[454,3915,3916],{},"Binance 多头亏损：-$23,000",[454,3918,3919],{},"Deribit 合成空头盈利：+$23,200",[454,3921,3903,3922],{},[429,3923,3906],{},[91,3925,3926],{},"无论涨跌，总利润始终为开仓时锁定的 $200。到期自动结算收敛，整个过程是左手倒右手，利润在开仓那一下就已经确定了。",[101,3928,3930],{"id":3929},"模型不难难的是工程","模型不难，难的是工程",[91,3932,3933],{},"这套套利的交易系统作者说过一句话：套利模型倒是不难，难的是一些工程上的事情。",[91,3935,3936],{},"确实，逻辑上这就是一个低买高卖的价差捕捉，但实际跑起来要处理的问题远比模型复杂：两个交易所的 API 延迟差异、订单簿深度和滑点、手续费摩擦对利润空间的侵蚀、资金在两个平台之间的划转效率、期权到期时的自动结算对齐、极端行情下的风控（硬止损、Gamma 检查、行情降级）、以及资金容量上限——能套的价差就那么多，资金量大了反而吃不掉。这些工程细节才是决定系统能不能真正赚钱的关键。",{"title":125,"searchDepth":126,"depth":126,"links":3938},[3939,3940,3941,3942,3943,3944,3945],{"id":3772,"depth":126,"text":3773},{"id":3782,"depth":126,"text":3783},{"id":3803,"depth":126,"text":3803},{"id":3824,"depth":126,"text":3825},{"id":3834,"depth":126,"text":3835},{"id":3851,"depth":126,"text":3851},{"id":3929,"depth":126,"text":3930},"看到一套量化套利系统后追问AI，拆解Deribit合成期货与Binance永续合约之间的跨平台套利逻辑，含完整数值演练。",{},"\u002Fwriting\u002F2026-07-26-btc-synthetic-futures-arbitrage","2026-07-26T13:37:11+08:00",{"title":3764,"description":3946},"btc-synthetic-futures-arbitrage","writing\u002F2026-07-26-btc-synthetic-futures-arbitrage",[3954,3955,3956,3957,3958,3959],"BTC","期权","套利","合成期货","Deribit","Binance","dVKWlNkJcxTfn3YYwF5uVjOPge4iiTrAaM6UeVy3dTE",{"id":3962,"title":3963,"body":3964,"category":3358,"date":382,"description":4129,"extension":134,"meta":4130,"navigation":18,"path":4131,"publishedAt":4132,"seo":4133,"slug":147,"stem":4134,"tags":4135,"updated":147,"__hash__":4139},"writing\u002Fwriting\u002F2026-07-26-why-vector-database.md","向量库到底有什么用",{"type":88,"value":3965,"toc":4122},[3966,3970,3973,3984,3987,4001,4005,4008,4022,4025,4029,4032,4035,4055,4062,4065,4068,4071,4089,4092,4095,4119],[101,3967,3969],{"id":3968},"sql-存个相同列-join-一下不就行了","SQL 存个相同列 join 一下不就行了？",[91,3971,3972],{},"这是我最初的问题。看起来很合理：embedding 不就是一串数字吗，存个字段，SQL join 一下就完事了。",[91,3974,3975,3976,3979,3980,3983],{},"但 SQL 擅长的是 ",[55,3977,3978],{},"WHERE A = B"," 这种精确匹配。Embedding 是高维浮点数组，代表语义特征。两句话语义相似，它们的向量数值却绝不相等。",[55,3981,3982],{},"WHERE Va = Vb"," 直接返回空。",[91,3985,3986],{},"所以向量库真正在做的事情有两层：",[631,3988,3989,3995],{},[454,3990,3991,3994],{},[429,3992,3993],{},"数学计算","：用余弦相似度等算法算高维空间的\"距离\"，而不是判等。",[454,3996,3997,4000],{},[429,3998,3999],{},"专属索引（ANN 算法）","：传统 B-Tree 索引对高维数据失效，会退化成全表扫描。向量库用 HNSW 之类的索引在高维空间建\"地图\"，做到毫秒级近似最近邻检索。",[101,4002,4004],{"id":4003},"那-rag-到底是怎么跑的","那 RAG 到底是怎么跑的",[91,4006,4007],{},"搞清楚向量库的作用之后，整个 RAG 链路就顺了：",[631,4009,4010,4013,4016,4019],{},[454,4011,4012],{},"用户提问 -> 经过 Embedding 模型 -> 转成向量",[454,4014,4015],{},"拿向量去向量库里找最近的文档片段",[454,4017,4018],{},"找到的相关资料 + 用户原问题一起拼成 Prompt 发给大模型",[454,4020,4021],{},"大模型结合资料回答，减少幻觉",[91,4023,4024],{},"核心就是：输入给大模型之前，先用向量检索把相关上下文捞回来，拼在一起再喂进去。",[101,4026,4028],{"id":4027},"全量召回还是选几条","全量召回还是选几条？",[91,4030,4031],{},"这是第二个直觉问题：如果数据库里相关的东西很多，比如 50 页文本都沾边，全部塞进大模型？还是挑几条最相关的？",[91,4033,4034],{},"答案是必须精选截断。原因有三个：",[451,4036,4037,4043,4049],{},[454,4038,4039,4042],{},[429,4040,4041],{},"上下文窗口有限","：大模型的 Context Window 有上限，塞不下就是塞不下。",[454,4044,4045,4048],{},[429,4046,4047],{},"中间迷失","：上下文太长时，大模型容易忽略中间的内容。",[454,4050,4051,4054],{},[429,4052,4053],{},"Token 费用","：输入越长越贵。",[91,4056,4057,4058,4061],{},"所以标准做法是设置 ",[55,4059,4060],{},"top_k","（比如 limit=5），只取相似度最高的前 N 个片段。入库之前也先把长文本切成小块（比如每段 500 字），精准匹配局部内容，避免带入无关段落。",[101,4063,4064],{"id":4064},"但我的数据量没那么大",[91,4066,4067],{},"说到这里我反应过来了--我的复盘日志根本没多少数据。几万字而已，全塞进去不就完了？",[91,4069,4070],{},"确实可以。小数据量下\"全上下文注入\"更简单有效：",[451,4072,4073,4079],{},[454,4074,4075,4078],{},[429,4076,4077],{},"逻辑完整","：保留完整的时间线和因果链，不会因为切片断章取义。",[454,4080,4081,4084,4085,4088],{},[429,4082,4083],{},"架构极简","：直接 SQL ",[55,4086,4087],{},"SELECT *","，全部喂给大模型，不需要向量索引和切片逻辑。",[101,4090,4091],{"id":4091},"那向量库还有没有意义",[91,4093,4094],{},"有。即便是小数据量，向量库（或 SQL 的向量插件）仍然有几个不可替代的能力：",[451,4096,4097,4107,4113],{},[454,4098,4099,4102,4103,4106],{},[429,4100,4101],{},"模糊语义匹配","：日志里写的是\"肝到两点\"或\"披星戴月\"，向量检索能匹配到\"加班\"的语义。传统 SQL ",[55,4104,4105],{},"LIKE"," 搜不到这种。",[454,4108,4109,4112],{},[429,4110,4111],{},"扩展性","：日志会越积越多，一两年后可能就塞不进上下文窗口了。向量检索的成本随数据量亚线性增长，全量注入则是线性上升。",[454,4114,4115,4118],{},[429,4116,4117],{},"聚类与挖掘","：基于向量距离可以做无标签的主题归类和情绪分析，这是全量注入给大模型做不到的。",[91,4120,4121],{},"所以比较务实的方案是：短周期（比如近一周）的分析直接 SQL 全量提取，喂给大模型；跨年度的特定问题搜索走向量匹配。两条路各管各的，不冲突。",{"title":125,"searchDepth":126,"depth":126,"links":4123},[4124,4125,4126,4127,4128],{"id":3968,"depth":126,"text":3969},{"id":4003,"depth":126,"text":4004},{"id":4027,"depth":126,"text":4028},{"id":4064,"depth":126,"text":4064},{"id":4091,"depth":126,"text":4091},"从\"SQL 加个列不就行了\"到理解向量检索和 RAG 的完整链路，以及小数据量场景下到底该怎么选。",{},"\u002Fwriting\u002F2026-07-26-why-vector-database","2026-07-26T00:09:14+08:00",{"title":3963,"description":4129},"writing\u002F2026-07-26-why-vector-database",[4136,4137,4138],"向量数据库","Embedding","RAG","9q4Dlkg3MPwjAbd68zr9nVdA_E9SlT8u4gPpEGXZKqQ",{"id":4141,"title":4142,"body":4143,"category":3747,"date":4271,"description":4272,"extension":134,"meta":4273,"navigation":18,"path":4274,"publishedAt":4275,"seo":4276,"slug":147,"stem":4277,"tags":4278,"updated":4280,"__hash__":4281},"writing\u002Fwriting\u002F2026-07-24-quilibra-tech-stack-and-design-direction.md","这个网站是怎样在 Codex 中一步步构建出来的",{"type":88,"value":4144,"toc":4261},[4145,4149,4152,4155,4158,4161,4165,4168,4171,4175,4178,4181,4184,4187,4190,4194,4197,4200,4203,4206,4209,4212,4215,4218,4222,4225,4228,4231,4234,4237,4240,4243,4246,4249,4252,4255,4258],[101,4146,4148],{"id":4147},"买了域名然后呢","买了域名，然后呢",[91,4150,4151],{},"7 月 21 日，域名到手，备案在走。我想给自己弄个网站，需求听着特别朴素：浅色、好看、能写东西、能给自建服务挂个入口。就这样。",[91,4153,4154],{},"参考了 xiaommx.cn，觉得人家做得挺炫，但冷静想了想--不要小游戏，不要数据库，不要后端，不要那些听着就维护不动的东西。网站只需要四样：介绍自己、写文章、服务入口、关于。这个判断很省事，后面所有技术选型都是被它倒推的。Nuxt 4、Nuxt Content、原生 CSS，没有 Hono，没有 SQLite，不用纠结。",[91,4156,4157],{},"\"算了，全权交给你负责了！Kimi 用的人太多了，整个网页全部交给你了！\"",[91,4159,4160],{},"于是 Codex 上场。接下来三天，8 个会话，大约 230 条输入。这个网站就是这么搞出来的。",[101,4162,4164],{"id":4163},"第一版什么都有但就是没意思","第一版：什么都有，但就是没意思",[91,4166,4167],{},"浅绿色、大图 Hero、导航栏、文章列表、服务区、关于页。功能该有的全有，看着也像模像样。但怎么说呢--就像一个精心装修过的样板房，你能看出花了心思，但说不出这是谁的家。",[91,4169,4170],{},"然后改文案。原来的介绍写得跟产品着陆页似的，特别正经。\"把那些尴尬的文案改了好不好。\"删掉那些抽象表述，换上\"这是我自己部署的个人主页\"和\"正在上班当牛马\"。这一步让我明白一件事：网站的性格不靠功能堆出来的，靠语气。",[101,4172,4174],{"id":4173},"复刻-raunome从真香到翻车","复刻 rauno.me：从真香到翻车",[91,4176,4177],{},"\"你详细调研一下 rauno.me，我想完全复刻这个网站做我的主页。\"",[91,4179,4180],{},"rauno.me 那种横向画框的玩法确实好看。旧首页二话不说推翻，改成五张横向全屏画框：自我介绍、文章、服务、联系方式、宣言。顶部还加了刻度和滑动指示器，像那么回事。",[91,4182,4183],{},"然后就开始跟滑动手感死磕。太慢、惯性不够、触控板方向反的、自动吸附老打断节奏。最后让滚轮和触控板只管注入速度，动画循环自己算惯性，去掉自动吸附，第一张画框加个弹簧聚焦。Playwright 测试也是这时候开始写的--手动搓滑动根本测不出问题。",[91,4185,4186],{},"复刻到一比一了，新鲜劲也过了。\"现在网站基本是一比一复刻，我想做出差异化。要不改成竖着的？横着的太明显了。\"道理很简单：可以学人家的视觉语言，但不能变成中文版 rauno.me。于是横改竖，每幕换个进入动画，去掉编号。",[91,4188,4189],{},"改完一看--好家伙，这不就是个 PPT 吗。",[101,4191,4193],{"id":4192},"不做-ppt-了做工作台","不做 PPT 了，做工作台",[91,4195,4196],{},"\"要不只保留第一张，把其他内容集成在第一个页面，参考 2023.rauno.me，保留一些好玩的互动。\"",[91,4198,4199],{},"这是整个项目拐弯最大的一次。不做滚动，不做转场，不做一幕一幕的切换。让所有东西同时出现在一个屏幕里：介绍、最近文章、服务、时间、坐标、调色器、栏目入口，全塞进去。然后砍掉第二幕，服务摆成无边框 2×2 矩阵，底部入口只留三个。首页钉死在视口里，没有导航栏，不产生原生滚动。",[91,4201,4202],{},"从\"复刻一个网站\"到\"设计一个工作台\"，就这么转过来的。",[101,4204,4205],{"id":4205},"右下角这块空地怎么办",[91,4207,4208],{},"工作台成型了，右下角一直空着。试了一圈：互动坐标场、大型指针圆圈、可拖动组件、涂鸦板。指针圆圈太大，喧宾夺主；拖动组件没啥用；涂鸦板跟网站气质完全不搭。最后只留了顶部一个克制的坐标读数。",[91,4210,4211],{},"\"我想把它做成斜纹的、可拖动调色的条带，用红绿蓝三基色混合，最后出来的颜色是混合的。\"",[91,4213,4214],{},"三条斜纹轨道放进去，拖红绿蓝三个通道调色，配黄橙蓝三个预设。但让它真正变成网站灵魂的决定是：这个颜色不只管按钮，而是接管整个页面--背景、网格、文字对比色、悬浮反馈、文本选中状态全跟着变。后来又顺手把浏览器标签页的 theme-color 和 favicon 也同步了，favicon 做成几何化的 Q，刷新还能恢复上次选的颜色。",[91,4216,4217],{},"本来只是想填个空，结果填出来一个控制中枢。",[101,4219,4221],{"id":4220},"首页热闹内页安静","首页热闹，内页安静",[91,4223,4224],{},"\"点进文章界面之后，不要再出现其他地方的入口，只专注于展示文章。\"",[91,4226,4227],{},"分工很明确：首页负责有意思，内页负责能读进去。文章、服务、关于三个内页不要公共导航、不要页脚，只留左上角一个返回入口。文章页有分类、搜索、前后篇导航。其他内页黑白排版，安安静静的。",[91,4229,4230],{},"大结构定了，剩下的全是鸡毛蒜皮的微调。\"最近写下的宽度稍微窄一点。\"\"SYSTEMS 再左移一点点。\"\"手机端网格线不能覆盖整个页面。\"\"返回按钮字体颜色淡一点，加上符号标识。\"\"状态小点再浅一点，深的看不清。\"每条单独看都不值一提，但加在一起就是\"差点意思\"和\"对了\"之间的区别。字号、间距、颜色、断点，全靠浏览器截图反复比对。最后紧凑桌面、超宽屏、手机都能正常显示，不会因为某个标题长了一点就整个错位。",[101,4232,4233],{"id":4233},"连发文章都想重新发明一遍",[91,4235,4236],{},"\"这都 2026 年了，谁还手写文章。我把和其他 AI 的对话链接分享给 agent，然后它自动按照模板整理好文章并分类发布。\"",[91,4238,4239],{},"文章不临时编，来源就是真实对话。分类定了随笔、学习、交易、观察四类。发布前跑一整套：内容验证、类型检查、单元测试、静态生成、Playwright 测试。",[91,4241,4242],{},"发文章还撞上一个离谱的问题：构建静态站点居然要占 3000 端口，也就是说每次发文章都得把线上服务停了。\"为什么发布文章还要占用 3000 端口？为什么要停止开机服务才能自动发布？\"改完之后，生产服务读版本化 release 的 current 链接，构建完原子切换目录，3000 端口根本不用动。开发预览走 3100，测试走 3101。构建失败也影响不到线上。",[91,4244,4245],{},"内容管理也顺手迁了：个人资料和文案放 YAML，文章还是 Markdown，加了 Sveltia CMS 做可视化管理，Git 当唯一真实来源。",[101,4247,4248],{"id":4248},"越做越少",[91,4250,4251],{},"\"能不能简单点？这么多策略配置，我觉得只需要维护一个 skill。\"",[91,4253,4254],{},"OpenClaw 工作区里重复的角色说明和工具配置全删了，文章整理和发布逻辑收进一个 personal-site-publisher skill。到最后整个系统就四样东西：一个静态站点、一套内容规则、一个发布 skill、一条原子部署流程。",[91,4256,4257],{},"回头看，这个网站不是哪个版本的直接产物。传统首页做过，横向画框做过，纵向幻灯片做过，第二幕做过，自动吸附做过，指针圆圈做过，涂鸦板做过--然后全删了。留下来的东西有个共同点：反复用着觉得对。单屏工作台、服务矩阵、RGB 全局调色、安静的阅读页、对话驱动的内容发布，每一个都是推翻好几轮之后才定下来的。",[91,4259,4260],{},"文章和服务越来越多之后，单屏首页还能不能撑住，得接着看。远程管理和自动部署等接了正式私有仓库再验证。",{"title":125,"searchDepth":126,"depth":126,"links":4262},[4263,4264,4265,4266,4267,4268,4269,4270],{"id":4147,"depth":126,"text":4148},{"id":4163,"depth":126,"text":4164},{"id":4173,"depth":126,"text":4174},{"id":4192,"depth":126,"text":4193},{"id":4205,"depth":126,"text":4205},{"id":4220,"depth":126,"text":4221},{"id":4233,"depth":126,"text":4233},{"id":4248,"depth":126,"text":4248},"2026-07-24","三天，230 条输入，四版被推翻的首页，最终留下一个单屏工作台和一堆被删掉的代码。",{},"\u002Fwriting\u002F2026-07-24-quilibra-tech-stack-and-design-direction","2026-07-24T19:32:20+08:00",{"title":4142,"description":4272},"writing\u002F2026-07-24-quilibra-tech-stack-and-design-direction",[3366,3368,573,565,4279],"OpenClaw","2026-07-25","1xyfQ8pi9KvnsWB_BeENERo0y41vQZMY9KrT8sdbj_E",1785121514638]