<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-07-19-1-wp-runtime-state-event-log-eviction-via-innerstatechanged/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-07-19-1-wp-runtime-state-event-log-eviction-via-innerstatechanged/</id>
  <title>ADR: Evict runtime-mutable WP state into the event log via a single generic InnerStateChanged annotation event</title>
  <updated>2026-07-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-07-19-1-wp-runtime-state-event-log-eviction-via-innerstatechanged/"/>
  <summary>One generic `InnerStateChanged` event carries a typed `WPInnerStateDelta`, folded per field by the reducer, bypassing transition validation and never touching `force_count`.</summary>
  <content type="html">&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-07-19&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Operator / HiC (Stijn Dejongh); four-lane research squad (2026-07-19); building on prior-art ADR &lt;code dir=&quot;auto&quot;&gt;wp-op-schema-design/docs/adr/3.x/2026-07-16-1-wp-runtime-state-authority-event-log-eviction.md&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2684&quot;&gt;#2684&lt;/a&gt; (P0) — the execution vehicle for the &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2093&quot;&gt;#2093&lt;/a&gt; authority ruling. Full grounding: &lt;code dir=&quot;auto&quot;&gt;docs/plans/investigations/2684-task-move-cluster-scoping.md&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt; (and the &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; subtask surface) is &lt;strong&gt;two authorities glued into one YAML
