Viewing profile — jolaflow

A modern issue tracker enabling replay for agentic workflows (via board time-travel) and focus on ergonomics (native to the terminal). https://ljtn.github.io/epiq/

As for issue tracking, there are also other git-native alternatives out there. Epiq is entirely git-backed, vendor agnostic and persists state as a versioned log in your repo. Im i…

That is also very true, and I think time-travel capabilities would help detect that too.

I think behavior driven development probably can make intent more explicit and standardized. However, I think they operate at different levels, or on a different axis if you will. …

Interesting. When it comes to auditing, I think there is also another layer to be verified - the intent. We have tooling for static analysis and automated tests, but drift in inten…

I have run into the same problem, and started calling the phenomenon vision drift. I noticed that the issue tracker I built was well suited to address this problem, as it handles b…

A gimmick feature turned out to be an essential capability in agentic workflows.

How new ways of working asks for a new generation of issue tracking capabilities

Thank you for the kind words!

Thanks! Id be happy to hear what you think after trying it out!

Thank you! I too am excited about next steps. There are a lot of interesting paths to explore still, and I do agree that the web interface would be a natural evolvement.

Thanks for the kind feedback! My initial motivation was of lack ergonomics in the tools I used. I had a vision of what I wished issue tracking was like, and the tools we were using…

That is a known limitation as of now. Text updates are currently handled as whole chunks, so Epiq does not implement character-level CRDT merging. In the event of conflicting updat…

Thanks for the encouraging input!

Thanks for the upvote! Let me address these: 1. I envision people already comfortable with the terminal as the first to pick it up, but as someone else pointed out, a considerable …

Thank you for the kind words!

They are not mutually exclusive. The MCP layer is there for deterministic outcomes, because there are times and places where that matters a lot.

It's mainly about robustness and deterministic outcomes. There is a small level of noise in TUI output, and structures that are easily parsed by a human can be ambiguous for an age…

Good point. A local web UI is probably one of the highest priorities from here. The UI, persistence and materialization layers are already fairly separated architecturally. The cur…

Thanks!

Thanks for input. Interesting list. A few notes on that: - Issue state is not tied to commits in the checked out repo. Events live in append-only user-scoped logs and are materiali…