Skip to main content

Products

BuilderDesignerDiscoveryBusiness(Coming Soon)
DocsPricingGet Started

Dismiss audit findings as stale

Sometimes an audit raises findings you've decided not to act on: maybe they're false positives, maybe you've accepted the risk for this release, maybe a different change already addressed them and the next scan will confirm. Jorv Builder has three clean exits.

Path A — Triage individually via Brainstorm

Best for: a few specific findings, possibly genuinely real.

  1. Open the audit card on the Mission Board.
  2. Click Open in Orbit (per-finding or per-card).
  3. Discuss with Orbit. For each finding, agree on:
    • Promote to a fix card (Orbit handles it)
    • Dismiss with a reason (Orbit verifies via current code state)

When all findings are triaged, the card auto-closes to Done.

Path B — Dismiss all & close

Best for: "I'm not going to triage these one by one, accept the risk."

  1. Open the audit card detail.
  2. Click Dismiss all & close.
  3. Enter a reason (required). Examples:
    • "Accepting risk for v0.5 launch — revisit pre-v1.0"
    • "Policy: ignore stylistic findings on this codebase"
    • "All flagged code is in vendored dependencies we don't own"
  4. Confirm. Every open finding is set to ignored with that reason; the card auto-closes to Done.

The reason is stamped on every dismissed finding so future-you (or future-Orbit, on a re-run) can see why each was dismissed.

Path C — Run Scan

Best for: "I think these are stale because the code moved."

  1. Open the audit card detail OR the Compliance Center Dashboard.
  2. Click Run Scan (per-card) or check the expert + click Run selected (Dashboard).
  3. The expert re-runs against current code; the findings array is replaced with the new state.
  4. If the new scan finds nothing, the card auto-closes to Done.

What happens if I just try mark_feature_done?

The writer rejects it for audit cards with open findings. You'll see an error pointing you at the three paths above. This guardrail exists to prevent silent drift between the Mission Board and the Compliance Center — see Concept: Compliance Center.

Related