README
¶
livt
Your team's product decisions, living in text — context for AI.
Why livt | Getting Started | Live Demo
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.
License
Documentation
¶
There is no documentation for this package.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package docs holds the site's text, in content/, and the HTML made from it, in site/.
|
Package docs holds the site's text, in content/, and the HTML made from it, in site/. |
|
internal
|
|
|
agreement
Package agreement checks that a rule naming the people whose agreement it needs is only marked accepted once they have agreed, and keeps the record of who did.
|
Package agreement checks that a rule naming the people whose agreement it needs is only marked accepted once they have agreed, and keeps the record of who did. |
|
automation
Package automation carries what an implementation repository's tests say they automate.
|
Package automation carries what an implementation repository's tests say they automate. |
|
config
Package config reads livt.yaml, the site config at the root of the livt repository.
|
Package config reads livt.yaml, the site config at the root of the livt repository. |
|
diff
Package diff says what changed between two revisions of a livt repository, one livt URI at a time.
|
Package diff says what changed between two revisions of a livt repository, one livt URI at a time. |
|
gitrev
Package gitrev reads the livt repository's own revision.
|
Package gitrev reads the livt repository's own revision. |
|
i18n
Package i18n holds the message catalogs for the site chrome — nav labels, headings, legends, empty states.
|
Package i18n holds the message catalogs for the site chrome — nav labels, headings, legends, empty states. |
|
mcp
Package mcp serves the livt repository (opportunities and their canvases, story maps, stories, example mappings, ubiquitous language) over the Model Context Protocol so implementation repos can fetch what was decided for a story or rule without reading livt's source.
|
Package mcp serves the livt repository (opportunities and their canvases, story maps, stories, example mappings, ubiquitous language) over the Model Context Protocol so implementation repos can fetch what was decided for a story or rule without reading livt's source. |
|
server
Package server builds artifacts and serves them with live reload, so edits to discovery and story files are previewed in the browser while editing.
|
Package server builds artifacts and serves them with live reload, so edits to discovery and story files are previewed in the browser while editing. |
|
uri
Package uri builds and parses livt URIs — the deployment-independent way to address one point of the livt repository: an opportunity, its canvas, a story map, a story, an example mapping, a rule, an example, a question, or a ubiquitous language term.
|
Package uri builds and parses livt URIs — the deployment-independent way to address one point of the livt repository: an opportunity, its canvas, a story map, a story, an example mapping, a rule, an example, a question, or a ubiquitous language term. |