Public Intelligence Schedules
TradeOS uses daily, weekly, and monthly review cadences for public-intelligence work. Exact job names, run times, platform client details, internal paths, and deployment schedules are operational configuration and are not published in external docs.
Review Cadence
| Cadence | Public purpose |
|---|---|
| Daily | Watchlist pulse, new thesis candidates, and material evidence changes. |
| Weekly | Token-risk review, outcome follow-up, and evidence-accountability checks. |
| Monthly | Longer-horizon thesis checkpoints and narrative radar. |
All public-intelligence outputs should pass review before they are published. Dry-run and preview modes exist so writing, formatting, evidence coverage, and policy behavior can be inspected safely.
What should run most often
Daily output should be reserved for the items most likely to change quickly:
- watchlist ranking;
- new candidate discovery;
- material evidence changes.
Weekly output fits slower changes:
- token risk;
- outcome follow-up;
- evidence cleanup and accountability.
Monthly output fits long-horizon themes:
- thesis checkpoints;
- narrative radar;
- sector drift.
That cadence keeps daily output useful without turning slower research into noise.
Digest vs thesis output
A digest groups multiple items into one readable briefing. It is useful for watchlists, risk reviews, material-change summaries, and narrative radar.
A thesis post focuses on one symbol or one research idea. It should explain the background, the thesis, the evidence, the uncertainty, and what would change the view.
In both cases, the output should be written for a human reader, not as operational diagnostics.