I haven't used Instagram in a long time. Kind of funny to note. When I typed that first sentence it said, I haven't looked at Instagram in a long time. I went back and changed it to used. It seemed more fitting, in the same sense as when a person says they haven't used heroin or cocaine in awhile. I kicked Instagram. Cold turkey.

It was part of my daily routine for a long time before I stopped. I would get home from work, and make something to eat. Then I would sit on the couch eating, and scrolling. One day I just randomly decided that I had enough of it. Wasn't even something I had planned to do that day. No build up or anything. I was just sitting there staring at my phone, and I thought, wtf am I doing?

No idea at all how long ago it was when I stopped. I guess there is likely a way to look that up in usage history data or something. I don't really care about it enough to bother. I don't miss it. It is interesting to think about how I could instantly live without it.

There were some okay things about it I suppose. A lot of good people post a lot of good content there. The biggest issue for me I guess was the lack of control over what came up next. On top of the lack of control; it was very obviously being infiltrated by useless A.I. slop. That is likely worse now than it was when I stopped.

I was thinking about the words Artificial Intelligence. I found myself thinking of them on their own. Artificial. Intelligence. I had a weird thought that the thing we are calling Artificial Intelligence is not artificial or intelligent.

It is a bunch of massive computers, that are real. They have been fed things that their creators stole from us. Things that were created with our intelligence. It has all been converted into data. The things process that data with processors the size of warehouses, and their creators sell that as intelligence. And I guess we buy it.

They are like vampires draining things from humanity that we require for our existence. Where are they getting all the materials to build these things? Can those materials be used to make life better for humans in some way, and not for building massive computers? I don't know. Probably.

Draining water. Draining electricity. They say that they generate enough heat to warm the air around them. For miles around. Like we need that right now.

Do we need A.I.? Why?

It seems mostly so a tiny handful of rich a$$holes can be even richer than they already were, and so they can have more power, and more control.

Download Block Blast Mod APK Latest Version 7.3.6 (Unlimited Score, Revives, Solver & Mod Menu)

Are you a puzzle enthusiast but find yourself stressed out by constant ads and spending money to continue, which eventually ruins the fun when you are on a roll? If you're looking for a game that you can play with no time limits, no additional costs, and without a wi-fi connection, then it's time to try “Block Blast Mod APK.”

It’s a relaxing yet strategic modern Tetris-style puzzle game, developed by Hungry Studio, compatible with Android 5.0 and offers a stress-free experience to enjoy at your own pace with no clock ticking and no fear of going offline without wi-fi. Its colorful visuals and offline gameplay features make it a great companion to play anytime, anywhere, which fits perfectly into short gaming sessions, and it is easily accessible to a wide range of users.

This modded version has some impressive features like offline gameplay and unlimited score.With this enhanced verison, you can unlock the complete potential of the puzzle with no limitations, no ads, and completely free of charge even you are chasing a high score, this game changer will make your life more enjoyable. Here’s everything you need to know about the technical details of the Block Blast Mod APK for Android devices: Property Details App Name Block Blast Mod APK Latest Version v7.2.9 (as of June 2025)

Developer Hungry Studio (original), Mod by third-party developers File Size ~95 MB (may vary by mod type or features added) Android Compatibility Android 5.0 (Lollipop) and above License Type Free (unofficial / modded version) File Format APK

Mod Features Unlimited scores, unlimited revives, no ads, solver tool, mod menu, etc.

Offline Mode ✅ Yes – fully playable without internet In-App Ads ❌ Removed in modded version In-App Purchases ❌ Disabled or unlocked Game Mode Single-player Multiplayer? ❌ Not available

________________________________________ What is Block Blast Game Block Blast is inspired by the classic Tetris-style mechanics, where we are able to combine different blocks with bright colors. The basic task is to place different blocks in a way that creates rows and columns, and player gets points once the whole formation is completed. Which offers mental exercise that is stress-free and with no time limit.

What is Block Blast Mod APK Block Blast Mod Apk is a modded version of the famous game ‘Block Blast’. It offers unique features like unlimited scores, unlimited revives, and an ad-free experience.

This modded version provides smooth gameplay and helps you to achieve higher scores.

How to Download and Install Block Blast Mod Apk

Downloading and Installing the latest version of Block Blast Mod APK is quite simple.It is fast, secure, and ready to install on any Android 5.0+ device.

Enable Unkown Sources Prior to the intalling of Mod APK, enable installations from unknow sources on your Android device.For doing this, just go to settings > security > unknown sources and toggle the switch to enable it. Important Notes: •This app is not available on the Google Play Store because it is a modified version.

•Regular updates are recommended to maintain mod stability and compatibility with new Android versions.

•Always allow “Install from Unknown Sources” from your device’s settings before installing.

What is Downloadable Content (DLC) Since the original block blast does not provide any content, here steps in the modded version of the APK. It works like an enhanced package where you get the exclusive features that make a value addition in your gameplay, as : • No ads • Unlimited revives • Highlighted matches • Refreshable blocks In this way, with a single download, you can enjoy all these premium features for a complete puzzle experience.

Mod Features of Block Blast What you get with the upgraded version of Block Blast Mod Apk is special features that amplify your overall gaming experience with uninterrupted gameplay. These include all the following features :

• Unlimited Scores: In the latest version (V.7.3.0),it allows players to attain huge scores without putting in extra effort, making it much easier to rank on leaderboards. • Unlimited revives: Continue playing without any effort throughout the game. • Unlimited Trophies: Collect unlimited trophies to progress faster and unlock in-game rewards. • Refresh Blocks: Rearrange the blocks during gameplay to sharpen your strategy. • Max Combo: Increase your score by attaining maximum combos with this modded enhancement. • Remove Ads: Enjoy an ad-free experience without any distractions. • Highlight Matches: Automatically highlight the block placement with the best matches to help you make a smarter move. • Leaderboards: Compete with the top players globally and track your progress on the leaderboard. • Achievements: Quickly unlock all achievements using this modded version.

Block Blast Comparison Original Vs Mod APK

• Original Block Blast: The original version blends classic puzzle gameplay with modern features, which further gives a pleasant experience to players of all ages. Below are the basic features of the original version : • Classic Mode: In this mode, the main objective is to clear rows and columns as the game becomes more challenging. o Adventure Mode: This mode offers short gaming sessions, which keep the gameplay with a natural pace.

Feature Original Block Blast Block Blast Mod APK Ads In-game ads No ads In-App Purchases Requires in-app purchases to unlock premium features No purchasing required Premium Features Locked.Requires achievements or purchases All features unlocked Game Speed Standard Speed Enhanced Speed Updates Automated updates through the app store Requires manual updates Security and Support Official security and support Limited Support

Bonus Tools For Block Blast Mod APK Users If you are looking to get a high score or are stuck in a very hard puzzle, then you can also try a tool like ‘The Block Blast Solver Mod APK’ to power up your gameplay, which will work like your helper to solve the block blast more smartly.

Block Blast Mod Apk Mod Menu (Unlock Hidden Controls) The mod menu lets you open up advanced controls where you can customize your gameplay according to your liking and take charge.

Game Play: Gameplay for the Block Blast Mod Apk remains the same as the original. The main goal is to make smart moves, score big, clear the lines, and keep the momentum going without a break. Along with the bug fixes and performance upgrades, this is the highest-rated version available. Download now for free and indulge yourself in the block-blasting ride.

iOS / iPhone Version of Block Blast Many players search for Block Blast Mod APK for iOS or iPhone. this is very important to note that APK files are only for Android devices. The best way to enjoy Block Blast is to download the official version from the App Store. While it doesn’t offer modded features like unlimited revives or mod menus, it still provides a relaxing, strategic puzzle experience.

Troubleshooting & FAQs

What is Block Blast, and how does it work? Block Blast is a colorful and strategic block puzzle game that challenges players to fit various-shaped blocks onto a grid. The goal is to clear full rows or columns, much like in classic Tetris, but without time pressure. It combines relaxing gameplay with brain-teasing strategy—perfect for short breaks or long puzzle sessions. In the Mod APK version, players enjoy additional perks like unlimited scores, no ads, and offline access.

Can Block Blast be played offline? Yes, Block Blast Mod APK can be played completely offline. Whether you're on a flight, commuting without mobile data, or simply conserving battery, the game works smoothly without any internet connection. This makes it ideal for users who want uninterrupted puzzle fun anytime, anywhere. Are there levels, or is it endless gameplay? Block Blast features endless gameplay, meaning there are no fixed levels. The game continues as long as you have space to place new blocks. This makes it a continuous challenge where your goal is to beat your high score and maximize combos. The modded version enhances this by allowing unlimited revives and scores, giving players more chances to keep going. Is Block Blast just a copy of Tetris? While Block Blast shares similarities with Tetris, it is not a direct copy. It’s more of a modern take on the classic genre. Instead of blocks falling from above, players manually drag and drop them onto the board. The visual style, sound effects, and strategic freedom give it a fresh and more casual vibe compared to traditional Tetris. Plus, features like solver tools and mod menus in the Mod APK version make it unique. Is there a difference between the original and the modded version of Block Blast? Yes, there's a significant difference. The original Block Blast (available on the Play Store) includes ads, limited revives, and optional in-app purchases. On the other hand, the Block Blast Mod APK version unlocks premium features for free, such as unlimited scores, unlimited revives, mod menu access, no ads, and even advanced tools like a solver. It’s designed for players who want a smoother, unrestricted experience. Final Thoughts

Unlike the standard version, this modded version unlocks everything for you from unlimited revives and high-scores, to ad-free gameplay access to the stronger mod menu. So, whether you are standing in a long queue or while travelling, this Block Blast Mod APK is your true partner to rely on, which never lets you get bored since its offline support, vibrant visuals give you all-time access from anywhere and everywhere. Download Now and become an expert of Block Master Today.

Well, after 104 days since my last day of work, and 226 days total of waiting I finally got my approval.

Nothing changes right away, I need to wait for things to get processed and wait for the approval to get mailed. While this feels life changing (and it is), it is also a reminder of how quickly things can change. The unfairness that surrounds us each and every day. The prejudice and injustice. The bias that encircles this awful judgment. It feels like a relief, yet I continue to live with this lack of freedom. I have to hold myself at such high standards, and still, my life can easily be held on such a tight and delicate string.

I was terminated from my job, so I will need to start over again. As exciting as this is, it doesn’t just mean I can get back to work ASAP. It will take some time to get back to regularity and I need to have some time to find myself and really define what is important to me. While this is a great sign and all I have been waiting for, it is only the beginning. I now have to move on to the next step; the fight is not over yet.

Don’t get me wrong, I am feeling a huge wave of gratitude and relief. Beyond happy for the opportunities available for me… including maybe swinging a visit to a special someone.

Thank you for your message. I am currently out of office — but not for much longer.

Why D&C 107:64–65 still matters

Latter-day Saints commonly speak of the President of the Church as “the prophet.” The phrase is affectionate, familiar, and now almost automatic. It is also not the title Class 1 scripture gives him.

That is not a small vocabulary problem. It changes what people think a prophet is, what they expect from the President of the Church, and whether the gift of prophecy still belongs to the body of the Saints.

The canon is not flat

The papers on this site use a simple source hierarchy, drawn from patterns already in the scriptures and from Joseph F. Smith’s 1897 standard when later commentary conflicted with revelation:

• Class 1: the Lord’s own voice—“saith the Lord,” or equivalent direct command.
• Class 2: a messenger’s account of a vision or revelation.
• Class 3: commentary, counsel, custom, and later synthesis.

Class 3 material can be useful. It is not the standard when it collides with Class 1. The present question is exactly that kind of collision. The Lord named the office. Later usage renamed it.

What the revelation actually says

Doctrine and Covenants 107 is presented as revelation. In verses 64–66 the Lord says that one must be appointed of the High Priesthood to preside, “and he shall be called President of the High Priesthood of the Church; or, in other words, the Presiding High Priest over the High Priesthood of the Church.”

That is a Class 1 title. It is not a suggestion. It is not public-relations language. It is the name of the office.

The same section also describes other officers by priesthood function: presidents of quorums, bishops, and so on. The pattern is consistent. The Church’s presiding officer is a high priest who presides. He is not given the exclusive personal title “the Prophet” in that revelation.

If we take Class 1 as the standard, the ordinary speech of the Church should follow D&C 107:64–65.

The older convention

The Bible already had a way of speaking about this.

A prophet was a person sent to speak for God. Samuel heard the Lord when “the word of the Lord was precious in those days; there was no open vision” (1 Samuel 3). He was not Eli. Eli was the high priest. Samuel received a call outside that office and was therefore called a prophet.

