Author: rudy

What I have done 1. Rebuilt the Available Budget model (again, but correctly this time) I redefined available budget as a first-class accounting concept, not a derived guess from balances. The final authoritative formula is now: Key changes: This made the budget explainable, auditable, and predictable. 2. Persisted risk_amount_usd at position open time Previously, risk was implicit and recomputed dynamically.Now:…

🛠️ Technical Journal — Today What I have done Today was a deep stabilization and UX-cleanup day for Egis. The work wasn’t about adding flashy features — it was about making the system honest, operationally safe, and pleasant to use. 1. Hardened position auditing & reconciliation This made Egis much closer to a self-healing system. 2. Removed legacy “Paper” trading remnants…

✅ What I Have Done 1. Re-established Alice’s production discipline 2. Improved operational observability mindset 3. Hardened queue job reliability thinking 4. Designed Alice’s BI system deliberately (not randomly) Instead of adding dashboards impulsively, I designed BI as a coherent system. BI pages defined (in order of importance): Each page: 5. Identified the single most important BI…

What I have done Today’s work focused on correctness, data integrity, and long-term reliability of Egis, especially around position lifecycle, signal execution, and repairability. What I have learned

What I have done Homework publish scheduling (published_at) Homework cloning (backend-first) Teacher Homework Edit stability & UX Direct upload experiments (and rollback) Infrastructure & safety discipline What I have learned Backend truth > UI assumptions SQL semantics matter Abstractions break at infrastructure boundaries CORS errors are often lies Google Drive has a hard auth split…

What I have done What I have learned Overall, this phase reinforced a core principle for Egis:clarity of state > cleverness of logic.Once the system clearly records what it believes and why, the rest becomes much easier to reason about and fix.

🛠 What I have done 1. Strengthened operational visibility across the system Today was largely about making invisible failures visible. I extended the Incident Hub so it is no longer just a dumping ground for generic errors, but a real diagnostic tool: This directly paid off when a vague UI message “Failed to remove schedule. Please try again.”turned…

Date: 2026-01-25 → 2026-01-26Project: AliceArea: Customers > Homework, Admin > Insights 1. Problem Being Solved Customers occasionally fail to upload homework proof images/videos due to: Previously: ➡️ Goal: turn silent frontend failures into first-class incidents that admins can inspect without reading logs. 2. Existing System (Baseline) Homework Proof Upload Video Processing Logging 3. New Concept Introduced: Incident Hub Purpose A central admin-only hub for frontend-captured errors.…

1. Context & Goal Project: Egis – private mobile-first trading systemStack: Laravel 12, Inertia + React, shadcn/ui, Binance Futures TestnetCore rule: Internal positions table is the single source of truth Goal of this phase: 2. Signal Hook Strategy (Design Decision) Strategy definition Why 3. Signal Hook Webhook Design Endpoint Payload format (wrapper required) Key rules 4. Persistence: signal_hook_events Every request is stored…

Budget Drift, Exchange Sync, and Transaction Safety Context Egis is a mobile-first trading system built with: Exchanges: Key architectural rule: Internal positions table is the single source of truth.Exchange tables are mirrors / execution logs only. 1. The Core Problem: Budget Drift Keeps Coming Back Symptom Repeated errors like: This happened multiple times under different forms. Root Causes (Confirmed)…