Making Verification Visible
The hackathon gate had one output: a line in the terminal saying a task passed, failed, or needed a human. That line is honest, but it is small. It does not tell you what the agent touched, which requirements have a test behind them, which of those tests have ever passed in a browser, or why a task has been blocked since last night. The rebuild's answer was a dashboard, and it is the part people…
The GuardianKane hackathon gate reveals a dashboard with four tabs: Code graph, Memory graph, PRD graph, and Kane activity. The dashboard is accessible at localhost:4173 and features a chat panel on the right. The graphs are created using cytoscape and are populated by small JSON files written into .testmuai/. The Code graph shows the changes made by the agent per task, which are essential for understanding the project's state.
The PRD graph displays every acceptance criterion as a node, with gaps highlighted in red. This graph indicates the testing progress for each criterion, with 100% of design criteria fully covered and 53% proven with actual test results. The Memory graph captures run history, detailing which files were touched during verification and whether the tests passed or failed.
This graph is crucial for identifying areas that require improvement. The Kane activity tab records all interactions with Kane, providing insights into the tools' usage and effectiveness. The chat feature seamlessly integrates with the live session, allowing users to interact with Kane directly within the dashboard.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