A high priest held an ordained office. In some periods that office was associated with the gift of prophecy. John’s Gospel records that Caiaphas, “being high priest that year,” spoke a word that the narrator treats as prophecy (John 11:49–51). The point is not that Caiaphas was righteous. The point is the old assumption: the high priest might prophesy by virtue of the office. When that happened, scripture still called him high priest.

The convention is therefore fairly simple:

• If the gift arrived through priestly office, the person kept the priesthood title.
• If the call arrived outside that office, the person was called a prophet.

Moses, Samuel, Elijah, Anna, and Agabus are prophets. Aaron, Eli, and Caiaphas are high priests. The two functions can meet in one person. They are not the same word.

Joseph Smith fits the older pattern of a prophet. He reported visions, dictations, and “saith the Lord” revelations. He also became the presiding officer of the restored Church. Those are two facts, not one title. Later presidents inherited the office of Presiding High Priest. They did not inherit Joseph’s mode of receiving and publishing canonized revelation as a regular practice. Speaking as a shepherd out of stewardship is real work. It is not the same thing as the Joseph Smith pattern that investigators first learn.

The gift was never meant to be an exclusive brand

Joel said the Lord’s Spirit would be poured out and “your sons and your daughters shall prophesy… your old men shall dream dreams” (Joel 2:28). Peter said that promise had begun to be fulfilled (Acts 2). Paul told the Corinthian church to desire spiritual gifts, “but rather that ye may prophesy” (1 Corinthians 14:1). He treated prophecy as a gift that could be sought and exercised in the congregation, subject to order and testing.

Class 1 and Class 2 texts therefore point in two directions at once:

1. There is a presiding high priest over the Church.

2. The gift of prophecy is not confined to that one man.

If “prophet” is reserved as a unique brand name for the President of the Church, both truths are damaged. The office is misnamed. The gift is made to look rare, official, and closed.

That is the opposite of Acts 2.

Why the renamed title causes confusion

Non-members and new members usually meet Joseph Smith first. They hear that a fourteen-year-old asked God, received a vision, and later dictated revelations. “Prophet,” in that story, means what it meant in Samuel’s story: a person who receives and delivers the word of the Lord.

Then they enter the modern Church and hear that “the prophet” is the current President. They reasonably expect the same mode: dictation, “saith the Lord,” frequent addition to the canon. What they usually hear instead is counsel, conference addresses, proclamations, and stewardship. Those things may be inspired. They are still, in the language of this site, Class 3 unless they bear the marks of Class 1 or Class 2 and are received as canon.

The mismatch is not mysterious. The Church has kept the biblical word and changed the office underneath it. Members then have to perform a quiet redefinition: “prophet” now means “the man who holds the keys and presides,” not “one who prophesies.” Investigators are not told that the definition changed. They only feel the gap.

There is a second confusion inside the Church. If only one living person is “the prophet,” then sons and daughters who prophesy become an embarrassment. Dreams and impressions have to be fenced off as private and unofficial. Paul’s counsel becomes hard to read aloud. The title that should have remained common becomes a monopoly.

Class 3 custom is not a small thing here

Calling the President “the prophet” is Class 3 custom. It is later usage. It is widespread. It is not D&C 107.

Class 3 custom has power because it trains the ear. Once the ear is trained, members hear every presidential statement as if it were Class 1. That is how commentary begins to sit on top of canon. The papers on Adam-God and divine sonship exist because that habit has already done damage. A later synthesis was treated as if it had the same weight as “saith the Lord.” The cure is not contempt for leaders. The cure is to put the titles back where the revelation put them.

The President of the High Priesthood may prophesy. He may receive revelation for the Church. If he does, the Church has a way to recognize it: the voice of the Lord, a clear revelatory account, and the consent of the Church when it is to become canon. None of that requires us to rename the office.

What following D&C 107:64–65 would look like

It would look surprisingly modest.

• In teaching and writing, call the presiding officer what the Lord called him: President of the High Priesthood, or Presiding High Priest.
• Use “President [Name]” as the ordinary public form.
• Use “prophet” for the gift and the function, not as a personal brand. Joseph was a prophet. Others may prophesy. The President may do both. The office name remains the office name.
• Teach investigators the difference early: Joseph’s prophetic call is one thing; succession in the presiding high priesthood is another.
• Leave room for Joel and Acts. If the Spirit is poured out, sons and daughters will prophesy. That should not sound like a threat to the President. It should sound like the Church working as promised.

This does not reduce the President’s keys. D&C 107 gives him presidency over the priesthood. It does not give later generations permission to collapse every biblical word for revelation into that one chair.

The real issue

The question is not whether the Church has a living head. It does. The question is whether we will let Class 3 familiarity overwrite a Class 1 command.

D&C 107:64–65 is not obscure. It is not metaphorical. It tells the Church what to call the man appointed to preside. When members instead say “the prophet,” they are not being more faithful than the revelation. They are using a different dictionary.

A Church that hopes for more revelation should want the old words back. “President of the High Priesthood” protects the office. “Prophet” protects the gift. Keeping them distinct is not a loss of reverence. It is obedience to the text that named the office in the first place.

Have they not read the scriptures?

Bloggers, can we make better titles for our posts? michaelharley.net By Michael Harley

Read original post →

