@GergelyOrosz I think we need a framework to assess the risk introduced with no human understanding how a system works. I have suggested the term Cost of Cognitive Debt, or CCD.
Elaborating on it here:
https://t.co/pom9pllkN0
@sophiamyang You might find Epiq interesting. It is a vendor agnostic, distributed kanban, build on top of Git, persisting state as an event graph, so ideal for tracing and replay:
https://t.co/swO14onBlT
@mikehostetler It's Git-backed and distributed, has multi-user collaboration, and traceability at its core. Issues persisted as an event-graph in user-scoped logs.
You can inspect what an agent did hours, or years, ago, including the associated code-diff inline in the ticket.
@ravinsharma7 Spot on. You may want to have a look at Epiq. It is a distributed issue tracker storing the board as an event graph in your repo, allowing you to replay, audit and inspect current or historical workflows, with integrated code diffs:
https://t.co/swO14onBlT
@colemurray You may wanna have a look at Epiq for reviews and workflow auditing. You get the overview and sense and direction via board time travel, but you can also drill down into the code diff in the ticket:
https://t.co/swO14onBlT
@DominikTornow You may wanna have a look at Epiq. It allows for better overview and workflow auditing. You can zoom in on individual agent workflows hours, or days ago, via time travel + filtering, and also drill down in the diff if needed:
https://t.co/swO14onBlT
@JohnKutay@colemurray I think you need overview, to then be able to zoom in on specific parts. You might find Epiq interesting, it lets you do just that via workflow replay:
https://t.co/swO14onBlT
@mikejulian@czpython@DuckbillHQ Would you be helped by Epiq? It is ideal for high level workflow auditing and real time workflow monitoring, also enabling you to drill down in the code diff when needed:
https://t.co/swO14onBlT
@GergelyOrosz I think it helps if you reinstate some of the architectural constraints that the review should live within. It, of course, requires you to have thought of an architecture to begin with.
@GergelyOrosz I use Epiq, which allows me to replay the workflow after the fact. So I review the intricate parts by filtering out noise and replaying:
https://t.co/swO14onBlT
@benawad You might find Epiq useful and lightweight enough. It tracks issues as code in your repository, and lets you replay historical workflows via time-traveling. It is super fast as it is distributed and local-first:
https://t.co/swO14onBlT
Not sure how it relates to what you are looking for, but you might be interested in Epiq. It stores your board as an event graph in your repo, so you can query, filter and time-travel your board + code.
It lets you reply individual agent workflows that happened in the past, or just monitor real-time sessions:
https://t.co/L2FSffkBDz