The retrospective
When the delivery pull request has merged and every task is done, cancelled, or deferred, choose Start retrospective. Only a person can start it; Kana and Koa can’t. Kanaeru then opens a Retrospective session, and Kana works through the cycle on her own. The Retrospective panel in the Execution tab shows what she finds:
Kana also scores spec drift, how far what was built moved from the blueprints you approved. A blocking drift verdict has to be acknowledged by a person before the outcome can complete.
Closing the retrospective
While Kana is still working, the button in Evidence & trust reads Retrospective still running. When she’s done, choose Accept delivery and complete outcome. The outcome completes only when the retrospective has at least one feedback item. Kana records her own during the session, so this is normally already true. Adding your own feedback is what earns Complete a retrospective toward your level. Completing the outcome also saves its retrospective as learnings. If that fails, the outcome stays in its retrospective and you see The retrospective findings could not be saved to the experience bank. Feedback you add after completion is still saved as learnings, within about a minute.Applying a finding
Each Challenges, Learnings, and Action Items finding in the Retrospective panel, Kana’s and your own, has an Apply to roadmap button. Applying a finding drafts a roadmap item from it, labeled From retrospective, and the finding then shows Applied with View in roadmap. The item stays proposed until you approve or reject it under Review auto-suggestions on the Roadmap tab. Applying the same finding again opens the same item. Applying a finding after you’ve completed a retrospective earns Apply a retrospective finding, one of the goals for reaching Autonomy. Editing the vision’s title or description after a retrospective still counts too. Either way it’s credited once per vision.Learnings
A learning is one lesson, such as a recurring failure and how to avoid it. Each learning has a scope:
And a status:
Outcome and workspace learnings are active as soon as Kana saves them. A company-wide learning waits as Pending review, because it would reach every workspace, unless it’s backed only by evidence observed in execution logs, which Kana admits on her own.
Approving company-wide learnings
Owners and admins review them in Agent Memory (see below) under Pending review. Open a learning to read its evidence, then Approve or Dismiss it with a reason. If it changed while you had it open, you’re shown the latest version to review again. The same works from the terminal:--revision is the hash from learnings get, so you decide on the version you read. Approving a learning makes it active and marks it as Human guidance. Dismissing one retires it together with every learning that shares its key, at every scope. See kana memory.
How learnings reach Kana
Kana doesn’t read every learning in every session. Each kind of session gets the active learnings that fit its work:
A session gets at most 10 learnings, most costly first. They’re added to Kana’s instructions for the session. On Claude Code they’re also restored when a session starts, resumes, or compacts its context. Sessions that get company-wide learnings also get your company notes, outside that limit.
Seeing what Kana has learned
Open a workspace’s … menu → Settings → Agent Memory:- Pending review (owners and admins only) lists proposed company-wide learnings to approve or dismiss.
- Saved learnings lists the workspace’s learnings and the company-wide ones it inherits, with each one’s scope, status, and source (Observed, Agent proposal, or Human guidance). Owners and admins can change a workspace or outcome learning here (see below).
- Company notes are key/value notes for your organization, such as your API style or naming rules. Kana’s Planning, Task Execution, Review, Vision & Roadmap, and Refinement sessions read up to 20 of them as company guidance, alongside their learnings. Only owners and admins can add, edit, or delete them. A note written by an agent isn’t read until an owner or admin saves it.
- On a workspace or outcome learning in Saved learnings: Resolve it when the problem is fixed (it comes back if the problem recurs), Dismiss it when the advice is wrong, or Reactivate a resolved one. Each changes only that learning.
- On a company-wide learning, Dismiss retires it together with every learning that shares its key, at every scope.