Show HN: Gitseq: A Repo Becomes a Workroom

Last week I was trying to figure out how to run a new project at work, where there are lots of technical artifacts, lots of stakeholders upstream and downstream, plenty of documentation for different audiences... all the usual stuff, and actually very little "code" and lots of "best practice" that the project will manage. I won't even be the subject-matter expert for most of it. Yikes.

Then I figured out a small thing that could make the whole job easier: git plus a sequencer plus some ontology. Proving the idea took a few hours, until it was bootstrapped enough to use as its own development harness with a handful of agents doing most of the implementation.

Work in progress - plenty still to do - but I think it's useful for agentic development. Hopefully it will eventually turn out to be the "PMO in a box" that I really need for that project.

A few artifacts:

- Blog post: https://generalbusiness.ai/blog/2026-08-09-gitseq/ - "Coordination and Traceability: Not Two Problems"

- GitHub repo: https://github.com/generalbusiness-ai/gitseq (MIT license, go kernel)

- 5-minute walkthrough video: https://youtu.be/LwVhU3mNXnM

The core of the idea is: coordination for agents (and people), in the "small pieces loosely joined" way, could use an event sequencer (I've just spent a few months poking at a distributed VM project inspired by Croquet and LambdaMOO that ended up using an event-sequencer as one of the key primitives) and deterministic "projections across a log" (to see the status of things); if the things whose status you track are work-products, this creates traceability from the get-go. "`make` for agentic stuff", if you like. And the sequencer is just built on top of git refs. Then, add a small amount of vocabulary (promises and conditions of satisfaction), that's enough to get real work done in a structured, traceable way. You can say "request: do X", then "I'll do it" (strongly referencing the request), then actually do it (strongly referencing the commitment), then... all the way to delivering the thing, which itself can say "this is based on X" in an auditable way.

The actual deliverable of that story is: a repo becomes a workroom. Or: an agent harness, where there's not much harness and it's mostly just git over MCP. Or: (the UI is ugly and honestly not very good) "slack for agents".

Hope you all find it interesting!