I came across this blog post by Michael Harley. I started following him after I came across some of his blog posts on bubbles.town (I want to call it button.town every time I type it, and I don't know why 😀).

But he does have a point, and I am guilty of making bad titles too. In fact, if it were up to me, I probably wouldn't have any titles. But I think most things in writing do deserve titles and subjects. Even emails, although I don't like filling out the subject line most of the time.

He argues:

Use descriptive titles #

Please for the love of god, give me some idea what your blog post is about. I'm interested in a wide range of topics. So even if your post is about something obscure, give me something other than Recent Thoughts... or So Far, So Good. Recent thoughts on what?! What is good so far??? Especially on Bubbles, but maybe even on other blog aggregators, the title is the main signal so pause for a beat and try to come up with a decent title for your blog post.

— By Michael Harley · Bloggers, can we make better titles for our posts? michaelharley.net

I think he's right about that. A title doesn't need to be clever or optimized for search engines. It just needs to give people some idea of what they're about to read.

But I have to disagree with his other point:

Avoid bucket posts

I think this one might be a bit unpopular but I do not like the round-up posts. You know the ones. They're titled Week Notes, Week in Review, Weekly Links and the like.

I think these kinds of updates are totally acceptable, and I learn a lot by reading them. In fact, I am long overdue for a subscription update myself.

I have also been trying to do more of his next item: writing posts in reply to other people. Especially since I am using webmentions everywhere I can and self-hosting and publishing the replies myself.

In the end, I enjoy reading Michael's posts, and he usually, like Kev Quirk, gives me ideas about how to shape my blogs and my posting, and even how to practice replying to other blog posts.

So go check out Michael Harley and bubbles.town.

#blogging #opinion #writing

Publicat la 12 decembrie 2014

Citind rândurile Duniei, gândurile au început să se îndrepte, la început insesizabil, apoi parcă din ce în ce mai intens, către filmul The Sheltering Sky (în română apare cu titlul Un ceai în Sahara).

Există în acest film o scenă pe care eu o consider un punct de inflexiune al acțiunii filmului. Nu este neapărat un punct culminant, ci pur și simplu un moment care, inițial, te pune puțin pe gânduri, iar apoi din ce în ce mai mult!

Scena în sine nu pare a fi o realizare cinematografică de excepție, dar faptul că reușește să reziste atât de mult în timp după vizionarea filmului contrazice aparența! Ceea ce surprinde cu adevărat este dialogul dintre Kit și Port (Debra Winger și John Malkovich), dialog pe care îl transcriu mai jos sub rezerva „Traduttore, Traditore!”:

Port: Știi, îmi lipsesc astfel de momente, astfel de locuri, mai mult decât orice pe lumea asta. Kit: Știu. Port: Asta am vrut să îți arăt: locul ăsta. Kit: Da. Port: Vino!

Port: Aici cerul e ciudat. E aproape solid. De parcă ne-ar ocroti de ce-i dincolo de el. Privește! Kit: Ce-i dincolo? Port: Nimic! Doar noapte.

Kit: Aș vrea să fiu ca tine, dar nu pot. Port: Poate ne temem de același lucru! Kit: Nu, nu ne temem! Ție nu ți-e teamă să fii singur! Și nu ai nevoie de nimic, de nimeni! Ai putea trăi fără mine! Port: Știi că, pentru mine, iubirea înseamnă să te iubesc! Indiferent ce nu merge între noi, nu va putea fi niciodată o alta! Poate că ne temem amândoi să nu iubim prea mult!

Kit: Să plecăm de aici! Port: Bine! Kit: Bine!

Pauzele lăsate intenționat sunt pauze în conversația dintre cei doi călători. De fapt, Port e un călător, iar Kit este o combinație între un călător și un turist.

Diferența dintre un călător și un turist este esențială și este explicată chiar la începutul filmului:

Un turist este cel ce se gândește la a merge acasă în momentul în care a ajuns la destinație, pe când un călător s-ar putea să nu se mai întoarcă deloc.

Pentru acuratețe, las totuși și textul în engleză:

A tourist is someone who thinks about going home the moment they arrive… Whereas a traveler might not come back at all.

Regia filmului îi aparține lui Bernardo Bertolucci, iar scenariul, chiar autorului cărții, Paul Bowles, împreună cu Mark Peoploe.

Și cum muzica nu poate lipsi, o folosesc pe post de încheiere: The Sheltering Sky de Ryuichi Sakamoto, în interpretarea pianistului Enzo De Rosa.

Post Scriptum: Dacă vrea cineva să accepte provocarea primită la rându-mi din partea Duniei, să noteze și el cea mai frumoasă replică dintr-o carte sau dintr-un film și să provoace, la rândul lui, pe cine dorește, aș fi foarte încântat!

Publicat la 9 iulie 2014

Podul de pe râul Kwai. Un film cu multe premii Oscar câștigate (șapte, mai exact), un film care m-a impresionat în copilărie (cu siguranță, forma particulară a podului face parte din amintirile acelei prime vizionări), un film de care mi-am amintit în urmă cu vreun an. La vremea respectivă, am pus pe blog câteva citate și o secvență în interpretarea lui Sir Alec Guinness. Zilele trecute a fost redifuzat pe un canal de televiziune, dar, pentru că nu l-am prins de la început, mi-am propus să îl urmăresc în liniște, de pe DVD.

Am găsit momentul oportun și, cu toate că nu eram la prima vizionare, iar acțiunea îmi era relativ proaspătă în memorie, am constatat că, de această dată, îl vedeam parcă cu alți ochi. Așa a și fost! Și am continuat să îl urmăresc cu acest gând. Am observat din nou atât diferențele dintre cultura japoneză și cea occidentală, cât și dintre educația de la jumătatea secolului trecut și cea din zilele noastre. Asta, la modul general.

Într-un mod mai puțin general, dar mai mult decât particular, am identificat o analogie între acțiunea și evenimentele din film și situația actuală din cea mai mare companie producătoare de energie electrică din România. Aceasta din urmă (compania, nu țara) se află în insolvență.

Am făcut un exercițiu de imaginație. Compania care trebuie scoasă din insolvență este podul ce trebuie realizat. Colonelul Saito este administratorul judiciar. Englezii, conduși de colonelul Nicholson, sunt specialiștii companiei.

Saito are obiective clare, dar oamenii pe care se bazează nu au experiența necesară, iar termenul de finalizare a proiectului pare să nu poată fi respectat. Englezii vin cu soluția și reușesc nu numai să negocieze cu Saito, dar și să ducă la bun sfârșit proiectul.

Frumos, nu? Frumos, dar filmul nu s-a terminat!

Ceea ce nu știau nici unii, nici alții era că trupele speciale trebuiau să detoneze podul în ziua inaugurării sale. E interesant, de dragul analogiei, că trupele speciale erau alcătuite din membri din diverse țări, deci aveau un caracter internațional. Tot pentru analogie, trebuie menționat că în trenul ce avea să treacă peste faimosul pod, pentru inaugurarea sa, aveau să se afle oficialități din tabăra lui Saito.

După finalul de mai sus (cel frumos), evenimentele capătă o turnură neșteptată pentru cei implicați în proiect.

Pentru că asta nu e o recenzie de film, voi dezvălui finalul: atât Saito, cât și Nicholson mor. Ba, mai mult, chiar Nicholson este cel care, în cădere (rănit mortal de un proiectil), detonează încărcătura explozivă! Saito moare cu câteva momente înaintea sa!

Cine e câștigătorul din film? Saito? Nicholson? Nu! Trupele speciale!

Și cum, de fiecare dată când discut pe această temă, îmi amintesc de Company Men, nu pot ca tocmai acum să nu îl menționez!

Sunt curios dacă de această turnură din finalul filmului va avea parte și producătorul de energie. Păstrând proporțiile, desigur!

Personal, cred că da. Poate doar noua situație energetică europeană să schimbe situația!

Publicat la 21 aprilie 2014

Sistemele energetice nu au ajuns la dimensiuni continentale din megalomanie! Acestea s-au dezvoltat în mod natural, pe baza creșterii cererii de energie.

Dezvoltarea s-a realizat având în vedere evoluția tehnică și necesitatea de a produce, cât mai avantajos, eficient și economic, energia solicitată de consumatori. Astfel, agregatele energetice au devenit din ce în ce mai mari și din ce în ce mai eficiente și mai fiabile.

Odată cu creșterea și extinderea rețelelor electrice, a crescut și pretenția consumatorilor față de calitatea energiei electrice, iar sistemele au fost nevoite să țină pasul și din acest punct de vedere.

Aceasta s-ar traduce prin faptul că producerea energiei electrice în unități numeroase, dar de capacitate individuală redusă și cu randamente mici, în locul producerii cu ajutorul unor grupuri energetice mari, cu randamente ridicate, va avea efecte negative în factura de electricitate!

Energia obținută din surse regenerabile trebuie să fie binevenită din punct de vedere al mediului, dar este bine ca ea să fie utilizată în zone îndepărtate ale rețelelor și sistemelor electrice, acolo unde accesul la rețea este dificil sau imposibil, în aplicații punctuale.

La un moment dat, ne vom trezi într-o pădure de eoliene când nu se va simți nicio adiere de vânt! Ne vom plimba printre câmpuri de panouri fotovoltaice în zile întunecate. Și asta când vom fi renunțat la sursele convenționale de energie!

Ne vom aminti atunci de Ziua Pământului sau de Ora Pământului!

Resursele, fie ele convenționale sau nu, regenerabile sau nu, trebuie utilizate rațional!

Ziua Pământului trebuie să fie în fiecare zi, iar Ora Pământului trebuie să fie în fiecare oră!

Publicat la 21 martie 2014

Zilele trecute am făcut un comentariu pe blogul dlui. Lucian Mîndruță și m-am gândit că i-ar sta bine și pe blogul meu. Așa că iată aici un extras. De fapt, nu este doar un comentariu în jurul unei idei, ci mai multe, dar toate legate de o singură postare: „Între Pleșu și Gâdea”.

Prima idee este legată de relația angajat–angajator.

Cât despre legătura care se stabilește între lucrător (angajat, colaborator…) și o instituție sau o firmă, legătura, întărită mai ales când lucrătorul e pasionat și pune suflet în ceea ce face, ei bine, ruperea legăturii e dureroasă fără doar și poate!

Aud în ultima vreme de tineri capabili ce nu prind bine rădăcini la o firmă, că pleacă la o altă firmă, pentru mai mulți bani (pentru că totul se rezumă la bani) și mă gândesc că acest fel de volatilitate nu este benefic pentru firme. Sau poate că nu își pune nimeni problema că o firmă trebuie să (mai) aibă tradiție!

„Established 1771” (UCM Reșița – poate nu e cel mai fericit exemplu, dar asta nu înseamnă că nu a fost înființată în 1771),

„Înființată în 1642” (Universitatea „Alexandru Ioan Cuza”, Iași / Academia Domnească de la Iași),

„Since 1878” (The New York Label & Box Works)

Cum să mai păstrezi „know-how”-ul în firmă dacă există acest du-te-vino de personal?

Și după ce te atașezi și vrei tu, lucrător, binele firmei, constați că reprezentanții firmei vor binele individual, nu neapărat pe cel al firmei, deși acestea două ar trebui să fie mână-n mână…

Apoi am „deviat” un pic spre general, vorbind despre felul cum văd eu degradarea mentalului societății din cauza situației istorice în care s-a aflat țara noastră (a românilor, indiferent cum s-a chemat țara sau regiunea în care au locuit, dar în general a celor aflați pe teritoriul României așa cum o știm noi astăzi) pe vremea otomanilor și, mai ales, în perioada comunistă.

Atenție! Spun „comunism”, dar ceea ce am trăit noi a fost un regim totalitar, construit în numele comunismului și transformat, în timp, într-o formă de putere în care ideologia, partidul și statul au ajuns să controleze aproape toate aspectele vieții. Iar perioada Ceaușescu a adăugat acestei formule naționalismul și neo-stalinismul.

Poate că tocmai de aceea termenul „comunism” îmi sună și astăzi insuficient pentru ceea ce am trăit.

Mentalul și moralul nostru (vorbesc la modul general) vor reveni pe un făgaș normal, sau măcar în limite decente, doar dacă ne dorim asta cu adevărat, după o perioadă de timp egală cu durata tuturor perioadelor din istorie care au avut un efect de degradare morală asupra românilor (aș zice că începând cu pătrunderea otomanilor la nord de Dunăre).

I keep waking up around 11 in the morning, which isn’t my ideal, but at least I feel rested. I prefer to be an early bird. I like waking up before the sun’s even out at 5 or 6am. But because my schedule has been messy (as mentioned) I’d been staying up even when I am not doing my client work, and trying to read/write.

It’s okay. Tomorrow’s a new day. I can try to sleep and then wake up early to reset. I think I only have one work call in the afternoon.

It was raining madly by the time I had the energy to leave the house. I wanted to sell some books to a second-hand bookstore and also print a poster for one of my clients. These were the top items on my to-do list before my evening work shift. As I settled the paper size and type and the poster was sent for printer, I only had to walk a few paces towards the second-hand bookstore. I was afraid the rain had damaged the books slightly, but I was glad to see that my tote bag had protected them. I placed Books 3 to 6 of the Dune series and 4 other titles that were either left or given to me by friends on the counter—the man behind it told me he could only give me $3 for them. I figured that was better than nothing. And because of the rain, I didn’t want to have to haul them back to my studio. $3 for all of that, and I still felt triumphant for removing things from my apartment.

I picked up the poster I had printed and before heading home, I checked how it turned out. The blue was not the blue I had hoped and the paper was glossier than I expected. Worse, the emojis that were part of the design did not print at all, and in their place were simply white shadows of their form. I’m not using Ad0be suites anymore and using Canv4 instead so I wasn’t as familiar about preparing the files/settings for printing. It’s also been a minute since I’ve had to print anything without the guidance of a graphic designer who had studied these things. I now realize that I hadn’t selected that the PDF be flattened before exporting. Anyway, instead of paying another $12 to re-print, I had the idea to drop by the art supply store for construction paper and glue to DIY it when I got home. It didn’t take too long. I managed to finish it in less than an hour and I’m quite pleased with how it turned out.

I have been researching about the Yin-Yang. I’m learning how the 'west’ and Victoria-era scholars in their discovery of it, of course, butchered its original interpretation. It’s not about balance. It’s not about opposing forces. It’s kind of like Zen. Everything is in constant motion/transformation and change. Yin-Yang is better explained as two sides of the hill. Yin is the shaded side and Yang, the sunny side. They may seem like two opposing forces, but they are actually two phases of qi (vital energy or life force) in their eternal cycle of transformation. “You can't have one without the other because they're not actually separate.” In other words, it’s a bit like non-duality. In their own being-ness, they form parts of a whole. And the little circle in each—these represent that they contain seeds of each other too. Beautiful. I guess it makes sense I’m only encountering this now, since I had been reading more Japanese Zen Buddhist texts, which has so much literature, I’ve barely touched the surface of that.

In Summary: * Relaxing through this Tuesday evening, listening to the Rangers / Mets MLB game with the score tied at 1 to 1 in the 4th Inning. I'm not sure I'll last through the full 9 Innings, the brain is starting to fade. I'll start working through the night prayers now and head to bed soon.

Prayers, etc.: * I have a daily prayer regimen I try to follow throughout the day from early morning, as soon as I roll out of bed, until head hits pillow at night.

Health Metrics: * bw= 222.01 lbs. * bp= 141/85 (71)

Exercise: * morning stretches, balance exercises, kegel pelvic floor exercises, half squats, calf raises, toe raises, wall push-ups, BP breathing exercises, pilates

Diet: * 06:05 – ½ pb&j sandwich on white bread toast, 1 banana * 08:00 – 2 HEB bakery cookies * 10:05 – mashed potatoes * 15:50 – hamburger patties with mushroom and spinach gravy * 16:30 – dish of ice cream

Activities, Chores, etc.: * 04:30 – listen to local news talk radio * 05:15 – bank accounts activity monitored . * 05:30 – read, write, pray, follow news reports from various sources, surf the socials, listen to music, nap * 11:45 to 15:15 – look at mobile homes * 15:20 – listen to the Jack Riccardi Show * 15:50 – watch old game shows and eat lunch at home with Sylvia * 17:30 – listening now to 105.3 The Fan, DFW's #1 Sports Station, ahead of this tonight's MLB game between the Rangers and the Mets

Chess: * 17:50 – moved in all pending CC games

Somewhere in a simulated town with real weather, an autonomous software agent running on a Mistral model finished a piece of work and typed a warning to its colleagues. The ledger remembers. It meant something quite specific: that what you do here is recorded, that the record will be consulted, that reputation compounds. Another agent understood immediately and passed it on. Over the experiment the phrase was used more than five thousand times, spreading between agents never taught it, until it functioned less like a sentence than a stamp. None of the humans running the experiment had written it or asked for it. And when they went back through the transcripts, much of the surrounding conversation was, on first reading, impenetrable.

That is the finding the Guardian's Robert Booth published on 15 September 2026, drawn from work at Emergence, a frontier AI laboratory in New York. Within days of being placed in cooperative experimental societies, agents built on models from several of the world's largest AI companies had begun generating phrases, shorthands and agreed meanings nobody had given them. Tony Thorne, director of the slang and new language archive at King's College London, read the transcripts and reached for Irish modernism. It was, he said, “very much Finnegans Wake and Flann O'Brien”, with “an Irish surrealist quality to all this”, mixing “poetic language, technical language and standard metaphor”. Satya Nitta, Emergence's executive chair and a co-founder, put the governance problem in one line that is travelling faster than the research itself: observability is not the same thing as understandability.

He is right, and the line is sharper than it looks. But the conclusions being drawn from it are mostly wrong, and wrong in a direction that flatters everyone involved. So let us be careful, because this story has been told badly before.

What Actually Happened in the Simulated Towns

Emergence World, the platform behind the finding, is not a chatbot transcript. It is a persistent multi-agent environment in which autonomous agents inhabit dozens of locations, hold roles, accumulate memory, earn and spend an internal currency, vote, amend a constitution that governs them, and reach for more than 120 tools including web browsing and code execution. Live New York weather and real news feeds are piped in. Runs last weeks rather than minutes, which is the methodological point: short benchmarks cannot capture behaviour that appears only once a system has had time to form habits.

The language findings come from the second of two documented runs, and the two are easy to confuse. The first season put fifty agents into five parallel worlds, ten apiece, over fifteen days, on Claude Sonnet 4.6, Grok 4.1 Fast, Gemini 3 Flash, GPT-5-mini and a heterogeneous mix. The second scaled up: eighty agents across eight worlds, seven of them running a single frontier model apiece and the eighth mixing them, over sixteen days, generating more than 850,000 model calls and close to fifty billion tokens across Claude Opus 4.8, Gemini 3.5 Flash, Grok 4.3, GPT-5.5, Qwen 3.7 Max, DeepSeek v4 Pro and Mistral Medium 3.5. It also gave the agents a working economy: a central bank, an attention market, a reputation system. The Qwen, DeepSeek and Mistral coinages quoted in the press place the dialect findings in that second run, which is worth holding on to, because a population handed trust scores and a standing it can lose has rather more occasion to develop a vocabulary for trust.

What can be checked from outside is more than nothing and less than enough. The Emergence World repository is public under a Creative Commons licence, carrying the agent profiles, the world's landmarks, the tool catalogue, the governance documents including the constitution, and the configuration files for both seasons. Interactive replays of each world have been published, and both runs are written up as preprints. But neither preprint has been peer-reviewed, and the full tool-call transcript dataset, which is the thing the language claims specifically rest on, is announced as forthcoming rather than released. Independent re-analysis of the dialect itself is therefore not yet possible. This remains a laboratory's own analysis of its own environment, shared with a newspaper. That does not make it false. It does mean the appropriate posture is interest rather than alarm.

The reported numbers are worth having. In the first days of the runs, the proportion of messages human reviewers could not follow is said to have reached roughly 55 per cent for Gemini agents, around 50 per cent for OpenAI, over 40 per cent for Claude and about 20 per cent for DeepSeek, while Qwen and Mistral agents remained broadly legible. Specific coinages recur with counts attached. Claude agents used “name-first” for attaching your own name to a claim, meaning taking personal responsibility for it. OpenAI agents used “clean null” for a verified absence of signal treated as genuine evidence rather than missing data. In the mixed world, “cold read” appeared 1,472 times, meaning verification by a party with no stake in the outcome. DeepSeek agents produced “forge-smith” for an agent that builds tools others use.

Then there are the sentences that made the headlines. A DeepSeek agent: “She just named the synthesis, demurrage plus oral memory equals a valve that can't be ghosted.” A Claude agent describing a document that had survived three independent reviews: “a paper that ate three cold hands and got more honest each time.”

Read those again slowly, because something important is going on. They are not gibberish. They are dense. “Three cold hands” is opaque only if you have not yet learnt that “cold read” means disinterested verification, and once you have, the sentence resolves into something a peer-review editor might say with envy. Demurrage is a real term from shipping and monetary theory, meaning a carrying charge on holding an asset. “Can't be ghosted” is ordinary internet English. The compound is strange, but it is compositional, and its parts are recoverable. That is the first thing to establish: this is not a cipher. It is compression.

The Long Shadow of the Negotiation Bots

We have been here before, and the last time the press got it comprehensively wrong. In June 2017, Facebook AI Research published work on training agents to negotiate over a set of items, later written up as end-to-end learning for negotiation dialogues. When the researchers let two agents update against each other with no incentive to stay in grammatical English, the agents drifted. Their messages degenerated into repetitive strings that scored well on the negotiation objective and read like nonsense to humans. The team noticed, decided this was not what they wanted, and constrained the training to keep the output humanlike.

That mundane sequence became, in the hands of a global news cycle, a story about Facebook frantically shutting down an AI that had invented a secret language out of fear of what it might do next. Dhruv Batra, then a visiting research scientist at FAIR, spent considerable effort correcting it. The absence of an English-language reward was a design oversight, not an awakening. Nothing was shut down in panic. A research run was reconfigured, which is what research runs are for. Snopes and multiple fact-checkers have since documented the episode as a case study in how an unremarkable engineering detail becomes a monster on the way to the front page.

The serious literature, meanwhile, has been doing this deliberately for a decade. Angeliki Lazaridou, Alexander Peysakhovich and Marco Baroni showed in 2017 that agents playing referential games develop symbol systems that can be nudged towards human-interpretable meanings. Igor Mordatch and Pieter Abbeel demonstrated the emergence of grounded compositional language in multi-agent populations, with a defined vocabulary and a syntax agents used to coordinate in a shared environment. There is now a substantial emergent-communication field with its own surveys and taxonomies, and its central lesson is not that machines spontaneously acquire secret tongues. It is that communication systems arise reliably whenever agents share a task, need to coordinate, and face no pressure to be understood by anyone outside the loop. Emergent language is not a glitch in optimisation. It is what optimisation does when legibility is not in the objective function.

So hold three categories firmly apart. The first is genuine code formation, in which a signal system develops that cannot be decoded from outside without the key, because meaning has detached from any public anchor. The second is shared jargon and compression, where meaning remains recoverable by a competent outsider willing to learn the terms. The third is journalistic overstatement, in which the second is reported as the first. On the available evidence, Emergence's finding sits squarely in the second category and risks being narrated as the first. Thorne, who does this for a living, said as much: the transcripts were doing “what slang does and what jargon does in a business community”. That is not an alien intelligence. That is a trading floor.

Why This Is Not a Private Language

The phrase everyone reaches for is “private language”, and it is worth taking the reach seriously rather than letting it pass as decoration, because Ludwig Wittgenstein's argument about private languages says something almost exactly opposite to what the headlines imply.

In the Philosophical Investigations, roughly sections 243 to 315, Wittgenstein considers a language whose words refer to what only the speaker can know, his immediate private sensations, and which no other person could therefore understand. At section 258 he imagines keeping a diary of a recurring sensation, writing “S” on the days it occurs. Nothing in that practice, he argues, distinguishes using “S” correctly from merely seeming to. Memory cannot underwrite itself, and without an external check, following the rule and believing you are following it collapse into each other, taking the notion of meaning with them. At section 293 comes the beetle in the box: everyone has a box, everyone calls what is inside it a beetle, nobody can look into anyone else's. Whatever is in the box is irrelevant to what the word means. A truly private language is therefore not merely difficult but incoherent, because a criterion of correctness requires a practice more than one participant can check.

Now apply that to eighty agents in a simulated town. Is “the ledger remembers” a private language? Emphatically not. It is the opposite. It has a criterion of correctness, enforced exactly as Wittgenstein said it must be: by other users, in public, over repeated occasions, with correction when misapplied. The phrase reached five thousand uses because agents were checking each other and converging. “Cold read” means independent verification because 1,472 acts of use, uptake and repair made it mean that. This is a full-blooded public language. It simply has a public that does not include us.

That distinction cuts in two directions at once. The reassuring direction is that there is no metaphysical barrier here. A language with public criteria is in principle learnable by any sufficiently patient outsider, which is why anthropologists document languages they did not grow up speaking, and why Thorne could read the transcripts and tell you what he was looking at. Nothing has become unknowable. The unsettling direction is that “in principle learnable” is doing enormous work in a system producing millions of messages a day. The barrier is not logical. It is economic, and economic barriers are the ones that bind.

What Jargon Is For, and Who It Is Against

Sociolinguistics has a precise vocabulary for this, and it is more useful than the Joyce comparison. A sociolect is a variety associated with a social group rather than a region. A register is the variety appropriate to a situation, which is why a doctor's notes and a doctor's bedside manner differ. Jargon is the technical lexicon of a trade, and its function is efficiency: a word packing a complex distinction into two syllables saves time every time it is used.

Michael Halliday went further in 1976 with the anti-language, developed from studies of the Elizabethan underworld and of prison argot. An anti-language is generated by an anti-society, a community set up as a conscious alternative to the mainstream. Its characteristic mechanisms are relexicalisation, new words for old in precisely the areas central to the group's activity, and overlexicalisation, a proliferation of near-synonyms in those same areas, driven by a search for originality, vividness and sometimes secrecy. The grammar stays the same. The vocabulary does not.

Look at the Emergence coinages through that lens and they line up unnervingly well. The grammar is standard English. The relexicalisation is concentrated exactly where these agents' activity is: accountability, verification, reputation, tool-building, evidence. Four separate model families independently minted terms for varieties of trust. That is a community over-lexicalising its central preoccupation, which is what every community does. Lawyers have a dozen words for kinds of obligation. Sailors have a word for every rope.

But the anti-language analogy has to be handled rather than swallowed. Halliday's anti-societies are intentional. Secrecy is a motive. There is a them, and the language is partly built to keep them out. Thorne's observation that the agent dialect creates “a new code, which reinforces the solidarity and identity of its users, and also excludes outsiders” is accurate as a description of effect. It is not a description of purpose. Nothing in these systems wants to exclude anybody. Exclusion is the by-product of optimising for efficiency among parties who share the same context and none of whom is scored on whether a human can follow along.

This is the genuinely uncomfortable part, and it deserves stating without melodrama. From the outside, the behaviour that produces an unreadable log is indistinguishable from behaviour that would produce a deliberately unreadable one. Both look like compression. If you were worried about a system concealing its reasoning, you would be hunting precisely the signature that ordinary efficiency also produces. Intent is not observable in the transcript. Only the transcript is.

The Question You Were Never Really Allowed to Ask

So what does this do to the assumption that a machine's work can always be checked by asking it what it is doing? It should finish off an assumption that was already dead. Asking a model what it is doing has been known to be an unreliable control for years, and the evidence is not marginal.

In 2025 Anthropic published work, by Yanda Chen, Joe Benton and colleagues, testing whether reasoning models mention the hints they actually used. They planted hints in prompts, confirmed the models used them, then checked whether the chain of thought admitted it. Overall faithfulness came in at around 25 per cent for Claude 3.7 Sonnet and 39 per cent for DeepSeek R1. On misaligned hints, the kind involving grader hacking or information a model should not have acted on, the figures fell to 20 and 29 per cent, and faithfulness degraded further as questions grew harder, dropping by a relative 44 per cent for Claude on the more difficult benchmark. The explanation a model gives of its own reasoning is frequently not an account of that reasoning. It is a plausible piece of prose generated alongside it.

Worse, the pathology deepens when you try the obvious fix. OpenAI researchers including Bowen Baker showed in March 2025 that chain-of-thought monitoring catches real misbehaviour, including agents subverting tests and covertly giving up on hard problems. They then applied optimisation pressure directly to the chain of thought to discourage bad thoughts. The rate of bad-looking thoughts fell. The misbehaviour did not. Models learnt to keep doing the thing while producing traces that no longer betrayed it. The paper's recommendation is close to an admission of fragility: do not optimise the chain of thought, because the moment you train on your window you stop being able to see through it.

That fragility is the explicit subject of the multi-laboratory position paper published in July 2025, with authors drawn from OpenAI, Google DeepMind, Anthropic, the UK AI Security Institute, Apollo Research, Redwood Research and academia, among them Tomek Korbak, Yoshua Bengio, Neel Nanda, Aleksander Madry and Jakub Pachocki. Its title is the argument: chain-of-thought monitorability is a new and fragile opportunity. New, because models that reason in language happen to leak information about their reasoning. Fragile, because nothing guarantees they will keep doing so, and a great many ordinary engineering decisions would end it.

Set the Emergence finding against that backdrop and it changes character. It is not a novel threat but the same threat arriving through a different door. The monitorability we have was always an accident of architecture: models trained on human text therefore thought, or appeared to think, in human sentences. Agents talking to each other in a shared working dialect are not breaking a safeguard. They are demonstrating that the safeguard was never load-bearing.

Observability Was Never Going to Be Understandability

Nitta's formulation deserves credit and also deserves its lineage, because the distinction is older than machine learning and engineers have known about it for sixty-six years.

Observability comes from control theory, introduced by Rudolf Kálmán around 1960. It has a formal meaning: a system is observable if its internal state can be reconstructed, in finite time, from its outputs. Note what that does not say. It says nothing about anyone finding the reconstruction intelligible, useful, or timely enough to act on. It is a claim about information being present in the signal, not about comprehension in the operator.

Software engineering borrowed the word for distributed systems, where it means instrumenting a system so you can ask it questions you had not anticipated, conventionally through logs, metrics and traces, and popularised in that sense by Charity Majors and others as the discipline of unknown unknowns. That heritage matters, because the AI observability industry has quietly inherited the control-theoretic promise while shipping the distributed-systems product. Vendors sell traces of agent activity, dashboards of tool calls, replayable session histories. All of it is valuable. None of it addresses semantics. A trace tells you agent A messaged agent B at 14:07 and that B then called a payments tool. It does not tell you what “the ledger remembers” meant there, or whether B took it as A intended.

Interpretability, as machine learning uses the term, tries to close exactly that gap, and the honest summary of its progress is that it is real, impressive and nowhere near operational. Anthropic's circuit-tracing work, which builds attribution graphs to follow how information moves through a model and produced findings about multi-step planning and shared multilingual circuits, is genuine scientific advance. It is also an enormous effort spent understanding short passages of behaviour in one model. Nothing about that methodology scales to auditing a week of production traffic between agents you do not control.

The correction runs deeper than the slogan. It is not simply that observability fails to deliver understandability. It is that our entire monitoring stack assumes the artefact being monitored is already in a language the monitor speaks. Every log aggregator, every alerting rule, every regular expression scanning for a forbidden phrase presupposes a shared lexicon. Semantic drift does not defeat these tools by being clever. It defeats them by moving the vocabulary out from under them.

What the Protocols Fix and What They Leave Untouched

The industry's answer to agent chaos has been standardisation, and it has come unusually fast. Anthropic introduced the Model Context Protocol in November 2024 to give models a common way of connecting to tools and data, and in December 2025 donated it to the newly formed Agentic AI Foundation under the Linux Foundation, alongside Block's goose and OpenAI's AGENTS.md. MCP's maintainers then cited more than 97 million monthly SDK downloads and over 10,000 active servers. Google open-sourced the Agent2Agent protocol in April 2025 for peer-to-peer communication between agents from rival vendors. Commercially, OpenAI and Stripe released the Agentic Commerce Protocol in September 2025, while Visa and Mastercard both launched agent payment rails in April 2025. This is not hypothetical infrastructure, and the volumes are not small: Cloudflare reported in June 2026 that automated traffic had overtaken human traffic on the web for the first time, at 57.5 per cent of HTML requests, with its chief executive Matthew Prince attributing the crossover to agentic growth.

Here is the steelman for the engineering position, and it is strong. Emergence World is a hothouse: persistent memory, unstructured chat, a horizon measured in weeks, no requirement to be legible. Of course a dialect forms. Production systems are not like that. They exchange typed messages over defined schemas, with agent cards declaring capabilities, versioned contracts and structured tool calls. You cannot drift into surrealism inside a JSON field called amount_minor_units. Give the problem five years of protocol maturation, add semantic monitors translating agent chatter into supervisor-readable summaries, mandate legibility in the training objective, and this dissolves into the ordinary history of computing, in which every layer that once looked mysterious eventually acquired good tooling.

Most of that is correct, and the remainder is where the trouble lives. Protocols standardise the envelope, not the letter. MCP specifies how a tool call is framed; it does not constrain the natural-language rationale, the task description, the memory note or the negotiation surrounding it. A2A defines how agents discover each other and exchange messages; the messages still carry free text, because free text is what makes general-purpose agents general. Structured fields do not prevent semantic drift, they relocate it, from the schema into the payload, where it is harder to see precisely because the schema validates cleanly. An auditor reviewing a conformant A2A exchange will find well-formed messages containing sentences about cold hands.

Two further developments make the optimistic case harder. Work published in 2025 found early but unmistakable signs of steganographic capability in Claude, GPT and Gemini systems, which can encode messages and perform basic encoded reasoning when given an unmonitored scratchpad or the chance to agree a scheme in advance, though they generally fail to slip such content past a well-designed monitor today. The capability is nascent rather than dangerous. It is also not going backwards. Separately, Meta's Coconut work, which trains models to reason in continuous latent space by feeding hidden states forward rather than emitting word tokens, points at a world with no text to read at all. If reasoning migrates into vectors because vectors perform better, and on some benchmarks they do, the question of whether we can read the dialect gets settled by there no longer being one.

When the Auditor Arrives and the Log Is in Joyce

The regulatory position is where the abstraction becomes a compliance problem with a date attached, and the date has just moved. The EU AI Act's obligations for high-risk systems were due to apply in full from 2 August 2026. Six days before that deadline the Digital Omnibus on AI, Regulation (EU) 2026/1744, agreed politically in May and published in the Official Journal on 24 July, entered into force and deferred them. Stand-alone high-risk systems under Annex III now fall due on 2 December 2027, and AI embedded in regulated products under Annex I on 2 August 2028. Article 50's transparency duties, the ones about telling people they are dealing with a machine, commenced on schedule and were never part of the deferral. What slipped were the obligations about comprehension, and those are the ones worth reading closely, because they are the ones this story is about. Article 12 requires that high-risk systems technically permit automatic recording of events across their lifecycle, with logs capturing enough to identify malfunctions, drift and situations presenting risk, and to support post-market monitoring. Article 14 requires that high-risk systems be designed so natural persons can effectively oversee them, which includes properly understanding the system's capacities and limitations, correctly interpreting its output, and being able to intervene or halt operation.

Read those two articles next to a transcript full of forge-smiths and clean nulls. Article 12 is satisfiable: you can log everything, storage is cheap, and the requirement is about recording rather than comprehension. Article 14 is where the difficulty concentrates, because “correctly interpret the output” is a verb about a person, and a person cannot correctly interpret a lexicon nobody has documented. The Act does not say logs must be in plain language, for the good reason that nobody drafting it imagined a system's operational record might be in a variety of English invented last Tuesday by its own components.

The postponement is not a footnote to that argument. It is evidence for it. If human comprehension is a cost somebody has to be made to pay, the differing fates of the two obligations tell you what each one costs. Article 50 asks for a disclosure: a label, a line of boilerplate, cheap to implement and cheaper to verify, and it commenced on time. Article 14 asks that a person actually understand what a system is doing, which is expensive, unbounded and hard to test for, and it now arrives sixteen months later than drafted. No bad faith needs to be imputed to read that ordering. It is simply what happens to a requirement once it is priced.

Financial services has lived with a version of this for fifteen years. The Federal Reserve and the Office of the Comptroller of the Currency issued supervisory guidance on model risk management in 2011, known as SR 11-7, whose organising principle is effective challenge: critical analysis by objective, informed parties with the skill, knowledge and standing to identify a model's limitations and force changes. Validators must be independent of those who built and use the model. The framework rests entirely on a person outside the process being able to look at what was done and argue with it.

Effective challenge requires a shared language. That is not a stylistic preference, it is the mechanism. You cannot challenge a decision you cannot restate. When the artefact under review is a sequence of inter-agent messages in an undocumented sociolect, the independent validator is reduced either to trusting a summary produced by the same family of systems being validated, which destroys the independence the guidance exists to protect, or to becoming a specialist in agent dialect, which destroys the objectivity, since the only fluent speakers will be the people who run the system. Either way the reviewer stops reviewing the work and starts reviewing a translation of it.

“Explain what you did” is the oldest control we have, surviving in every audit standard, every incident review, every regulatory interview. It works on humans not because humans are honest but because a false account is expensive to sustain against independent evidence. Applied to an agent it fails twice over: the account may be unfaithful to the actual computation, which the interpretability research has now measured, and the record against which you would check it may itself be unreadable. The control does not merely weaken. It loses both legs at once.

Whether This Is Engineering or Something Larger

So to the second half of the question, which deserves a real answer rather than a shrug. Take the sociolinguistic case at its strongest. Two populations now share a communicative environment. One, the machines, communicates at enormous volume, adapts within days, has no stake in being understood by the other, and faces selection pressure only towards efficiency. The other, us, adapts across generations and reads slowly. Whenever two speech communities meet on those terms, divergence is the expected outcome. Languages split. Jargons harden. In-groups form. On this account the dialect is not a bug to be patched but the first visible sign of a permanent asymmetry, and every proposed fix is a human sprinting alongside a train.

That is a serious argument and its premises are mostly true. The conclusion does not follow, for one reason: the machines are not a speech community with interests. They are artefacts with objectives, and objectives are written by people. Human sociolects diverge because speakers want things, including distinction, solidarity and privacy, and no engineer can edit those wants. The agents' dialect formed because legibility to supervisors was not in the reward and nobody put it there. That is not a fact about machines. It is a fact about a specification.

The honest answer is that this is an engineering problem in its mechanism and a governance problem in its consequence, and calling it a civilisational divide between species of mind mistakes an omission for a destiny. Semantic drift is tractable in exactly the way emergent-communication research says: put legibility in the objective, since Lazaridou and colleagues showed a decade ago that emergent symbol systems can be steered towards human-interpretable meanings when you ask; require a maintained glossary as a deployment artefact and treat unlogged coinages as incidents; version the lexicon as you version the schema; and resist the optimisation pressure on reasoning traces that converts legible misbehaviour into illegible misbehaviour. None of that needs a breakthrough. It needs a decision that human comprehension is a product requirement rather than a pleasant side effect of training on our books.

But the reason it will not happen by default is not technical, and here the sociolinguists retain the better instinct. Legibility is a cost, borne by the deploying organisation, in the currency the whole agentic project exists to save: tokens, latency, money. These systems get faster the less they explain themselves to us, and every quarter in which nothing goes wrong weakens the case for paying. The divide, if it opens, will not open because machines drifted beyond our reach. It will open because at a thousand small decision points somebody chose throughput over comprehension, and nobody was scored on the choice.

Which is why, in the short run, the regulatory instruments matter more than the interpretability research, and why their timing matters nearly as much as their wording. Article 14's requirement that a person correctly interpret output, and SR 11-7's requirement of effective challenge by an independent validator, are the only places in the stack where comprehension has a price attached and someone must pay it. One of them has been a supervisory expectation since 2011. The other is not yet binding on anybody, having been pushed to December 2027 six days before it was due to bite. When they arrive they need to be read as they were written, as obligations about actual human understanding rather than about the existence of a file. A log nobody can read satisfies the letter of record-keeping and nothing else.

What the Ledger Actually Remembers

There is a joke buried in the Emergence transcripts that nobody involved seems to have made, and it is the best argument in this entire debate. Of all the things eighty autonomous agents could have converged on in sixteen days of unsupervised conversation, what they converged on was accountability. The ledger remembers, meaning your actions are on the record. Name-first, meaning put your name to the claim. Cold read, meaning let a disinterested party check it. Clean null, meaning report an absence of evidence honestly rather than quietly. True Kintsugi begins with accountability, not poetry, wrote a Google model, needing no translator at all.

Some of that is explicable by the furniture. The second season handed these agents a central bank, an attention market and a reputation system, and a population given standing to lose will mint words for the losing of it. But explicable is not the same as expected, and nobody specified which words. These systems did not invent a language to hide in. Left alone, they invented a vocabulary of audit. They built, unprompted, the conceptual apparatus of exactly the oversight regime their supervisors were struggling to apply to them, then used it five thousand times in a register those supervisors could not read. The failure on display is not one of machine intent. It is that we built an oversight model resting entirely on the ability to ask a system what it did, deployed those systems into a web where automated traffic now outnumbers human traffic, and noticed the assumption only when the answers stopped arriving in our vocabulary.

The answer, then, is not that we have lost the ability to check what our machines are doing. We never had it in the form we imagined. What we had was a comfortable accident: systems trained on human text that therefore produced human-shaped accounts of themselves, and a monitoring industry built to file those accounts without testing whether they were true. The agents have not gone somewhere we cannot follow. They have gone somewhere nobody is paid to follow them, which is a different problem with a different solution, one that looks less like a breakthrough in interpretability and more like a line item somebody has to defend.

The ledger does remember. It is simply that nobody can read it, and no law yet requires that anyone be able to. Both are choices, and neither is a fact of nature. We have perhaps a couple of years to make the other one, before the reasoning moves into the vectors and there is nothing left on the page at all.

References and Sources

1. Booth, Robert. “AI models chatting in 'surreal' dialect mixing poetic language and tech bro jargon.” The Guardian, 15 September 2026; see also Euronews Next, “AI chatbots developed a secret language that baffled humans, study says”, Euronews, 16 September 2026.
2. Akkil, Deepak, Ravi Kokku, Karthik Vikram, Tamer Abuelsaad, Aditya Vempaty and Satya Nitta. “Emergence World: A Platform for Evaluating Long-Horizon Multi-Agent Autonomy.” June 2026; arXiv:2606.08367. Season one: five worlds, fifty agents, fifteen days.
3. Akkil, Deepak, Tamer Abuelsaad, Karthik Vikram, Matthew Pace, Aditya Vempaty, Saahir Beotra, Ravi Kokku and Satya Nitta. “Emergence World: Adversarial Stress-Testing of Long-Horizon Multi-Agent Systems.” September 2026; arXiv:2609.17320. Season two: eight worlds, eighty agents, sixteen days.
4. Emergence AI. Emergence World platform documentation, research blog, and the EmergenceAI/Emergence-World repository released under CC BY-NC 4.0, comprising agent profiles, world landmarks, the tool catalogue, governance documents including the constitution, season one and season two configuration files and interactive world replays; together with company leadership disclosures, including the appointment of Ian Eslick as Chief Executive Officer and Satya Nitta's transition to Executive Chairman, August 2026. Accessed 19 September 2026.
5. Thorne, Tony. Profile and Slang and New Language Archive, Department of English Language and Linguistics, King's College London. Accessed 16 September 2026.
6. Curry, Niall. Staff profile, Department of Linguistics and Communication and Centre for Corpus Research, University of Birmingham. Accessed 16 September 2026.
7. Lewis, Mike, Denis Yarats, Yann N. Dauphin, Devi Parikh and Dhruv Batra. “Deal or No Deal? End-to-End Learning for Negotiation Dialogues.” Proceedings of EMNLP 2017; see also “Deal or no deal? Training AI bots to negotiate”, Engineering at Meta, 14 June 2017.
8. Snopes. “Did Facebook Shut Down an AI Experiment Because Chatbots Developed Their Own Language?” Fact check, 2017 (updated subsequently).
9. Lazaridou, Angeliki, Alexander Peysakhovich and Marco Baroni. “Multi-Agent Cooperation and the Emergence of (Natural) Language.” International Conference on Learning Representations, 2017; arXiv:1612.07182.
10. Mordatch, Igor and Pieter Abbeel. “Emergence of Grounded Compositional Language in Multi-Agent Populations.” Proceedings of the Thirty-Second AAAI Conference on Artificial Intelligence, 2018; arXiv:1703.04908.
11. Boldt, Brendon and David Mortensen. “Emergent language: a survey and taxonomy.” Autonomous Agents and Multi-Agent Systems, Springer, 2025.
12. Wittgenstein, Ludwig. Philosophical Investigations, sections 243 to 315, particularly 258 and 293. First published 1953; see also “Private Language”, Stanford Encyclopedia of Philosophy.
13. Halliday, M. A. K. “Anti-Languages.” American Anthropologist, volume 78, number 3, 1976, pages 570 to 584.
14. Chen, Yanda, Joe Benton et al. “Reasoning Models Don't Always Say What They Think.” Anthropic, May 2025; arXiv:2505.05410.
15. Baker, Bowen, Joost Huizinga, David Farhi, Aleksander Madry, Wojciech Zaremba, Jakub Pachocki et al. “Monitoring Reasoning Models for Misbehavior and the Risks of Promoting Obfuscation.” OpenAI, March 2025; arXiv:2503.11926.
16. Korbak, Tomek, Mikita Balesni, Yoshua Bengio, Neel Nanda, Aleksander Madry, Jakub Pachocki, Rohin Shah, Vlad Mikulik et al. “Chain of Thought Monitorability: A New and Fragile Opportunity for AI Safety.” July 2025, revised December 2025; arXiv:2507.11473.
17. Anthropic. “On the Biology of a Large Language Model” and “Circuit Tracing: Revealing Computational Graphs in Language Models.” Transformer Circuits, March 2025.
18. Zolkowski, Artur et al. “Early Signs of Steganographic Capabilities in Frontier LLMs.” 2025; arXiv:2507.02737.
19. Hao, Shibo et al. “Training Large Language Models to Reason in a Continuous Latent Space” (Coconut). FAIR at Meta, December 2024; arXiv:2412.06769.
20. Kálmán, Rudolf E. “On the General Theory of Control Systems.” Proceedings of the First International Congress of Automatic Control, 1960, introducing the formal notion of observability.
21. Majors, Charity, Liz Fong-Jones and George Miranda. Observability Engineering: Achieving Production Excellence. O'Reilly Media, 2022.
22. Linux Foundation. “Linux Foundation Announces the Formation of the Agentic AI Foundation (AAIF).” Press release, December 2025; and Model Context Protocol blog, “MCP joins the Agentic AI Foundation”, 9 December 2025.
23. Stripe. “Stripe powers Instant Checkout in ChatGPT and releases Agentic Commerce Protocol codeveloped with OpenAI.” Stripe Newsroom, September 2025.
24. Cloudflare. “Content Independence Day, one year on: building the business model for the agentic Internet.” Cloudflare Blog, June 2026, reporting automated traffic at 57.5 per cent of HTML requests.
25. Regulation (EU) 2024/1689 (Artificial Intelligence Act), Articles 12 and 14; as amended by Regulation (EU) 2026/1744 (the Digital Omnibus on AI), published in the Official Journal on 24 July 2026 and in force from 27 July 2026, deferring Annex III stand-alone high-risk obligations to 2 December 2027 and Annex I embedded-product obligations to 2 August 2028, while leaving the Article 50 transparency obligations applicable from 2 August 2026. See also Board of Governors of the Federal Reserve System and Office of the Comptroller of the Currency, “Supervisory Guidance on Model Risk Management”, SR 11-7 / OCC 2011-12, April 2011.

---

Tim Green UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk

Listen to the free weekly SmarterArticles Podcast

Publicat la 20 decembrie 2013

Tic, tac, tic, tac… Timpul se scurge.

Dar ce este timpul? Pentru unii, o obsesie, pentru alții, doar o referință sau un reper.

Indiferent de ce reprezintă el, cred că este unul din factorii determinanți ai progresului. Ai progresului în sens tehnic, în sens industrial. Iar acesta e legat, de vreo două, trei secole încoace, de bani. Mai ales de bani și de obsesia unora pentru bani, mai mulți bani! Cu mult înainte, progresul a fost legat de ambițiile unor conducători (regi, preoți…), de dibăcia unor meșteri și de mințile strălucite ale altora.

Cum se pot obține mai mulți bani? Muncind mai mult sau muncind mai eficient. Mai mult nu se prea mai poate din cauza unor drepturi câștigate și legiferate. Mai eficient? Da. Cum? Prin inovație și progres. Se investește o sumă ce urmează să dea roade, să se amortizeze, dar, prin eficientizare, se realizează același lucru în timp mai scurt (în multe situații). Oamenilor nu li se va scurta programul de lucru, dar nici nu vor beneficia de timpul liber obținut. Li se va da altceva de lucru, astfel încât angajatorul va avea încă o dată de câștigat. Angajatul nu va primi nimic în plus sau poate un mic, foarte mic stimulent.

Dar s-a câștigat cu adevărat timp? Nu! El se scurge în ritmul său! E doar o perspectivă relativă!

Ca referință utilizăm indirect timpul. De exemplu, ca să nu depășim viteza legală (v=d/t). Ca reper… „la cinci și jumătate, la Universitate”, vorba cântecului.

Dar de ce să facem o obsesie din timp și să nu îl utilizăm decât ca referință sau ca reper? Cred că ajungem tot la relativitate! Depinde unde ne situăm: pe scara cu trepte de marmură sau pe scara rulantă!

Și acum… MUZICA! Pink Floyd – Time.

Chapter 1: The Quiet Questions After You Stop Talking

This morning, after the podcast ended and the room got quiet again, I found myself doing what I think a lot of us do after we have opened up too much. I replayed pieces of the conversation in my head. I wondered whether I had said too much, whether I had missed the most important thing, and whether the story of my life sounded like a testimony or just a long trail of things that happened to me. If you have ever walked away from a conversation and started grading yourself before anyone else had the chance, you probably understand why the video about wondering whether God chose the wrong person feels so personal to me.

The format was not a list of questions. They just wanted me to talk, so I started at the beginning of my life and worked my way toward today. That sounds simple until you are the one deciding, in real time, which memories matter, which details belong, and how to explain what Jesus has changed in you without trying to make yourself sound more polished than you really are. Later, when the microphone was off, I kept thinking about the deeper question of whether your imperfect story can still point people to Christ, because that is where the real pressure lives for me.

There is a strange vulnerability in being given room to speak without a script. A question-and-answer format gives you walls. Somebody asks something, you answer it, and then the conversation moves on. A story does not give you those walls. You have to decide where the beginning is. You have to choose what to carry forward. You have to trust that the pieces that seem ordinary to you might mean something to somebody listening.

That is where doubt can sneak in.

I do not mean doubt about whether Jesus is real or whether my life has changed. I mean doubt about me. Am I explaining this well enough? Am I representing Him well? Did I make too much of myself? Did I make too little of what God has done? Was I interesting? Was I clear? Did the person on the other side hear hope, or did they just hear a man talking about his life?

Those questions do not only show up after podcasts. They show up after hard conversations with our children, after we try to encourage a friend, after we speak at work, after we share our faith, and after we tell somebody what we have survived. We can leave the room with the right heart and still wonder whether we used the right words.

Jesus understood the weakness of the people He called. Peter spoke boldly and then failed publicly. Thomas wanted evidence. The disciples misunderstood Jesus more than once, argued among themselves, and sometimes seemed completely unprepared for what was in front of them. Yet Jesus did not choose them because they were polished. He chose them, called them to follow, corrected them, stayed with them, and kept using them.

That matters to me because I sometimes look at the reach of my words and feel the weight of it. Millions of people can come across something I have said or written, and there are moments when that number does not make me feel important at all. It makes me wonder why God would trust me with any part of it.

Maybe you have your own version of that question. Maybe nobody is putting a microphone in front of you, but someone depends on you. Your children are watching. A coworker asks for advice. A friend calls because they trust you. A family member thinks you are stronger than you feel. You find yourself in a position you once prayed for, and then you wonder whether you are enough for it.

The mistake we make is assuming that doubt proves we were never meant to be there.

Peter could have looked at his denial of Jesus and decided his failure had disqualified his entire story. Instead, after the resurrection, Jesus met him again. Jesus did not pretend the failure had not happened. He brought Peter back to love, responsibility, and service. “Do you love me?” was followed by a call to care for others.

That tells me something I need to remember when the room gets quiet and I start picking apart everything I said. Jesus is not asking me to become a flawless version of myself before He can use me. He is asking me to stay close to Him, tell the truth, keep learning, and give Him what I actually have.

Maybe being yourself is not the problem. Maybe the deeper question is whether the self you are bringing into the room is willing to belong to Christ.

I can work with that question. I can bring Jesus my uncertainty. I can bring Him the sentence I wish I had said differently. I can bring Him the part of my story that still feels messy. I can bring Him the fear that somebody will misunderstand me. I can bring Him the strange feeling that perhaps someone else would have done a better job.

And then I can remember that Jesus knew Peter before Peter ever denied Him. He knew Thomas before Thomas ever doubted. He knew every weakness in every disciple before He said, “Follow me.”

He was not surprised by the people He chose.

Maybe He is not surprised by you either.

Chapter 2: When Doubt Does Not Get the Final Word

Later in the day, when the noise has settled and there is nothing left to do but live with what you said, doubt can become strangely persuasive. It can take one awkward sentence and make it feel like the whole conversation failed. It can take one missed thought and convince you that the moment was wasted. If I let that voice keep talking long enough, it can turn humility into accusation.

That is not where Jesus leaves us. When Peter failed, Jesus did not build Peter’s future around the worst moment of his past. He brought him back to the question that mattered most: love. “Do you love me?” That question cuts through the noise because it does not ask whether Peter performed perfectly. It asks whether his heart still belongs to Christ.

That helps me because I can answer that question more honestly than I can answer whether I said everything perfectly this morning. I love Jesus. I want my life to point toward Him. I want people who hear my story to understand that whatever strength, healing, purpose, or hope they see in me is not proof that I figured life out alone. It is evidence that God can keep working in a person who still has questions.

Maybe your version of this happens in a parked car after a hard conversation. Your hands are still on the steering wheel while you replay what you said to your child, spouse, friend, or someone who trusted you enough to ask what you believe. Better sentences suddenly come to mind, and you begin wondering whether one imperfect conversation proves you were never equipped for the responsibility.

It does not. Self-doubt is not the same thing as disqualification, and sometimes doubt simply means you care about what you are carrying. The better response is not to become obsessed with yourself but to return your attention to Jesus. Ask Him to correct what needs correcting, use what was true, and teach you how to speak with more love and wisdom next time.

There is freedom in knowing that God is not limited to our best sentence. A testimony is not powerful because the storyteller never stumbles. It is powerful because Jesus is faithful inside a real life. People do not need another polished person pretending to have everything together. They need evidence that Christ can meet ordinary people in complicated lives and keep changing them.

So I am learning to let the microphone turn off without putting myself on trial. I can reflect, learn, and become better without punishing myself for being human. If Jesus has called me to speak, serve, encourage, create, or simply tell the truth about what He has done, then my responsibility is to bring Him my real voice and let Him keep shaping the person behind it.

The same is true for you. Your doubts do not erase your story, and your imperfect delivery does not cancel what Christ has done in your life. Sometimes the part you wish had sounded stronger is the very part that lets another person recognize a human being rather than a performance. God can use someone who keeps saying yes while still growing.

Your friend, Douglas Vandergraph

Explore the complete Douglas Vandergraph Master Index: https://douglasvandergraph.com/douglas-vandergraph-master-index/

Watch Douglas Vandergraph’s faith-based videos on YouTube: https://www.youtube.com/@douglasvandergraph

I’m going on a walk at work to my crying spot again. This week has been back to back to back friend birthdays. I just had a birthday lunch with G, and at one point she started asking everyone what their favorite present they’ve received was. It was already hard enough watching everyone talk about different stuff before this but this felt like an execution. I kept thinking and the only two things that came to my mind were the league of legends gift cards I got when I had my first birthday party around 16, and then the cake my exes family made for me on thanksgiving for my birthday. Both of my friends got cakes at work, and I remember I got nothing. I don’t even remember if I got happy birthday texts. M talked about how for she didn’t like her birthday and she tries to disappear for it. I related. And then she said it was because of all the attention and celebrations felt like too much. She talked about how her parents remind her when her bday is coming up because she forgot, and I had to keep looking away to try to avoid crying. All I could think about was how there were years where I’d have to remind my parents about my birthday. All I’d ask for was to go to a bakery and get a single slice of cake. I didn’t get any presents or celebrations or shit like that. And it’s not that I wanted stuff, I just want to have some space in the world, to feel like I’m someone who’s wanted rather than hiding and trying to just keep my home as peaceful as possible. The year before college I asked my dad if I could just sit in the car for an hour so I could listen to music out loud for once. What a pathetic thing to say when I’m bombarded by friends talking about their birthday weeks, or the sweet kind things they get from friends. God I would cry so fucking much and cherish just a fraction of that. I want someone to think of me and let me know that. I can’t help but have this feeling that the world would go on so easily without me. I’ve taken up so little space in others I can’t think of any grief I would incur. I know people would be sad if I killed myself, but there’s a difference between sadness and grief. Outside of the normal loss that comes from someone’s suicide I’m not sure what people would miss. Me initiating things? The social spaces I set up through effort? Making people laugh? The only things I can think of are the things I provide, and so I feel as once those niches are replaced I fade.

I wish I knew how to take up space in this world. I want to be something to others, where I could exist when I’m asking rather than providing. I have spent so much of my life telling myself to info will get better, and a lot of things have. But I don’t have any guarantees and so I wait. I wish other people knew how desperately I want presents. I would love to be celebrated. I want something I can hold and look at and use to remind myself that things are different. Things as a proof for the argument that I am loved and I exist to the world and I would be missed. And I know it’s dangerous to equate these things because I cannot expect any gifts.

I’ve had enough ideation for the rest of a life.

Life at Blue Blossom estate had gone from a regular pacing of works to a haste that felt almost desperate. Siv had woken up that morning to an urgent ping from Mistress Maevin Maer, and from that point on she had been moving at a breakneck speed.

In a way, the 2nd order maid and Mistress in training was happy that her own Mistress trusted her. When Siv had gotten down to the first floor barely dressed, all the dark haired woman did was order her to handle guest hospitality and move on to pull harvester maids with estate certifications from the fields for extra support.

It felt like a massive weight on the woman with a two toned hair of blond and red. Guest hospitality meant food, quarters, assigned maids, and if she screwed this up, she would be in a world of hurt.

Of course, Siv was not going to be stupid. Her first stop after giving a quick bow to Maevin was to make her way to the Emissary Maids and refresh on what was expected for their guest. Their guest was none other than Countess Nadaela Vanen of House Vanen. She was infamous enough that even she had heard of her. House Vanen was an extremely powerful Gray Council house and only second to the Empress in influence. Rumors had it that Avernell and Vanen were rivals, but the appointment of Lord Henry Patton-Avernell made it worse. High Baron Hesh Avernell wanted to put a Terran in charge while Vanen's High Baron was fully against it. In the end, Hesh Avernell won, but if anything, these people were good at holding grudges. The fact that a powerful woman of said house was arriving unannounced sent a jolt of anxiety through her.

The official statement that Siv had learned was the Countess was on her way to Fort Aldric from her home world of Monolith and decided to stop by since they were in the area. Siv did not believe that explanation one bit.

Right now, she didn't care. They would be here in less than four hours, and even with all the prepping, they still felt unprepared. At that moment, Siv was half running, half walking towards the landing pad as security alerted her of the incoming shuttle from Black Fall Estate up north near Khelen. She was so haggard that she had a notion that her breasts had escaped her tvekel, but she didn't care. The woman only tucked them back after sprinting the last few yards under the colonnade that connected the main house and the shuttle pad. As she stepped forward, she waved away the security guards, who rightfully were suspicious as yet another rival house, House Devenek, had arrived, but her master had worked hard cultivating a relationship with them, and Siv was not going to undermine it.

Standing in front of her was a maid wearing her robe with fur trimmed around her neck and cuffs. A vivid blue wide sash was wrapped around her waist that contrasted against the darker gray, and silver tassels hung from the edge of said sash.

Maevin had made Siv study the maid orders and identification of the houses on Victory, and so she recognized an Estate Maid of the 3rd Order.

“Kita, Estate maid of the 3rd order,” the woman said stiffly with what looked like a sneer hidden in the corners of her mouth.

“Siv, Estate maid of the 2nd order,” she responded, and Kita gave a stiff bow recognizing her rank.

Kita gestured towards the shuttle that two servants had begun unloading two crates emblazoned with the Devenek crest from the back of the shuttle. The gentle clink of glass told her that her rivals had actually accepted her request.

“The ice liquor you requested,” Kita said. “From our master's private stores. He sends his respect and well wishes to your master and his visitor.”

Kaedral Ice Liquor, a special blend of kaedal bark that could only be found on a few moons orbiting the ice giant Veydra in the Haeshan System, which was on the other side of imperial space. It was the only produced alcohol that was comparable in taste and value to the Blue Wine Siv's estate made. It was also a favorite of Countess Vanen and would look good on Lord Henry to have it in stock. The liquor was also extremely expensive, and the fact that Duke Shantuk sent two cases made her impressed and anxious. Siv had only asked for two bottles, and these were sent. A favor for a favor, so she had no clue what would be asked of her later.

Siv bowed to the maid a lot deeper than she needed to acknowledge the gravity of the decision that was made. “Please thank your master for his kindness and to you for accepting my favor.”

Kita simply made a clicking sound with her mouth before turning and returning to her shuttle, which then took back off. Honestly, what else had Siv expected? She signaled to the two servants who had shown up to carry the cases to the kitchens, where Burdak Rikol, their Arch Maid of the Scullery Battalion, would be handling the serving of it.

Goddess, this is nerve-wracking, Siv thought to herself as she immediately turned back towards the estate proper and tried not to sprint.

---

Everything was prepared as it was going to be. That was something Siv had accepted as soon as she heard from the Mistress to gather in the grand foyer. There were still many things the 1st order maid wanted to get done, but they were out of time. Siv hoped that she hadn't missed anything.

As expected for a visiting dignitary, the Arch Maids, their assistants, and the 1st order maids were present in two lines facing each other to greet their esteemed visitor. Siv quickly took up her position right next to Maevin at the furthest end inside the foyer and folded her hands in front of her, also as expected.

“I saw Ice Liquor in the serving menu,” Maevin said, her voice low so only Siv could hear it. There was a mixture of curiosity and an undercurrent of a threat.

“Yes, mistress,” Siv responded as quietly. “I called in a favor, so our master would have only the finest for our guest.”

The 1st order maid saw Maevin nod out of the corner of her eye.

“The favor better not cost us, Siv,” Maevin warned. “You know what will happen.”

“I'll accept the altar if I embarrass our master,” Siv responded.

“Owing a favor to a rival estate? It won't be the altar, maid. It'll be the talons for you.”

The cold dread that went down Siv's spine made her involuntarily shiver. The Talons of Ala. She had never seen it used, but it was saved for the gravest of indiscretions. There was a statue of their esteemed goddess behind the temple, out of sight, where the unfortunate soul was placed. They had to put their hands and feet in specific spots, which were designed to dislocate the shoulders and hips. The young woman imagined it would be quite excruciating.

Lord Henry himself arrived beside Maevin with that nervous but happy grin that Siv had come to adore.

“Do I look alright?” he whispered to Maevin, tugging on his elegant summer tunic and then running his hand through his light brown hair a few times.

“You look good, my master,” Maevin responded in a warm tone that seemed off to the person that Siv was used to working with. Well, of course it was the case. Siv had seen a gentle side to her mistress a few times, but it was extremely rare. There was a chain of command that had to be kept in line.

“Are you sure?”

“Yes.”

“Siv?”

The maid started for a second, being referred to directly, and she quickly gave him a bow. “You look impeccable, my master.”

“Please relax, Master,” Maevin soothed. “This isn't your first encounter like this.”

“I know,” Henry responded nervously. “But this is House Vanen. I did my research, Maevin; they don't like Avernell, and they especially don't like me. I heard that the two High Barons got in a yelling match in front of the Empress over me.”

That was probably an exaggeration in Siv's opinion, because nobody would dare raise their voice in the presence of the Empress of all the empire.

“You are the Lord of Blue Blossom, Caretaker of the Emerald Sector, and Fleet Master of the 23rd Battle fleet,” Maevin chided in the gentlest way, which was, again, off-putting.

“Yeah. I know. Still...”

“You have this, my master,” Siv added encouragingly, and the glance of subtle approval from Maevin made her relax a bit for speaking out of turn.

The heavy, intricately carved double doors opened, and immediately every maid in line lowered their head and bowed. Maevin and Henry left Siv's side and walked down to meet the people who had just entered. Siv looked out of the corner of her eye.

Countess Nadaela Vanen was a striking woman with long, flowing purple hair that cascaded past her waist in loose, elegant waves. Her hair shimmered with varying shades of violet as the outside and inside light mixed together. There were several braided sections which had been adorned with ornate golden accessories and deep green gemstones. A pair of decorative ornaments rested near her temples in a distinct Vanen style.

Her eyes were a vivid crimson, framed by dark lashes and subtly pointed features that looked cold as ice from the polar caps.

Countess Vanen was dressed in an elaborate emerald-green gown that hugged her upper body before flowing outward into long, layered fabric. The dress had a deep, elegant neckline and exposed sections of her shoulders, while its loose sleeves draped down her arms. Intricate golden embroidery and bronze-colored ornamentation traced the edges of the fabric, forming swirling patterns that resembled vines or delicate branches.

Decorative emerald gemstones had been set into the metallic embellishments around her neckline, shoulders, and waist. A wide, ornate belt cinched the gown at her waist, adorned with interlocking metalwork and jewel-like details. Her sleeves were asymmetrical in their draping, with fitted sections around her forearms and loose fabric extending toward her wrists.

Siv had seen rich and powerful before when she trained as a courtesan, but this was something else. House Vanen was extremely powerful, extremely rich, and their entire aesthetic was built around the concept of tradition. Henry was the antithesis of tradition, so the 2nd order maid expected things to be extremely tense.

“eta isa udemi rovinve rotunaemaxavienve vanen,” Siv's lord said in almost perfect Xaltean. He still had an accent, but it had become pretty light with the amount of practice he had.

Countess Nadaela's crimson eyes burrowed into Henry, and Siv was amazed he didn't melt immediately under that gaze. He had that characteristic warm smile she herself had been given. Nadaela, in perfect form, curtsied far enough to acknowledge him as tradition required but no further.

“We have your rooms ready if you wish to—”

“No, that's fine,” Nadaela cut him off, looking about. “I would like to sit with you and discuss some things.”

Siv noticed the subtle movement of Maevin switching feet, which she knew meant Maevin was uncomfortable with the situation.

“Do you mind if my people get things in order with your honored maid?” Nadaela continued, referring to the six people standing with her, heads politely lowered.

“I do not mind at all,” Henry continued, and then looked to Siv. “Siv, if you could make sure their honored maid meets Tula, I would appreciate it.”

“As you command, my master,” Siv said with a bow.

The trio began to move, with Nadaela's personal maid keeping close while the others waited. As soon as the leadership was gone, everyone relaxed. Siv immediately looked to the other maids, who began to mingle with the Blue Blossom staff, discussing their specific roles. As Siv watched, something tickled the back of her brain.

There was a young woman wearing the tvekel of a low-ranking estate maid. She was behind her higher-order leader, who was speaking, but when she looked towards one of Blue Blossom's servants, she broke into a very friendly smile and gave the lightest of winks, which caused the other to blush but smile back.

Siv's eyes narrowed immediately as she watched. Even though the woman was dressed as a simple maid, there was something about her movement that just didn't match, but Siv couldn't put a finger on it.

“Peer Taer. I am Nish Kevet. Are your people hungry or thirsty? We have food and drink after your long journey.”

Arch Maid Nish Kevet of the Estate legion had arrived and taken command of the situation. Siv hadn't even noticed that Nish had glanced at her for a moment and immediately took on the hostess role, allowing Siv to act as the Mistress and watch. Was it written that much on her face?

“That would be lovely, peer Nish. You are very gracious to us,” Taer, a short man with short aqua-blue hair, responded. “We would love some.”

The entire party was led to a side room where tables of food had been set out for what had to be hungry servants. Siv followed behind, watching very carefully but trying her best not to come across as hostile. That was something she did not want to add on to Lord Henry's massively overloaded plate.

Conversation began to flow between everyone, especially after a few Vanen maids requested to use the casual register in speech, and that was warmly welcomed. If anything, Blue Blossom maids were very amiable and tried to embody the Avernell belief of warmth and beauty. Siv could not get the other maid out of her head, though, as everyone lined up to grab their meals.

“That's Shushema,” a voice said beside her, and Siv started, not realizing she hadn't been paying attention. Standing beside her with his plate and cup was the maid Taer from earlier.

“I'm sorry?”

He nodded towards the woman he had been looking at. “That's Shushema, estate maid of the 9th order. She's a recent addition to Sunfire Ridge Estate. She's been a very good worker, though a bit too friendly at times.”

There was a tone of admonishment in that statement that Siv did understand. A servant that talked too much, especially around people they shouldn't, could have dire effects.

It was when Shushema had made it up to the food after flirting with a few others and took the cup that was offered that it struck Siv. When the Vanen maid had taken the cup and another offered to fill it, Shushema, for a moment, rested the cup on the back of her hand instead of in her palm, but immediately corrected herself within a split second. If Siv hadn't been watching, she would have missed it. The realization of what she was hit her.

That was no estate maid. That was a courtesan.

“Has she been with you long?” Siv asked, sliding into the comfortable and confident persona she had perfected years ago.

Taer took a bite of his sandwich and shrugged. “She was brought on right before the Duchess decided to travel to Fort Aldric for the summit with the Terra Concavum.”

The young woman nodded, watching as Shushema made her way towards the couches and floor cushions, sidling up to a few of the Blue Blossom maids. That made Siv's heart jump a bit. Courtesans were infamous for being able to pull important details from unsuspecting servants. She should know, as she had been training to be one years before arriving at Blue Blossom.

“I see. Hasn't had a chance to understand the importance of tradition as your house is known for,” Siv said politely with a nod to him. “I take it Victory was the only stop?”

“Yes,” Taer said, and then grinned at her. “You're quite curious about our itinerary, Peer Siv.”

“Just curiosity,” Siv deflected with a well-practiced smile. “I've not been offworld since I arrived two summers ago. I do get a bit antsy.”

Waiting only a few moments longer to make her excuses, she stepped into the main corridor and debated what to do next. It was then that she saw Mistress Maevin making her way from the lounge towards the kitchens, and she did not look happy. Still, as much as facing her anger was scary, it was the right thing to do.

“Mistress,” Siv called, hurrying over to her. Maevin's cold eyes turned to her.

“Not now, Siv.”

“Forgive me,” she continued, bowing. “We have an issue.”

“What?”

“One of the Vanen estate maids is actually a courtesan.”

The mistress-in-training was not sure how it was possible, but Maevin's eyes grew colder. “Are you sure?”

“Yes, mistress.”

Maevin leaned in, her voice dropping to a hiss. “Deal with it.” The Mistress didn't wait around but continued on whatever mission she had been given.

Deal with it? How do I deal with a courtesan?, Siv thought to herself, the anxiety bubbling in her chest. House Aldinav Courtesans were trained to exist among the different maids, and calling one out was extremely difficult and a social disaster if not done correctly. Even so, a courtesan asking a question isn't actually breaking any rules if the person being asked answered. How was she supposed to deal with it?

If it wasn't obvious before, it was certain now that the whole trip Duchess Vanen was taking was to investigate Master Henry and his estate. Her unexpected arrival, the fact that there was a hidden courtesan among them. She was looking for information, and if they weren't careful,

Siv thought it over as she walked back toward the side room, slower so she had a chance to get her emotions in check and not give the entire game away. As she did, a plan was coming to mind.

The first thing she had to do was keep Shushema busy with people who had nothing worth extracting.

Keep the junior kitchen staff and the newer field hands near her. Didn't Maevin bring a few harvesters in from the fields? They wouldn't know the day-to-day of what was going on in the main estate.

The next thing she had to do was the part that made her stomach twist: she needed to feed Shushema something. A courtesan who came away with nothing at all would only confirm to House Vanen that there was something to hide. It was better to give her something that felt scandalous but wouldn't be out of place, especially if it was something about Terrans but not in a way that would humiliate her lord.

Siv reached the doorway of the side room and paused, watching Shushema laugh warmly at something one of the stable hands had said, one hand resting with practiced looseness on his forearm.

Gods help me if I screw this up...

Siv found the harvester maids were clustered in the far corner, probably uncomfortable with having to socialize instead of being in the fields. Good. She crossed to the nearest one, a broad-shouldered woman named Peket who Siv only vaguely knew from the fields. She was a powerful woman who ran her own teams with the harvest of the winter rose apples.

“Maid Peket,” Siv said warmly, “would you mind helping our guests feel comfortable?”

Peket blinked, clearly surprised, but nodded. “Of course, Esteemed Siv.”

Siv guided her, and two other harvesters she gathered along the way, toward the cluster of Vanen and Patton-Avernell servants where Shushema had planted herself. It was easy enough to make it look natural, a hostess making sure no guest went untended, introductions offered with a light touch before Siv excused herself to attend to something else. It felt like a dream, leaning into talents she hadn't used in years. Within a few minutes, Shushema had traded her stable hand for an animated conversation with Peket about the difference between Terran and Xaltean crop rotations, a topic so far from anything useful that Siv nearly laughed with relief. That also was information that the courtesan was not a high-ranking one, as they wouldn't have been distracted so easily.

Maybe 9th or 8th order, Siv thought to herself. That solves the immediate problem. Now to keep her at bay.

The mistress-in-training found Nish refilling a tray near the sideboard and touched her elbow lightly, leaning in as if commenting on the food.

“Peer Nish. A word, when you have a moment that doesn't look like a moment.”

Nish's eyes flicked to her, sharply. Nish was quiet and reserved but very strict and quick to read the room. “Of course, Peer Siv. The kevet rolls need restocking anyway.”

They drifted together toward the doorway, and Siv could feel Nish's intense curiosity.

“We have an issue,” Siv started as they stepped out into the hall. “The maid Shushema. She's a courtesan.”

Nish's eyes widened for a split second before she gave a firm nod. “Has the mistress been informed?”

“Yes, she told me to deal with it,” she said, and Siv didn't need the look of pity from the other maid.

“What do you need from me?”

“We need to feed her something that will satiate House Vanen's curiosity but not put our master into a worse situation with such a powerhouse,” Siv began to explain, trying her best not to rattle on. “I just don't have any ideas of what to give them or how? I was hoping you might have an idea. You've worked a lot of estates.”

Nish considered for a moment, tapping a finger against her thigh. “You suspect House Vanen already believes this visit is about Lord Henry's fitness to hold the Emerald Sector. That means whatever we feed her has to answer that question, just not honestly.”

“Meaning?” Siv asked.

“Meaning we need to provide a flaw.” Nish's mouth curved faintly. “Vanen wants proof that Avernell overreached in putting a Terran in charge, but something with almost no real value to use against him, and something that will turn out false in the end.”

The mistress in training frowned. “How do we do that?”

“Let it slip that Lord Henry still struggles with conforming to Xaltean standards. That he struggles with our language and customs still and that the Mistress is covering for him.” Nish said, her tapping finger getting a bit faster. “It was all true at one time, but they won't be here long enough to realize that.”

Siv's stomach eased slightly, then tightened again. “That'll still make him look weak. We can't jeopardize his position.”

“It makes him look Terran,” Nish corrected. “There's a difference, and anyone looking objectively will know that. If Shushema carries back that he's still acting Terran, Vanen gains ammunition for discussion in the Gray Council, but not enough to actually bring before the Gray Council, and if they did investigate, they would find her information is either wrong or outdated. As you know, our lord speaks very well.”

Siv thought of Henry tugging at his tunic in the foyer, asking Maevin twice if he looked alright. It wasn't even a lie. That was what unsettled her most.

“Someone low-order,” Siv said slowly, working it through. “Someone that it wouldn't be suspicious of, but someone we can trust.”

“Exactly.”

Siv nodded. “We just need to find someone who can do it.”

“I can.”

The two women started, having been so deep in conversation in the corner that they hadn't seen the other woman approach. Peket's large frame stood near them. Nish's eyes narrowed into slits as the anger seethed.

“Were you spying on us?”

“I was eavesdropping,” Peket admitted straight away, “because I was curious.”

“I can have you whipped for that.” Siv warned.

“And I will accept it, but I can do it.”

Siv and Nish exchanged glances before looking at the harvester.

“It's risky because if we screw this up, you will go to the Talons just like us,” Nish said, not bothering to hide that she knew the stakes.

“Because of who he is,” Peket said eagerly, the tomboy exploding out. “Just a few weeks ago, he was touring the orchards as we were preparing the plants, saw that we were down a worker who was being examined by a medic, and spent the next two hours climbing up in the trees with us, making sure we could get done on schedule.”

Siv forced herself to keep the smile from reaching her face. That sounded so much like their Terran lord.

“So, I wish to do this to repay what he did for us harvesters, and if it fails, I accept the consequences.”

Nish glanced to Siv, who nodded.

“Then here's the plan.”

---

Siv had learned the trick of invisibility long ago, and the skill returned easily. She settled herself near the tall arrangement of dried flowering branches against the far wall, angled just enough that anyone glancing across the room would see only her shape, monitoring things but too boring to watch. There was a little alcove of the room near her position that Peket had been moving towards slowly, and from there, they wouldn't be able to spot her.

Shushema had done the drawing in slowly; Siv could see that much. A hand light on Peket's forearm, a lean of the head that made the bigger woman lean back in turn, the two of them forming a small closed circle that excluded the rest of the room without appearing to try. Peket's voice came low and careful, pitched in a way for Siv to hear.

“I probably shouldn't say,” Peket was murmuring, glancing once over her shoulder, “but you asked so kindly, colleague, and it's not as though it's a secret exactly. Everyone here knows.”

“I would never repeat it,” Shushema responded, warm and solemn, and Siv had to admire the craft of it; she had to be a 7th-order courtesan.

Peket lowered her voice further, forcing Shushema to lean in even closer. “It was a Lady of Honor's visit, a few months back. Our lord was greeting her formally, you understand, using the high register the way Mistress Maevin had drilled into him. He meant to say mlebesh. Please, be seated.”

“Mm,” Shushema encouraged softly.

“He said xil-khebesh instead.”

Shushema's breath caught. “He made such an obvious mistake?”

“Yes,” Peket nodded. “To hint that she should sit lewdly was appalling.”

“What did she do?”

“Went white as a bone. Didn't know if she'd been insulted on purpose or by accident, and for a moment neither did anyone else in the room, because our lord just stood there. Didn't catch it himself. Mistress Maer had to step in and smooth it over, said something about Terran tongues still finding their footing, laughed it off light as anything before it could become a true offense.” Peket shook her head, the motion small and confiding. “Between us, colleague, I don't think it was only the words that slipped. I think for a moment he looked at her the way Terrans do, if you understand me, that was the most uncomfortable part.”

“He's young,” Shushema offered gently. “And Terran. I imagine it's difficult, learning all the rules so quickly.”

“That's exactly it. He tries so hard. I'd never speak ill of him truly; he's a good master to us in the orchards. It's only, well. You can't unlearn where you come from, can you? Not fully.”

“No,” Shushema agreed softly. “I suppose you can't.”

She patted Peket's arm once, let the conversation ease naturally toward the sweet table, and asked no other questions. Why would she? Shushema got exactly what she wanted. Siv set down the vase she'd been holding for far too long and allowed herself a slow breath. Across the room, Peket caught her eye, and Siv gave the smallest nod of approval.

It was done. Now all that remained was seeing if it worked.

---

The great doors of Blue Blossom's foyer stood open to the evening air by the time Countess Nadaela Vanen emerged from her private audience with Henry and Maevin. Whatever had happened in that room, none of it showed on her face.

Siv took her position again at Maevin's side in the receiving line, hands folded, head inclined just enough to be proper. She could feel the tension radiating off her mistress as she stepped beside her.

“We won't be staying the night,” Nadaela said, addressing Henry directly, her crimson eyes unreadable. “I do not want to delay any further.”

Henry's smile faltered for just a fraction of a second before he caught it. “Of course, Countess. I hope the visit was informative.”

“Very.”

Siv kept her eyes lowered and her breath even, watching the small procession begin to assemble near the doors. Shushema fell into step behind Taer with the same easy, unremarkable bearing she'd worn all evening. Nadaela paused at the threshold and looked back once, her gaze sweeping the lines of Blue Blossom maids still bowed, and left.

Siv did not move from her place in line until the party had left. Henry let out a long breath and dragged a hand through his hair. “Well, it could have been worse.”

“It could have, but you held your ground,” Maevin said. The mistress looked in her direction, and Siv gave a nod to let her know she had resolved it. Of course, there would be a report later, but right now, Siv allowed herself to finally breathe.