Brand
MarketDaily
Type
Own product · subscriber email
Lines
Content Line, Run
Our own subscriber product. Readers pick the stocks they hold; the system writes one letter per reader, not one letter sent to everyone. It is also the rig we test our own engines on before any of it touches a client.
What we did for MarketDaily
Two sends a day on a fixed schedule — 07:00 and 20:00 Taipei time — with generation started hours earlier so a slow model never delays the send.
Each issue is written by several models and picked by a judge, rather than taken from whichever model answered first.
A deterministic gate before the send: figures, undefined CSS classes, thin reasoning. Anything that fails drops to a safe version instead of going out as it is.
Two independent senders — this machine and a cloud failover that takes over if the 07:30 check finds nothing delivered — sharing one definition of "already delivered", so a handover cannot become a double send (2026-07-30).
Free since 2026-07-09: anything that analyses an individual security is open to every reader and identical for all of them.
What keeps it from breaking quietly
A watchdog checks the public archive four times a day and pushes an alert when an issue is missing — it does not wait for a reader to notice.
When an issue drops to the safe version because a check failed, a scheduled job opens a worktree, fixes the cause, runs the tests and only pushes if they pass.
Where it stands
Running every day. The archive is public and every issue carries its date, so it can be read rather than taken on trust.
