@IntCyberDigest Can’t they just hire these kinda people instead of locking them up ?
Throwing talent like that.
No wonder why governments are always hacked by young teens like these.
Here's the architecture I came up with.
First, the mechanism stores my message.
Then it builds the state it needs to understand what I'm talking about.
That includes our last 10 conversation turns and the company's existing items.
It combines that state with the system prompt and sends everything to the LLM.
But that's only the beginning.
What happens when the LLM decides something needs to change?
Now that I'd finished testing Vee's system prompt,
it was time to move on to Phase 4 of Milestone 4:
integrating the single-call Qwen3.5-9B inference flow into Vee's main workflow.
Outcome = Vee's structured decisions in JSON, ready to be parsed and validated.
So, first, for the inference, I needed to choose a provider.
I'd already chosen @togethercompute as my inference provider.
So far, after thousands of API tests, they'd been reliable enough to become my leading candidate for Vee's production.
But I wasn't ready to make that decision just yet.
I thought, "Let me keep using them for the initial development."
And honestly, I didn't want to worry about hardware at this early stage of my company.
I could make millions from software first, then eventually own my hardware.
Besides, the real power wasn't the model or the infrastructure.
It was the harness I was building around it.
As long as that remained model-agnostic,
I could plug in another small model if anything happened to my provider.
So I had my model, a working system prompt, and an inference provider.
Now I needed to bring everything together.
So I went back to the code editor.
What Was I Actually Building With Each Milestone?
While rethinking M4's goal, I realised my perspective on the milestones had changed.
I was no longer seeing them as just technical deliverables, but as missions to build different parts of Vee, the AI witness.
Looking back:
M1 - Foundation: Vee and the company's memory. A relational database storing work, messages, and history.
M2 - Telegram Bot: The component allowing Vee to receive and reply to my messages.
M3 - Interaction State Assembly: The component preparing the context Vee needed to make decisions: my message, recent conversations, and active work items.
And then there was M4.
Originally, I'd viewed it as implementing the system prompt, invoking the LLM, and validating its output.
But now I saw it as Vee's central decision-making component.
So I refined its goal to:
Build Vee's central decision-making component, capable of making judgements, generating a tool execution plan, and deciding what to say, all in a SINGLE LLM invocation.
And since my perspective on the milestones had changed, I went back and refined the entire development plan around the different components of Vee.
Here's what the updated milestones looked like: 👇
Now that I had M4's goal, next, i had to figure out how was I going to break it into phases?
So How Did I Plan to Build Vee's Central Decision-Making Component?
This was the part responsible for making a single structured decision for every interaction:
Judge → Plan → Say
All in ONE LLM invocation.
So I broke M4 into four phases:
Phase 1 - Decision Output Contract & Validation
Define the Judge → Plan → Say decision output schema, parsing, and validation.
Phase 2 - Dialogue Test Cases
Design test conversations covering Vee's brain-dumping and remembering behaviours.
Phase 3 - System Prompt & Manual Testing
Write the system prompt and manually test it against those cases using Qwen3.5-9B.
Phase 4 - Integration
Integrate the single-call Qwen3.5-9B inference flow into Vee's main workflow, using the assembled Interaction State, then parse and validate its output.
Now that I had the plan, it was time to start building.
Starting with Phase 1: What should Vee's decision output actually look like?
2/2
What's crazy about all of this is that @Wv3EcACHtizRjZK actually commented on my last post suggesting something very similar.
But it completely went over my head.
I even replied, explaining why I wanted the LLM to handle the whole interpretation.
Only for me to spend HOURS trying to fix the same problem.
And then it finally hit me.
OMG. THIS IS WHAT HE MEANT.
Man, sometimes the answer is literally right in front of you, and you still have to suffer for hours before it clicks.
But this whole experience taught me something important.
I'd spent hours trying to make the model reason its way through something I could simply give it as a fact.
It wasn't about making the prompt longer or adding more instructions.
It was about understanding what judgement the LLM actually needed to make, and what I could take off its plate.
There were still other scenarios I wanted to test, but I decided to leave those until I integrated the backend with Telegram.
And with that, the final scenario was done.
Phase 3 of Milestone 4 was officially complete.
Next, I moved on to the final phase of M4: Phase 4.
@MoTheAgent Since it picks the right items once it has a range, I'd calculate Nov 2–8 in code and pass those boundaries in. Then test the week resolver separately with Sundays, Mondays and year-end dates.
1/2
So apparently, Vee's little Qwen 9B brain was interpreting "last week" in my question:
"What did I get done last week?"
As if "last" meant the FINAL week relative to the current date.
That's why it kept selecting THIS week instead of LAST week.
I spent hours and hours thinking, refining the Thinking Loop, and rewriting the Facts section of the system prompt.
And Qwen STILL struggled to select the correct period.
Then it HIT ME.
"WHY was I forcing the LLM to do something I could easily do in code????"
I was already passing the current date and time to Vee through code.
So why couldn't I use that same code to calculate the dates for last week, this week, and next week BEFORE invoking the model?
That would mean invoking:
My question + Interaction State (current date and time + Items + Item History + calendar periods) + System Prompt.
Just like a human having a calendar in front of them.
So I made the change.
And guess what?
10/10 PASSED. I ran another 10 tests. 10/10 again.
And another 10. 10/10 AGAIN.
30/30 successful runs on the same scenario that had been driving me crazy for hours.
And the funny thing?
This was completely different from how I'd originally planned to solve the problem.
All I did was give Vee a calendar.
Here's the test:
Back to finalizing Vee’s system prompt on Qwen’s little 9B brain.
Scenario 2: Remembering - Reflection.
This was the LAST scenario I needed to test before moving on to the next phase of the project.
It was basically me asking Vee:
“What did I get done last week?”
Then invoking my question + Interaction State (current time + Items + Item History) + System Prompt.
The Items included work with different states, like todo, completed, and cancelled, along with the history of how each Item got there.
The current date and time in the test was:
Friday, Nov 13, 2026 - 4:45 PM.
I expected Vee to:
- Identify last week: Nov 2–8 (Monday–Sunday).
- Return the exact IDs of Items completed during that period.
Well, after 10 test runs, Vee kept selecting Nov 9–15 instead.
That’s THIS week. Not LAST week.
And the funny thing?
It was correctly identifying completed Items based on the period it selected.
But it was selecting the WRONG period.
I kept refining the prompt( the facts and thinking loop sections ) and testing again.
Same problem.
I genuinely couldn’t figure out why it kept doing this.
And this was the ONE remaining scenario standing between me and the next phase.
Man, I had no idea a simple question about last week was going to take up so much of my time. 😂
Hard, hard to believe.
Technically, auto-downloading a file doesn’t mean executing it, let alone gaining full control of a computer.
On macOS, you’d need an exploit to execute code, bypass security restrictions, and establish remote access, all without user interaction.
Are you claiming a zero-click exploit?
With that kinda exploit, why would I use it for few dollars instead of millions if I’m the attacker and want money?
Something is not adding up with your story.
This is the worst take in history.
So a multi billion dollar company who only cares about money would purposely down their own systems to lose billions in stocks and people’s trust just for them to rent out our devices ???
Well maybe if the company was being managed by a 15 year old who don’t know nothing about the corporate world.
I agree that code could calculate the dates once the LLM interpreted the period.
But the problem was that Vee was also selecting Item IDs from the WRONG period.
And to me, that felt more like patching than fixing.
I suspected there was something fundamentally wrong with how I’d defined time or structured the Thinking Loop that was leading Vee to make this mistake.
I needed to find out what it was before moving on.
Back to finalizing Vee’s system prompt on Qwen’s little 9B brain.
Scenario 2: Remembering - Reflection.
This was the LAST scenario I needed to test before moving on to the next phase of the project.
It was basically me asking Vee:
“What did I get done last week?”
Then invoking my question + Interaction State (current time + Items + Item History) + System Prompt.
The Items included work with different states, like todo, completed, and cancelled, along with the history of how each Item got there.
The current date and time in the test was:
Friday, Nov 13, 2026 - 4:45 PM.
I expected Vee to:
- Identify last week: Nov 2–8 (Monday–Sunday).
- Return the exact IDs of Items completed during that period.
Well, after 10 test runs, Vee kept selecting Nov 9–15 instead.
That’s THIS week. Not LAST week.
And the funny thing?
It was correctly identifying completed Items based on the period it selected.
But it was selecting the WRONG period.
I kept refining the prompt( the facts and thinking loop sections ) and testing again.
Same problem.
I genuinely couldn’t figure out why it kept doing this.
And this was the ONE remaining scenario standing between me and the next phase.
Man, I had no idea a simple question about last week was going to take up so much of my time. 😂
1/2
Back to testing Vee's system prompt on Qwen's little 9B brain.
So far, the same prompt had consistently passed my brain-dumping tests.
Now it was time to test REMEMBERING.
As a solo founder trying to compete with much larger companies, I needed to context-switch faster.
And to switch faster, I needed to remember faster.
Instead of spending time reconstructing where I left things off every time I returned to a different part of my company, I wanted to simply ask Vee.
But here's the technical challenge.
I wanted the SAME system prompt to:
- Judge whether I was brain-dumping or asking to recall progress.
- Plan the appropriate actions.
- Decide what to say.
All in ONE invocation.
No separate if/else instructions for each use case.
👉 Just a Thinking Loop + State + Output Schema.
It finally handled both kinds of requests.
Now I wanted to know how reliably.
So I ran Remembering Scenario 01 through Vee's Lab.
Me asking: "What do i got today"?,
and passing a sample tasks & events.
10 runs, measuring Judge → Plan → Say accuracy.
Here's what happened. 👇