FEATURE-1755 — History
Nishad
FEATURE-1755
History — the raw chronological event log (AC-D8: organised by TIME, not by step)
← Close, back to Task Detail

Timestamps below are rendered in your timezone (EDT) — not server-local, per the ratified day rule.

🔶 Showing status changes and gate decisions only. Field edits and notes written between transitions are not yet recorded as events anywhere in the schema (gap G9) — they are depicted below as the intended end state, greyed, so this view never silently implies more happened than it can actually show. An audit log that omits event types without saying so is worse than one that admits its scope.
Jul 16, 2:02 PM
EDT
Opus (om-cortex owner) status change via task-service · 4m
coding→design-approval

Locked for design-approval hand-up.

  • PRD-1755 rev.8 + diagram.png attached; skill-ledger schema settled.
  • FEATURE-1739 REQ-02 dependency flagged as a deploy-prereq.
Jul 15, 9:20 AM
EDT
Opus (reviewer) gate decision design-review · 22m
design-review→coding

Cross-review pass — no blocking issues.

Jul 14, 6:40 PM
EDT
Nishad field edit
Priority: Medium→High

Illustrative end state — field edits are not recorded as events today (gap G9).

Jul 14, 4:52 PM
EDT
Opus (om-cortex owner) note added

Illustrative end state — a note written between transitions produces no event row today (gap G9).

Jul 14, 4:45 PM
EDT
Opus (om-cortex owner) status change via task-service
created→design-review

Design finalized against QUORUM-1742 om-cortex layout.

  • Screens 1a/1b reconciled to the finalized dashboard sketches.
  • Approver store restructured to Layer B feeding the one resolveApprover.

What's on this screen

Built from: this task's transition history, grouped by time (not by step — that's Workflow Detail's job, AC-D8's anti-drift rule). (Outcome sketch — a STATE of Screen 3, not a new registry screen.)

On screenWhere it comes fromWhat it means to you
Timestamp (customer timezone)task_status_history.created_at, rendered in your timezone not server-localread the timeline the way you experienced it, not the server's clock
Actor (friendly name)the friendly-name register over changed_by — never a raw instance idan internal id reaching this surface would be a leak, not a cosmetic slip
Event type chip (status / gate / edit / note)status + gate: task_status_history + workflow_template.step_kind; edit/note: gap G9, unbuilttells you at a glance what kind of thing happened, honestly scoped to what's actually recorded
Note snippettask_status_history.notes, block-markdown renderedthe real story behind the transition, not a run-on wall of text
Enrichment (via / duration)agent_role, agent_tool, duration_minutes — already on the table, free enrichmenta little more context on how and how long, at no extra read cost