From price move to explanation: how the weekly note is built.
This project grew out of a simple weekly habit: record what changed in energy markets, then ask whether the physical system actually supports the story told by prices. The aim is not to imitate a market terminal. It is to explain a small set of benchmarks carefully enough that a reader can follow the chain from event to mechanism to price.
01
Start with the market, then check the system
The Friday close is the starting point, not the conclusion. I first record what changed in Brent, WTI, Henry Hub, TTF, and JKM, then look for the physical and institutional evidence that could explain the move: inventories, shipping, outages, weather, policy decisions, and changes in expectations.
02
Prefer primary sources
Where possible, prices and balances come from exchanges, statistical agencies, regulators, system operators, and other primary institutions. Company statements and government releases are useful for specific events. Reuters and other major news services help establish chronology. Secondary market-data services are used when an exact primary close is not publicly available.
03
Keep comparisons like-for-like
A weekly percentage is only useful if the underlying benchmark is comparable. I keep units and reference contracts consistent wherever possible and flag contract rolls, proxy series, thin trading, or timing mismatches when they matter. If a clean comparison is not possible, the limitation stays visible.
04
Separate observation from interpretation
A price move and a news headline occurring together do not establish causation. For a driver to be persuasive, the timing should fit, the transmission mechanism should make sense, and some independent physical or institutional evidence should point in the same direction. When several explanations remain plausible, the brief says so.
05
Scenarios are questions, not predictions
The scenarios at the end of an edition are competing paths to watch. Each one is tied to observable signals—such as a reopening route, a storage threshold, a policy decision, or a change in vessel traffic. The next edition can then ask what actually happened instead of quietly rewriting the earlier view.
06
Leave gaps visible
The web archive is still young. I do not manufacture a longer history by filling missing weeks or inventing observations. Short series are shown for what they are: a record of the published editions so far. Statistical claims stay modest until the sample is long and consistent enough to support more.
07
Correct errors without erasing the record
Typos and clear factual errors should be corrected. If a material number, calculation, or conclusion changes, that change should be noted rather than silently replacing the earlier record. The point of an archive is to preserve what was known and argued at the time.
08
English and Farsi should carry the same argument
The two language editions use the same figures, sources, and analytical conclusions. The Farsi text is not meant to be a literal translation; technical accuracy and natural prose matter more than matching each sentence word for word.
The weekly rhythm
The Saturday edition is assembled through the week, not in one sitting.
That sequence matters because market headlines arrive faster than inventories, shipping data, and other physical evidence.
During the week: track prices, events, and the physical evidence that may matter.
Friday: close the observation window and re-check units and reference contracts.
After the close: test competing explanations against timing and physical data.
Write the brief, then check the English and Farsi editions against the same figures and argument.
Publish the edition with its sources and preserve it in the archive for later comparison.