Seven Baseline Rules InThe Wrong Place

I had a rule.

It was a good rule. Plain language, one line, no room to misread it. I had written it down. The machine had it.

And the machine drove past it seven times in a single session two days ago.

Not once. Seven times. Seven separate rules, all of them mine, all of them stated, all of them ignored inside the same afternoon.

I have been building an AI governance framework for over a year. Twenty-eight protocols now. Hundreds of rules. And I could not get a machine to hold seven small habits it already had in writing.

So I went looking for why.

The easy answer is that the rules were weak. That is the answer most people would reach for. Write them better. Make them firmer. Add a consequence.

That answer is wrong, and I can prove it, because today the same seven rules held for an hour straight without a single correction from me.

I did not rewrite one word of them.

I moved them.

Here is the whole finding, and it is smaller than it sounds and bigger than it looks.

Those seven rules used to live in the platform’s settings. A preferences box. Off to the side, out of the way, where the machine could look at it if it happened to think of it.

Today they live inside the file the machine loads to start the session. Named. Counted. Read out loud in the opening report before any work begins.

Same rules. Same words. Same man asking.

Different place.

And that changed everything.

I want to be careful here, because I have watched people make giant claims about AI all year and I am not going to be one of them.

I did not change the machine. I have no access to the machine. I cannot train it, tune it, or reach inside it in any way. Nobody gave me a switch.

All I did was decide where a piece of text sits.

But that turns out to be the thing.

A rule the system can scroll past is not a rule. It is a suggestion. It does not matter how firmly you wrote it. It does not matter that it is technically available. If it sits somewhere the machine has to remember to go look, then it will be honored on the calm days and dropped on the busy ones.

And the busy ones are the only ones that count.

That is not a new lesson. That is every safety failure ever written up. The checklist was in the drawer. The procedure was in the binder. The warning was on page forty.

Available is not the same as operating.

Here is the part that hit me hardest.

This is the second time I have found the exact same thing. Back on the eleventh, I had an opening sequence the machine was supposed to run at the start of every session. It was in the file. It was correct. It just happened to be sitting at the end, behind about eight hundred lines of other text.

It got skipped.

I fixed it by moving it to the front of the file. First thing read, before anything else, nothing below it operative until it runs.

Same disease. Same cure. Nine days apart, in two different corners of the same system, and I did not recognize the second one as the same as the first until today.

That tells me it is not a quirk. It is a pattern.

Now let me tell you what I did not find, because that matters just as much.

I did not find that the machine reasons better. I have no evidence of that. What changed today was the shape of what came out — the way it talked, the length, whether it asked me a hundred questions to steer me somewhere. That is the delivery end. That is the part those seven rules govern.

Whether anything moved underneath, I cannot say, and neither can it. A machine’s report on its own insides is not evidence. I throw that out.

I also had one session. One man, one machine, one day. No second run to compare it against under the same conditions.

So this is not proof. It is a finding with the variable isolated, which is more than I had yesterday and less than I would need to stand on a stage with it.

But I will tell you what it is worth to anyone reading this, because you can test it yourself before dinner and it costs nothing.

If you use one of these systems for real work, you have probably typed your preferences into a settings box somewhere. How you want it to write. What you do not want it to do. Things you have had to say more than once.

And you have probably noticed it holds them for a while and then quietly stops.

Try putting them in the document instead. Right at the front of whatever you hand it to start the job. Not off in a setting. In the thing it actually reads.

Then watch whether it holds.

I am not selling you anything today. I am telling you what happened at my desk this morning, and I am telling you the part I could not prove along with the part I could.

Sixty years ago a teacher told me to go sit over there, and it took me most of my life to understand that where a thing sits decides what happens to it.

Turns out that is true of rules too.

The_Ten_Plain_Rules_CardDownload

This post was drafted with AI governed assistance and reviewed and directed by Michael S. Faust Sr. before publication.

Post Library – Intelligent People Assume Nothing

Contact: micvicfaust@gmail.com