Category: Uncategorized

  • Technical Journal — Homework Archiving & Operational Reality

    Date: TodaySystem: AliceTheme: Archiving, storage truth, and learning how production really behaves What I worked on Today was about turning “archive homework” from an idea into a production-safe operation. I built and iterated on an alice:homework:archive command with very strict constraints: The command does more than just flip a status: Once the manual command was stable, I designed the automation layer: Problems…

  • Technical Journal — 03/02/2026 (Alice)

    Today was about closing the loop between logs, reports, and human understanding. Not adding features—making reality visible. What I did What I learned Outcome By the end of today, Alice is closer to being a self-explaining system: No refactors. No new features.Just clearer truth.

  • Technical Journal — Border Generation & Audit System

    Date: 04/02/2026 What I did today Today was a long but important day focused on making the border-generation pipeline observable, auditable, and safe to operate. I worked through the entire lifecycle of border generation, not just execution, but accountability. Key things I built and fixed: What I learned Closing thought Today reinforced something I keep relearning: Good systems…

  • Egis Technical Journal – 2026-02-02

    What I have done Today was largely about consolidation, correctness, and restraint rather than adding raw features. I made a deliberate effort to reduce ambiguity in Egis by: What I have learned Closing thought Today wasn’t about shipping fast.It was about making Egis quieter, stricter, and more honest. And that’s usually a sign the architecture is moving in…

  • Technical Journal — Signal Hooks, Orders, Logs, and System Calm

    What I have done Over this session, I focused on making Egis more observable, calmer, and more explainable, without refactoring core logic. On the Signal Hooks and Orders side, I: On the logging and audit side, I: On the testing and safety side, I: Finally, I performed a deep forensic analysis of a “failed” stop-loss order by: What I have learned Closing thought This…

  • Technical Journal — Duplicate Position Guard, Signal Discipline, and Indicator Maturity

    What I have done Today I tightened several critical edges in the Egis trading system, focusing on correctness over convenience and clarity over silent behavior. 1. Fixed duplicate position blocking logic (core trading safety)Previously, Egis blocked new order placement if any open position existed for the same symbol, regardless of side.I refined this rule so that duplication is now checked…

  • Alice Technical Journal – 2026-01-30

    What I have done Today was about stabilizing Alice through observability, not adding features. Instead of building new flows, I focused on making the system explain itself when things go wrong, especially around homework uploads and admin tooling. 1. Introduced disciplined incident analysis via log-driven reporting I designed a clear, repeatable process for reading production logs (laravel-2026-01-29.log) and…

  • Technical Journal — Risk, Budget, and Control Hardening in Egis

    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:…

  • Egis Technical Journal – 2026-01-29

    🛠️ 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…