Ngenaire Docs
Log inSign up free

Project Inbox

The Project Inbox is a per-project triage queue of AI-generated findings about your project's health. Findings come from three sources — the Project Monitor, the Consistency Auditor, and inline Critique — and land here so you can decide, in one place, what to act on and what to dismiss.

Sidebar location: Track → Project Inbox (/projects/inbox).

What an inbox item contains

  • Kind — which source produced it (monitor, consistency, or critique).
  • Severity — info, low, medium, high, or critical.
  • Title — a one-line summary of the finding.
  • Body — the explanation, naming the source artifact.
  • Source — the artifact the finding is about (requirement, risk, SOW, diagram, and so on).
  • Status — open, resolved, or dismissed.

Walkthrough

  1. Open Track → Project Inbox. Items are listed newest first.
  2. Use the filters to focus by status, kind, or severity.
  3. Open an item to read the finding and see the source artifact it points to.
  4. Act on each item: resolve it once you have fixed the underlying issue, or dismiss it if the finding is wrong or not worth acting on.
  5. Run a scan on demand with Run monitor or Run consistency audit (see below). Repeated runs deduplicate against still-open findings, so the queue does not pile up duplicates.

The Project Monitor

A rule-based scan that posts findings of kind = monitor. It looks for:

  • Low requirement quality — requirements whose cached quality score is below the target.
  • Suspect trace links — links whose source requirement was edited after the link was created, so the downstream artifact may need re-review.
  • RVTM gaps — verification coverage below the project target.
  • Risk-trigger keywords — open issues whose text contains language often associated with unregistered risks.
  • Schedule slip — tasks past their planned finish date and still not complete.
  • Unverified critical/high requirements — high-priority requirements with no verification allocated.

The Consistency Auditor

A rule-based cross-artifact trace scan that posts findings of kind = consistency. It looks for:

  • SOW trace links — a statement of work not traced to any requirement.
  • UML flowdown — a diagram with no flowdown requirements declared.
  • CONOPS requirement references — a CONOPS document whose sections reference no requirement.
  • Risk-requirement linkage — a risk that should be linked to requirements but is not.

Inline Critique findings

The inline Critique panel on artifact edit pages produces a focused review of a single artifact. When you save a critique to the inbox, it lands here with kind = critique.

Tips

  • Run the monitor before a design review. A clean inbox is a good signal of artifact health.
  • Treat consistency findings as cheap wins. Most are one-line fixes — add a requirement reference, add a flowdown link.
  • Triage daily. Open findings accumulate quickly; a short daily pass keeps the queue honest.

Related