The Architecture I Built vs. The Architecture I Could Deploy

Description and use

<p>I participated in a competition and it gave me an insight into something interesting and it led me to build Vicquant. An offline financial advsior app but when i was building it, i ran into a problem and and this aid me in solving real world problem and be innovative for the time being.</p> <p>Vicquant's core idea is a dual local-model setup with zero cloud dependency: Llama-3.1-8B-Instruct for deep financial reasoning, Phi-3.5-mini as a fast, low-RAM fallback, both running through llama.cpp directly on the user's device. I will explain the reason for the split in an article soon, the short

Problem

<p>I participated in a competition and it gave me an insight into something interesting and it led me to build Vicquant. An offline financial advsior app but when i was building it, i ran into a problem and and this aid me in solving real world problem and be innovative for the time being.</p> <p>Vicquant's core idea is a dual local-model setup with zero cloud dependency: Llama-3.1-8B-Instruct for deep financial reasoning, Phi-3.5-mini as a fast, low-RAM fallback, both running through llama.cpp directly on the user's device. I will explain the reason for the split in an article soon, the short

Outcome

<p>I participated in a competition and it gave me an insight into something interesting and it led me to build Vicquant. An offline financial advsior app but when i was building it, i ran into a problem and and this aid me in solving real world problem and be innovative for the time being.</p> <p>Vicquant's core idea is a dual local-model setup with zero cloud dependency: Llama-3.1-8B-Instruct for deep financial reasoning, Phi-3.5-mini as a fast, low-RAM fallback, both running through llama.cpp directly on the user's device. I will explain the reason for the split in an article soon, the short

Evidence

The Architecture I Built vs. The Architecture I Could Deploy

Source