展示HN：放弃Wix，选择了一个AI边缘代理，这样我就不必再雇佣初级员工了。
我经营一家建筑设计咨询公司。我厌倦了每月支付40美元给Wix，只为了一个无法回答简单服务问题的宣传册，同时还浪费了几个小时在同样的常见问题上。
于是我决定彻底放弃，花了4个月时间构建一个“对话者”： [https://axoworks.com](https://axoworks.com)
这个技术栈完全是临时拼凑的：Netlify的10秒无服务器超时迫使我将代理分成三个部分：大脑（边缘计算）、双手（浏览器）和声音（边缘计算）。我已经有30年没写代码了。这一过程就像是前进三步、后退两步，主要依靠人工智能的指导。
证明它有效的斗争：两周前，一位持证建筑师对我的机器人发起攻击，试图证明我的商业模式对这个行业有害。AI（DeepSeek-R3）完全驳倒了他的论点，过程非常幽默且尖锐。
日志： [https://logs.axoworks.com/chat-architect-vs-concierge-v147.html](https://logs.axoworks.com/chat-architect-vs-concierge-v147.html)
一些“战斗伤疤”：
* 网络语音API工作得很好，直到有人在没有切换语言模式的情况下说中文。然后它会强行输出英语发音的胡言乱语，依然让人头疼。
* 责任是致命的。如果虚构了一条建筑规范条款？我们就完了。保险公司不会理会我们。
* 我们发布审计日志，以保持诚实并确保系统的安全性。
审计： [https://logs.axoworks.com/audit-2026-02-19-v148.html](https://logs.axoworks.com/audit-2026-02-19-v148.html)
最困难的部分是正确理解意图：让一个大型语言模型在与房主交流时无缝切换到温暖的校长语气，而在受到同行攻击时则变得像一只防御性的斗牛犬。这花了我2.5个月的调试时间。
我们通过一种“急切的RAG”黑客技术（预取猜测）快速消耗令牌，以提高响应速度。我还去掉了“必要的”持久数据库——不到5%的访客会再次访问，那何必呢？如果客户在查询过程中中途退出，他们的会话就会消失。没有服务器端的队列。
重点是：让我能够与一群经验丰富的专业人士合作，并精简流程。
试着去破坏它。我会在评论区等你。
查看原文
I run a building design consultancy. I got tired of paying Wix $40/month for a brochure that couldn’t answer simple service questions, and me wasting hours on the same FAQs.<p>So I killed it all and spent 4 months building a 'talker': <a href="https://axoworks.com" rel="nofollow">https://axoworks.com</a><p>The stack is completely duct-taped: Netlify’s 10s serverless timeout forced me to split the agent into three pieces: Brain (Edge), Hands (Browser), and Voice (Edge). I haven’t coded in 30 years. This was 3 steps forward, 2 steps back, heavily guided by AI.<p>The fight that proved it worked: 2 weeks ago, a licensed architect attacked the bot, trying to prove my business model harms the profession. The AI (DeepSeek-R3) completely dismantled his arguments. It was hilariously caustic.<p>Log: <a href="https://logs.axoworks.com/chat-architect-vs-concierge-v147.html" rel="nofollow">https://logs.axoworks.com/chat-architect-vs-concierge-v147.h...</a><p>A few battle scars:<p>* Web Speech API works fine, right up until someone speaks Chinese without toggling the language mode. Then it forcefully spits out English phonetic gibberish. Still a headache.<p>* Liability is the killer. Hallucinate a building code clause? We’re dead. Insurance won’t touch us.<p>* We publish the audit logs to keep ourselves honest and make sure the system stays hardened.<p>Audit: <a href="https://logs.axoworks.com/audit-2026-02-19-v148.html" rel="nofollow">https://logs.axoworks.com/audit-2026-02-19-v148.html</a><p>The hardest part was getting the intent right: making one LLM pivot seamlessly from a warm principal’s tone with a homeowner, to a defensive bulldog when attacked by a peer. That took 2.5 months of tuning.<p>We burn through tokens with an 'Eager RAG' hack (pre-fetching guesses) just to improve responsiveness. I also ripped out the “essential” persistent DBs—less than 5% of visitors ever return, so why bother? If a client drops mid-query, their session vanishes. No server-side queues.<p>The point: To let me operate with a network of seasoned pros, and trim the fat.<p>Try to break it. I’ll be in the comments. Kee