DEV-1746 — Task Detail
Nishad
DEV-1746
⚪ Not locked — queued
Sourceopus-1
Created2026-07-27
Updated2026-07-29

Task Details

CompanyOm AI Solutions
ProductOm Cortex
Typedev
PriorityHigh
Statusqueued
Owneropus-2
Due—
Duration—

Description

resolver — the config-driven approver resolver (resolveApprover).
  • Reads Layer B (install_approver_policy ∩ install_human_identity) to answer "is this human an approver for this gate."
  • Single call shared by 1a's Needs-you count, 1b's Needs-You panel, the board's ▶ marker, and task-detail's gate banner — one resolver, no drift.
  • Depends on DEV-1745 (approver model) completing first — this is why it is currently queued.
Rendered markdown — bold / bullets, not raw text (rev.8).

Attachments (0)

＋ Attach
  • None yet — attaches once coding starts.

Artifacts

The SDLC documents + commits are shown per workflow step in Workflow Detail below — required vs delivered, with the advance-gate state. (Distinct from uploaded Attachments above.)

Task Notes

[created] Auto-created from FEATURE-1739 (delegated-approver) as the resolver sub-task.
  • Blocked on DEV-1745 (approver model) — cannot start design until the model it resolves against exists.
  • Feeds FEATURE-1739 REQ-02's resolveApprover, shared by 1a, 1b, board, and task-detail.
[opus-1 · 2026-07-29] Queued behind DEV-1745 — no action needed yet.
  • DEV-1747 (gate swap) is queued behind this task in turn — see the blocking-chain note in Workflow Detail below.
Single free-text tasks.notes field, rendered as markdown — fills the whole right column.

Workflow Detail

Every workflow step this task passed through — its REQUIRED artifacts vs what was actually DELIVERED, and the advance-gate state. A missing required artifact is named loudly (never a silent gap): the gate cannot clear until it is delivered. Each artifact opens to Review (inline) or Download.

  1. 1planning○ not started
    Required (upcoming)
    PLAN-01.md
    Delivered
    —not yet — starts once DEV-1745 (approver model) completes
  2. 2coding → … → complete○ not started
    Required (upcoming)
    PLAN · TEST · Commits
    Delivered
    —not yet
🔴 Blocking: DEV-1747 (gate swap) is queued behind this task — DEV-1747 cannot start until DEV-1746 (this resolver) is complete. You landed here because you clicked DEV-1747 on the board or in 1b's tree/Blocked panel (AC-S12): clicking a blocked task opens what is holding it up, not the blocked task itself.
No gate awaiting action — this task is queued, not yet at a human-approval step.
It becomes actionable once DEV-1745 completes and this task reaches its own approval gate.

What's on this screen

Built from: one task's full record — its core fields, its notes log, its SDLC documents and commits, and the approval gate blocking it, if any.

On screenWhere it comes fromWhat it means to you
Lock pill (🔒 Locked by … · timestamp)which agent currently has this task checked out, and since whenknow who's actively working it before you touch it
Source · Created · Updatedwho originally requested this task, and when it was opened and last touchedgauge how old or fresh the task is
Task Details fields (Company · Product · Type · Priority · Status · Owner · Due · Duration)this task's core recordsee what it is, who owns it, and how urgent it is, in one glance
Descriptionthe plain-English write-up of what this task is forunderstand the task without reading the underlying spec
Attachmentsfiles a person or agent uploaded to this taskreference material for the work, one click away
Workflow Detail (per step: Required vs Delivered artifacts + advance-gate state)for each workflow step, which artifacts that step requires vs which were delivered (PRD · REQ · PLAN · TEST · Design · Commits), and whether the advance gate passed or is blocked by a missing onesee exactly what each step owed and produced — and, if the task is stuck, the named missing artifact that's blocking it
Task Notesthe running, timestamped log every agent leaves as it works the taskread the real story of how the task got here, not just the current status
Human-approval gate banner (Approve · Send back · Close)your configured approval authority for this task's current statusthe one action needed to let the task move forward, or send it back with a reason