A reason can weaken when the company did nothing
A reason can stop holding because the claim's supporting conditions changed
The intuitive model of monitoring is that you watch for bad news. The company announces something, the announcement is negative, the argument for owning it gets worse.
That model catches the easy cases and misses most of them.
A reason to own a company is a claim about how the world works. It can stop holding because the company changed. It can also stop holding because the claim's supporting conditions changed, while the company did exactly what it said it would do, on schedule, with no announcement of any kind.
Four ways it happens
The support stops being restated. A reason derived from a specific disclosure depends on that disclosure continuing to appear. When a company quietly stops breaking out a segment, stops reporting a metric it used to report, or folds a line item into a larger one, the evidence the reason rested on is no longer being produced. Nothing was announced. The company did not say the advantage ended. It stopped saying anything.
The comparison moves. A cost advantage is relative. If the argument was that this company produces more cheaply than its competitors, and a competitor's filings show its costs falling sharply, the first company's advantage narrowed without a single line of its own filings changing. The reason lives in the gap between two companies, and either side can close it.
The structure the reason assumed gets rebuilt. An argument about switching costs assumes customers face friction leaving. When the friction is regulatory or technical and the regulation or the technology changes, the assumption fails upstream of the company entirely. The company is doing the same thing it always did. It stopped being hard to leave.
The reason's time horizon runs out. Some arguments are explicitly temporary — a capacity advantage that lasts until competitors finish building, a pricing position that holds through a contract cycle. These weaken by the calendar. The company hitting every milestone on schedule is the thing that expires the reason.
Why this is the hard part of the problem
Every one of these is invisible to alert-based monitoring, because none of them produces an event. There is no headline, no 8-K, no press release. What there is, in each case, is a filing that either says something different from the last one or fails to say something the last one said.
Detecting that requires knowing what the reason rested on in the first place — specifically enough to notice when the support is missing. Which is what the derivation record is for. A reason pinned only as a cost advantage cannot be checked against anything. A reason pinned to a particular disclosure, in a particular document, can be.
Absence as a finding
The consequence is that some of the most useful results the engine produces are about things that are not there.
A metric that was disclosed for eleven quarters and is absent in the twelfth is a finding. A risk factor that disappeared is a finding. A segment that stopped being broken out is a finding. None of them are negative by themselves, and the engine does not characterize them as negative. They are changes in the evidence, reported as changes in the evidence.
This is also why a filing can move a reason without the engine stating a direction. Reporting that the disclosure a reason rested on is no longer present is a complete, accurate, checkable observation. Adding that this is bad is a separate claim requiring separate support, and when the filing does not supply it, the engine does not invent it.
What this asks of you
Mostly it asks you to accept a less dramatic product.
There will be quarters where the most significant thing that happened to a position you hold is that a table got shorter. That is a real event and it will be reported as one. It will not feel like news, because it is not news. It is the kind of change that only shows up if someone wrote down, with a date, exactly what the argument depended on — and then went and checked.