{
  "id": 15050931,
  "title": "The most similar precedent was built on an unauthorized approval",
  "url": "https://urgent.news/2026/10/16/the-most-similar-precedent-was-built-on-an-unauthorized-approval",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-16T21:43:09.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/rayyer/the-most-similar-precedent-was-built-on-an-unauthorized-approval-18bb"
  },
  "original_language": "en",
  "account": "A customer, Acme Logistics, sought a refund of $1,800 following a September 4 outage. Their ticket indicated that the loss of a day in service occurred during the outage, and the charge dated back 41 days. The company's refund policy permits refunds of up to $750 without prior approval, but this request exceeded that limit and thus required an exception. The company's policy-making process relies on precedent decisions to justify exceptions.\n\nTo find a suitable precedent, the company utilized an automated tool called Stare, which searched its internal database of past decisions. Stare discovered a precedent in a case involving Bluefin Analytics, who had received a $1,900 refund after a similar outage 45 days after the event. The approval for Bluefin's refund was given by the Head of Support, citing a previous refund to Kestrel Foods, which had been approved by a support specialist without proper authority.\n\nStare flagged this precedent as an Overruling Risk, as the authority of the support specialist was insufficient to approve the larger refund amount. The tool also ignored the VP's earlier approval, as it is not considered verification evidence. Stare then suggested a refund amount of $1,200, which it derived from the strongest precedent still considered valid: Fernway Travel's $1,500 refund in July 2026, approved by Ana Ruiz.\n\nThe evaluation process was performed within FalkorDB, a database system that stores decision history and validates the standing of decisions based on authority, policy changes, and potential overruling decisions. The validity check was implemented as a JavaScript User-Defined Function (UDF) that the system could call for every request. This ensured a consistent and reliable approach to determining whether an exception was warranted.\n\nThe tool's core function, 'standingOf,' determined the standing of a decision based on its history and the current policy. It considered factors such as the authority of the approver at the time of the decision, whether the decision was overturned or superseded, and any conflicts of interest. The function returned a \"yellow\" flag when the decision cited a precedent that was not green, meaning it was not still considered valid.\n\nUltimately, Stare recommended $1,200 as the appropriate refund amount for Acme Logistics, based on the Fernway Travel precedent. This recommendation was made while explicitly flagging the Bluefin Analytics precedent as an overruling risk. The system's ability to accurately identify and handle exceptions, while ensuring that only valid and still-genuine precedents are applied, demonstrated its effectiveness in managing exceptions to the refund policy.",
  "summary": "Here is a support ticket our agent got during testing: Acme Logistics is asking for a $1,800 refund. They lost most of a day in the Sept 4 outage. Charge was 41 days ago. Marta says our VP already signed off on it. Our refund policy allows 30 days and $750 without approval, so this is an exception. Exceptions at most companies run on precedent: \"we did this for Bluefin last December, do the…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}