T4T Macro IFVG — Execution Log
Earlier settings, and what they produced
⭐ Kept because the trades are evidence about that configuration. ⚠ They are not pooled with the live figures — comparing two different strategies as one sample would say nothing true about either. Nasdaq 3-minute
Notes on the strategy, from running it →
⭐ What running this on live accounts has made visible that a backtest cannot show — the division of labour between the strategy and the executor, what we measured, the gaps, and the design questions that belong to the author rather than to us. ⛔ Including the four changes we expected to help, measured, and dropped.
KV writes today — 593 of 1,000
The relay runs on a free tier capped at 1,000 writes a day, and ⛔ nothing would announce running out — writes would simply start failing while the relay kept answering and this page kept rendering the last good record. ⭐ So the figure is derived rather than counted: a counter would itself cost a write every time it moved.
| Source | Writes/day | Scales with |
|---|---|---|
| Heartbeats | 576 | ⚠ executors, not instruments — another instrument on an existing account costs nothing here |
| Trade reports | 13 | trades × ~5 legs each |
| Events | 4 | plans, and ⚠ a refusal costs two |
| Projected total | 593 (59%) | at today's rate, 93% of the day elapsed |
⭐ One more executor would add 288 writes a day before it placed a single trade — that, not more trading, is what would breach this. The durable record already lives in a database; this budget only governs the relay's own working store.
Deadlines and gaps
- Next deadline: Vantage demo account, 24 days away