A knowledge base for the decisions behind every release

Keep proposals, release checklists and product decisions together. Use Kivrelune to capture the reasoning, find the latest scope and update the handoff as work ships.

Kivrelune workspace
Orris Field Co.Kivrelune AgentSearchUpdatesReview queueRecent documentsTechnical proposalsRelease planningProduct decisionsChannelsCompanyEngineeringTeam library
Self-maintaining

Product & Engineering

From the first proposal to the note that goes out after rollout.

Meet the teams inside our example workspaces.

OlvarynTavirelMeruvelleOrris Field Co.
Kivrelune Agent

Carry the decision into the release brief

Turn an issue or an engineering note into a draft for the product team. Keep the source and the reason for the change beside the decision it affects.

Book a demo
Release Checklist
Source · Branchloom

The rollout checklist now calls for a verification note in the support handoff.

Preparing an update

I found the related passage in Release Checklist. Here is a draft for the owner to review.

Suggested addition

Include the release verification note in the support handoff.

Release Checklist
“Confirm test coverage, review the change list and name the on-call owner.”
Before the releaseRelease Checklist · Orris Field Co. sample
Ask

Look up the release steps as you ship

Open the checklist from a question about rollout. The cited passage takes you straight to the tasks the release owner needs to finish.

Book a demo
Release Checklist
Question

What should the release owner do after rollout?

Answer from your workspace

Record the shipped version and let support know which behaviors changed. Keep that handoff with the release checklist.

Release ChecklistSource passage
“Record the version and update the support handoff with any changed behavior.”
After the rolloutRelease Checklist · Orris Field Co. sample
Knowledge maintenance

Bring the checklist up to date after rollout

Compare a Branchloom update with the current handoff. Approve the revised instruction so the next release starts with the verified steps.

Book a demo
Release Checklist

Review proposed change

The rollout checklist now calls for a verification note in the support handoff.

Proposed wording

Include the release verification note in the support handoff.

Release Checklist Owner review
“A repeatable handoff for the release owner.”
Release ChecklistRelease Checklist · Orris Field Co. sample

Templates

Start with an outline for your team’s next document.

See more templates

Frequently Asked Questions

How do we capture the reasoning behind a technical choice?

Use the technical proposal to compare options, then put the chosen approach and its evidence in a decision record.

Where can engineers find the rollout steps?

Open the Release Checklist in the Engineering channel. It groups the checks before rollout and the handoff afterward.

How can product and engineering share a release brief?

Use the release brief template for scope, ownership and rollout details. Link the decision record that explains the change.

What does the agent use to prepare a draft?

In this example, a note from Branchloom provides the signal. The proposed update stays linked to Release Checklist so that the owner can inspect the context.

Can I explore this workflow myself?

Yes. Open the sample workspace from the top of this page and read Release Checklist. The review queue lets you inspect and approve a suggested change.

Can I reuse the document templates?

Open any template to read the prompts, copy the Markdown or download a file you can adapt to your own team.

A shared library for your team
and the AI they work with.