What do all these stories amount to?
Finance and politics arrive as a stream of separate stories. Following the news can tell us what happened without explaining how much the bigger picture has changed.
The Observatory began with a desire to follow those connections over time. Pressure Atlas gives its research a consistent reading experience, where new evidence can strengthen an interpretation or change its direction.
Designing the system behind the screen
I conceived the Observatory and directed its development over months of iteration with several AI models. The design work included deciding how research becomes a publishable argument, then shaping the software that lets readers examine it.
- Qualify evidence before it supports a claim.
- Keep contrary evidence beside the interpretation it limits.
- Carry an approved briefing through product checks before release.
- Record completed work and unresolved issues for the next session.
A working thesis about connected pressure
The research follows pressure through four stages. Each connection is an argument to examine, with evidence that can support or interrupt the sequence.
Built for the days that do not go to plan
The system was refined through months of use, including runs that could not proceed. It needed a clear response when evidence did not qualify and when a product check interrupted a release.
Held
September 28, 2026
Insufficient eligible fresh evidence. The previous briefing stayed available.
Resumed
October 8, 2026
A mobile layout defect was repaired. The unfinished release continued with its evidence intact.
Continuity is part of the product
The next session inherits the work
The handoff records the state of the run, including completed work and the checks still outstanding. After the October 8 repair, the same briefing reached production without repeating its research.
For readers, continuity means the published argument stays available as the next assessment develops.
From research to a checked briefing
The workflow connects research to publication through explicit checks. Each stage has a purpose, including a handoff that closes the run or preserves an unfinished release.
One connected publishing workflow
- 01
Research
Gather the evidence
- 02
Assessment
Qualify what can support a claim
- 03
Narrative
Develop a connected interpretation
- 04
Web briefing
Present the argument for examination
- 05
Release checks
Publish when the evidence and product pass
- 06
Handoff
Record the state for the next session
A run starts manually. Publication depends on the checks.
Design direction across the whole system













