I've shut down AEGIS v1 and archived github.com/hikmahtech/aegis. The code stays public and MIT-licensed. You can still read it, fork it and learn from it. It just won't get fixes, releases or answers to issues any more.
AEGIS itself isn't going away. It is being rebuilt as version 2, and version 2 is not open source. This post explains why, what v2 looks like, and what is already running on it.
What v1 was
AEGIS v1 was one system that did everything for one person: my tasks, email, money, research, and the alerts from the machines in my house. Three services shared one Postgres database. A Temporal worker ran every workflow on one task queue. A handful of named agents each owned a slice of the work, and every time one needed me, it asked through the same approval card.
I open-sourced it in July, and the ideas in it held up. One primitive for every interruption. Durable workflows that survive a weekend of waiting for my tap. Local models first. An audit line for everything that matters. None of that is changing.
What went wrong with one system
The shape was the problem, not the ideas.
- One deploy for everything. A fix to bank-statement parsing redeployed the code that restarts services in my homelab. Every change carried the risk of every other area.
- One database for everything. The accounting tables and the alert tables lived side by side. Nothing stopped one area from reading or writing another's rows, so over time some did.
- Nothing could leave. If someone wanted just the bookkeeping part, there was no way to give it to them. It came with my task manager, my research feeds and my infrastructure agent attached.
The last one matters most. The bookkeeping lane is useful to people who aren't me. To hand it to anyone, it has to stand on its own.
This is the first part. The full post, including the rest of the working details, is on my site: AEGIS v1 is archived. Here is what replaces it
Top comments (0)