2h 12m 19s logged

Devlog#19 - Greeting Everyone!

TL;DR -

Originally built the planned reasoning-heavy approach, then identified it as unnecessary complexity and hard-reset all of that work to the clean retrieval baseline. Replaced it with a minimal, structured LLM selection layer where the model only decides include + confidence, while repository intelligence and deterministic metadata remain authoritative.

Long Story -

So initially i was continuing my plan to have reasoning for every candidate why it was choosed . like was a reasoning heavy context approach includes LLM reasoning. Was working on implementing it throught a flow.
during testing, debugging and checking that it works perfectly but things went the other ways. during the checking, i got to a problem that LLM gives out many token in reasoning and which exceeds the limit or the max_tokens limit that i have. it was bad as i couldnt get reasoning perfectly for the per candidate.
the i thought of another approach. i will generate the candidates and then i will give all the reasoning fo all of the candidates at the end of it. but this want also working as i wanted it to.
i had committed the wrong changes and then i had to hard reset to a stable previous commit whcih didnt had this.
then i realized that i was making the system too complicated and it wasnt needed so i remove dthe reasoning nd hard reset to a previous atable commit.
I used AI to fix the broken code for the reasoning part that i built but after multiple attempts . So as i said before, 1 option only i reverted to a old git commit .

this took most of my time but then did some chages also

now context_forgehandes repo intellengence and LLM which decide only what is actually worth keeping.
added a strict context-selection contract.
Added the selection service to handle the model interaction and validate its response
Selection confidence is carried into the final context as metadata, keeping the output inspectable without depending on generated explanations.
Added and updated tests around the contract, selection service, package construction, and engine integration

Well so this much only today. This day was hassle ful. I’ve used AI 2 times to fix the tings but 1 time i was successful and 1 time i am not. But keeping it aside. i am close to complete the ‘source code’ but not too close. I am thinking of having a brew tap for mac users and another way for windows and linux. The system isnt perfect but it is running. I will make it better nd make it functionable in real world.

SO these chages today were light. Most time spent was on Debuging and checkigerrors an fixing them.

If hackatime would calculate time spent debugging or xiing, tiday would be 6h+ devlog.

Leave ur thouhts in the coments and plz like it.