Outcomes that arrive later

​

Set a horizon

{"outcomes": [{"document_id": "inv_2043", "judgment": "goes_overdue", "value": true, "observed_at": "2026-10-15T00:00:00Z"}]}

​

How outcomes meet answers

• Windows. A document’s first answer opens a window, which runs for the horizon from the time of the answer. Answers made while it is open do not open windows. The first answer after it closes opens the next. Each window is measured on the answer that opened it.
• Labels. An outcome labels the window that its observed_at falls in. Two outcomes in one window count once. An outcome you posted wins over one a rule made. Otherwise a true wins.
• “It did not happen”, after the window. A false observed after a window closed, and before the next one opens, labels the window that closed. Post “it did not happen” on day 40 and it counts for the answer made on day 0. A true already in that window stays, unless a rule made it.
• Late outcomes count. Brussle matches outcomes each time the fit or the report reads them, so a result you post weeks after the event labels its window at the next fit.
• Engine epochs. A window counts for the epoch of the answer that opened it.

​

Outcomes that count nowhere

• an outcome observed before the document’s first answer (before_first_evaluation);
• an event (true) observed after a window closed and before the next answer (after_horizon).

​

After the event

​

Deleted and rewritten documents

• A document written again after a delete starts a new window at its first new answer, even after an event. An answer is about one life of its document, so an outcome observed after the first answer of the new life never labels a window from before the delete.
• An outcome observed while its document is deleted labels no window, and counts in unmatched_outcomes.no_evaluation. A document remembers the last 8 deletions of its id, so this holds however late you post the outcome, as long as the deletion is still recorded when Brussle stores or reads the outcome, or when you write the id again.

​

Post what did not happen

• Post false after the window has passed, at any time. It answers the window that closed, unless an event was already posted in it.
• Turn on implicit negatives, if you record every event. Then each window that closes with no outcome counts as false.

​

Turn on implicit negatives

{"outcomes": {"implicit_negatives": true, "rules": [
  {"when": {"path": "attributes.status", "becomes": "overdue"}, "value": true}
]}}

await ns.judgments.update("goes_overdue", {
  outcomes: {
    implicit_negatives: true,
    rules: [{ when: { path: "attributes.status", becomes: "overdue" }, value: true }],
  },
});

ns.judgments.update("goes_overdue", outcomes={
    "implicit_negatives": True,
    "rules": [{"when": {"path": "attributes.status", "becomes": "overdue"}, "value": True}],
})

• A window that closes with no outcome counts as false, for the answer that opened it.
• A window that is still open counts nothing yet. An answer from yesterday on a 30-day judgment does not count, because its outcome can still come.
• Outcomes you post, or that rules make, always win in their window. Post a positive quickly, or let a rule make it from the write that records the event. Until then, the window counts as a negative when it closes.
• A window whose document was deleted before it closed is left out, unless an outcome labels it: the event may have happened to a deleted document, so its silence is not a “no”. After the deletion is no longer recorded, the document counts as existing until its newest answer.
• A window opened after the event is left out. The event already happened to that document.
• The report shows the counts: implicit outcomes in each epoch’s implicit_negatives and in outcomes_by_source, and the windows left out in censored_predictions: window_open (not closed yet), document_deleted (deleted before it closed) and after_positive (opened after a true).
• A judgment with many judged documents is fitted on a representative sample of them, with the outcomes posted for those documents, so the share of positives stays true.

• you record only some of the events, such as refunds from one payment system but not another;
• outcomes arrive long after the horizon, such as chargebacks that take 90 days to report on a 30-day judgment;
• the judgment has the default 0s horizon. Brussle refuses implicit negatives there.