<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/architecture/trail-model/">
  <id>https://docs.spec-kitty.ai/architecture/trail-model/</id>
  <title>Trail Model</title>
  <updated>2026-11-10T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/architecture/trail-model/"/>
  <summary>Operator reference for the Phase 4 trail model: how every standalone spec-kitty dispatch writes an auditable JSONL trail for accountability, SaaS coherence, and provenance.</summary>
  <content type="html">&lt;span id=&quot;trail-model&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;em&gt;Operator reference for the Phase 4 runtime consumption baseline.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&quot;overview&quot;&gt;Overview&lt;/h2&gt;
&lt;p&gt;Every standalone Spec Kitty dispatch leaves an auditable trail. The trail serves three purposes:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Local accountability&lt;/strong&gt;: operators can reconstruct what happened on any checkout without SaaS connectivity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hosted coherence (design intent)&lt;/strong&gt;: a hosted timeline could show the same history as the local audit log. No hosted projection path is live today; see &lt;a href=&quot;#saas-read-model-policy&quot;&gt;SaaS Read-Model Policy&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Governance provenance&lt;/strong&gt;: downstream retrospective and doctrine work can reference specific invocations.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;minimal-viable-trail&quot;&gt;minimal viable trail&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;One JSONL file per invocation, written locally before the executor returns.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Every &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch &quot;&amp;#x3C;request&gt;&quot;&lt;/code&gt; call writes a &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event to:&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;kitty-ops/{invocation_id}.jsonl&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;When &lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete&lt;/code&gt; is called, a &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event is appended to the same file.&lt;/p&gt;
&lt;p&gt;This is the unconditional minimum — it is always written, regardless of SaaS connectivity, charter state, or sync configuration. The data model is defined in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/record.py&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Mission-scoped dispatchers may also record &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;wp_id&lt;/code&gt; on the
&lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event. An implement or review claim that supplies &lt;code dir=&quot;auto&quot;&gt;--invocation-id&lt;/code&gt;
treats those values as a provenance assertion: the requested ULID and the
record’s embedded ID, mission, WP, action and profile must agree exactly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;No model identifier is recorded (#7013).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt; carries the harness key
(&lt;code dir=&quot;auto&quot;&gt;claude&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;codex&lt;/code&gt;, …) and is the only runtime identity a committed record holds.
The router’s catalog pick stays advisory on the dispatch payload and is never
written into the journal, because a committed artifact may not carry an AI model
identifier. A claim therefore has no durable evidence for a resolved model: it
refuses &lt;code dir=&quot;auto&quot;&gt;--model&lt;/code&gt; and records the model slot as explicitly absent
(&lt;code dir=&quot;auto&quot;&gt;RESOLVED_MODEL_ABSENT&lt;/code&gt; in the WP’s status snapshot) rather than fabricating one.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Records written before #7013 still carry &lt;code dir=&quot;auto&quot;&gt;model_id&lt;/code&gt;, and they stay that way.&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;ULID&gt;.jsonl&lt;/code&gt; is an immutable archive root (the
historical-preservation gate), so no migration rewrites them; they keep parsing
because the record model ignores keys it no longer declares, and nothing copies
the value forward into a new record.&lt;/p&gt;
&lt;h2 id=&quot;mode-of-work-taxonomy&quot;&gt;Mode-of-Work Taxonomy&lt;/h2&gt;
&lt;p&gt;Every invocation belongs to one of four work modes. The mode determines which optional trail tiers are eligible — it does not override the mandatory Tier 1 rule.&lt;/p&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Mode&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;th&gt;Example actions&lt;/th&gt;&lt;th&gt;Tier 2 eligible&lt;/th&gt;&lt;th&gt;Tier 3 eligible&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Standalone governed work, including advice, review, code changes, and test runs&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Yes (caller-triggered)&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt;&lt;/td&gt;&lt;td&gt;One step in a governed mission workflow&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Yes (caller-triggered)&lt;/td&gt;&lt;td&gt;Yes&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;query&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Read-only, no execution&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;profiles list&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;invocations list&lt;/code&gt;&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Mode-of-work is recorded on the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event as the &lt;code dir=&quot;auto&quot;&gt;mode_of_work&lt;/code&gt; field. New standalone dispatch records use &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt;. Runtime enforcement is active: &lt;code dir=&quot;auto&quot;&gt;profile-invocation complete --evidence&lt;/code&gt; is rejected for records that are not evidence-eligible (see “Mode Enforcement at Tier 2 Promotion” below).&lt;/p&gt;
&lt;h3 id=&quot;mode-enforcement-at-tier-2-promotion&quot;&gt;Mode Enforcement at Tier 2 Promotion&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete --evidence &amp;#x3C;path&gt;&lt;/code&gt; is rejected with &lt;code dir=&quot;auto&quot;&gt;InvalidModeForEvidenceError&lt;/code&gt; when the target invocation is not evidence-eligible. The enforcement runs &lt;strong&gt;before&lt;/strong&gt; any write, so the invocation remains open and uncommitted — rerun &lt;code dir=&quot;auto&quot;&gt;complete&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--evidence&lt;/code&gt; to close cleanly. Unsupported evidence (not UTF-8 text) is likewise rejected before any write, with &lt;code dir=&quot;auto&quot;&gt;UnsupportedEvidenceError&lt;/code&gt; surfacing as &lt;code dir=&quot;auto&quot;&gt;complete_failed&lt;/code&gt; (exit 1).&lt;/p&gt;
&lt;p&gt;Pre-mission records (invocations opened before this enforcement landed) have no &lt;code dir=&quot;auto&quot;&gt;mode_of_work&lt;/code&gt; field and are accepted by enforcement — legacy behaviour is preserved. See ADR-002-mode-derivation.md for the full derivation table and rationale.&lt;/p&gt;
&lt;h2 id=&quot;trail-tiers&quot;&gt;Trail Tiers&lt;/h2&gt;
&lt;h3 id=&quot;tier-1--every-invocation-mandatory&quot;&gt;Tier 1 — Every Invocation (mandatory)&lt;/h3&gt;
&lt;p&gt;Written unconditionally before the executor returns.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Storage&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;kitty-ops/{invocation_id}.jsonl&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Content&lt;/strong&gt;: Two JSONL lines — a &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event and (after completion) a &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;When&lt;/strong&gt;: All standalone &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; invocations.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;glossary-check-event-conditional-tier-1&quot;&gt;Glossary Check Event (conditional, Tier 1)&lt;/h3&gt;
&lt;p&gt;When the invocation executor’s glossary chokepoint scan detects at least one
conflict — or encounters an error — it appends a &lt;code dir=&quot;auto&quot;&gt;glossary_checked&lt;/code&gt; event to the
same Tier 1 JSONL file, immediately after the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Written ONLY when:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;all_conflicts&lt;/code&gt; is non-empty (one or more semantic conflicts detected), OR&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;error_msg&lt;/code&gt; is non-null (the chokepoint scan encountered an unexpected exception).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Clean invocations produce NO &lt;code dir=&quot;auto&quot;&gt;glossary_checked&lt;/code&gt; line.&lt;/strong&gt; This keeps Tier 1
files minimal when there are no glossary issues to report.&lt;/p&gt;
&lt;p&gt;Example &lt;code dir=&quot;auto&quot;&gt;glossary_checked&lt;/code&gt; event line:&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;json&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;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;event&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;glossary_checked&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;invocation_id&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;01HXYZ...&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;matched_urns&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: [&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;glossary:d93244e7&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;], &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;high_severity&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: [{&lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;term&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;lane&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;conflict_type&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;ambiguous_scope&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;severity&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;HIGH&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;candidate_senses&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: [&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;execution lane (WP routing)&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#C789D6;--1:#7C5686&quot;&gt;git branch lane (worktree)&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;]}], &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;all_conflicts&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: [&lt;/span&gt;&lt;span style=&quot;--0:#FFFFFF;--1:#984E4D&quot;&gt;...&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;], &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;tokens_checked&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;8&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;duration_ms&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;2.7&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&quot;error_msg&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#FF6A83;--1:#A24848&quot;&gt;null&lt;/span&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;p&gt;Readers that encounter &lt;code dir=&quot;auto&quot;&gt;&quot;event&quot;: &quot;glossary_checked&quot;&lt;/code&gt; and do not recognise this
event type may safely skip the line — it is additive metadata and never affects
the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; pair.&lt;/p&gt;
&lt;h3 id=&quot;correlation-links-tier-1-extension&quot;&gt;Correlation Links (Tier 1 extension)&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete&lt;/code&gt; accepts two additional flags that append correlation events to the invocation JSONL:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--artifact &amp;#x3C;path&gt;&lt;/code&gt; — repeatable. Each value appends one &lt;code dir=&quot;auto&quot;&gt;{event: &quot;artifact_link&quot;, invocation_id, kind, ref, at}&lt;/code&gt; line to &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;id&gt;.jsonl&lt;/code&gt;. Refs are stored repo-relative when the resolved path is under the checkout, absolute otherwise.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--commit &amp;#x3C;sha&gt;&lt;/code&gt; — singular. Appends one &lt;code dir=&quot;auto&quot;&gt;{event: &quot;commit_link&quot;, invocation_id, sha, at}&lt;/code&gt; line.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both events are append-only (never mutate existing lines) and readable by a single-file scan. Readers that do not recognise these event types may safely skip the line — the same additive-reader invariant that protects &lt;code dir=&quot;auto&quot;&gt;glossary_checked&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SaaS projection status&lt;/strong&gt;: Correlation events are &lt;strong&gt;local-only&lt;/strong&gt;. The projection policy (&lt;code dir=&quot;auto&quot;&gt;POLICY_TABLE&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/projection_policy.py&lt;/code&gt;) assigns &lt;code dir=&quot;auto&quot;&gt;project=True&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt; correlation events, but no SaaS client is registered (see &lt;a href=&quot;#saas-read-model-policy&quot;&gt;SaaS Read-Model Policy&lt;/a&gt;), so nothing leaves the checkout.&lt;/p&gt;
&lt;p&gt;See ADR-001-correlation-contract.md for the design; contracts/profile-invocation-complete.md for the CLI shape.&lt;/p&gt;
&lt;h3 id=&quot;tier-2--evidence-artifact-optional-caller-triggered&quot;&gt;Tier 2 — Evidence Artifact (optional, caller-triggered)&lt;/h3&gt;
&lt;p&gt;Created when the caller explicitly flags that the invocation produced checkable output.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Trigger&lt;/strong&gt;: Caller sets &lt;code dir=&quot;auto&quot;&gt;--evidence &amp;#x3C;path&gt;&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Storage&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/evidence/{invocation_id}/evidence.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/evidence/{invocation_id}/record.json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Format&lt;/strong&gt;: UTF-8 text only, checked before the &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event is recorded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;When&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt; modes only.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;tier-3--durable-project-state-optional-action-driven&quot;&gt;Tier 3 — Durable Project State (optional, action-driven)&lt;/h3&gt;
&lt;p&gt;Promotion to &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; or doctrine artifacts only when the invocation changes project-domain state.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Trigger&lt;/strong&gt;: Action is in &lt;code dir=&quot;auto&quot;&gt;TIER_3_ACTIONS&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;{specify, plan, tasks, merge, accept}&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Storage&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/{mission_slug}/&lt;/code&gt; — existing spec/plan/tasks/status files.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;When&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt; mode only.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;promotion-rules&quot;&gt;Promotion Rules&lt;/h3&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;Tier 1 always written&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;+-- If caller sets evidence_ref --&gt; Tier 2 artifact created&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;+-- If action in TIER_3_ACTIONS --&gt; Tier 3 artifacts produced by workflow&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h2 id=&quot;doctor-sweep-closures-and-the-archive-freeze-4397&quot;&gt;Doctor-Sweep Closures and the Archive Freeze (#4397)&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; is one of the four immutable archive roots under the
historical-preservation gate (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_archive_root_byte_identical.py&lt;/code&gt;):
a &lt;strong&gt;pre-existing&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;invocation_id&gt;.jsonl&lt;/code&gt; file may never be modified
— not on disk, not in the index, committed or not. An agent close appends its
&lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event to the per-record file and that is legal only because the
record was minted in the same session (new archive history, &lt;code dir=&quot;auto&quot;&gt;A&lt;/code&gt; status). The
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops --close-stale&lt;/code&gt; sweep closes Ops that are, by definition,
already committed — so recording the closure by mutating the per-record file
(and auto-committing it) reds the preservation gate.&lt;/p&gt;
&lt;p&gt;The resolved design (#4397, option “record closure on the append-only spine”):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Per-record &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;id&gt;.jsonl&lt;/code&gt; files are byte-frozen once committed.&lt;/strong&gt;
The sweep never touches them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sweep closures are recorded on a dedicated append-only spine,
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/op-closures.jsonl&lt;/code&gt;&lt;/strong&gt; — one v2 &lt;code dir=&quot;auto&quot;&gt;OpCompletedEvent&lt;/code&gt; JSON line per
closure (same frozen model as the per-record &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event, carrying
&lt;code dir=&quot;auto&quot;&gt;outcome=&quot;abandoned&quot;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;closed_by=&quot;doctor_sweep&quot;&lt;/code&gt;). The preservation gate
admits this one path the same way it admits &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt;:
a modification is legal only as a byte-prefix-preserving append whose new
rows parse as valid v2 completed events.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The close still goes through the canonical executor path&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;ProfileInvocationExecutor.complete_invocation&lt;/code&gt;, research R4): the spine
append &lt;em&gt;is&lt;/em&gt; that path’s write for a &lt;code dir=&quot;auto&quot;&gt;closed_by=&quot;doctor_sweep&quot;&lt;/code&gt; close, the
event is still submitted to the SaaS propagator, and the idempotent
already-closed guard now checks both the per-record file (concurrent manual
close) and the spine (concurrent sweep).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Open-Op detection reads both surfaces&lt;/strong&gt;: an Op is closed when its
per-record file carries a &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event OR the spine carries a closure
for its invocation id (&lt;code dir=&quot;auto&quot;&gt;list_orphan_ops&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The sweep covers every checkout of the repository&lt;/strong&gt; (#6661). Op records are
written in the checkout the command ran in (#6564), so &lt;code dir=&quot;auto&quot;&gt;doctor ops&lt;/code&gt; enumerates the
checkouts &lt;code dir=&quot;auto&quot;&gt;git worktree list --porcelain&lt;/code&gt; reports (one call per run, the same
enumeration Op custody uses) and reads each checkout’s own &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; and spine.
&lt;code dir=&quot;auto&quot;&gt;--close-stale&lt;/code&gt; closes each stale Op through an executor rooted in the checkout
that owns it, so a worktree’s closure is appended to — and auto-committed on —
that worktree’s branch, never the root checkout’s. The session-start/stop
reminder stays a single-checkout, git-free scan.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The sweep auto-commits only the spine&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;op(&amp;#x3C;profile&gt;): &amp;#x3C;action&gt; [&amp;#x3C;id8&gt;] (doctor sweep)&lt;/code&gt;). A refused commit (e.g. the protected-branch guard
on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;) is reported per entry in the sweep output and stated in the
command’s output: the closure stays on disk, uncommitted. A committed one is
visible only on branches that carry the commit. The agent close path is just
as visible: a refused per-record auto-commit is printed as a warning
(&lt;code dir=&quot;auto&quot;&gt;executor.last_op_commit&lt;/code&gt;) instead of dying in a &lt;code dir=&quot;auto&quot;&gt;logger.warning&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The auto-commit runs only where the repository tracks Op records (#6410).&lt;/strong&gt;
Both close paths commit onto the checked-out branch, so they are skipped
when:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the exact path being committed (the record, or the spine) matches an
ignore rule (&lt;code dir=&quot;auto&quot;&gt;git check-ignore --no-index&lt;/code&gt;), or&lt;/li&gt;
&lt;li&gt;the primary branch tracks no &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;ULID&gt;.jsonl&lt;/code&gt; record, locally or
on &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;. Special files such as &lt;code dir=&quot;auto&quot;&gt;ops-index.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lifecycle.jsonl&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;propagation-errors.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;op-closures.jsonl&lt;/code&gt; do not count.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The primary branch is &lt;code dir=&quot;auto&quot;&gt;origin/HEAD&lt;/code&gt;, else &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;master&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt;. It
is never the checked-out branch, so an earlier &lt;code dir=&quot;auto&quot;&gt;op(...)&lt;/code&gt; commit on an issue
branch cannot turn the commit back on. A skipped close keeps the record on
disk, where &lt;code dir=&quot;auto&quot;&gt;spec-kitty invocations list&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor ops&lt;/code&gt; find it. The
close output says so (&lt;code dir=&quot;auto&quot;&gt;OpCommitOutcome.skipped&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;skipped:&amp;#x3C;reason&gt;&lt;/code&gt; in
the sweep entry). An uncommitted spine can still block a checkout of a
branch that commits &lt;code dir=&quot;auto&quot;&gt;kitty-ops/op-closures.jsonl&lt;/code&gt;; move or commit it first. The decision lives in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/op_commit_policy.py&lt;/code&gt;. A repository that tracks
Op records, this one included, keeps the current-branch commit.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Rejected alternatives: letting the sweep mutate per-record files without
committing (still reds the gate, which compares the working tree against the
merge-base — and leaves closures non-durable), and narrowing the archive roots
themselves (weakens the preservation guarantee far beyond this surface).&lt;/p&gt;
&lt;h3 id=&quot;lifecycle-records-in-the-same-sweep-7346&quot;&gt;Lifecycle records in the same sweep (#7346)&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; writes WP lifecycle records, one file per record under
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&lt;/code&gt; (ADR 2026-11-01-2), and pairs a &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record only when
it reports a result. &lt;code dir=&quot;auto&quot;&gt;doctor ops --close-stale&lt;/code&gt; closes the rest:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every checkout is read first, the project root first. A record that several
checkouts hold (tracked on a shared branch) is closed at most once: never when
any checkout already holds its completion, otherwise once, in the first checkout
that holds it. The branches therefore never collect two completions for one
record when they meet. To tell which record a completion closed, the sweep pairs
an &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; record with the exact record its &lt;code dir=&quot;auto&quot;&gt;metadata.closes_started_at&lt;/code&gt;
names, any other completion with the latest record of its agent and work
package started before it, and a completion left over with the oldest remaining
record; pairing counts per group are unchanged.&lt;/li&gt;
&lt;li&gt;One older than &lt;code dir=&quot;auto&quot;&gt;--threshold&lt;/code&gt; (any, at &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt;) gets an &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt;&lt;/strong&gt; record in the
checkout that holds it: a new file, copying the action id, agent, Mission and
work package, with a reason that names the sweep, &lt;code dir=&quot;auto&quot;&gt;metadata.closed_by = doctor_sweep&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;metadata.closes_started_at&lt;/code&gt;. Pairing counts it as a completion. Nothing is rewritten, so the
preservation gate admits it as any other added &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; file.&lt;/li&gt;
&lt;li&gt;Each checkout’s closures are committed once (&lt;code dir=&quot;auto&quot;&gt;op(doctor): close N stale lifecycle record(s) (doctor sweep)&lt;/code&gt;) through the same executor commit as an Op
close, with the #6410 rules judged for lifecycle records: the commit is skipped
when the path is ignored or the primary branch tracks no
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ULID&gt;.json&lt;/code&gt; record. A protected-branch refusal is
reported and the closures stay on disk. &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; treats a root
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ULID&gt;.json&lt;/code&gt; file as bookkeeping, so a closure committed on
an approved lane branch does not count as a commit after the approval.&lt;/li&gt;
&lt;li&gt;Mission status, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and work package files are never touched.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; lists them under the additive &lt;code dir=&quot;auto&quot;&gt;lifecycle_records&lt;/code&gt; key; a fresh one left
open makes the command exit 1, as a fresh Op does.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;saas-read-model-policy&quot;&gt;SaaS Read-Model Policy&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;No SaaS projection path is live.&lt;/strong&gt; The invocation propagator (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/propagator.py&lt;/code&gt;) asks an adapter seam for a SaaS client, and no package registers one, so every call is a no-op (#3030, the hosted-consent incident whose fix removed the dead registration). The sync transport that once sat behind it was retired. Whoever registers a real transport owns the auth and admission gate that makes it safe, because the payload carries &lt;code dir=&quot;auto&quot;&gt;request_text&lt;/code&gt;, the verbatim agent prompt.&lt;/p&gt;
&lt;p&gt;The policy table below is what the propagator consults per &lt;code dir=&quot;auto&quot;&gt;(mode_of_work, event)&lt;/code&gt; once a client exists (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/projection_policy.py::POLICY_TABLE&lt;/code&gt;).&lt;/p&gt;











































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;mode_of_work&lt;/th&gt;&lt;th&gt;event&lt;/th&gt;&lt;th&gt;project&lt;/th&gt;&lt;th&gt;include_request_text&lt;/th&gt;&lt;th&gt;include_evidence_ref&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;task_execution&lt;/td&gt;&lt;td&gt;started&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;task_execution&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;task_execution&lt;/td&gt;&lt;td&gt;artifact_link&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;task_execution&lt;/td&gt;&lt;td&gt;commit_link&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;mission_step&lt;/td&gt;&lt;td&gt;started&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;mission_step&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;mission_step&lt;/td&gt;&lt;td&gt;artifact_link&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;mission_step&lt;/td&gt;&lt;td&gt;commit_link&lt;/td&gt;&lt;td&gt;yes&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;query&lt;/td&gt;&lt;td&gt;any&lt;/td&gt;&lt;td&gt;no&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Pre-mission records (no &lt;code dir=&quot;auto&quot;&gt;mode_of_work&lt;/code&gt;) project under the &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt; rules (the legacy behaviour, kept for them).&lt;/p&gt;
&lt;p&gt;Policy is additive and resolvable from code/config alone. See ADR-003-projection-policy.md for the rationale.&lt;/p&gt;
&lt;p&gt;Projection is additive. Events accumulate; there is no deletion, replay-based overwrite, or idempotency-key gating.&lt;/p&gt;
&lt;h2 id=&quot;tier-2-saas-projection--deferred&quot;&gt;Tier 2 SaaS Projection — Deferred&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Status&lt;/strong&gt;: Tier 2 evidence artifacts (&lt;code dir=&quot;auto&quot;&gt;.kittify/evidence/&amp;#x3C;invocation_id&gt;/evidence.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;record.json&lt;/code&gt;) are &lt;strong&gt;local-only&lt;/strong&gt;. They are not uploaded to SaaS. This decision was finalised by the Phase 4 closeout mission (ADR-004-tier2-saas-deferral.md).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reasoning&lt;/strong&gt;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The product has always behaved this way (since the 3.2.0a5 baseline); operators see local-only evidence.&lt;/li&gt;
&lt;li&gt;SaaS projection of evidence bodies requires privacy, redaction, and size-limit design that lies outside the Phase 4 closeout scope.&lt;/li&gt;
&lt;li&gt;Future projection remains possible without contract change — a later epic can read the existing local artifact and emit its own envelope.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Revisit trigger&lt;/strong&gt;: any of (a) a named future epic accepts SaaS evidence projection as scope, (b) operators actively request the feature with a concrete use case, (c) a regulatory or audit requirement mandates centralised retention.&lt;/p&gt;
&lt;h2 id=&quot;retention-and-redaction&quot;&gt;Retention and Redaction&lt;/h2&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Field&lt;/th&gt;&lt;th&gt;Treatment&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;request_text&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Retained as-written in local JSONL. No automatic redaction.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;governance_context_hash&lt;/code&gt;&lt;/td&gt;&lt;td&gt;First 16 hex chars of SHA-256 only. Full governance context is never persisted.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;JSONL files&lt;/td&gt;&lt;td&gt;Persist indefinitely unless the operator purges &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SaaS propagation&lt;/td&gt;&lt;td&gt;None live today. The policy is additive, with no delete-on-disable.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Propagation failures are written to &lt;code dir=&quot;auto&quot;&gt;kitty-ops/propagation-errors.jsonl&lt;/code&gt; and never affect the CLI exit code.&lt;/p&gt;
&lt;h2 id=&quot;spec-kitty-intake--not-a-profile-invocation&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty intake&lt;/code&gt; — Not a Profile Invocation&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty intake&lt;/code&gt; ingests a plan document into &lt;code dir=&quot;auto&quot;&gt;.kittify/mission-brief.md&lt;/code&gt; for use by &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; brief-intake mode. It is &lt;strong&gt;not&lt;/strong&gt; a standalone Op and produces no &lt;code dir=&quot;auto&quot;&gt;InvocationRecord&lt;/code&gt;. The governed trail begins when the host calls &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch &quot;&amp;#x3C;request&gt;&quot;&lt;/code&gt; — not when the user stages a brief.&lt;/p&gt;
&lt;h2 id=&quot;host-surfaces-that-teach-the-trail&quot;&gt;Host surfaces that teach the trail&lt;/h2&gt;
&lt;p&gt;The standalone dispatch surface is taught to host LLMs through per-host skill packs. See &lt;a href=&quot;/architecture/host-surface-parity/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/host-surface-parity.md&lt;/code&gt;&lt;/a&gt; for the authoritative matrix of supported hosts and each host’s parity status.&lt;/p&gt;
&lt;h2 id=&quot;spec-kitty-explain--deferred-to-phase-5&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty explain&lt;/code&gt; — Deferred to Phase 5&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty explain&lt;/code&gt; (issue #534) is not part of this release. It requires Phase 5 DRG glossary addressability to produce fully-cited answers. A partial implementation without glossary citations would be misleading.&lt;/p&gt;</content>
</entry>
