在流浪期间用 Rust 构建了一个 130 万行代码的 Agent-Native 操作系统,现在该怎么办?

3作者: jamieoglindsey5 个月前
我直说了吧,我不知道还能向谁求助了。<p>我爸被诊断出癌症。他住院期间,议会清空了他的房子。我所有的东西都在那栋房子里。价值超过 2 万英镑的设备、多年的研究成果、一个服务器,里面有数千小时的工作成果。我孩子们的头发。照片。全都被扔进了垃圾场。<p>我的家人让我弥留之际的父亲与我为敌。最后我只能和一个患有妄想症的人一起生活。我接下来要描述的大部分内容都是在那里完成的。三天前,遭受了 24 小时的虐待,现在我和我的狗一起住在帐篷里。气温 5 摄氏度。身无分文。<p>议会拒绝提供住房。政府不承认我的自闭症。他们希望我每周在帐篷里找 35 个小时的工作。<p>我并非无能。我养育了一个家庭。我整个成年生活都在工作。我曾监督团队、纹身、自由职业编程,在过去 20 年里一直从事 Linux 相关的专有后端系统构建工作。我的自闭症在这里不是一种障碍。这正是我能够将整个操作系统架构牢记于心,并了解每个组件如何连接的原因。当我的大脑专注于一个问题时,它会产生有效的系统,其速度让大多数人难以置信。<p>在过去的 4 个月里,我一直在构建 OctantOS。一个用于自主 AI 代理的操作系统。不是框架。不是容器包装器。而是一个真正的操作系统,拥有自己的内核(OctantCore,从头开始用 Rust 编写)、自己的虚拟机管理程序(OctantVMM)、一个单二进制 Rust 用户空间,以及一个 10 层安全堆栈,在内核级别强制执行代理权限。<p>总共约 130 万行代码。约 80 万行 Rust 代码。50 个 crate,约 25 个卫星项目。3900 多个测试。单人开发者。没有计算机科学学位。4 个月。<p>论文主题:应用层信任对于自主代理来说是不够的。OctantCore 将代理身份、能力边界、TTL 强制执行和审计作为一流的内核原语。清单编译为内核强制执行策略。代理不决定它能做什么。内核决定。<p>Rust LSM 补丁已在 lore.kernel.org 上接受了 Google 的 Rust-for-Linux 团队和 LSM 维护者的审查。OctantCore 在 OctantVMM 上启动,带有内存管理器、中断、系统调用接口、代理描述符表和能力执行器,在启动时初始化。通过同时编排 10-12 个并行的 AI 编码会话来构建。<p>它超越了隔离。代理会识别自身知识的空白,并寻找它们所不知道的东西(好奇心子系统,已实现)。后台推理会巩固学习到的模式(做梦)。一个在宪法安全边界内的 7 阶段自我进化管道。新技能通过网状层在全球范围内传播到每个 OctantOS 实例。所有这些都受到内核的约束。<p>以前从未有过类似的东西。如果我无法继续下去,这就是将要消亡的东西。<p>我需要稳定。一个可以居住的地方,以及足够维持 3 个月基本生活的资金,以便让 OctantOS 做好投资准备。一位愿意支持我的天使,为我提供这段时间的支持。一家公司说“来这里工作吧,我们有地方”。我明天就可以带着我的狗搬到任何地方。或者只是来自有类似经历的人的建议。<p>我只需要有人相信这个大脑在没有在帐篷里挨冻的情况下能做什么。<p>https:&#x2F;&#x2F;github.com&#x2F;MatrixForgeLabs&#x2F;OctantOS https:&#x2F;&#x2F;octant-os.com https:&#x2F;&#x2F;gofund.me&#x2F;f554a86ee
查看原文
I’m going to be straight about my situation because I don’t know where else to turn.<p>My dad was diagnosed with cancer. While he was in hospital, the council emptied his house. Everything I owned was in that house. £20,000+ of equipment, years of research, a server with thousands of hours of work. Locks of my kids’ hair. Photos. All thrown in a tip.<p>My family turned my dying dad against me. I ended up living with someone suffering from paranoid psychosis. That’s where I built most of what I’m about to describe. Three days ago, 24 hours of abuse, and now I’m in a tent with my dog. 5°C weather. No money.<p>The council refused housing. The government won’t recognise my autism. They want me job hunting 35 hours a week from a tent.<p>I’m not incapable. I’ve raised a family. I’ve worked my whole adult life. Supervising teams, tattooing, freelance programming, building proprietary backend systems across 20 years of working with Linux. My autism isn’t a disability here. It’s the reason I can hold an entire OS architecture in my head and see how every component connects. When I point this brain at a problem, it produces systems that work, at a speed that doesn’t make sense to most people.<p>Over the past 4 months, I’ve been building OctantOS. An operating system for autonomous AI agents. Not a framework. Not a container wrapper. An actual OS with its own kernel (OctantCore, from-scratch Rust), its own hypervisor (OctantVMM), a single-binary Rust userspace, and a 10-layer security stack enforcing agent permissions at the kernel level.<p>~1.3M total lines of code. ~800K Rust. 50 crates, ~25 satellite projects. 3,900+ tests. Solo developer. No CS degree. 4 months.<p>The thesis: application-layer trust is insufficient for autonomous agents. OctantCore makes agent identity, capability boundaries, TTL enforcement, and audit first-class kernel primitives. Manifests compile to kernel enforcement policies. The agent doesn’t decide what it can do. The kernel does.<p>Rust LSM patches reviewed on lore.kernel.org by Google’s Rust-for-Linux team and the LSM maintainer. OctantCore boots on OctantVMM with memory manager, interrupts, syscall interface, Agent Descriptor Table, and capability enforcer initializing at boot. Built by orchestrating 10-12 parallel AI coding sessions simultaneously.<p>It goes beyond isolation. Agents identify gaps in their own knowledge and seek out what they don’t know (curiosity subsystem, implemented). Background inference consolidates learned patterns (dreaming). A 7-stage self-evolution pipeline within constitutional safety boundaries. New skills propagate across every OctantOS instance globally via the mesh layer. All kernel-constrained.<p>Nothing like this has existed before. That’s what dies if I can’t keep going.<p>I need stability. A place to live and enough to cover basics for 3 months to get OctantOS investment-ready. An angel willing to back me for that runway. A company that says “come work here, we have a place.” I’ll relocate anywhere, tomorrow, with my dog. Or just advice from someone who’s been here.<p>I just need someone to take a bet on what this brain can do when it’s not freezing in a tent.<p>https:&#x2F;&#x2F;github.com&#x2F;MatrixForgeLabs&#x2F;OctantOS https:&#x2F;&#x2F;octant-os.com https:&#x2F;&#x2F;gofund.me&#x2F;f554a86ee