I’ve been building Hubnot, a collaboration tool that keeps signed work records alongside your code in Git.
The latest work gives it a richer issue model: descriptions, acceptance criteria, labels, assignees, relationships, and revision history. You can start with a title and add structure as the work grows.
The part I care about is how it handles uncertainty.
When two people edit an issue independently, both changes remain visible. Resolution is explicit. When an automation retries a successful request, it gets the original result without creating duplicate work. Stale updates fail clearly.
Those details matter for cognitive ergonomics. People and tools need to understand what happened, what changed, and what still needs a decision.
This also gives agents a more dependable interface: documented JSON commands, bounded queries, and a working consumer example. Assignment and issue status remain descriptive; permission to execute work belongs to the system doing the execution.
https://github.com/LynnColeArt/hubnot
#OpenSource #DeveloperTools