This week was a bit of a ride with OP Markets, OpenAI & Large-Language Models. Orbital sub-stations, satellite area networks, and outer space have provided a strong case to continue decentralizing Treasury infrastructure for virtual money. And by the way, I was not sponsored by Refinitiv, but I will let my friends at Trade News figure that one out.

So, going down the checklist from a Technology Provider’s perspective after a 2-minute phone call with OP Markets:

1. Equity Research is gone now and has been gone – and your organization can delete it, too! One of the most important Finnish market co-ops for money has decided yield hunting, bonds, and providing liquidity to global reserves may hold little or no meaning within decentralized data exchanges or switchboards. Will Refinitiv or alternative data mean anything this year or 5-years out?
2. The Equity Desk is largely populated by 21-year-olds who have a hard time understanding what a Treasury Bill is, and have lost the basic definitions of Adhesha. Whether that will be a good thing for trying to peg Commodity Futures against the Nordics`thesis that limitless wind supply can still be considered a commodity by companies such as Myrsky remains to be seen.
3. OpenAI / GitHub connectors open up a road to further Metadata Management, viewing the bit-string representations at market liquidity providers, and it was only this quarter that I was able to discover certain macros still remained unimplemented until I did a bit of prompting to see by eye that Advent Calendar macros for checking the rolling dates on trading days were simply written in an hour after the LLM told me the truth of the situation:
   • Organizations that provide market liquidity run in silos
   • Triggers remain unimplemented or may never go into production because of arcane ownership structures having little fit with distributed engineering practices in the next four years of money
   • And here is the code, in case anyone is interested in studying or using it at work:

We created a mini-program, which we’ll call a “macro.” This macro is a bit like a shortcut that does a bunch of steps in one go. We’ve named it run_model_if_date_changed.

Here’s what each part of the macro does:

1. We ask the computer for today’s date and save it as current_date.
2. We pull information from a specific file (the yaml_path you tell us), which has a date inside of it. We’ll call this data_date.
3. If today’s date is different from the date inside the file, that means the data is not up-to-date. So our macro acts:
   • It runs a function named run_model with the model name you provided. Think of it like telling the computer to start a specific program.
   • If the dates are the same, it does nothing.

This macro is handy because it automates the process of checking dates and updating data when necessary.

{% macro run_model_if_date_changed(model_name, yaml_path) %}
{% set current_date = execute(‘select current_date’) %}
{% set data_date = yml_read(yaml_path)[‘vars’][‘data_date’] %}
{% if current_date != data_date %}
{% do run_model(model_name) %}
{% endif %}
{% endmacro %}

1. And knowledge capital may be enough to give you creative freedoms to write an article about the unfortunate situation(s), but:
   • Market stability is tenuous in European exchanges, if it exists in physical reality at all
   • Forced or free labour is an acceptable motive for a non-finite sum of EU entities
   • NASDAQ solved this problem in the 1980´s with multi-casting

Please feel free to text me directly if this was the right kind of spice for your trading desk: +358 45 787 10515. The future from here-on-out is hardly manageable, but please give the technicians a fair market rate. We know our institutions can afford it.

PS. I would like to thank Perttu Kajatkari for introducing me to the Finnish market landscape in 2022. We have a bit of work to do; together! And yes, AI / SQL is a scary subject, but we are still alive.