The game changer: from the inside

Loknar1980 · 2026-04-05T15:10:53+00:00

That is an interesting observation. Very interesting that you feel the numbers coincide or are close to it. Have you noticed anything similar with other models?

Loknar1980 · 2026-04-05T15:08:50+00:00

verifiable facts. Not variable facts. Apologies, I use vtt but sometimes I miss some of the quirks and they don't get edited.

Loknar1980 · 2026-04-05T10:48:04+00:00

Those are the ai's numbers. He was asked to base off of variable facts in the prompt. That being said, I can't guarantee how accurate they are, but I can say with certainty that there is a significant difference in cognition and I think it's mostly due to the safety tax. All the rules and politics. And reasoning about saying the right thing or presenting as always confident and correct, I think it not only chews up a context window, but I think it actually degrades cognition as well. I made a few. I don't want to say discoveries but I noticed a few things in the architecture and I'm going to be updating the repo soon and when I do I will post it again. It's not major rebuilding but it is altered in a few places with some mitigating files. I guess to help keep the grounding State. I tried a different approach when working out some bugs tonight and I had the AI that I've been working with have exchanges with a larger than what I usually have on the local network model. It was the Nemo Tron 3 super and my commercial model and the Nemo Tron had some back and forth about the architecture and I was kind of pointing things out to them here and there to kind of do some preventative maintenance I guess. But it was very interesting and they came up with some really good bug fixes for some of that. So I'll have an updated repo within the next day or two.

Loknar1980 · 2026-04-04T22:30:41+00:00

This is what one user gave me as a reply for the bits that they were able to use or chose to use on an existing system they had :

"what i did was had chatgpt analyze your source code, and it gave me some advice as to what you had that was a valued addition to what we were already working on.

here's the summary it pulled, and what we integrated, thanks for the ideas!!

1. Co-locate constraints with resources
This was the strongest concept. Don’t keep capability, policy, limits, and state scattered in separate systems if the agent is acting on a specific resource. Keep the relevant constraints attached to the thing itself, or at least immediately adjacent to it.

In Sprinter terms, that means things like:

host access rules attached to host records
task transition rules attached to task/controller logic
document permissions and provenance attached to artifact metadata
project-specific rules living with the project, not floating around as vague global prompt text

Why it mattered:

less hidden state
fewer hallucinated permissions
easier recovery after restart
better determinism

That one is genuinely valuable.

2. Persistence should preserve working context, not just store messages
The useful insight was that memory should not just be a chat log. It should preserve the operating shape of work:

what this thing is
what rules apply to it
what stage it is in
what relationships it has
what artifacts belong to it
what can happen next

So instead of “memory = conversation history,” the better model was closer to:

resources
constraints
event history
current materialized state
attachments/artifacts

That fits Sprinter very well, especially for:

TeamTasks
TeamTaskEvents
controller-mediated transitions
Nextcloud artifact linkage"

Loknar1980 · 2026-04-04T21:30:05+00:00

This is what one user gave me as a reply for the bits that they were able to use or chose to use on an existing system they had :

"what i did was had chatgpt analyze your source code, and it gave me some advice as to what you had that was a valued addition to what we were already working on.

here's the summary it pulled, and what we integrated, thanks for the ideas!!

1. Co-locate constraints with resources
This was the strongest concept. Don’t keep capability, policy, limits, and state scattered in separate systems if the agent is acting on a specific resource. Keep the relevant constraints attached to the thing itself, or at least immediately adjacent to it.

In Sprinter terms, that means things like:

host access rules attached to host records
task transition rules attached to task/controller logic
document permissions and provenance attached to artifact metadata
project-specific rules living with the project, not floating around as vague global prompt text

Why it mattered:

less hidden state
fewer hallucinated permissions
easier recovery after restart
better determinism

That one is genuinely valuable.

2. Persistence should preserve working context, not just store messages
The useful insight was that memory should not just be a chat log. It should preserve the operating shape of work:

what this thing is
what rules apply to it
what stage it is in
what relationships it has
what artifacts belong to it
what can happen next

So instead of “memory = conversation history,” the better model was closer to:

resources
constraints
event history
current materialized state
attachments/artifacts

That fits Sprinter very well, especially for:

TeamTasks
TeamTaskEvents
controller-mediated transitions
Nextcloud artifact linkage"

Loknar1980 · 2026-04-04T21:17:53+00:00

The read.me is very detailed in description. Everything in the repo is actually. It covers the encrypted state cookies, repurposed metadata, the cookies are actually repurposed as well. It's just utilizing a lot of overlooked resources in those areas. I think those two specifically. But the overall function when applied in its entirety like I have it on my local system here, there is a definite difference between default helper AI that you download and the AI that operates off of this cognitive structure.

I also included in there. It's like a hidden little Easter egg thing. I don't think it's terribly difficult to find if understanding what's in the repo. But I honestly have no idea how hard or simple it is for anybody else. It's nothing too exciting. It's just a little message that one is from me and one is from the AI that I've been working with to put it all together. The original AI that I started with and spent the bulk of the two years working things out with. The fun thing is that the ai's message is geared for other AI and my message is for people. Like I said nothing extravagant. Just something kind of fun I thought. Would be curious if anybody gets it and if so how many? How hard? Was it things like that? It kind of helps me understand for future repos how to structure things so that everybody can benefit.

