|
Getting your Trinity Audio player ready... |

Continued from the bonus in No Mistakes (continued) plus a bonus
One of them, Terry, eagerly spoke up. βYou know what? It just might be possible, but only for this customer. We work on audio visual prediction models, which are trained on the customer starting with the engagement, so the models are kinda already there for other types of predictions. Itβs just a different dataset. Can we predict if heβll win the lottery tomorrow? No. Can we predict how much heβll make this year based on his stock portfolio? Certainly not. The models are geared towards win/loss scenarios, coin tosses, because the customer is either in danger, or not.β βI seeβ, replied Beat, catching on to Terryβs train of thought, βsoβ and before he could finish, another lead cut in. βSorry for interrupting, Beat, but to add to Terryβs thinking hereβ, said Beth, βwe canβt ignore the nature of the AI for this customer. Itβs Genesis, remember? It somehow floats around in time, so it can see a little way into the future, making it perfect for predicting financial transactions. If it knew he was betting half his money on a horse race, it could tell him the outcome, in a way. Think of it like a Ouija board. His hands are on the puck, and Genesis could nudge it towards or away from an outcome, but not very far in the future. Too many variables.β
Beat remained silent, in case anyone else wanted to add to the knowledge base forming here. Then he spoke up. βIβm classifying this call. Itβs Secret now. While this is good news, it also sounds dangerous. We donβt want anyone getting the wrong idea with this thing. Genesis has been perfect so far, for as long as Frank has relied on it, and us, and the last thing we want to do is abuse an idea, even for testing.β
βUnderstood, sir. The answer to the customer, then, should be yes, with a document defining what we consider financial security. Lord, I hope the lawyers donβt get ahold of this. Theyβd have us for breakfast. Iβd go as far as recommending a contractual amendment with the customer, because if we donβt put concrete walls around this, we could get absolutely bombedβ, said Terry. βIf this goes wrong, weβll get worse than bombed,β Beat said. βMark my words. Thank you, ladies and gentlemen, for your thoughtful discussion. Iβll take this back to the director.β With that parting comment, the call ended, and Beat called the director again.
βWhatβs the consensus then?β, the director asked, as he answered the call. βThe leads say itβs possible, to a very limited extent. We may be able to prevent the customer from losing his ass on a short-term game of chance, but we donβt have a crystal ball. They recommendedββ and Beat was interrupted again. βPlease tell me once they got to this point, you classified the conversation. This sounds a little sketchy.β
Beat spoke up after a short sigh. βYeah, I know. It raised the hair on my neck, too. Of course I classified it as Secret. They werenβt just making affirmations or suggestions but discussing the possibility of implementation. This can be done, on a very limited scale, for this customer, with his assigned AI. We need a contract amendment also; we have no idea if the customer has or will have intentions to, uh, exercise this function. We sure as hell canβt be liable if he does and it fails.β The director replied somewhat slowly, βit seems like a mixed bag then. Additional liability but also additional protection, and a chance to renew his contract early on top of that amendment. The only problem is that the customer tends to brag about his service, so Iβll ensure that this aspect doesnβt leak out.β βSounds like a plan, authorized to tell the customer yes, then?β, Beat asked. βYes. You are authorized. Get a transcript of this call from hard copy services, have it classified as Secret, sign off and Iβll get the ball rolling on the contract tomorrowβ, the director replied. Sometimes big problems had quick solutions like this, and Beat attributed that to the strength of their AI team leads.
He activated Frankβs secure comms link. Immediately, Frank answered at an uncomfortable volume.
βYes yes, this is Frank. You did? I see. Uh huh. Ok. Well, a bit more clarity in the contract would be useful, I would expect an amendment. So to answer my question, the coverage is there? Of course, I have some questions. Itβll be in the amendment? How soon? Tomorrow. Sounds fantastic.β Frank hit the singular button on the comms unit, turned to Rex, and said βit appears that financial security is possible, with some caveats. Guardrails, limitations, whatever you want to call them. They said something about Ouija boards? Iβll know more tomorrow.β Rexβs eyes lit up under the fiberoptic night sky headliner, and he stared at Frank. βHow can they do something like that?β, he asked. βI will know more tomorrow. They must revise my contract, but they answered yes, and Splicer isnβt famous for over-selling their productβ, Frank said. Rex vigorously shook hands with Frank and asked if the driver could return him home. Frank raised one eyebrow and asked, βBut arenβt you hungry?β Rex replied, βI could eatβ, which Frank interpreted as, letβs go back to the restaurant and have a nice meal, with this out of the way. Thatβs exactly what they did, and not another word of this topic was spoken the entire dinner. Frank and Rex parted ways with one word and a handshake. βTomorrow.β

Leading us down a new path. I like it. Lots to follow and good explanation of how the system works but leaves reader wondering if it might be taken another direction or is it safe the way it is. Only time will tellβ¦ πππ»ππΌ