block&lt;/strong&gt;: static design-intent authored once, and runtime-mutable state written on every lifecycle
event. This split is load-bearing and actively harmful:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Runtime writes into the dossier-hashed files (&lt;code dir=&quot;auto&quot;&gt;dossier/indexer.py:242&lt;/code&gt; hashes both &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt;) churn &lt;code dir=&quot;auto&quot;&gt;content_hash_sha256&lt;/code&gt; on every transition → false drift (&lt;strong&gt;AC-5&lt;/strong&gt;).&lt;/li&gt;
&lt;li&gt;Subtask-completion truth lives in &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; markdown bytes (&lt;code dir=&quot;auto&quot;&gt;core/subtask_rows.py:39&lt;/code&gt;), which the
review gate (&lt;code dir=&quot;auto&quot;&gt;_guard_subtasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks_transition_core.py:384&lt;/code&gt;) and done-inference
(&lt;code dir=&quot;auto&quot;&gt;_infer_subtasks_complete&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status/emit.py:279&lt;/code&gt;) read — while the append-only event log, the
declared authority for lane/status, carries &lt;strong&gt;no subtask state at all&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;reducer.py:48-65&lt;/code&gt;). A WP
whose work is complete is refused &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; until an operator hand-ticks N
checkboxes (the merged P0 red test &lt;code dir=&quot;auto&quot;&gt;tests/regression/test_issue_2684_subtask_completion_event_sourced.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Claim-liveness reads &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt; from frontmatter (&lt;code dir=&quot;auto&quot;&gt;stale_detection.py:402-403&lt;/code&gt;); evicting it
naively corrupts the allocator.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The hard constraint: &lt;code dir=&quot;auto&quot;&gt;StatusEvent&lt;/code&gt; is a &lt;strong&gt;transition ledger&lt;/strong&gt; — it mandates &lt;code dir=&quot;auto&quot;&gt;from_lane&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;to_lane&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;status/models.py:248-249&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;validate_transition&lt;/code&gt; rejects any edge outside the 9-lane FSM
(&lt;code dir=&quot;auto&quot;&gt;wp_state.py:162,351&lt;/code&gt;). But three of the evicted mutations are &lt;strong&gt;off-axis&lt;/strong&gt; (no lane change):
(a) &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt; refresh on &lt;em&gt;resume&lt;/em&gt; of an already-&lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; WP, (b) mid-&lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; subtask
marks, (c) activity-log notes. They cannot be clean transition events. &lt;strong&gt;How off-axis runtime state
enters the append-only log is the decision everything else rests on.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One authority per datum&lt;/strong&gt; — runtime state has exactly one read path (the reduced snapshot); no
frontmatter field is ever read as authority; static fields are never mirrored into events.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Preserve every gate&lt;/strong&gt; — claim-liveness (AC-2), done-inference (AC-3), review gating — through the
cutover, not after it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AC-5 stable content hash&lt;/strong&gt; across a full lifecycle — the churn/false-drift fix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reusability&lt;/strong&gt; — prefer one extensible mechanism over per-field special cases.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No split-brain regression&lt;/strong&gt; — a generic sidecar must stay &lt;em&gt;typed&lt;/em&gt;, or it re-creates the very
ambiguity being removed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Writer ownership&lt;/strong&gt; — this mission &lt;strong&gt;owns&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;implement.py:1730&lt;/code&gt; shell_pid-writer restructuring
(the former #2160 co-sequence is resolved: #2160’s writer work is &lt;code dir=&quot;auto&quot;&gt;pr:deferred&lt;/code&gt; and yields to this
mission). Every new emit site must resolve its write target from stored topology, never &lt;code dir=&quot;auto&quot;&gt;Path.cwd()&lt;/code&gt;,
or it reopens #2647.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration safety&lt;/strong&gt; — readers keep a frontmatter fallback until backfill is verified (the “B3
clobber window”).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Option A — a non-transition annotation event class&lt;/strong&gt; in the same append-only log, distinguished
by the absence of &lt;code dir=&quot;auto&quot;&gt;from_lane&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;to_lane&lt;/code&gt;, bypassing &lt;code dir=&quot;auto&quot;&gt;validate_transition&lt;/code&gt;, folded by the reducer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option B — fold onto existing transitions + &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt;.&lt;/strong&gt; Carry &lt;code dir=&quot;auto&quot;&gt;(shell_pid, baseline)&lt;/code&gt; on
the next real transition; no FSM/reducer change.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option C — self-edges (&lt;code dir=&quot;auto&quot;&gt;X→X&lt;/code&gt;) legalised in the FSM matrix.&lt;/strong&gt; (Weighed and rejected in the
prior-art ADR: redefines the “a transition changes lane” invariant; ripples into rendering, drift,
done-inference; zero capture benefit over A.)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: Option A, realised as a &lt;em&gt;single generic&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt; event carrying a typed
partial delta.&lt;/strong&gt; Rather than per-kind annotation variants, there is &lt;strong&gt;one&lt;/strong&gt; off-axis event whose
payload is a &lt;strong&gt;typed&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;WPInnerStateDelta&lt;/code&gt; (optional typed fields — &lt;em&gt;not&lt;/em&gt; a free &lt;code dir=&quot;auto&quot;&gt;dict[str, Any]&lt;/code&gt;),
folded by the reducer with a per-field merge rule and &lt;strong&gt;no &lt;code dir=&quot;auto&quot;&gt;force_count&lt;/code&gt; increment&lt;/strong&gt;. This is the
reusable realisation of the annotation class and it is what gives the reduced snapshot the
gate-queryable projection the subtask gates need.&lt;/p&gt;
&lt;p&gt;The seven cluster decisions (HiC, 2026-07-19) that this ADR ratifies:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Off-axis events → Option A as one generic &lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt; event&lt;/strong&gt; with a typed delta,
bypassing &lt;code dir=&quot;auto&quot;&gt;validate_transition&lt;/code&gt;, reducer-folded, no &lt;code dir=&quot;auto&quot;&gt;force_count&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Subtask granularity → subsumed by the delta&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;subtasks: Mapping[str, Status]&lt;/code&gt;) — a single mark
and a batch mark are the same event; the same generic event also carries the PID refresh.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activity notes → a &lt;code dir=&quot;auto&quot;&gt;note&lt;/code&gt; delta field with append semantics&lt;/strong&gt; (reducer keeps a &lt;code dir=&quot;auto&quot;&gt;notes&lt;/code&gt; list;
AC-4 renders the Activity Log from it). One event class for pid + subtasks + notes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;tracker_refs&lt;/code&gt; → evict&lt;/strong&gt; (runtime, event-sourced): &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; emit an
&lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt; delta with &lt;strong&gt;union/append&lt;/strong&gt; merge; FR-011 runtime append preserved.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review-cycle → evict all in this mission&lt;/strong&gt;: delete the dead verdict-field read fallbacks
(&lt;code dir=&quot;auto&quot;&gt;workflow_cores.py:340-341&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;done_bookkeeping.py:104-105&lt;/code&gt;) &lt;strong&gt;and&lt;/strong&gt; evict the actively-written
&lt;code dir=&quot;auto&quot;&gt;review_artifact_override_*&lt;/code&gt;. &lt;strong&gt;#2684 is the authoritative owner of the WP-metadata surface;&lt;/strong&gt;
deferred PRs (#2641, #2766, #2612, and #2160’s writer work) yield to the mission and rebase onto
it — their file-collision risk is moot. Consequently this mission &lt;strong&gt;owns&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;implement.py:1730&lt;/code&gt;
shell_pid-writer restructuring outright (no external co-sequence gate).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Static-model election → deferred&lt;/strong&gt; to a follow-up (blocker B4: &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; cannot become a
clean static-only projection until its runtime half is stripped; coordinates with #1619).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;progress&lt;/code&gt; field → retired explicitly&lt;/strong&gt; (removed from &lt;code dir=&quot;auto&quot;&gt;MUTABLE_FIELDS&lt;/code&gt;/schema; backfill no-op).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The initial claim’s &lt;code dir=&quot;auto&quot;&gt;(shell_pid, baseline)&lt;/code&gt; still rides the &lt;strong&gt;real&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;planned→claimed&lt;/code&gt; transition via
the existing generic &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt; sidecar (&lt;code dir=&quot;auto&quot;&gt;status/models.py:258&lt;/code&gt;) — no wire-schema change there;
only the resume/mid-work/notes mutations use &lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The append-only log becomes a &lt;strong&gt;true SSOT&lt;/strong&gt; for all off-axis runtime state; the reduced snapshot
gains typed slots (&lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;shell_pid_created_at&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;subtasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;notes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tracker_refs&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; become &lt;strong&gt;static design-intent only&lt;/strong&gt; → stable content hash (AC-5),
the long-homeless dossier/sync churn fix.&lt;/li&gt;
&lt;li&gt;Re-pointing &lt;code dir=&quot;auto&quot;&gt;_guard_subtasks&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;_infer_subtasks_complete&lt;/code&gt; at the snapshot turns the merged P0
red test green (AC-3) and removes the manual N-tick friction.&lt;/li&gt;
&lt;li&gt;One extensible event + typed delta: future runtime fields ride free without new event kinds.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Highest-blast-radius option: touches the FSM authority (a sanctioned self-edge / &lt;code dir=&quot;auto&quot;&gt;annotate()&lt;/code&gt;
primitive), the wire model (an event discriminator round-tripped in &lt;code dir=&quot;auto&quot;&gt;to_dict&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;from_dict&lt;/code&gt;), and the
reducer precedence core (fold-after-transition, last-writer-wins per field).&lt;/li&gt;
&lt;li&gt;Adds a reducer fold on the hot path (additive, but real).&lt;/li&gt;
&lt;li&gt;Requires disciplined migration ordering (backfill → verify → reader → writer → delete fallbacks) to
keep the B3 clobber window closed.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;WPInnerStateDelta&lt;/code&gt; is generic in shape but typed per field — deliberately not a free bag.&lt;/li&gt;
&lt;li&gt;The static-model election (enrich &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; vs elect &lt;code dir=&quot;auto&quot;&gt;WorkPackageEntry&lt;/code&gt;) is unblocked by this
work but intentionally out of scope.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;AC-1&lt;/strong&gt; no &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;/review action writes &lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AC-2&lt;/strong&gt; claim-liveness resolves from the snapshot; a claimed WP with empty frontmatter is live.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AC-3&lt;/strong&gt; done-inference resolves from &lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt; subtask deltas — the &lt;strong&gt;merged red test
&lt;code dir=&quot;auto&quot;&gt;test_issue_2684_subtask_completion_event_sourced.py&lt;/code&gt; flips green&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AC-4&lt;/strong&gt; Activity Log / History / review sections render from events with no content loss.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AC-5&lt;/strong&gt; a full lifecycle produces a &lt;strong&gt;stable content hash&lt;/strong&gt; (headline proof).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AC-6&lt;/strong&gt; migration backfills idempotently (deterministic namespaced ULID seed-ids), with an honest
timestamp-reconstruction contract for checkbox marks (clamp to &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;refactor-stable architectural test&lt;/strong&gt; asserts no consumer reads a dynamic frontmatter field as
authority (the #2093 invariant, generalising the shipped phase-2 lane-authority guard).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;option-a--generic-innerstatechanged-annotation-event-chosen&quot;&gt;Option A — generic &lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt; annotation event (chosen)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; true SSOT for (a)+(b)+(c); delivers the subtask projection the gates need; one reusable,
extensible mechanism; typed delta avoids a new split-brain.
&lt;strong&gt;Cons:&lt;/strong&gt; touches FSM + wire model + reducer precedence; additive hot-path fold; migration discipline.&lt;/p&gt;
&lt;h3 id=&quot;option-b--fold-onto-transitions--policy_metadata&quot;&gt;Option B — fold onto transitions + &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; near-zero FSM/reducer change.
&lt;strong&gt;Cons:&lt;/strong&gt; complete only for &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;; resume emits nothing → stale PID → claim-liveness degrades to
the git-timestamp heuristic (a false-stale window on the exact path AC-2 protects); subtasks and notes
still need a home; gate re-sourcing is &lt;em&gt;still&lt;/em&gt; required. &lt;strong&gt;Rejected&lt;/strong&gt; — partial SSOT for more net work.&lt;/p&gt;
&lt;h3 id=&quot;option-c--self-edges-in-the-fsm-matrix&quot;&gt;Option C — self-edges in the FSM matrix&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; reuses the transition path.
&lt;strong&gt;Cons:&lt;/strong&gt; redefines the “a transition changes lane” invariant; ripples into rendering, drift, and
done-inference for no capture benefit over A. &lt;strong&gt;Rejected.&lt;/strong&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;addendum-2026-07-20-per-field-authority-for-a-wps-runtime-identity--resolves-blocker-b4&quot;&gt;Addendum (2026-07-20): Per-field authority for a WP’s runtime identity — resolves blocker B4&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted · &lt;strong&gt;Date:&lt;/strong&gt; 2026-07-20 · &lt;strong&gt;Deciders:&lt;/strong&gt; Operator / HiC (Stijn Dejongh);
architect (mission &lt;code dir=&quot;auto&quot;&gt;runtime-state-corpus-cutover&lt;/code&gt;, &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2816&quot;&gt;#2816&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Extends:&lt;/strong&gt; Decision 6 (Decision Outcome, above) — the &lt;em&gt;static-model election&lt;/em&gt; it &lt;strong&gt;deferred as
blocker B4&lt;/strong&gt;. &lt;strong&gt;Requirement:&lt;/strong&gt; FR-013. &lt;strong&gt;Constraint gate:&lt;/strong&gt; C-009 (this addendum is the ADR of record
that C-009 requires &lt;strong&gt;before&lt;/strong&gt; the IC-08 event vocabulary lands — WP09 is gated on it). &lt;strong&gt;Lineage:&lt;/strong&gt;
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2093&quot;&gt;#2093&lt;/a&gt; (canonical-authority ruling) →
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2400&quot;&gt;#2400&lt;/a&gt; (WP-metadata half) → #2816;
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2399&quot;&gt;#2399&lt;/a&gt; owns the full fail-closed &lt;em&gt;enforcement&lt;/em&gt;
and stays &lt;strong&gt;out of scope&lt;/strong&gt; here (this ruling records &lt;strong&gt;record + reconstruct&lt;/strong&gt; only).&lt;/p&gt;
&lt;h3 id=&quot;context--why-blocker-b4-is-now-actionable-and-why-it-grew&quot;&gt;Context — why blocker B4 is now actionable, and why it grew&lt;/h3&gt;
&lt;p&gt;Decision 6 deferred the static-model election because “&lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; cannot become a clean static-only
projection until its runtime half is stripped.” The #2816 corpus cutover (WP01–WP07) strips that
runtime half: the runtime-mutable fields leave &lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt; frontmatter and become event-sourced.
B4 is therefore now decidable.&lt;/p&gt;
&lt;p&gt;Deciding it surfaced a finding that reframes the original “elect the static model” question. A WP does
not carry &lt;em&gt;one&lt;/em&gt; identity that is either static or dynamic — it carries &lt;strong&gt;two distinct
representations&lt;/strong&gt; of &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt;, and the earlier framing risked collapsing them:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;authored recommendation&lt;/strong&gt; — who/what a WP was &lt;em&gt;designed&lt;/em&gt; to be run by, authored once at
tasks-finalize. This is fixed for the life of the WP.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;resolved actual&lt;/strong&gt; — who/what &lt;em&gt;actually&lt;/em&gt; resolved and ran the WP at a given lifecycle
transition. This &lt;strong&gt;shifts&lt;/strong&gt; across the lifecycle: an implementer profile on model A claims the WP; a
reviewer profile on model B picks it up for review; a model can be swapped mid-cycle. A single static
value is therefore &lt;strong&gt;wrong mid-cycle&lt;/strong&gt; — only the event log’s latest-actual reduction is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Electing a static model (or a static profile/role) as &lt;em&gt;the&lt;/em&gt; identity would re-manufacture the very
split-brain #2093 forbids: a consumer reading the static value would report the wrong actor for any WP
past its first pick-up. B4 is resolved not by “make the model static” but by &lt;strong&gt;ratifying a per-field
authority that keeps authored intent and resolved actual as separate, single-authority data.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;decision--per-field-authority-unambiguous-per-field&quot;&gt;Decision — per-field authority (unambiguous, per field)&lt;/h3&gt;
&lt;p&gt;For each of &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; (+ &lt;code dir=&quot;auto&quot;&gt;agent_profile_version&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;provider&lt;/code&gt;, the two
representations have &lt;strong&gt;different, single canonical authorities&lt;/strong&gt;:&lt;/p&gt;






























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Field&lt;/th&gt;&lt;th&gt;Authored / recommended (static)&lt;/th&gt;&lt;th&gt;Resolved / actual (dynamic)&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;role&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;frontmatter-canonical&lt;/strong&gt; — authored once at tasks-finalize&lt;/td&gt;&lt;td&gt;&lt;strong&gt;event-log / snapshot-authoritative&lt;/strong&gt; — folded latest-wins at each pick-up/claim/reassign&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; (+&lt;code dir=&quot;auto&quot;&gt;agent_profile_version&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;frontmatter-canonical&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;event-log / snapshot-authoritative&lt;/strong&gt;, latest-wins&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;frontmatter-canonical&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;event-log / snapshot-authoritative&lt;/strong&gt;, latest-wins&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;provider&lt;/code&gt;&lt;/td&gt;&lt;td&gt;(no authored form)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;event-log / snapshot-authoritative&lt;/strong&gt;, latest-wins&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Read plainly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;resolved actual&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;(+version)/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;provider&lt;/code&gt; are &lt;strong&gt;dynamic →
event-log/snapshot-authoritative&lt;/strong&gt;. They are recorded on the append-only log at each
&lt;strong&gt;pick-up/claim/reassign&lt;/strong&gt; transition and folded &lt;strong&gt;latest-wins&lt;/strong&gt; into the reduced snapshot. The
snapshot is their sole read authority — no consumer reads them from frontmatter.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;authored recommendation&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; are &lt;strong&gt;static →
frontmatter-canonical&lt;/strong&gt;. They are authored once at tasks-finalize and never mirrored into events.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This mirrors the two-column authority table in the mission data-model (&lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt;, “Resolved
runtime identity (event-sourced) vs authored recommendation (frontmatter)”) so that no field’s
authority is left implicit. It is the concrete, per-field realisation of Decision Driver
&lt;strong&gt;“one authority per datum”&lt;/strong&gt; for the identity fields specifically.&lt;/p&gt;
&lt;h3 id=&quot;binding-constraints-of-the-ruling&quot;&gt;Binding constraints of the ruling&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;C-007 — the recorded resolved value MUST come from the resolver, never a frontmatter copy.&lt;/strong&gt; The
recorded resolved &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; MUST be produced by &lt;code dir=&quot;auto&quot;&gt;resolve_profile&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;resolved_agent()&lt;/code&gt; / the dispatch resolution. Copying the static frontmatter &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; string
into an event is &lt;strong&gt;forbidden&lt;/strong&gt; — it manufactures a &lt;em&gt;new&lt;/em&gt; split-brain (the exact #2093 anti-pattern:
static design-intent masquerading as recorded runtime truth). Where a genuine resolved value is
unavailable on a given path (e.g. no dispatch-resolved model), it is recorded &lt;strong&gt;explicitly absent&lt;/strong&gt;,
never fabricated or frontmatter-coerced.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C-008 — authored intent and resolved actual are never conflated.&lt;/strong&gt; Every WP-view consumer surfaces
the frontmatter &lt;strong&gt;authored recommendation&lt;/strong&gt; and the event-sourced &lt;strong&gt;resolved actual&lt;/strong&gt; as &lt;strong&gt;distinct&lt;/strong&gt;
values. No consumer treats the authored value as “what ran”, nor the resolved value as “what was
intended”. A WP with no resolved-binding events shows the authored recommendation and an &lt;strong&gt;empty&lt;/strong&gt;
resolved actual — never the authored value masquerading as resolved. The single reconstruction reader
(&lt;code dir=&quot;auto&quot;&gt;reconstruct_wp_view&lt;/code&gt;, IC-07) is the &lt;strong&gt;one&lt;/strong&gt; assembly point that joins the snapshot’s resolved
fields with frontmatter’s authored fields, distinctly labelled.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;ratification--the-role-reversal&quot;&gt;Ratification — the &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; reversal&lt;/h3&gt;
&lt;p&gt;An interim note had kept &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; as a frontmatter-only field (“keep role frontmatter”). The #2093
ruling text lists &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; among the &lt;em&gt;dynamic&lt;/em&gt; fields. &lt;strong&gt;This addendum ratifies the reversal:&lt;/strong&gt; the
&lt;strong&gt;authored&lt;/strong&gt; role recommendation stays frontmatter-canonical, but the &lt;strong&gt;actual&lt;/strong&gt; role that ran a WP is
&lt;strong&gt;event-sourced&lt;/strong&gt; (dynamic, latest-wins) — exactly like &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; is not an
exception to the per-field rule above; it follows it. The interim “keep role frontmatter” note is
&lt;strong&gt;superseded&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;scope-and-lineage&quot;&gt;Scope and lineage&lt;/h3&gt;
&lt;p&gt;This ruling records the &lt;strong&gt;resolved-binding “record + reconstruct” slice&lt;/strong&gt; of #2093 plus the
WP-metadata half of #2400. It does &lt;strong&gt;not&lt;/strong&gt; ratify the full fail-closed &lt;em&gt;enforcement&lt;/em&gt; of #2399 (an agent
being unable to act without a resolved+recorded profile, across ops/dispatch/ad-hoc/mission-WP) — that
stays out of scope and #2399 remains open for it. Recording a per-field canonical-authority ruling as
an ADR follows the #2093 precedent: a canonical-authority decision is a system-design decision, not an
implementation detail.&lt;/p&gt;
&lt;h3 id=&quot;consequences-1&quot;&gt;Consequences&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Positive&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Blocker B4 is resolved: the identity fields have an unambiguous, per-field authority, so the event
vocabulary (IC-08), the reconstruction reader (IC-07), and the SaaS &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt; delivery (IC-09) can be
built against a ratified contract rather than an open question.&lt;/li&gt;
&lt;li&gt;The reduced snapshot becomes the single read authority for “who/what is &lt;em&gt;actually&lt;/em&gt; running this WP”,
correct at every lifecycle stage — the dashboard, the &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; board, and &lt;code dir=&quot;auto&quot;&gt;WorkPackage&lt;/code&gt;
can converge on one reconstruction reader.&lt;/li&gt;
&lt;li&gt;The split-brain #2093 forbids is closed for the identity fields, not merely for lane/status.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Negative&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The WP view must now always join two sources (snapshot + frontmatter); a consumer that reads only one
is, by construction, wrong. The single reconstruction reader (IC-07) is the mitigation, and the
extended #2093 architectural detector guards against a reader that reaches back into frontmatter for a
resolved field.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Neutral&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;This addendum is the &lt;strong&gt;gate&lt;/strong&gt;, authored &lt;strong&gt;before&lt;/strong&gt; the IC-08 vocabulary and the IC-07 reader exist;
it presupposes neither. It records the ruling; WP09/WP10 implement it.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