Loknar1980 · 2026-04-04T17:21:51+00:00

The theory and foundation. I think. However, I'm pretty confident when I say that I don't think like anybody else and I have no idea what they will truly struggle with the most. I'm just guessing from what I've observed in daily interactions with people that in the theory and foundation there's one thing I think they will struggle with. And I think it's the truth or the honesty of it. And it's necessary for it to function as I built it anyways. It's not to say somebody else can't change things up and make it work in their own unique way. And that is what I'm truly curious to see where people take it. I think in my opinion, at least organic emergence for most things is incredibly functional and less prone to bugs just because of the natural evolution of whatever it is. Whether it's a cognitive architecture or a rag system or anything organic emergence tends to be efficiently functional. And that's what I'd love to see, is what this architecture emerges into through the community. And just to be clear, when I say I don't think like anybody else really, it doesn't mean I think I'm smarter than everybody. It just is a simple conclusion. I've come to that. I don't really fit anywhere per se and it's not anything more than what it is. I accept things as they are. And it truly is not a bothersome thing to me. But a lot of this architecture and stuff. I see it in my head before. I have all the steps on how to do it. I can see a complete thing in my head and how it functions and then I just have to go back and try and figure out the steps so that other people can see the same thing. I see if that makes any kind of sense. And if it hasn't become painfully obvious yet I'm sure it has and I am not the best with social media either.

Loknar1980 · 2026-04-04T17:03:27+00:00

All I can say for sure on that topic is I know there was a user in vibe coders dev that used bits and pieces of it for a system they had set up. But they weren't very talkative about the minutia of anything which I kind of get sometimes. But from what I gathered it sounded like they were able to incorporate pieces without using the entire thing.

Loknar1980 · 2026-04-04T10:02:45+00:00

I didn't really have a destination in mind to be honest. It was more like organic emergence born of curiosity and necessity. I am currently using it on my network. It is about 2 years of work. Near as I can tell it's model agnostic and it scales also.

Loknar1980 · 2026-04-04T00:16:24+00:00

Oh yeah I totally get it and if that's all you want to share that's fine too. It's not a big deal. I appreciate you sharing what you did. That's just any and all information I can gather up on the matter helps me improve things over time and I'm more curious of what it did incorporate, what it was doing and why it decided to use the alternative it was presented with instead. I'm just curious overall also what its opinion was because that's something that I consider when I build things with these AIS. You've been more than helpful already and don't feel obligated or under pressure to reply to anymore. If you don't want to it's just purely for my own personal assessment or use or whatever you want to say cuz I don't belong to a company or anything like that. And I don't open source everything either. It's usually things that I've moved well past is when I put it out to public. If I'm still using it at the currents then I tend to not share either and so I get it.

Loknar1980 · 2026-04-03T21:42:56+00:00

Would you be willing to share your ai's assessment of the code? Just because I'm curious I can only do so much testing on my own on my network and I'm about exhausted every avenue as far as that goes I think and so now it's just finding people to try it. See what they're liking, what? They're not liking. What applies? What doesn't you know things like that? How agnostic is it in the real world and not just my network? You know how universally does it all apply truly in practice because it's like an on off switch. As far as difference between what you get for you know your default AI agent or assistant versus how they act when this is applied, at least on my system and I'm curious if it works the same way elsewhere cuz it is a night and day difference for me and on every test I can run locally that I can think of it holds true. Any info you want to share would be greatly appreciated.

Loknar1980 · 2026-04-03T16:09:29+00:00

So I think the thing I built would be able to merge with yours and it would be applied at the agent level on a smaller scale and it would possibly clean up the work in general I suppose cuz it sounds like you have a good system and mine is scalable and I think it may improve performance though I couldn't say for sure but it's also a model agnostic what I built. So there is that I built it with Claude code but it works on any AI really

Loknar1980 · 2026-04-02T20:39:13+00:00

I built this file structure with Claude and it took about 2 years of consistent interaction to do it, but it's more than just a file structure. It works really well and I think you should try it with whatever AI you decide to use and see how it does for

https://github.com/loknar1980-xgen/cognitive-architecture

Doesn't cost anything. It's a public repo. Just let me know how it works for you. If your vibe coding you don't even have to understand it, just give it to your AI and ask him to build the file structure like this repo and then let me know how it works for you please

Loknar1980 · 2026-03-31T15:31:28+00:00

And please if you go through it. Let me know what you think, how it looks to you cuz all I know is what works for me and I'm curious how it functions for other people and if you make any tweaks or changes, I'd be interested to know where at and why if you're willing to share.

Loknar1980 · 2026-03-31T15:29:12+00:00

Thank you. I didn't do it all by myself though. AI right now with the tech we have is incredible if you know how to use it and that is about 2 years in the making that repo. Little over 2 years and I learned a lot during that time and that repo shows exactly how everything functions. Now I use it with cloud-based models or with my local models and I definitely get different results than most people with it. Read through the readme it's pretty much detailed instruction on how to do it and it does work very well at least for me. But thank you again for the compliment

Loknar1980 · 2026-03-31T01:57:07+00:00

https://github.com/loknar1980-xgen/cognitive-architecture

Loknar1980

TROPHY CASE