kadence

About kadence

Tasks, their whole history and the time they took live in your git repo as an append-only journal: one JSON file per event, never edited, never deleted. Everyone else keeps state — a task file, a row, a spec. State drifts, conflicts on merge and forgets. Events cannot: board and velocity are folded from the journal on read. Your team reads it in the terminal, your AI agents read the same thing as --json. No server, no account, no network. MIT.

The person behind kadence

• 
  Andriy Bohutskyy

  Maker

  PM & Solo Developer

  Email not found yet