<h1 align="center"livt</h1
<p align="center" <bYour team's product decisions, living in text — context for AI.</b </p
<p align="center" <a href="https://boykush.github.io/livt/"Why livt</a | <a href="#getting-started"Getting Started</a | <a href="https://boykush.github.io/livt/demo/"Live Demo</a </p
What is livt?
livt is your team's decision log for the opportunities it is working on. It keeps what a discovery session decided as text in a repository, shows it as the board it came from, and serves it as context to the coding agents that build it — so the decision is still readable, and still quotable, when someone implements it months later. It is not a specification of everything the product already does.
Why livt says which problems it is built against and when it is the right tool.
Getting started
Install livt. mise checks the release's build provenance before installing it:
mise use "github:boykush/livt@<version>"A binary from GitHub Releases, or go install github.com/boykush/livt@<version, works as well; SECURITY.md says how each release is built and how to verify it.
Then give your coding agent the skills that write a livt repository. Each plugin under plugins/ says in its README what it is for and how to install it; livt-discovery is where a team starts.
After a session, give your agent the board — a photo, an export, or the stickies pasted as text — and ask it to record it. In the repository it wrote to, livt serve shows the result at http://localhost:3000.
There is no command or format reference to read: each detail lives where it cannot drift, and Reference says where.
Contributing
Issues and pull requests are welcome — see CONTRIBUTING.md. For vulnerability reports, see SECURITY.md.
Acknowledgements
livt renders practices it did not invent. livt and BDD credits the people who wrote them down, and says what livt added and where it departs on purpose.