Skip to content

tarsiThe release plane

Changelog → semver bump → tag → publish — one ops wire for humans, agents, and campaigns.

What it is ​

Tarsi is the org's release plane: changelog → semver bump → tag → publish, exposed as tarsi-serve ndjson ops. Repo config is tarsi.toml; org conventions ride type: tarsi tamias profile packs; there is deliberately no tarsi CLI.

Why ​

Every repo was reinventing release plumbing — changelog rendering, commit→bump inference, tag schemes, publish ordering. Tarsi makes release semantics a shared, deterministic ops surface that humans, agents, and peregrin campaigns all drive identically, with dry-run as the default so probing never mutates.

Boundary ​

  • Owns: release semantics — plans, bumps, changelogs, tags, publish orchestration.
  • Doesn't own: orchestration timing/approval (peregrin), distribution (tamias), git itself (lasius-vcs).

Where to go next ​

You want to…Go to
Cut a real release end to endTutorial
Do a task (write tarsi.toml, author a profile, drive ops)How-to
Understand the design (ops wire, semantics, boundaries)Explanation
Look up an op, config field, or pack layoutReference

MIT licensed — part of the 9aia GAIA stack.