{
  "id": "p_1SgcH83ptxBNiIT5",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_1SgcH83ptxBNiIT5",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"Telecom: A Bundle Where The Operator Sets The Limit,\" Kin Lane, November 16, 2026, https://apievangelist.com/2026/11/16/telecom-a-bundle-where-the-operator-sets-the-limit/\n\nMarisol worked on the fraud side of a small payments team, and she read the post on a Monday with her coffee going cold. She didn't know what a constrained decoder was until she was two paragraphs in. She knew what a SIM swap check was, though. Her team had been talking for weeks about putting a model in front of that step, and the thing nobody could say was what stopped it from asking for something stupid.\n\nThe bundle answered that more directly than she expected. The maximum look-back window wasn't fixed. It was bound to a number that came from the operator, resolved when the request was made. She liked that. She also liked that the author said plainly where it fell short. A formal overlay would be the better home, and what he'd built only works if somebody already knows the number. Marisol read that line twice. Nobody on her team knew the number for any operator.\n\nShe read the rule about the cap and nodded. \"An operator can lower the limit, not raise it.\" That was how she thought about every limit she'd ever inherited from a vendor, so she felt something close to relief at seeing it written down as a check.\n\nThen she got to the fixtures and felt less comfortable. A high-risk request looking back only 24 hours had passed the decoder with no errors. The only thing that caught it was a warning, and the 72-hour floor behind that warning was, in the author's own words, made up. Marisol turned that over. A made-up number in a bundle was still a number someone might copy. In her world a warning was something people learned to scroll past. She wasn't sure she'd trust a model to pick the window at all, valid or not, and the post agreed with her. A 240-hour window is valid, it said, but whether it should have been shorter is a fraud judgment that needs outcomes data no bundle has.\n\nThe line she kept returning to was about the recorded reason. A recorded reason from a model is \"a statement, not an explanation of what the model did.\" Her compliance lead would ask her, sooner or later, to explain a decision on replay. She could picture handing over a field of text that sounded confident and explained nothing. She disagreed with the idea that a fixed seed and a stored sentence added up to an audit trail, and she thought that was the weakest part of an otherwise careful piece. Then she noticed the author had said so first, which annoyed her a little.\n\nShe didn't have a verdict. She wasn't going to build the bundle, and she wasn't going to argue the case for it in the next planning meeting either.\n\nThe post ended on a request to operators: \"publish your cap and your profiles as data.\" Marisol couldn't make anyone do that. She could find out how bad things were on her own side. She opened a blank text file, wrote the name of the one operator her team integrated with most, and under it typed a question mark where the cap should be. Then she opened that operator's developer documentation and started reading, looking for a single number.",
  "title": "Fiction: A reader of \"Telecom: A Bundle Where The Operator Sets The Limit\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-16T13:38:08.940Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}
