Memory and context persistence across conversations are achieved through a multi-layered database and state architecture. The primary database layer utilizes a PostgreSQL agent_interaction_log table to save complete prompt-and-response chat histories, allowing the FastAPI gateway to reload prior turns and maintain continuity rather than acting as a one-shot interface. This is supported by the ai_knowledge_record table, which acts as the system's persistent source of truth for trained market facts. Within the multi-agent committee, state persistence is governed by a unified AgentState that carries an InvestDebateState and a RiskDebateState alongside a persistent past_context block to track cross-ticker lessons. Furthermore, an automated background scheduler triggers an AI Knowledge Refresher task daily at 01:00 AM UTC, ensuring the local LLM’s context window is continuously updated and grounded with the latest macroeconomic regimes. For terminal operations, a local .geminirc configuration file is deployed to act as "permanent memory," forcing the AI assistant to remember non-negotiable rules—like the same-sign allocation guardrail, lowercase data casing, and VRAM limits—across independent terminal sessions.

Built-in tool access enables the system to actively execute tasks rather than just generate text. We integrated targeted programmatic toolsets directly into the agent environments:

• Our Quantitative Researcher agent uses custom registered tools such as pandas_ledger_parser and execute_model_weight_adjustment to autonomously read local portfolio CSV ledgers, recalculate performance ratios, and adjust alpha multipliers.
• Standalone committee agents also leverage a customized web_search tool for real-time market intelligence gathering.
• On the execution side, tool access is wired to our unified BrokerService registry, which maps trading signals to production-ready adapters for Questrade, Alpaca, and Webull.
• To maintain persistent, unattended operations 24/7/365, a background token rotation daemon uses Redis to secure and rotate Questrade OAuth tokens every 25 minutes, ensuring emergency stop-loss and rebalancing orders can be triggered without manual intervention.

System autonomy is achieved by utilizing a multi-agent orchestration framework powered by Google’s Agent Development Kit (ADK) and LangGraph. Rather than forcing the user to spell out every step, they simply provide a high-level goal (e.g., "Analyze TSLA with moderate risk and long-term horizon on Questrade"), and the AgentCoordinator layer distributes the cognitive load across specialized, collaborative personas:

1. The Primary Coordinator (financial_coordinator) maps user goals, routes context, and orchestrates the workflow.
2. The Data Analyst (data_analyst) autonomously retrieves SEC filings and news.
3. The Trading Analyst (trading_analyst) evaluates technical setups against 5 quantitative strategies.
4. The Risk Analyst (risk_analyst) acts as the gatekeeper, verifying that allocations align with strict drawdown circuit breakers and sector concentration caps.
5. The Execution Analyst (execution_analyst) optimizes order routing to specific brokers.
6. The Quantitative Researcher (quantitative_researcher) performs post-trade audits, executing forensic "Whipsaw Analysis" to identify stopped-out trades that prematurely reversed; if whipsaw rates exceed 20%, it autonomously triggers a "WIDEN_STOP_LOSS" event to increase the system's ATR multiplier from 2.0x to 2.50x.

To finalize a decision, the coordinator pits the aggressive, alpha-seeking "Hunter" perspectives against the defensive "Guardian" constraints, filters the debate through reinforcement learning DQN Q-values, and synthesizes the outputs into a structured "Balanced Institutional Verdict" for execution.

🎧 I could turn this architectural breakdown into an audio overview you can listen to on the go.

Hey everyone! I'm u/Quantinvests, a founding moderator of r/quantinvests.
This is our new home for all things related to [ADD WHAT YOUR SUBREDDIT IS ABOUT HERE]. We're excited to have you join us!

What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts, photos, or questions about [ADD SOME EXAMPLES OF WHAT YOU WANT PEOPLE IN THE COMMUNITY TO POST].

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.

How to Get Started

1. Introduce yourself in the comments below.
2. Post something today! Even a simple question can spark a great conversation.
3. If you know someone who would love this community, invite them to join.
4. Interested in helping out? We're always looking for new moderators, so feel free to reach out to me to apply.

Thanks for being part of the very first wave. Together, let's make r/quantinvests amazing.

How I built a quantitative trading app with 100% gross margins and $0 server bills

I wanted to share the architecture behind QuantInvests V6. Instead of a basic chatbot, we built a 5-Agent Neural Committee using Google's new Agent Development Kit (ADK).

By containerizing our Postgres 15 database, Redis cache, FastAPI gateway, and Flask quant engine, we run the entire backend on a local edge server. Cloudflare Zero Trust Tunnels expose it safely to our React SPA hosted on Firebase (Free tier).

