Daily Brief
You open APEX and already know what matters today. Three to five factors, each with where it comes from and why it matters to someone who invests.
You open APEX and already know what matters
A greeting, one sentence and three to five lines with where they come from. First thing on the Dashboard, and you can close it: tomorrow the briefing is a different one.
The Daily Brief answers “what happened today?”. It is not a news digest or a newsletter: it is the set of factors APEX measured that an investor should keep in mind, each with where it comes from and why it matters.
That “why it matters” is declared by the server for each type of instrument, and it contains no action verb: no buy, no sell, no take advantage. There is a test that scans that map looking for one. A generic “this may affect your trades” is not shown: if there is no declared sentence, there is no sentence.
No language model writes this
Not once. And it is not a technical limitation: it is what makes the briefing verifiable.
What the briefing says are measured figures. Asking a model to write “+13.6% since the close” would only add a surface where that number can come out wrong, and what it would add in return —prose— is exactly what a briefing does not need. APEX composes it with arithmetic on sourced data.
There is a second reason, more boring and also real: a briefing goes out to every user several times a day on the same global data. Generating it with a model would use up the whole project's quota before lunch. Because it is identical for everyone, it is served from the network cache: a thousand visits are one real request.
- Facts
- What was measured, with time and source. Its own field.
- Observations
- What is derived from two or more facts. Its own, separate field.
- Possible explanations
- Temporal coincidences, presented as coincidences, with the warning attached to the text. Without that warning, the explanation is discarded entirely. A third party's interpretation (“analysts see pressure”) cannot even be proposed: it is not a dated fact.
- How many factors
- Five at most, and there is no minimum. A minimum is only met by padding, and a briefing that pads teaches you to ignore it. If there are only two things to tell today, two are told.
- Without an earlier snapshot
- It literally says
NO_HISTORY. Never 0% and never “no change”: both would claim a measurement that does not exist.
The briefing knows what time it is
The one you open. On Monday morning it looks at Friday, not Saturday.
The only one that interrupts. That is why having factors is not enough: it needs a change measured against the previous snapshot. An interruption with nothing to say teaches you to ignore all the others.
The day's recap, with what really moved.
There is no briefing. There is nothing to tell, and making one up would be the product's first lie.
The time zone is the project's, not your account's: APEX does not store yours yet. And without a holiday calendar, a holiday is treated as a business day — it is not approximated with a hand-written list that would age on its own.