Suspect Detector
The suspect detector compares what was recorded against what is current and derives each edge’s state from the difference. Its requirements enumerate the four states that comparison yields, fix the two record sources it may derive them from — binding the recorded one to the affirmation store — and cover the case where an endpoint has disappeared from source entirely. Because the states are derived on every run rather than stored, suspicion raised by a descendant clears itself once that descendant is affirmed again — no separate act is needed, and none is offered.
While an affirmed edge’s endpoint content differs from the content recorded at its last affirmation and every strong edge it depends on is active, the suspect detector shall report that edge as directly outdated. |
While an affirmed edge’s endpoint content matches the content recorded at its last affirmation and any strong edge it depends on is not active, the suspect detector shall report that edge as transitively suspect. |
While an affirmed edge’s endpoint content differs from the content recorded at its last affirmation and any strong edge it depends on is not active, the suspect detector shall report that edge as doubly outdated. |
While an affirmed edge’s endpoint content matches the content recorded at its last affirmation and every strong edge it depends on is active, the suspect detector shall report that edge as active. |
The suspect detector shall derive each edge’s state from a recorded record source and a current record source alone. |
The suspect detector shall take its recorded record source from the affirmation store. |
The suspect detector shall report every edge touching a node that is absent from the current records as broken. |
The suspect detector shall leave recorded affirmations unchanged when it derives edge states. |
For an edge that has been affirmed, the suspect detector shall report, for each named content hash of either endpoint, whether that hash’s current digest matches the digest the affirming review event recorded for that endpoint, together with both digests’ anchors and the source revision the review event recorded for that endpoint. |
The suspect detector shall report, for each named content hash that the node record the case holds or the node record of the current stream carries, whether the current digest matches the recorded digest, differs from it, or exists on one side only. |