In July I wrote that Loomfield had to make sense without its builder in the room. These two weeks, September 20 through October 3, were the first time it actually left.

It was also the busiest window yet, with about 550 commits. A lot of them were fixes that only showed up once someone else installed it.

Taking me out of it

Loomfield had a lot of me baked into it. My timezone, my contacts, my wording in prompts. All of that got stripped out, and a build-time scan now looks for anything personal and refuses to ship until it finds nothing.

A fresh install now starts with an empty Weave, a setup screen, a getting-started checklist, and a starter set of general-purpose tools. That set started at 55 and got trimmed down to the ones that are useful to almost anyone.

The first alpha builds went out for Mac, then Windows a few days later, with release notes written for people instead of for me. Access is invite-only for now.

Follow along at loomfield.ai

The install bugs my tests missed

Several Mac releases would have been rejected by macOS as a damaged app. The bundle was only partly signed. My end-to-end test downloaded it with a command-line tool that doesn't mark files as coming from the internet, so macOS never ran the check a real user would hit. Releases are now blocked unless the bundle passes the strict signing check.

On Windows, updates kept failing and the old version kept showing up even after an uninstall. Stopping the app only stopped the launcher. The hub process underneath kept running and held the folder open. Every stop path now ends that process too.

There was also a generic "didn't install" message that swallowed the real error. That one got fixed, and it went on my growing list of failures that hide themselves.

Decisions with a state

Decisions in the Weave now have a real lifecycle. A decision is open, decided, superseded, retired, or rejected, and separately it's either ratified by the owner or not. An agent can't mark its own idea as approved. Owner approval only counts when it matches words I actually typed.

Every project also got an operating view built from those records. It shows the current state, the calls waiting on me, what's on hold, and recent activity. It's generated instead of hand-written, so it can't drift.

Files and capability code moved into the database too, which finished retiring the old folder the system grew up in.

Guarding the edges

Once outside content enters a session, risky actions like sending data out or deleting in bulk now get flagged or need confirmation. I tuned it so it protects without babysitting.

A new research feature lets Loomfield build expertise on a topic in the background, under a daily spend cap. The first reviews of it failed. Its restrictions were a blocklist, so a research session could still find a way around them. It's deny-by-default now.

Still open

Windows installers still aren't code-signed, and invites aren't email-verified yet.

I also added a release rule out of all this. Nothing gets published that my own hub isn't already running.