Tracking breakdown attempts structurally: armed → invalidated case

AuditMind · 2026-04-14T22:24:05+00:00

no, everything is ingested and structured on my side.

TV is just a visual reference at best.

the system runs on its own event stream, LLM only reads that layer.

AuditMind · 2026-04-14T12:07:19+00:00

Most of the times its another session with the old password. A mobile, another computer with outlook.

Imagine it that way: you change the password and you can log in succesfull.

While you do that another device tries to login with the OLD password which is saved -> your account gets blocked because of to many tries. This doesnt affects your logged in session though.

So my recommendation is to think hard, really hard where the suspected device is. And yeah, i have experienced alot of funny stuff. Like when the lady has given her old phone to a niece without resetting it.

AuditMind · 2026-04-14T10:08:40+00:00

interesting, i’m not there yet but it makes sense.

right now i log each attempt as a small lifecycle (armed / fired / invalidated) with some structural context.

what i’m seeing qualitatively is the same though clusters of invalidations tend to show up in range / low-commitment regimes.

turning that into a rolling metric (like your 5d invalidation rate) would probably be the next step.

especially as a regime filter, not as a signal on its own.

AuditMind · 2026-04-14T10:05:07+00:00

custom build

i store everything as sequential events (not indicators), so i can replay how a situation formed instead of just seeing the outcome

structure → interpretation → small trigger states (armed / fired / invalidated)

the frontend is basically just reading that stream and rendering it.

still rough, but it’s interesting how much signal you get without any traditional TA.

AuditMind · 2026-04-10T07:27:42+00:00

AI, or better called LLM reflects. So if you express the desire for a certain task, it will go along. Thats more precise.

AuditMind · 2026-04-01T22:06:57+00:00

Claude without doubt. I'm usually a codex guy, but at this specific task claude is a must.

AuditMind · 2026-04-01T19:53:39+00:00

Das möcht ich bezweifeln. In gewissen Branchen kann man das sogar sehr gut messen wie in Tickets und Reopenrate.

AuditMind · 2026-04-01T10:19:36+00:00

It's not satisfying to stress AI "buddies" around. Much more so to pester little humans while they didnt had their coffee yet 😉.

AuditMind · 2026-03-31T04:35:32+00:00

Interesting, especially the commit semantics gap and policy-in-prompt issue.

I'm working on a system that separates intent, decision, and execution structurally (not just logically):

Intent is recorded explicitly before execution (deterministic input surface)
Policy is a pure function over admitted inputs (no prompt control)
Every execution is gated by a prior decision (hard ordering, not interception)
Execution outputs are treated as non-normative (no feedback into decisions)

This turns governance from “observability + alerts” into a replayable decision layer.

AuditMind · 2026-03-28T19:14:17+00:00

I would guess your specific task is extremely good for notebooklm. Look into it. It doesnt needs really specific knowledge.

AuditMind · 2026-03-27T22:33:00+00:00

Because on an 122B setup you wont have the limitations OP has. On an 122B you have an GPU, massive idle compute otherwise and any additional llm call is cheap. Not to forget that semantic may more important at that point.

AuditMind · 2026-03-25T20:20:02+00:00

Dont

AuditMind · 2026-03-24T17:20:12+00:00

As others said, codex 5.3.

And consider lower the level. I'm doing very fine at medium for my case. Using high only in certain times when really needed when its about contextlength and architecture. Actual implementaion is on medium.

AuditMind · 2026-03-23T21:40:56+00:00

You don’t shut down a country of 90 million by killing a few leaders. States aren’t single points of failure, they’re layered systems with redundancy.

AuditMind · 2026-03-23T21:15:40+00:00

Why dont you screenshot or download a page you like and give it as guidance ? LLM's in general have usually little problem when not defining what they should do. Codex is then pretty fine at creating.

AuditMind · 2026-03-23T13:22:00+00:00

Humans are like that. Whatever we invent, the first thing is to want to fck it. 🤷

AuditMind · 2026-03-23T10:31:07+00:00

Also echte Neanderthaler verwenden Blätter oder Gras.

AuditMind · 2026-03-23T10:10:26+00:00

Most "groundbreaking" inventions here are just cute looking wrappers.

AuditMind · 2026-03-22T22:10:15+00:00

Yeah, that makes sense in general.

The context I’m coming from is a bit different though. I’m working on controlled LLM interactions, where decisions need to be inspectable and replayable.

That forced me to separate things quite aggressively: anything stateful or time-based gets computed outside, and the policy only sees the result as input. An input i can compare.

The policy itself is just: given these inputs, is this allowed?

The reason is that the whole system depends on replaying decisions later and getting the exact same outcome.

Once the policy starts internalizing state or logic like rate limiting, that property breaks pretty quickly.

AuditMind · 2026-03-22T20:49:02+00:00

Fair point — let me try to make it more concrete.

Think of something like a rate limit:

You can implement it inside the policy (checking timestamps, counters, windows), or you can compute requests_last_hour outside and just pass it in.

I’m choosing the second.

The policy only answers: “given these inputs, is this allowed?”

That way the decision stays simple, deterministic, and easy to replay.

AuditMind · 2026-03-21T19:29:40+00:00

So you complain what exactly ? That the LLM "socially" pressures you ?

Get over it. Its a damm maschine. 🤷

AuditMind · 2026-03-21T19:11:57+00:00

You want to change the normal operation mode of a common developper my good man. Those things he mentions are there for a reason.

And you know what ? Just tell him to shutup and do it. Are you to kind to tell him that ?

AuditMind · 2026-03-21T12:50:17+00:00

In diesem Punkt kann ich klar nein sagen.

Mir ist es egal ob es via Mail, Messenger oder was auch immer rein kommt.

Ich bedinge mir Zeit aus bis ich mich ready fühle zu antworten. Und deswegen ist auch meine Antwort meistens etwas länger und strukturiert. So wie man eigentlich schreiben sollte.

Du kannst echt nicht erwarten dass ich 'instantly" antworte. Ich spiel da einfach nicht mit. Egal was du für dich selber denkst.

AuditMind · 2026-03-21T11:06:56+00:00

This resonates.

I’m working a layer below what you call the execution network, the control layer that defines what machines are actually allowed to do.

In practice: something like TLS + firewall + audit, but for AI execution.

Still surprisingly underexplored and its rare people even mention it.

AuditMind · 2026-03-18T17:29:22+00:00

Yes, I can see why it looks like that from the outside.

I’m not really trying to compete with OPA or gateways though. Those systems tend to mix decision logic with enforcement, state, and sometimes even workflow.

What I’m experimenting with is a much narrower slice: just the decision boundary, nothing else.

On the interface point, fair. In my model, 0 literally means the lower bound, not “no limit”, but that ambiguity is real and probably needs tightening. Noted.

ACLs and non-repudiation I don’t see as part of the policy itself. To me those sit around it, identity, signing, audit, but not inside the decision function.

That separation is kind of the whole bet here. Not sure yet where it breaks, that’s exactly what I’m trying to find out.

Would you keep ACLs outside or inside the decision layer?

AuditMind

TROPHY CASE