<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/architecture/retrospective-learning-loop/">
  <id>https://docs.spec-kitty.ai/architecture/retrospective-learning-loop/</id>
  <title>Understanding the Retrospective Learning Loop</title>
  <updated>2026-09-30T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/architecture/retrospective-learning-loop/"/>
  <summary>Conceptual explanation of the four-category model, bounded contexts, event-model layering, and the synthesize anti-corruption layer.</summary>
  <content type="html">&lt;span id=&quot;understanding-the-retrospective-learning-loop&quot;&gt;&lt;/span&gt;
&lt;p&gt;This document explains why the retrospective learning loop exists and how it works at a conceptual
level. For the operator how-to, see
&lt;a href=&quot;/guides/how-to/governance/use-retrospective-learning/&quot;&gt;How to Use Retrospective Learning&lt;/a&gt;. For the schema
reference, see &lt;a href=&quot;/api/retrospective-schema/&quot;&gt;Retrospective Schema Reference&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;why-retrospectives-exist&quot;&gt;Why retrospectives exist&lt;/h2&gt;
&lt;p&gt;Governance without feedback is static. If your &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; never changes, your project’s policy
doctrine never improves. Directives that are unhelpful stay unhelpful. Glossary terms that are
missing stay missing.&lt;/p&gt;
&lt;p&gt;The retrospective learning loop is the mechanism by which completed missions feed back into
governance. When a mission finishes, the runtime captures structured findings: what helped, what
did not help, what governance or context gaps appeared, and what concrete changes are proposed to
the doctrine, DRG edges, or glossary. Over many missions, the retrospective summary reveals
patterns — directives that are consistently flagged as unhelpful, terms that are consistently
missing, DRG edges that would improve context relevance.&lt;/p&gt;
&lt;p&gt;Without retrospectives, governance stagnates. With them, governance is a living system that
improves with every completed mission.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-four-category-model&quot;&gt;The four-category model&lt;/h2&gt;
&lt;p&gt;The retrospective system maps onto four conceptually distinct categories:&lt;/p&gt;






























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Category&lt;/th&gt;&lt;th&gt;What it is&lt;/th&gt;&lt;th&gt;Primary artifact&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Policy&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;When / whether / how-to-fail the loop runs&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml#retrospective&lt;/code&gt; or charter frontmatter&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Record&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Structured findings and proposals for one mission&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;mission_id&gt;/retrospective.yaml&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Summary&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Read-only aggregation across all records&lt;/td&gt;&lt;td&gt;stdout / JSON via &lt;code dir=&quot;auto&quot;&gt;retrospect summary&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Application&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Human-approved mutation of doctrine / DRG / glossary&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize&lt;/code&gt; with explicit &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Each category has one and only one authoritative operation. Conflating them — for example, treating
&lt;code dir=&quot;auto&quot;&gt;summary&lt;/code&gt; as the authoring step — is the most common documentation error. The canonical post-merge
sequence is: &lt;strong&gt;mission review → author or verify retrospective (&lt;code dir=&quot;auto&quot;&gt;retrospect create&lt;/code&gt;) → surface
findings (&lt;code dir=&quot;auto&quot;&gt;summary&lt;/code&gt; aggregates; &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; reviews proposals)&lt;/strong&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;bounded-context-map&quot;&gt;Bounded-context map&lt;/h2&gt;
&lt;p&gt;This mission spans four bounded contexts. The crossings are explicit and mediated:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;┌──────────────────────────────┐         ┌──────────────────────────────┐&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ Retrospective Authoring      │         │ Mission Lifecycle /          │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│                              │         │ Event Log                    │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - RetrospectivePolicy        │         │                              │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - RetrospectiveRecord        │         │ - runtime_bridge.py          │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - generator (pure Python)    ├────────►│ - retrospective_terminus.py  │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - writer (merge/overwrite)   │ emits   │ - status.events.jsonl        │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - events (additive)          │ events  │ - reducer (no-op for         │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│                              │         │   retrospective events)      │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;└────────┬─────────────────────┘         └──────────────────────────────┘&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ proposals[] (data only)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;▼&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;┌──────────────────────────────┐         ┌──────────────────────────────┐&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ agent retrospect synthesize  │         │ Doctrine / DRG / Glossary    │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ (anti-corruption layer)      ├────────►│                              │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│                              │ apply   │ - human-approved mutations   │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - preview proposals          │ (gated) │ - structural changes always  │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│ - apply with human approval  │         │   require explicit consent   │&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;└──────────────────────────────┘         └──────────────────────────────┘&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Retrospective Authoring → Event Log&lt;/strong&gt;: explicit, additive event payloads
(&lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptureFailed&lt;/code&gt;). The reducer treats them as no-ops for
lane state; they are purely informational events in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retrospective Authoring → Doctrine/DRG/Glossary&lt;/strong&gt;: never direct. Proposals are data; their
application goes through the &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; anti-corruption layer with human approval. The runtime
does NOT auto-apply structural governance changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CLI Surface → Retrospective Authoring&lt;/strong&gt;: through documented JSON contracts in
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/retrospective-default-policy-01KS049J/contracts/&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-generator-pure-python-module&quot;&gt;The generator: pure-Python module&lt;/h2&gt;
&lt;p&gt;The default retrospective generator is a pure-Python module (not an agent profile invocation).
This design choice was deliberate:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Sub-second latency&lt;/strong&gt;: the default-on path runs at every mission boundary; agent dispatch
(5–30 s) would be incompatible with that.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Determinism&lt;/strong&gt;: the FR-021 “byte-identical reductions” guarantee requires the same inputs to
always produce the same output. A pure function satisfies this; an agent-authored record
does not.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Testability&lt;/strong&gt;: unit tests scaffold mission artifacts on disk and call the generator directly,
with no agent harness mocks.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;retrospective-facilitator.agent.yaml&lt;/code&gt; profile exists as a &lt;strong&gt;human-mediated tool&lt;/strong&gt; for richer
post-mortems via explicit operator invocation. It is not the runtime default.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;event-model-layering-renatas-wp04-note&quot;&gt;Event-model layering (Renata’s WP04 note)&lt;/h2&gt;
&lt;p&gt;There are two event namespaces in the codebase:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;retrospective.events&lt;/code&gt;&lt;/strong&gt; (older): the autonomous-terminus lifecycle wrapper, retained for
back-compat with pre-3.2.0 flows. It wraps the facilitator dispatch lifecycle (start / complete
/ fail) in a style consistent with the older HiC/autonomous gate model.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;retrospective.lifecycle_events&lt;/code&gt;&lt;/strong&gt; (new, FR-024-compliant): the canonical contract surface
used by post-mission flows in 3.2.0+. These events (&lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptureFailed&lt;/code&gt;) are emitted into &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and are the authoritative
record of retrospective authoring state.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The two namespaces are cleanly layered: &lt;code dir=&quot;auto&quot;&gt;lifecycle_events&lt;/code&gt; is the public surface that
orchestrators and dashboards consume; &lt;code dir=&quot;auto&quot;&gt;events&lt;/code&gt; is the internal lifecycle wrapper the facilitator
runtime uses. They do not conflict, but contributors should import from &lt;code dir=&quot;auto&quot;&gt;lifecycle_events&lt;/code&gt; for any
new code that reacts to retrospective completion.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;policy-resolution-and-precedence&quot;&gt;Policy resolution and precedence&lt;/h2&gt;
&lt;p&gt;Policy is resolved at call time from a three-tier stack:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Charter frontmatter&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;): wins by default for governed projects.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;retrospective:&lt;/code&gt; key): active when charter does not define the
field, or when charter explicitly sets &lt;code dir=&quot;auto&quot;&gt;retrospective.precedence: config&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Runtime defaults&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;enabled: true&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;timing: after_completion&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;failure_policy: warn&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The resolver returns &lt;code dir=&quot;auto&quot;&gt;(policy, source_map)&lt;/code&gt; where &lt;code dir=&quot;auto&quot;&gt;source_map&lt;/code&gt; records the origin of every
leaf field — operators can always trace which file and key drove a given gate behavior.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;proposal-lifecycle&quot;&gt;Proposal lifecycle&lt;/h2&gt;
&lt;p&gt;A completed retrospective produces &lt;strong&gt;proposals&lt;/strong&gt; — structured suggestions for governance changes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;add_glossary_term&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;update_glossary_term&lt;/code&gt; — add or update a glossary term&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;flag_not_helpful&lt;/code&gt; — mark a DRG artifact as not helpful&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;add_edge&lt;/code&gt; — add a relationship to the DRG&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;synthesize_*&lt;/code&gt; — more complex doctrine synthesis proposals&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Their lifecycle:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Generated&lt;/strong&gt;: the pure-Python generator produces proposals and writes them to
&lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;mission_id&gt;/retrospective.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Staged&lt;/strong&gt;: proposals are visible in &lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize&lt;/code&gt; (dry-run by default). No changes
have been made to governance state yet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Applied or rejected&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize --apply &amp;#x3C;id&gt;&lt;/code&gt; validates, conflict-checks,
and applies. Rejected or conflicting proposals are not applied.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Provenance recorded&lt;/strong&gt;: every applied change carries provenance back to the originating
mission, proposal ID, and evidence event IDs.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;flag_not_helpful&lt;/code&gt; is auto-included in the effective apply batch; it still requires
&lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt; and never mutates state during preview.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-synthesizers-role-anti-corruption-layer&quot;&gt;The synthesizer’s role (anti-corruption layer)&lt;/h2&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize&lt;/code&gt; command is the &lt;strong&gt;only&lt;/strong&gt; path from retrospective output to
governance change. Its role is to validate, conflict-check, and apply proposals that already
exist in the retrospective record — not to generate content.&lt;/p&gt;
&lt;p&gt;The synthesizer is &lt;strong&gt;fail-closed on conflicts&lt;/strong&gt;: if two proposals contradict each other (for
example, both add the same glossary term with different definitions), it applies nothing from the
conflicting set.&lt;/p&gt;
&lt;p&gt;You cannot bypass the synthesizer by editing governance files directly — those files are derived
artifacts and would be overwritten on the next &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; run. The correct path:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Review proposals (&lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize&lt;/code&gt;, dry-run by default)&lt;/li&gt;
&lt;li&gt;Resolve any conflicts (manually, in &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; if needed)&lt;/li&gt;
&lt;li&gt;Apply (&lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize --apply &amp;#x3C;id&gt;&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt; for full batch)&lt;/li&gt;
&lt;li&gt;Re-run &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; if &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; was edited&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&quot;cross-mission-summary&quot;&gt;Cross-mission summary&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty retrospect summary&lt;/code&gt; aggregates retrospective records across all missions in the
project. This read-only view reveals governance patterns not visible from any single mission —
for example, a directive flagged as not helpful in 5 of 10 missions is a strong signal to revise
or remove it.&lt;/p&gt;
&lt;p&gt;The summary tolerates a mix of complete, skipped, missing, and malformed records without aborting.
Malformed records are excluded from counts with a structured reason. Use &lt;code dir=&quot;auto&quot;&gt;--include-malformed&lt;/code&gt;
to see details.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See Also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/governance/use-retrospective-learning/&quot;&gt;How to Use Retrospective Learning&lt;/a&gt; — operator how-to&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/retrospective-schema/&quot;&gt;Retrospective Schema Reference&lt;/a&gt; — YAML and event schemas&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/adr/3.x/2026-05-19-1-retrospective-default-policy-architecture.md&quot;&gt;ADR: Retrospective Default-On Policy Architecture&lt;/a&gt; — architectural decisions&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
