downtime_attribution
Ranks stoppages and attributes downstream stops to their declared upstream origin by topology and stop order, separating the true trigger from consequences.
Instructions
[READ][risk=low] Which stoppage started it, and which ones were downstream of it.
RCA weights evidence by TIME alone — a signal before onset counts, one after
counts less. That is the honest half of the axis. Run `downtime_root_cause`
per asset after one upstream stop and every downstream machine comes back
with its own confident local root cause: each internally consistent, each
citing real signals, and all but one about a machine that stopped because it
was starved. The distinguishing fact is not in the evidence — it is the
line's topology.
Two rules decide an attribution and both must hold: the candidate must be
**declared upstream** of the asset, and it must have **stopped first**. An
upstream asset that stopped later cannot have caused an earlier stop, however
upstream it is.
Topology is declared, never inferred (D25). Co-occurrence on a production
line is guaranteed — everything stops together — so mining it for edges would
manufacture the causality this exists to remove. With no relations declared
every row comes back `not_evaluable` and the reason names the command that
fixes it. Assets the topology does not connect are left `unattributed` rather
than folded into the origin's column.
This ranks the stoppages; it does not diagnose the origin. Run
`downtime_root_cause` on the origin asset for that.
Args:
stoppages: [{asset, start, end?}] for one incident window (ISO-8601).
site: Which declared line topology to use (default "default").
max_lead_s: A downstream stop is attributed only if it began within this
many seconds of the upstream one (default 900).
Returns dict: {site, stoppages_evaluated, relations_declared, max_lead_s,
verdict ('origin'|'multiple_origins'|'unattributed'|'not_evaluable'),
origins, consequence_count, attributions:[{asset, start, status,
origin_asset?, hops_upstream?, lead_s?, explains?, detail}], advisory}.
Example: downtime_attribution(stoppages=[{"asset":"filler","start":"2026-01-05T06:00:00Z"},
{"asset":"capper","start":"2026-01-05T06:01:00Z"}]).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"stoppages": "<stoppages>"
},
"name": "downtime_attribution"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site | No | default | |
| stoppages | Yes | ||
| max_lead_s | No |