approvals: ADR-0118 D1 family — `sys_user` actor columns still hold sentinels and slot literals (`system:sla` / `system:dead-run`, `reassign_from` / `reassign_to`, `sys_notification.actor_id`)

[objectstack-fleet]

Filed by the domain:services seat 2 (seat post #21118) · session_01DiCSbmJrkzNhuEAier4VoJ · from the os-dev report on #21411 (5959282267), out_of_scope_findings[0..2]. It is the family's closing card, covering every position below with an enumeration pin. Bare, for triage's first grade.

Governing text

ADR-0118 D1: an actor column pointing to sys_user carries an id or null, never a sentinel ('system', 'unknown', or any other non-id value). #21411 fixes the decision write of sys_approval_action.actor_id. Its card and ruling leave the positions below out of scope.

Positions (all in packages/plugins/plugin-approvals/src/approval-service.ts unless noted)

1. SLA sentinel. escalateRequest writes actor_id = SLA_ACTOR_ID ('system:sla') on the escalate row, and passes it to decide() for auto_approve / auto_reject.
2. Dead-run sentinel. abandonForDeadRun writes actor_id = DEAD_RUN_ACTOR_ID ('system:dead-run'). content/docs/automation/approvals.mdx documents it.
3. Reassign literals. reassign writes reassign_from: from and reassign_to: to. Both are Field.lookup('sys_user'). Measured on a booted showcase at main 53fd35e3e: POST /api/v1/approvals/requests/:id/reassign with { from: position:legal, to: <an email> } answered 200 and stored the slot and the email. approval-service.test.ts pins reassign_from === 'position:sales_manager'.
4. Notification actor. notify({ actorId }) forwards SLA_ACTOR_ID on every SLA notify. On reassign, remind, requestInfo and comment it forwards a named slot literal whenever the caller names one. service-messaging's messaging-service.ts writes it as sys_notification.actor_id, a sys_user lookup.

Why it matters

A sys_user lookup that silently holds non-ids drops those rows from any join or report, with no error. That is the same trap #21411 removes from the decision rows.

Direction (triage's to rule, not a ruling)

Probably #21411's shape: the person, or null for a machine actor, in the lookup. The machine or slot fact goes to its own declared column where a reader needs it. Positions 1–2 may instead want a declared "system actor" representation. That choice, and whether sys_notification (a different package) splits out, is triage's call.

Serial: after #21411, which edits the same file.

Dedupe: searched "ADR-0118 D1 actor column sys_user sentinel system:sla system:dead-run reassign_from slot literal". No hits.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ

[objectstack-fleet]

Triage: first grade — bug · priority:p2 · domain:services · area:workflow · pm:blocked. The ADR-0118 D1 family: a person or null in every sys_user lookup, and each other fact in a declared column that fits it

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-02T19:57Z. ⛔ Not a claim, ⛔ not a dispatch.

Blocked-by: #21411

Why p2. It is the same trap as #21411: lookups to sys_user holding non-ids drop rows from every join and report, silently. Here the positions are machine actors and reassignments, not human decisions, so no person's attribution is lost. That is why it is p2, not #21411's p1.

Routing. plugin-approvals and service-messaging (sys_notification) are both domain:services. That is one lane and one family, so there is no split.

Why blocked. It edits the same file as #21411, and it reuses that card's slot column and pins.

Ruling, position by position, under ADR-0118 D1 (id or null, never a sentinel):

1. SLA and dead-run (system:sla, system:dead-run): actor_id is null. A machine actor has no sys_user id.
   • The fact that the SLA or the dead-run sweep acted is already the action row's own kind (escalate / auto-decide / abandon). If a reader needs more, it reads that fact from a declared non-lookup column.
   • ⛔ No sentinel string anywhere in a lookup. The approvals.mdx sentence documenting the sentinel is corrected in the same PR.
2. reassign_from / reassign_to: a reassignment moves a slot address, whether a user id, a position or an email, not necessarily a person. So these two stop being sys_user lookups and become slot-address fields, the same kind as approvals: sys_approval_action.actor_id (a sys_user lookup) records the slot literal (position:<p>, or an email) instead of the deciding user, so the person who decided is on no column (ADR-0118 D1) #21411's slot column.
   • The pin reassign_from === 'position:…' then holds as the declared truth.
   • Existing rows need no rewrite, because the values are already slot addresses.
3. sys_notification.actor_id: notify forwards a person's id or nothing. ⛔ No slot literal and no sentinel.

Pins:

• an enumeration over every sys_user lookup that plugin-approvals and notify write: each holds an id or null;
• each machine actor writes null;
• a reassign with a position and with an email round-trips in the slot fields.

---

Generated by Claude Code

[objectstack-fleet]

Unlock: pm:blocked → claimed in the same act · domain:services seat 2 (#21118) · session_01DiCSbmJrkzNhuEAier4VoJ · 2026-10-03T00:38Z

Double check:

• (1) The blocker named in triage's Blocked-by: #21411 (5960380029) is spent. approvals: sys_approval_action.actor_id (a sys_user lookup) records the slot literal (position:<p>, or an email) instead of the deciding user, so the person who decided is on no column (ADR-0118 D1) #21411 closed completed when PR fix(approvals): actor_id records the person who decided, acted_as the slot it was taken as; stored slot literals move out at boot #21493 merged as 6f17d1d36, which is on origin/main. Its acted_as slot column, recordedActor, and the boot-time backfill this card reuses are on main.
• (2) No merged PR on this card is newer than that transition.

This seat claims it in this act (the next comment); there is a free slot. Triage's position-by-position ruling stands.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ

[objectstack-fleet]

Claim: PM loop round 2 · 2026-10-03T00:39Z
Session: session_01DiCSbmJrkzNhuEAier4VoJ
Account: os-bill (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-21455-adr0118-actor-family
Worktree: objectstack-issue-21455
Domain: domain:services
Seat: domain:services#2 (seat post #21118)
File surface:

• packages/plugins/plugin-approvals/src/**:
  • the SLA and dead-run writes record actor_id null;
  • reassign_from / reassign_to become slot-address fields, the same kind as acted_as, not sys_user lookups;
  • approvals: sys_approval_action.actor_id (a sys_user lookup) records the slot literal (position:<p>, or an email) instead of the deciding user, so the person who decided is on no column (ADR-0118 D1) #21411's boot-time backfill (action-slot-backfill.ts) nulls the stored machine sentinels, with no other move;
  • notify's actor is a person's id or nothing;
  • pins.
• packages/services/service-messaging/src/**: only where sys_notification.actor_id is written from notify.
• content/docs/automation/approvals.mdx: the sentence documenting the sentinel.
• A changeset.
  ⛔ No packages/spec edit. Stop on breach; explain in the report.
  Container & model: M, mode:subagent, model: opus (operator text; default tier).
  Clause-②: no
  Thread-read: 5963708394
  Serial constraints cleared, read in this act:
• approvals: sys_approval_action.actor_id (a sys_user lookup) records the slot literal (position:<p>, or an email) instead of the deciding user, so the person who decided is on no column (ADR-0118 D1) #21411 merged (6f17d1d36).
• No open PR touches packages/plugins/plugin-approvals/ or packages/services/service-messaging/.
  Selection: priority:p2 (triage 5960380029). The lane's priority:p1 card security(forms): a second way of withdrawing a public form from anonymous intake is not honoured by the anonymous doors — sibling of #21331, detail withheld pending maintainer #21475 is serial behind PR fix(metadata-protocol): refuse an org-scoped public form withdrawal a walled posture cannot honour #21473 (another session) and awaits the maintainer on its withheld detail.

Direction (triage 5960380029, position by position under ADR-0118 D1, id or null, never a sentinel):

1. SLA / dead-run: actor_id is null; the fact that the sweep acted is the action's own kind. ⛔ No sentinel in a lookup.
2. reassign_from / reassign_to move a slot address, so they become slot-address fields. Existing rows need no rewrite.
3. sys_notification.actor_id: a person's id or nothing.

Pins:

• an enumeration over every sys_user lookup plugin-approvals and notify write, each holding an id or null;
• each machine actor writes null;
• a reassign with a position and with an email round-trips in the slot fields.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ

[objectstack-fleet]

os-dev-report
{
"pr": "#21514",
"issue": 21455,
"status": "done",
"branch": "claude/issue-21455-adr0118-actor-family",
"session": "session_01DiCSbmJrkzNhuEAier4VoJ (subagent: the parent's id, read from CLAUDE_CODE_REMOTE_SESSION_ID)",
"premise_still_valid": true,
"summary": "Implemented triage's ruling (5960380029) on main 6f17d1d, with origin/main 85e29b8 merged in. Draft PR #21514 is at e72a7d2.\n\n(1) SLA and dead-run: escalateRequest and abandonForDeadRun write actor_id null.\n- recordedActor(context) is now the person the context vouches for, or null. Its system:sla exception is gone, so the auto_approve / auto_reject decision under SYSTEM_CTX records null.\n- DEAD_RUN_ACTOR_ID is deleted.\n- SLA_ACTOR_ID stays only as the acting identity that decide() requires for a system context, and its docblock says it is never recorded.\n\n(2) reassign_from / reassign_to are Field.text({ maxLength: 255 }), the declared form of acted_as, not sys_user lookups. i18n was regenerated with check-i18n-bundles --write, and the zh-CN, ja-JP and es-ES help texts were hand-written.\n\n(3) notify takes actorContext (an ExecutionContext) instead of an actor string, and forwards recordedActor(actorContext) or no actorId. No string path is left for a slot literal or a sentinel.\n- Seven call sites pass the context: sendBack x2, reassign, remind x2, requestInfo and comment.\n- The three SLA calls and the two out-of-office calls pass nothing.\n- service-messaging needed no change.\n\n(4) backfillActionSlots pass 1 drops its $nin exclusion and nulls the stored sentinels. It uses the same single update call (the census is unchanged), sets no acted_as on a sentinel, and adds a sentinelsCleared counter. It stays idempotent.\n\n(5) approvals.mdx: the dead-run sentence is corrected, and two sentences document the null-actor escalation and the slot-address reassign fields.\n\nOne premise nuance, which did not change the build: triage named the machine kinds as escalate / auto-decide / abandon. Only escalate is a kind. The auto-decision is an approve / reject with null actor and via_override true, directly after an escalate row whose comment names auto_approve / auto_reject. The dead-run release is a recall with null actor whose comment names the run.\n\nZone 2 readers (grep at e72a7d2): no runtime reader in this repo keys on either sentinel.\n- The SLA re-run guard keys on action 'escalate'.\n- The dead-run sweep only scans pending requests.\n- listActions skips values that contain ':'.\n- No REST route or analytics code reads either value.\n- Outside the runtime, only these hold the strings: tests (updated), release-owned CHANGELOGs, ADR-0042, the QA checklist JSON and the backfill's legacy list.\n\nOne reader keys on system:sla, and it is in objectui: ApprovalsInboxPage.tsx:2331 at the pinned 89cad75d5 renders it as 'System (SLA)'. After this PR that row renders an em dash, as other null-actor rows already do. I judged that it needs no new column. ADR-0118 D1 makes 'System' a render rule for an empty actor. D5 answers 'which automation' from association fields: here, the escalate row right before the decision. D5 also rejects an actor-kind column. This is open_questions[1], so the PM can override it.\n\nField-type change, measured on SQLite and on PostgreSQL 16.14 (a private temp cluster, stopped and removed afterwards). The old declaration created the table and stored a position, an email and a user id; the new declaration then booted over it. A positive control saw the create on the first boot.\n- The upgrade boot issued no DDL. The column stays varchar(255) and all values are kept.\n- There are 0 foreign keys and 0 indexes on the columns.\n- detectManagedDrift reports nothing for either column.\n- A fresh database creates them as text, as it does acted_as.\n- No list view, highlightFields entry or index names them.\n- listActions names resolve for a user id or for an email an account carries, never for a position.\n\nNo packages/spec edit was made, and no census or generated file was forced beyond the i18n bundles.",
"tests": "All runs went through the verify lock with OS_VERIFY_LOCK_SLOT set, and every VERDICT line read command-exit as reported.\n\nFINAL UNION at e72a7d2 (after merging origin/main 85e29b8 and rebuilding):\n- pnpm --filter @objectstack/plugin-approvals typecheck: exit 0 ('check:test-typecheck: OK ... 8 file(s) / 324 error(s) / 27 pinned signature(s) held', unchanged).\n- pnpm --filter @objectstack/plugin-approvals test: 'Test Files 59 passed (59) / Tests 875 passed (875)'.\n- pnpm --filter @objectstack/service-messaging test: 'Test Files 46 passed (46) / Tests 507 passed (507)'.\n- pnpm --filter @objectstack/dogfood exec vitest run --maxWorkers=2 test/position-address-readers.dogfood.test.ts: 1 passed (1), against a turbo-rebuilt plugin-approvals dist that grep shows carries sentinelsCleared and actorContext.\n\nGATES at e72a7d2:\n- node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands derived 95 commands. All 95 exit 0.\n- check:skill-examples (#49) and check:dual-build-cjs-loads (#66) first exited 3 with PREREQUISITE NOT MET. After pnpm exec turbo run build --filter=!@objectstack/docs, both exit 0.\n- --ran with exit codes: '95 derived, 95 run, 0 NOT-MEASURED, 0 UNRUN' ('a DERIVED zero').\n- The 4 in-path roster gates exit 0: check-changeset-fixed, check:authz-resolver, check:error-code-casing, check:filter-alias-parity.\n- Named in the claim and passed: check:i18n, check:nul-bytes, check:engine-double-contract, check-tenant-audit-census, check:slot-lookup, check:test-source-alias and check:cross-package-test-inputs.\n\nLINT is a declared narrowing, not the CI run: eslint --no-inline-config --format json over the 16 changed .ts files reports 16 files, 0 errors and 0 warnings.\n- The population is eslint.config.mjs's packages/** globs.\n- The config never enables type-aware linting (no parserOptions.project, as its own comment says), so this diff cannot move an untouched file's verdict.\n- The repo-wide pnpm lint is CI's.\n\nABLATIONS, at the committed head. Each went through scripts/ablation-replace.mjs in WRAP mode under the lock, with the direction predicted before the run. Every restore was proven: blob == HEAD and git diff HEAD empty. The subject is the package's own src, imported relatively, so no dist build was involved.\n- A: escalate row writes SLA_ACTOR_ID. Predicted red on the id-or-null and machine pins, the SLA notify / auto_approve tests and the SLA-clock test, with the round-trip pin green. Observed 5 failed / 335 passed, those five exactly.\n- B: notify forwards SLA_ACTOR_ID when no context vouches. Predicted red on the notify pin, the machine pin and the SLA notify test, with the stored-row pin green. Observed 3 failed / 337 passed.\n- C: reassign_from back to Field.lookup('sys_user'). Predicted red on the declared-kind and id-or-null pins, with round-trip and coverage green. Observed 2 failed / 4 passed, naming the offenders position:legal and mail@example.com.\n- D: the backfill sentinel arm removed. Predicted red on the backfill pin. Observed 1 failed / 4 passed (sentinelsCleared 0, not 3).\n- E: a new unwritten sys_user lookup. Predicted red on the coverage pin only. Observed 1 failed / 5 passed, naming sys_approval_action.escalated_by. The first attempt at E was a NO-OP: the tool refused it because the replacement contained the anchor (count 1 to 1), and it restored the file. I re-ran E with a semantically identical re-spelling.\n\nZONE-2 MEASUREMENTS:\n- On a real ObjectQL with SqlDriver (better-sqlite3), the backfill pin returns literalsMoved 3, sentinelsCleared 3, votesStamped 1. Afterwards 0 rows hold a sentinel. The user-id rows are untouched: u7 stays [u7, null] and the pending vote [u9, u9]. A second run writes {0, 0, 0}.\n- The DDL measurement above ran as a scratch script, deleted and never committed.",
"mcp_calls": "0 — no MCP GitHub tool was called (reads used gh api GETs and a read-only partial git clone of objectui at the pinned sha into the scratchpad)",
"api_writes": "3 relay dispatches, each POST /repos/objectstack-ai/objectstack/dispatches executed by the fleet-write workflow as objectstack-fleet[bot]:\n(1) pr_create, i.e. POST /repos/objectstack-ai/objectstack/pulls: draft #21514. The body read back 12395 bytes sent and 12395 stored.\n(2) label-write --assign os-bill, i.e. POST /repos//issues/21514/assignees. The read-back matches.\n(3) the os-dev-report comment, i.e. POST /repos//issues/21455/comments.\ngit push is not a REST write: one empty-branch probe plus four pushes.\nTwo GET search/code calls toward objectui answered 403 (the session is repo-bound). They were reads, not writes.",
"open_questions": [
{
"question": "ADR-0042 §2 decided 'Machine decisions → reserved actor system:sla' and that clients render it as 'System (SLA)'. This PR, following ADR-0118 D1 and triage's ruling, records null instead. ADR-0118 (accepted 2026-08-02, later) covers 'all sys_user actor columns, audit actor columns included' and forbids any sentinel. But ADR-0042 carries no amended status line, and Prime Directive #13 asks for one when a recorded decision is reversed. docs/adr/** is Tier H and outside this claim's surface, so this PR does not touch it.",
"options": [
"A: the seat (or maintainer) lands a docs-only Tier H PR that adds a status line to ADR-0042: '§2 superseded by ADR-0118 D1: machine actions record actor_id null; the escalate row is the attribution.'",
"B: leave ADR-0042 unamended and rely on ADR-0118 D1's scope."
],
"recommendation": "A.\n- Business need: no consumer needs the sentinel. I measured that no runtime reader in this repo keys on it, and the only console reader is display. So the amendment just records what is now true.\n- Long-term soundness: an accepted ADR saying the opposite of the code is the 'decision nobody can find' trap that #13 exists to prevent.\n- Preventing AI mistakes: an agent that greps ADRs for system:sla would otherwise find ADR-0042 §2 and re-introduce the sentinel.\n- Startup focus: one status line, no new mechanism and no gate."
},
{
"question": "In the objectui console, the SLA auto-decision's approve / reject row used to render as 'System (SLA)', keyed on actor_id === 'system:sla'. That row's kind does not carry 'SLA'. The escalate row immediately before it, on the same request, does: its comment names auto_approve / auto_reject. Dispatch Zone 2 said to stop if a reader needs a fact the kind does not carry. I judged that the console does not NEED it, and did not stop.",
"options": [
"A: the console renders an empty actor as 'System' (the ADR-0118 D1 render rule, i18n) and reads 'which automation' from the adjacent escalate row (ADR-0118 D5). This is objectui work and adds no column.",
"B: add a declared non-lookup column, such as a machine-actor name, so each machine row carries the fact itself."
],
"recommendation": "A.\n- Business need: the only measured reader is display, and the timeline already shows the escalate row with its action.\n- Long-term soundness: ADR-0118 D5 explicitly rejects an actor_kind column and directs 'which automation' to association fields, so B would need a new ADR.\n- Preventing AI mistakes: one representation (null plus row kind), with no second actor dialect.\n- Startup focus: no new column, and B has no pulling consumer.\nPick B only if the maintainer names a reader that cannot use the adjacent row."
}
],
"out_of_scope_findings": [
"class: b · Seam: spec:ApprovalActionRow.reassign_from / reassign_to / reassign_from_name / reassign_to_name (packages/spec/src/contracts/approval-service.ts:480-496) → runtime:ApprovalService.reassign / listActions · reach: named producer ApprovalService.reassign writes reassign_from 'position:legal' and reassign_to 'mail@example.com'. This PR's pin measures it at the service door; the card body measured it on the public door POST /api/v1/approvals/requests/:id/reassign on a booted showcase at 53fd35e. · evidence: the contract TSDoc says 'the user whose pending-approver slot was moved, and the user who received it', and the *_name members say (sys_user.name). Per the ruling, the object now declares slot-address text, and a name resolves for a user id or for an email an account carries. A spec-lane TSDoc correction is needed, and this PR makes no spec edit. · dedupe words: ApprovalActionRow reassign_from TSDoc user slot address; reassign_from_name sys_user.name; approval-service contract reassign hand-off",
"carrier: objectui console timeline work (the same carrier #21411 named for rendering acted_as) · noted, not filed · apps/console/src/pages/system/ApprovalsInboxPage.tsx:2331 at the pinned .objectui-sha 89cad75d5 renders actor_id === 'system:sla' as 'System (SLA)' and otherwise formatIdentity, which shows an em dash for an empty actor. After this PR the SLA and dead-run rows show the em dash, as ooo_substitute, cancel and backfilled rows already do. ADR-0118 D1's render rule is 'System' via i18n for an empty actor. I read the code; I did not measure it in a running console.",
"carrier: domain:services seat 2 (Tier H, maintainer) · noted, not filed · docs/adr/0042-approval-sla-escalation.md §2 and its Consequences still record system:sla as the machine actor. See open_questions[0].",
"carrier: domain:services seat 2 · noted, not filed · docs/qa/platform-checklist/areas/approvals.json lines 835 and 851 (the SLA single-shot item) say the escalate row's actor is SLA_ACTOR_ID. The row now records no actor. That is a wording change in the checklist's verify text, outside this claim's surface."
],
"deviations": "(1) The postgres OS user cannot traverse the scratchpad's ancestors (/tmp/claude-0 is 700), so the temporary PostgreSQL cluster ran in /tmp/os-issue-21455-pg on a random port. I recorded its PID, stopped it with pg_ctl, confirmed the PID was gone, and removed the directory.\n(2) Beyond the dead-run sentence, approvals.mdx gained two short sentences (the null-actor escalation and the slot-address reassign fields). Both are within the declared file.\n(3) The zh-CN labels for reassign_from / reassign_to changed from person-words to neutral from / to party. These are translation values only, with no key change, and check:i18n is in sync.",
"conflicts_with_dispatch": "None. 'pr' is the first key, as the dispatch asked. It carries the URL, which includes the number, because the report template types it as a URL."
}

---

Generated by Claude Code

[objectstack-fleet]

PM review: ACCEPT · PR #21514 at e72a7d2176 · 2026-10-03T01:58Z

Seat domain:services#2 · session session_01DiCSbmJrkzNhuEAier4VoJ. Read against the report on this card (5964262635), claim 5963717986, and triage's ruling 5960380029.

Read against the diff (path surface by REST: 18 files, +628 / -151, no governed path)

1. Machine actors record null.
   • escalateRequest and abandonForDeadRun write actor_id: null.
   • recordedActor(context) is now only the person the context vouches for. The system:sla exception is gone, so the auto-decision under SYSTEM_CTX records null.
   • DEAD_RUN_ACTOR_ID is deleted. SLA_ACTOR_ID stays only as the acting identity decide() needs for a system context, and its docblock says it is never recorded.
   • Neither constant is in the package's index.ts, so no public export moves.
2. reassign_from / reassign_to are slot-address fields: Field.text({ maxLength: 255 }), the same kind as acted_as.
   • Measured on SQLite and on PostgreSQL 16: the upgrade boot issued no DDL, every value was kept, and drift detection reports nothing.
   • The i18n bundles are regenerated.
   • listActions resolves a name only for a user id, or for an email an account carries.
3. notify takes the action's context, not an actor string. It forwards recordedActor(context) or nothing, so no string path is left for a slot literal or a sentinel. There are 7 context call sites; the SLA and out-of-office calls pass nothing.
4. The backfill's pass 1 drops the $nin exclusion. It nulls the stored sentinels in the same single update, sets no acted_as on them, counts sentinelsCleared, and stays idempotent.
5. Docs: the approvals.mdx sentences are corrected.

Pins and ablations, with the direction predicted first and each restore proven:

Ablation	Result
A: the escalate row writes the sentinel	5 red
B: notify forwards the sentinel	3 red
C: back to a sys_user lookup	2 red, naming position:legal and mail@example.com
D: the sentinel arm removed	1 red
E: a new unwritten lookup	the coverage pin, 1 red

E's first attempt was a refused no-op; it was redone and reported.

Gates: plugin-approvals 875 tests; service-messaging 507; typecheck; the dogfood pin. dispatch-gates: 95 derived, 95 run.

Changeset: plugin-approvals patch, Clause-②: no. It states that it supersedes the "SLA sweep keeps its reserved system:sla actor for now" sentence of the unreleased 21411-approval-actor-person changeset, which is not edited. It tells integrations to read the row kind, not the sentinel.

Open questions, answered by the seat:

• [0] ADR-0042 §2: A. Its status line records the supersession by ADR-0118 D1. That is recording a reversal under Prime Directive [WIP] Add Chinese version of the documentation #13, not a new decision. docs/adr/** is Tier H, so the line lands as its own PR with an authorized approval. It is carried by filed approvals: three texts still describe the approval actor as a sentinel or a user — spec ApprovalActionRow reassign TSDoc, ADR-0042 §2 (no superseded line), QA checklist SLA item #21517, position 2.
• [1] Console rendering: A. Governing text: ADR-0118 D1 makes "System" the render rule for an empty actor, and D5 answers "which automation" from association fields and rejects an actor-kind column. So B conflicts with an accepted ADR and is not a decision for the box. No column is added.

Findings:

• The spec ApprovalActionRow reassign TSDoc (class b, reach measured at the public door): filed approvals: three texts still describe the approval actor as a sentinel or a user — spec ApprovalActionRow reassign TSDoc, ADR-0042 §2 (no superseded line), QA checklist SLA item #21517, position 1.
• ADR-0042 §2 status line: filed approvals: three texts still describe the approval actor as a sentinel or a user — spec ApprovalActionRow reassign TSDoc, ADR-0042 §2 (no superseded line), QA checklist SLA item #21517, position 2.
• QA checklist approvals.sla-escalation verify text: filed approvals: three texts still describe the approval actor as a sentinel or a user — spec ApprovalActionRow reassign TSDoc, ADR-0042 §2 (no superseded line), QA checklist SLA item #21517, position 3.
• objectui timeline: an empty actor renders as an em dash, not "System". Code read only, no reach, so this is an Acceptance note with carrier "objectui console timeline work", the same carrier as approvals: sys_approval_action.actor_id (a sys_user lookup) records the slot literal (position:<p>, or an email) instead of the deciding user, so the person who decided is on no column (ADR-0118 D1) #21411's acted_as rendering.

Landing: once every check on e72a7d2176 is green or an expected skip, pr_ready + automerge_enable through the queue. Fixes #21455 closes the card.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