Methodology

How a TradingFuse note actually gets to the page.

The short version: MetraFuse drafts, an editor reviews, a human signs. The long version, including what the system can and cannot do, lives below.

The pipeline, end to end

Every note follows the same six-stage pipeline. The pipeline is the methodology. We do not have an "express lane" that skips review.

1. Brief. A research brief is produced from the upcoming calendar or an editor's prompt. Briefs name the question the note will answer and the data it must cite.
2. Draft. The MetraFuse agents assemble a first draft, with sources fetched, dated, and stored at the moment of retrieval. Charts are generated from the same stored series, so the note can be reproduced exactly.
3. Review. A human editor reads the draft against the brief, checks every sourced figure, and challenges the argument. Notes that do not answer the brief are sent back, not polished.
4. Revise. Edits are applied; if a source has moved or been re-released since the draft, the agent re-fetches and the figure is updated.
5. Sign. The reviewing editor initials the note. The byline carries a human name. There is no "MetraFuse" byline, ever.
6. Publish. The note appears on /research and in the Atom feed. Corrections, if needed, are dated and visible at the top of the affected note.

What MetraFuse cannot do

The gates listed on the engine page are enforced in code, not just culture. To restate:

• Publish without an editor’s initials.
• Generate a price target.
• Issue a recommendation to trade.
• Cite a source it has not fetched and stored.
• Re-publish a corrected piece without a dated note.
• Run unattended for more than 24 hours.

Data and sourcing

Every figure in a note has a source named on first use. We prefer primary sources: the BLS for payrolls, the BEA for GDP, the Treasury for auction results, the central bank itself for policy decisions and minutes. Where we use a market-data feed for a real-time price, that price is taken from a market-data aggregate sourced from regulated venues. Sample series in charts are labelled as such, in the figure caption, on first use.

We do not republish proprietary data. Where a chart depends on a paywalled dataset, we recreate the underlying series from public sources and note the construction.

Corrections

Mistakes happen. When we make one, we say so. A correction note is added to the top of the affected piece, with the date, the original claim, and the corrected claim. The original text is preserved with a strikethrough where the change is in-line. The corrections log on the about page lists every correction issued, in date order, going back to launch.

Versioning

The MetraFuse system itself is versioned. Each release is dated, the changelog is published, and any change that affects the agents, sources, or pipeline gates is reviewed by an editor before it goes live. The current release is v2026.05, and the full changelog appears on the engine page.

What we do not publish

• Price targets or trade recommendations.
• Signals, "ideas of the day," or model portfolios.
• Affiliated-broker links or rev-share marketing copy.
• Anonymous notes. Every piece carries a human signature.

Questions about how a specific note was built? Write to hello@tradingfuse.com and we will reply with the source list and the build timestamp.