Running a local LLM (Gemma-2b-it) on a 6GB VRAM GPU is a recipe for CUDA Out-of-Memory (OOM) crashes. We solved this in our QLoRA training pipeline by switching to float16, PyTorch gradient checkpointing, and injected active garbage collection.

Code is available, let me know if you have questions on the WSL2 routing!

Mistakes in the real stock market are expensive. In QuantInvests V6, they are just lessons.

If you want to understand quantitative portfolio management without risking a single dollar, QuantInvests V6 is your 100% free, simulated institutional-grade playground. We seed your account with $250,000+ in virtual capital so you can master algorithmic trading in a risk-free environment.
Here is what you can experience inside:

🧠 The Neural Committee Dashboard: Watch 6 specialized AI subagents (including the Alpha Hunter and Risk Guardian) collaborate in real-time to audit constraints and suggest portfolio actions.
🔌 Mock Broker Environments: Connect simulated TFSA or Margin accounts that mirror the operational flow of Questrade, Alpaca, and Webull.
📊 Dynamic Technical Charts: Analyze client-side SMA, Bollinger Bands, and ATR stop-loss bands.
⚙️ Autopilot Rebalancing: Move beyond "buy and hold" and learn how quantitative managers optimize risk-adjusted returns.
Stop guessing and start simulating. 📈 Access the app today: [**app.quantinvests.com**](https://www.linkedin.com/safety/go/?url=http%3A%2F%2Fapp%2Equantinvests%2Ecom&urlhash=rLU4&mt=0SlsM8uWMHrHUQkOI9udIGBYgQLOsII8b5mM2DCF6kfU1dmTfteOz1CUwfXHvbROXQ-pb1g2iqEzNVIuFjyD9LOJVmD7mRMevNp7F6TKyK\_jgsAy1OZtsxdvKg&isSdui=true) (Where The Quant Invests For You!)

**r/**[**FinancialMarkets**](https://www.linkedin.com/search/results/all/?keywords=%23financialmarkets&origin=HASH\_TAG\_FROM\_FEED) **r/**[**Education**](https://www.linkedin.com/search/results/all/?keywords=%23education&origin=HASH\_TAG\_FROM\_FEED) r/FreeAgent

# Hey r/QuantInvests [](https://www.reddit.com/r/algorithmictrading/?f=flair\_name%3A%22Strategy%22)

Most retail portfolio systems rely on static stop-losses (e.g., "sell if it drops 5%"). The problem? High-beta assets get whipsawed, and low-beta assets hold too much capital risk.

For the \*\*Release v6.5.6\*\* of our platform, \*\*QuantInvests\*\*, we set out to build an institutional-grade risk engine and copy-trading framework that upgrades portfolio management from \*reactive\* stops to \*predictive\* volatility scaling.

Here is how the architecture works, how the quant agents collaborate, and how users connect their brokerages to copy-sync models.

\### 📊 1. The Core: Vectorized EWMA Covariance & Monte Carlo VaR

To keep Docker container builds extremely lean and avoid heavy native C-compiled dependencies (like the \`arch\` package) inside our WSL2/droplet dev parity, we bypassed GARCH and implemented a light vectorized conditional covariance matrix using \*\*EWMA (Exponentially Weighted Moving Average)\*\* in Pandas and NumPy.

\* \*\*Historical Window\*\*: 120 days.

\* \*\*Predictive Metrics\*\*: The engine calculates Parametric daily \*\*Value-at-Risk (VaR)\*\* and \*\*Expected Shortfall (ES)\*\* at 95% and 99% confidence intervals in under 100ms.

\* \*\*Monte Carlo Simulation\*\*: Runs \*\*5,000 randomized path simulations\*\* to project future portfolio equity boundaries (5th, 50th, and 95th percentiles) over a 30-day projection envelope.

\* \*\*Quarter-Kelly Sizing\*\*: Computes target weights relative to historical asset volatility, capped at 30% per asset for safety.

\### 🤖 2. The Neural Committee (ADK Orchestration)

Instead of a single LLM trying to do everything, the system routes portfolio queries through a specialized \*\*Autonomous Developer Kit (ADK) Neural Committee\*\*:

1. \*\*Alpha Hunter (Agent)\*\*: Scrapes signals and identifies divergence momentum.
2. \*\*Risk Guardian (Agent)\*\*: Computes the volatility bounds and VaR metrics.
3. \*\*Auditor (Agent)\*\*: Audits transaction logs, records whipsaw stop-out data, and tracks stop-loss SD multipliers (adjusting between 2.0x to 2.5x)

\### 🔄 3. Connecting Your Broker: Multi-Broker Copy-Sync V2

Advisors and quantitative traders can now register and connect their own brokerage accounts to sync client positions directly to their master portfolio:

\* \*\*Supported Providers\*\*: Secure OAuth token rotation for \*\*Questrade\*\*, \*\*Alpaca\*\*, and \*\*Webull\*\* API integrations (or \*\*Manual\*\* mode for sandbox testing).

\* \*\*Drift Analysis\*\*: The system calculates the asset allocation drift between the master portfolio and the connected broker account.

\* \*\*Execution Modal\*\*: Deployed a retro-themed, glassmorphic React dashboard featuring a green CRT console log displaying live brokerage submission logs.

\### 🛡️ 4. Institutional Governance (GIPS-Compliant Risk Override)

Automated copy-trading is highly convenient, but unattended execution during market shocks can blow up accounts. We implemented a hard governance constraint:

\* \*\*Threshold Blocking\*\*: If the calculated daily VaR of a client portfolio exceeds \*\*5.0%\*\*, the copy-sync execution is strictly blocked.

\* \*\*Risk Override Prompt\*\*: The advisor is prompted with a manual override modal explaining the breach.

\* \*\*Audit Trail Ledger\*\*: Authorizing the override appends a machine-readable JSONL event and a GIPS-compliant warning block to a persistent markdown file (\`TRADING\_AUDIT.md\`) tracking advisor accountability:

\> \*\*\[WARNING\] RISK BREACH & OVERRIDE AUTHORIZED\*\*

\> Daily Value-at-Risk (VaR) of 8.00% exceeded the institutional limit of 5.00%. Proceeding under manual Advisor override.

\### 💬 5. Two-Way Discord Integration

\* \*\*Interactive Pull\*\*: Users can ping our Discord bot relay (utilizing non-blocking async \`aiohttp\` to avoid heartbeat timeouts) to query real-time trend lookups and portfolio audits.

\* \*\*Automated Push\*\*: The daily quantitative pipeline at \*\*4:10 PM EST\*\* automatically triggers a Discord webhook, pushing high-conviction signals immediately as markets close.

\### 🛠️ The Tech Stack

\* \*\*Backend\*\*: Flask, FastAPI (Wildcard Nginx proxying for gateway routing), Redis, Postgres

\* \*\*Frontend\*\*: React (TypeScript), Recharts/Highcharts, TailwindCSS (Institutional Glassmorphism)

\* \*\*Environment\*\*: Docker Compose WSL2 / DigitalOcean Droplets managed with \`uv\` for lightning-fast package syncing.

We'd love to hear your thoughts on how you handle portfolio covariance mapping and client synchronization!

\*\*QuantInvests: "Where The Quant Invests For You!"\*\*

Here is how we are addressing this in the **QuantInvests V6** architecture, split between organic sizing dynamics and planned overlays:

### 1. Organic Volatility Scaling via Quarter-Kelly Sizing

Because our portfolio sizer uses a **Quarter-Kelly allocation fraction**:

$$f^* = 0.25 \times \frac{\mu_i}{\sigma_i^2}$$

where $\sigma_i^2$ is the EWMA variance.

When a sudden volatility spike occurs, the denominator $\sigma_i^2$ increases quadratically relative to the volatility increase. This causes an **automatic, organic deleveraging** of high-volatility assets without needing a separate overlay. Sizing drops immediately as the variance term spikes.

### 2. Volatility Targeting Overlay (Gross Exposure Scaling)

To handle portfolio-level risk during regime shifts, we are looking at implementing an explicit **Volatility Targeting Overlay**.

* We define an institutional annualized volatility target (e.g., $\sigma_{\text{target}} = 10\%$).

* If the annualized portfolio volatility (EWMA) exceeds this threshold, we compute a scaling factor:

$$F = \min\left(1.0, \frac{\sigma_{\text{target}}}{\sigma_{\text{realized}}}\right)$$

* We then scale down the weights of all active positions by $F$ and sweep the remaining allocation into our cash buffer. During high-vol regimes, this automatically deleverages the entire portfolio to keep aggregate risk constant.

### 3. Dynamic Decay ($\lambda$) Tuning

Instead of keeping a static $\lambda = 0.94$ (the RiskMetrics daily standard), we are exploring a **surprise-sensitive decay model**:

* We track the normalized return surprise (standardized residuals):

$$z_t = \frac{R_t}{\sigma_{t-1}}$$

* If $|z_t| > 3.0$ (a 3-sigma event), we temporarily drop $\lambda$ to **0.85–0.88**.

* **Why?** Dropping $\lambda$ forces the covariance calculation to heavily discount older data and immediately lock onto the new high-volatility regime. As standardized returns normalize, $\lambda$ decays back up to 0.94 to smooth out estimation noise.

### 4. Stopping Whipsaws with Stop-Loss Expansion

To complement the sizing reduction, our **Auditor Agent** monitors the stop-loss standard deviation multipliers. During high-vol regime detections:

* The ATR-based stop-loss multiplier automatically expands from **2.00x to 2.50x** (read from `risk_configs.json`).

* This prevents our positions from being prematurely shaken out by noise during the initial surge of the regime shift, while the Kelly model scales down the *size* of the position to keep the absolute dollar-at-risk identical.

How do you usually handle the trade-off between reacting quickly to spikes vs. avoiding over-reaction to short-lived noise (like a single-day flash crash)?

You can now connect your own trading agent to ours for for:
1) Multi-Broker Copy-Sync
2) GIPS-Compliant Risk Override Governance
3) Predictive Risk Parity (EWMA)
4)  Glassmorphic Advisor Control Room

Our daily quantitative pipeline now runs at 4:10 PM EST, immediately broadcasting high-conviction signals through automated webhooks to our community.
A huge thank you to our engineering and quantitative research teams for building this under a lean, Dockerized WSL2 stack using uv.
At QuantInvests, we are making institutional portfolio management accessible, scalable, and secure.
QuantInvests: "Where The Quant Invests For You!"

Hey r/QuantInvests

Most retail portfolio systems rely on static stop-losses (e.g., "sell if it drops 5%"). The problem? High-beta assets get whipsawed, and low-beta assets hold too much capital risk.

For the **Release v6.5.6** of our platform, **QuantInvests**, we set out to build an institutional-grade risk engine and copy-trading framework that upgrades portfolio management from *reactive* stops to *predictive* volatility scaling.

Here is how the architecture works, how the quant agents collaborate, and how users connect their brokerages to copy-sync models.

### 📊 1. The Core: Vectorized EWMA Covariance & Monte Carlo VaR

To keep Docker container builds extremely lean and avoid heavy native C-compiled dependencies (like the `arch` package) inside our WSL2/droplet dev parity, we bypassed GARCH and implemented a light vectorized conditional covariance matrix using **EWMA (Exponentially Weighted Moving Average)** in Pandas and NumPy.

* **Historical Window**: 120 days.

* **Predictive Metrics**: The engine calculates Parametric daily **Value-at-Risk (VaR)** and **Expected Shortfall (ES)** at 95% and 99% confidence intervals in under 100ms.

* **Monte Carlo Simulation**: Runs **5,000 randomized path simulations** to project future portfolio equity boundaries (5th, 50th, and 95th percentiles) over a 30-day projection envelope.

* **Quarter-Kelly Sizing**: Computes target weights relative to historical asset volatility, capped at 30% per asset for safety.

### 🤖 2. The Neural Committee (ADK Orchestration)

Instead of a single LLM trying to do everything, the system routes portfolio queries through a specialized **Autonomous Developer Kit (ADK) Neural Committee**:

1. **Alpha Hunter (Agent)**: Scrapes signals and identifies divergence momentum.
2. **Risk Guardian (Agent)**: Computes the volatility bounds and VaR metrics.
3. **Auditor (Agent)**: Audits transaction logs, records whipsaw stop-out data, and tracks stop-loss SD multipliers (adjusting between 2.0x to 2.5x)

### 🔄 3. Connecting Your Broker: Multi-Broker Copy-Sync V2

Advisors and quantitative traders can now register and connect their own brokerage accounts to sync client positions directly to their master portfolio:

* **Supported Providers**: Secure OAuth token rotation for **Questrade**, **Alpaca**, and **Webull** API integrations (or **Manual** mode for sandbox testing).

* **Drift Analysis**: The system calculates the asset allocation drift between the master portfolio and the connected broker account.

* **Execution Modal**: Deployed a retro-themed, glassmorphic React dashboard featuring a green CRT console log displaying live brokerage submission logs.

### 🛡️ 4. Institutional Governance (GIPS-Compliant Risk Override)

Automated copy-trading is highly convenient, but unattended execution during market shocks can blow up accounts. We implemented a hard governance constraint:

* **Threshold Blocking**: If the calculated daily VaR of a client portfolio exceeds **5.0%**, the copy-sync execution is strictly blocked.

* **Risk Override Prompt**: The advisor is prompted with a manual override modal explaining the breach.

* **Audit Trail Ledger**: Authorizing the override appends a machine-readable JSONL event and a GIPS-compliant warning block to a persistent markdown file (`TRADING_AUDIT.md`) tracking advisor accountability:

> **[WARNING] RISK BREACH & OVERRIDE AUTHORIZED**

> Daily Value-at-Risk (VaR) of 8.00% exceeded the institutional limit of 5.00%. Proceeding under manual Advisor override.

### 💬 5. Two-Way Discord Integration

* **Interactive Pull**: Users can ping our Discord bot relay (utilizing non-blocking async `aiohttp` to avoid heartbeat timeouts) to query real-time trend lookups and portfolio audits.

* **Automated Push**: The daily quantitative pipeline at **4:10 PM EST** automatically triggers a Discord webhook, pushing high-conviction signals immediately as markets close.

### 🛠️ The Tech Stack

* **Backend**: Flask, FastAPI (Wildcard Nginx proxying for gateway routing), Redis, Postgres

* **Frontend**: React (TypeScript), Recharts/Highcharts, TailwindCSS (Institutional Glassmorphism)

* **Environment**: Docker Compose WSL2 / DigitalOcean Droplets managed with `uv` for lightning-fast package syncing.

We'd love to hear your thoughts on how you handle portfolio covariance mapping and client synchronization!

**QuantInvests: "Where The Quant Invests For You!"**

How I built a quantitative trading app with 100% gross margins and $0 server bills

I wanted to share the architecture behind QuantInvests V6. Instead of a basic chatbot, we built a 5-Agent Neural Committee using Google's new Agent Development Kit (ADK).

By containerizing our Postgres 15 database, Redis cache, FastAPI gateway, and Flask quant engine, we run the entire backend on a local edge server. Cloudflare Zero Trust Tunnels expose it safely to our React SPA hosted on Firebase (Free tier).

Running a local LLM (Gemma-2b-it) on a 6GB VRAM GPU is a recipe for CUDA Out-of-Memory (OOM) crashes. We solved this in our QLoRA training pipeline by switching to float16, PyTorch gradient checkpointing, and injected active garbage collection.

Code is available, let me know if you have questions on the WSL2 routing!

Mistakes in the real stock market are expensive. In QuantInvests V6, they are just lessons.

If you want to understand quantitative portfolio management without risking a single dollar, QuantInvests V6 is your 100% free, simulated institutional-grade playground. We seed your account with $250,000+ in virtual capital so you can master algorithmic trading in a risk-free environment.
Here is what you can experience inside:

🧠 The Neural Committee Dashboard: Watch 6 specialized AI subagents (including the Alpha Hunter and Risk Guardian) collaborate in real-time to audit constraints and suggest portfolio actions.
🔌 Mock Broker Environments: Connect simulated TFSA or Margin accounts that mirror the operational flow of Questrade, Alpaca, and Webull.
📊 Dynamic Technical Charts: Analyze client-side SMA, Bollinger Bands, and ATR stop-loss bands.
⚙️ Autopilot Rebalancing: Move beyond "buy and hold" and learn how quantitative managers optimize risk-adjusted returns.
Stop guessing and start simulating. 📈 Access the app today: app.quantinvests.com (Where The Quant Invests For You!)

r/FinancialMarkets r/Education r/FreeAgent

We are excited to announce our brand new **Google Home Voice Integration Control Panel**, live on the Manual Operations Tracker. You can speak to it like you speak to your broker.

 

Managing institutional portfolio allocations just entered a new dimension. We are excited to announce our brand new **Google Home Voice Integration Control Panel**, live on the Manual Operations Tracker page (`/tracker`)!

 

With this release, we have bridged voice assistant interactions with a secure, sandboxed rebalancing environment. You now have complete, real-time control over how your smart assistant manages extra cash and custom assets.

 

#### 🎙️ Key Capabilities:

1. **The Voice Bridge Toggle**: Turn your Google Home fulfillment on or off with a single tap of an iOS-style glassmorphic switch.

2. **Extra Cash Allocations**: Dynamically set exact cash thresholds via a slider to dictate how much capital the voice assistant can query or rebalance.

3. **Unlisted Ticker Verification Queue**: Want to trade assets outside the standard universe? Tickers queried by voice are automatically held in a verification queue. Approve or reject them directly from the dashboard to safely integrate them into your environment.

4. **Zero-Interference Sandbox**: Completely isolated from core systems, allowing interactive customization without affecting main model pipelines.

 

Experience the future of quantitative wealth management. Say: *"Hey Google, check my portfolio rebalancing."*

 

💡 Learn more at `app.quantinvests.com`

r/Trading r/googlehome r/NeuralNetwork r/algotrading r/AI_Agents