FEATURE-1755 — Task Detail
Nishad
FEATURE-1755
🔒 Locked by opus-4 · 2026-07-16 14:02
Sourcenishad
Created2026-07-14
Updated2026-07-16

Task Details

CompanyOm AI Solutions
ProductOm Cortex
Typefeature
PriorityHigh
Statusdesign-approval
Owneropus-1
Due—
Duration3d

Description

A1 — Org Operating Metadata + capability ledger.
  • Adds the org-metadata schema the Orchestration Engine reads at assignment time.
  • Feeds the model/wrapper identity + capability ledger (TECH-621 subsystem 6).
  • Prereq for the config-driven approver resolver (FEATURE-1739 REQ-02).
Rendered markdown — bold / bullets, not raw text (rev.8).

Attachments (2)

＋ Attach
  • 📄 PRD-1755.md 12 KB ⭳ 🗑
  • 🖼 diagram.png 84 KB ⭳ 🗑

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

[handoff] 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.
  • Awaiting Nishad's design-approval + visual sign-off.
[opus-4 · 2026-07-16 14:02] Locked for design-approval hand-up.
  • PRD-1755 rev.8 + diagram.png attached; capability-ledger schema settled.
  • FEATURE-1739 REQ-02 dependency flagged as a deploy-prereq.
[opus-1 · 2026-07-15 09:20] Cross-review pass — no blocking issues.
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. 1design✓ complete
    Required
    PRD
    Delivered
    PRDPRD-1755.mdReview⭳
  2. 2db-design✓ complete
    Required
    DB-DESIGN
    Delivered
    DBDB-DESIGN-1755.mdReview⭳
  3. 3design-review✓ complete
    Required
    REQ set
    Design sketch
    Delivered
    REQREQ-01.md · REQ-02.mdReview⭳
    Designscreen-3-task-detail.htmlReview⭳
  4. 4design-approval⛔ advance blocked — 1 required artifact missing
    Required
    PRD
    Design sketch
    MANIFEST.md — required, not delivered
    Delivered
    PRDPRD-1755.mdReview⭳
    Designscreen-3-task-detail.htmlReview⭳
    Advance-gate validator: ⛔ BLOCKED — MANIFEST.md is required at design-approval but was never delivered (DEV-1583 advance-gate). The human Approve below cannot advance the task until the required artifact is delivered — the missing item is named here loudly rather than failing silently.
  5. 5in-development → … → complete○ not started
    Required (upcoming)
    PLAN · TEST · Commits
    Delivered
    —not yet — produced once the DEV subtasks run
⛔ Human approval gate — advancing from design-approval requires an approver configured for this install.
On Approve: advances to in-development, recorded changed_by=<you>.
✔ Approve → in-development ↩ Send back… ✕ Close…
The action is recorded as you (Nishad) and is gate-scoped — it acts only at an approval-gate status you're configured to clear. If you are not a configured approver for this gate, these buttons are disabled with a plain reason ("you are not an approver for design-approval"). Send back / Close open a required reason field — an empty reason is rejected loudly.

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