watchdep
Sign inSource
Docs / Concepts / 07

Decisions and a finding's life

Section
Concepts
Page
07 of 16
Reading time
5 min
Read next
Alerts

A finding is one advisory affecting one application, across every part, file, path and version it touches. It is kept until production no longer has it or a person decides it, and every change to it, by a person, a tool or watchdep itself, is written to a log that can never be edited.

States

State Meaning
new First seen, or reopened.
acknowledged A person has seen it and it is being dealt with.
fix pull request open A pull request with the fix is waiting for a person to merge it.
fix merged, not yet in production The fix is merged, but production does not have it yet.
fixed Production has no affected place left.
accepted A person accepted the risk until a date.
not affected A person said the application is not affected, with a reason.
withdrawn Every advisory behind the finding was withdrawn by its source.

Open means new, acknowledged, or one of the two pull request states. Decided means fixed, accepted, not affected or withdrawn. The “Open across all apps” and “Decided” views in the explorer follow these words.

Decisions

Decision Allowed from Needs Becomes
Acknowledge new nothing acknowledged
Accept the risk until a date new, acknowledged, either pull request state a reason, and a date after today and at most a year away accepted
Mark not affected new, acknowledged, either pull request state, accepted a reason not affected
  • Not affected keeps the evidence. When a code check has run, its latest verdict, reason and evidence are kept with the decision in the log. See The code check.
  • An acceptance ends at the start of its date (the 00:15 UTC run): “accepted until 20 November” reopens as new on 20 November, with a log entry by the system. Silence never extends a decision; to keep accepting, a person accepts again.
  • All or nothing. The decision, the places it covers, the state change and the log entry are written together; if any of them fails, nothing changes.
  • Keyboard: on a finding’s page, a acknowledges, n opens not affected and r opens accept, for people who may decide, and never while typing.

Who may decide

Role Read Decide findings
owner yes yes
admin yes yes
member yes yes
viewer yes no

A viewer sees no decision controls, and a decision posted anyway is refused. Two other ways in follow the same rules:

  • A host application (for example Prospec360 showing findings to its own people) decides through a workspace API token that may write decisions, always naming the person. When the email matches a member, that member’s role applies, so a viewer named by a host cannot decide. A person with no watchdep account may decide this way: the host vouches for its own people. See the API.
  • An agent (Claude Code or any MCP client) acts as the person who connected it, with their role, and may decide only if they ticked “decide” when connecting. A viewer’s agent is refused even with it ticked. See Agents.

When production changes

Findings follow production. Every new production inventory, every nightly re-check and every new advisory rebuilds the findings, and a finding’s state moves with what production actually contains.

  • Fixed means production agrees. A finding is fixed only when production has no affected place left. A merged pull request is not fixed. What production means is set per part: the head of the production branch, or, once the part reports deployments, the last deployed commit. See Fixes and pull requests.
  • Gone only where watchdep looked. A place is marked gone only when the new inventory read the file it came from, checked its ecosystem, and the check did not fail. A lockfile that became unreadable can never make a finding read as fixed.
  • Fixed applies to decided findings too. An accepted or not affected finding whose places all leave production becomes fixed.
  • A decision covers only what it was made for: the places present when the person decided, and each place’s dependency paths at that moment. When an accepted or not affected finding later appears in a new part, a new file, or on a new path, it reopens as new for the new places. The older places keep their decision, and the log says which places are new and which the earlier decision still covers.
  • A pull request closed without merging returns the finding to the state it had before (new or acknowledged).

Reopening

A finding reopens as new, keeping its whole history, when:

  • a fixed or withdrawn finding reappears in production;
  • an accepted or not affected finding reaches a new part, file or path;
  • an acceptance reaches its date.

A reopened finding alerts as if it were new. See Alerts.

The log

Every change writes an append-only entry in the same transaction as the change itself: new (with its level and why), level changed (from and to), places changed (now also in, gone from), fixed, reopened (and why), withdrawn, every decision, code check verdicts, pull requests opened, merged or closed, and who was told. The log cannot be edited or deleted, in the application or in the database. The finding page shows it in full, newest first.

Each entry names who acted:

Who Shown as
A person D. Kim
A host application deciding for a person Jane Smith, via Prospec360
An agent acting for the person who connected it D. Kim, through Claude Code
The CLI, with the name of the token it used CLI (token api-ci)
watchdep itself (nightly re-checks, expiries, new data from a source) system

A decision through a host application is recorded as the person the host named; the log never claims watchdep checked who they are.