Skip to main content

Daily economic accountability — facts, sources and consequences

Read our standards

Editorial methodology

Facts first. Argument second.

Trump Economic Disaster has a clear editorial point of view. Credibility therefore depends on discipline: accurately describe the policy, identify the strongest available evidence, separate observed facts from forecasts and causal inference, and show readers where the conclusion becomes judgment.

1
Documented fact

A verifiable action, statement, measurement, release, or other element of the public record.

2
Economic analysis

An explanation of mechanisms, incentives, incidence, tradeoffs, and likely transmission through the economy.

3
Editorial judgment

A conclusion about responsibility, performance, risk, fairness, or the adequacy of a policy claim.

Reporting workflow

Evidence is the structure, not decoration.

The same sequence should govern a daily brief, a policy analysis, a fact check, and a longer accountability report.

  1. Identify the actual decision.

    Begin with the order, law, proclamation, agency action, tariff schedule, regulatory change, budget decision, court filing, or direct statement that changed the policy record.

  2. Present the administration’s case.

    State what the policy is intended to accomplish and how the administration says the benefit will occur. Criticism is stronger when the opposing claim is described accurately.

  3. Establish the economic baseline.

    Use the newest appropriate data available before the policy’s effects could reasonably appear. Do not attribute preexisting inflation, job losses, growth changes, or market conditions to a newly announced action.

  4. Trace the transmission mechanism.

    Explain how the action can move through import costs, supplier decisions, margins, prices, wages, hiring, investment, credit, public services, tax revenue, or government borrowing.

  5. Test alternative explanations.

    Consider timing, monetary policy, global conditions, sector-specific shocks, prior legislation, private behavior, statistical noise, and other causes that could weaken a simple attribution.

  6. State the conclusion at the right confidence level.

    Observed outcomes, estimates, projections, reasonable expectations, and editorial conclusions should never be written as though they carry identical certainty.

Evidence classification

Six categories readers should be able to distinguish.

An article does not need a label before every sentence, but material claims should make their evidentiary status clear through wording, context, source descriptions, or explicit callouts.

01 · Official action

What the government did.

The controlling text, effective date, scope, exceptions, legal authority, implementation status, and any unresolved procedural questions.

02 · Observed data

What has been measured.

Published figures with the correct period, units, seasonal adjustment, preliminary or final status, and known revision schedule.

03 · Reported development

What credible reporting establishes.

Negotiations, private communications, implementation details, or contemporaneous events not yet fully documented in an official record.

04 · Estimate or projection

What a model suggests.

A quantified expectation based on assumptions. The institution, model period, scenario, and material limitations should be identified.

05 · Economic analysis

How the effect is expected to travel.

Reasoned interpretation of incentives, incidence, timing, substitution, retaliation, financing, distribution, and other mechanisms.

06 · Editorial conclusion

What the evidence means for accountability.

A judgment about whether the policy claim survives scrutiny, who bears the cost, and whether the decision reflects competent stewardship.

Causation and uncertainty

Sequence is not proof of cause.

Economic outcomes are usually produced by several forces acting at once. A policy can contribute to an outcome without explaining all of it, and a plausible mechanism can exist before a measurable effect appears.

  1. Respect the timeline.

    A policy cannot explain an observation collected before it took effect. Publication dates, reference periods, implementation dates, and lag structures must be kept separate.

  2. Use proportional language.

    “Caused,” “contributed to,” “increased the risk,” “is consistent with,” and “is expected to” make different claims and require different evidence.

  3. Do not hide uncertainty.

    Unsettled negotiations, incomplete product lists, preliminary data, scenario-dependent estimates, and unknown private responses should be identified directly.

  4. Update rather than rewrite history.

    When later evidence changes the conclusion, preserve the original publication date and add a visible, dated explanation of what changed.

Live transparency audit

How the published record is signaling its evidence.

This automated review can detect links, structured source entries, evidence-label language, public-information cutoff notes, and explicit correction/update notices. It cannot determine whether an argument is economically correct; readers should use the source record and article reasoning for that judgment.

Loading the published methodology record…

Revision policy

Economic data changes. The record should show it.

Routine revisions are not evidence of misconduct; they are part of statistical production. The editorial obligation is to distinguish a routine update from a material change to the article’s conclusion.

Material change

Add a dated correction or update when a revised number, final rule, court decision, implementation notice, or newly verified fact changes the article’s central factual claim or analysis.

Non-material change

Spelling, formatting, broken-link repair, and wording changes that do not alter meaning may be corrected without a formal log entry.

Current status

The live Corrections page reads explicit article notices automatically. A modified timestamp alone is not treated as evidence that a correction occurred.

The conclusion should be inspectable—even when it is forceful.

Review the underlying source directory or inspect the visible record of corrections and meaningful updates.