Editorial Standards & Methodology

How Stack & State sources, verifies, and corrects.

This page describes the sourcing discipline, editorial firewall, confidence classification, and correction policy that govern every piece Stack & State publishes. It is the public accountability document for the publication.

Sourcing discipline

Stack & State uses primary government databases, procurement records, company filings, institutional reports, permitting records, trade data, and public capital announcements where available. Our preferred sources include:

• Government databases: USASpending.gov, SAM.gov, FPDS, Federal Register, SBIR.gov, Congress.gov
• Institutional reports: GAO, IEA, USGS, Congressional Research Service, agency annual reports
• Company filings: SEC filings, public company investor materials, public announcements
• Trade and permitting data: ITC trade data, FAST-41 Permitting Dashboard, public procurement records

We also receive direct signals from operators in the ecosystem -- founders, investors, program officers, and analysts. Direct signals are treated as leads for verification, not as verified facts. Before publication, every signal is checked against at least one institutional source or confirmed by a second independent signal.

Published articles carry visible source notes where public institutional sources support specific claims. If a claim lacks a public source note, readers should treat it as analytical interpretation until reviewed.

Confidence classification

Every analytical claim published by Stack & State is classified by its source confidence. The three tiers:

• Primary: The claim draws on a named, publicly verifiable institutional source (government database, official report, regulatory filing, public company filing). Primary-confidence claims carry a visible source citation.
• Mixed: The claim combines public data with analytical interpretation of market conditions. The factual components are sourced; the interpretation is editorial.
• Analytical: The claim reflects Stack & State ecosystem observation and pattern recognition. Analytical classifications represent our best assessment, not verified fact. They are hypotheses for navigation, not assertions of verified fact.

Analytical classifications should not be used as legal, investment, procurement, or compliance advice. Readers should verify time-sensitive details before acting on them. This confidence framework is structurally analogous to how intelligence products distinguish between signals intelligence, open-source analysis, and analytical judgment -- and is designed to be read that way.

Editorial firewall

Editorial judgment is independent. Companies, sponsors, members, and investors cannot buy coverage, placement, or protection from editorial criticism. This firewall is structural, not a promise. It works as follows:

• Independent analysis. Editorial decisions are based on source material, market relevance, and operator usefulness. No outside party reviews, approves, or influences editorial content before publication.
• No paid coverage. Companies, sponsors, members, and investors cannot purchase editorial placement. Coverage is earned by relevance to the publication's thesis, not by commercial relationship.
• Labeled sponsorship. Sponsored research, events, or partner work are identified clearly and separated visually and contextually from editorial content. If a reader cannot tell the difference, the labeling has failed.
• Separated introductions. Membership and introduction access are separate from editorial selection and criticism. A company's membership status or introduction history has no bearing on whether it is covered, how it is covered, or whether it is criticized.
• No pay-to-play. Stack & State does not operate a pay-to-play network. Introductions are routed only when there is clear mutual fit; no fee is charged; no guarantee is made.

If you believe this firewall has been breached, report it to walter@juncturepolicy.org.

Correction policy

If Stack & State publishes something wrong, we correct it publicly. The correction policy is:

• Significant errors -- factual mistakes that change the meaning of a piece -- are corrected on the published page with a visible correction note (date, description of the error, and the correction). If the error was distributed by email or syndication, a correction is sent through the same channel.
• Minor errors -- typographical fixes, formatting corrections, or clarifications that do not change meaning -- are corrected silently on the page.
• Retractions are rare and reserved for pieces whose central claims cannot be substantiated after publication. A retracted piece remains online with a visible retraction notice.

To report a correction, email walter@juncturepolicy.org or use the Send a Signal form. Include the specific claim, the error, and a supporting source if available.

What we do not do

• We do not sell editorial placement or coverage.
• We do not guarantee introductions.
• We do not provide legal, investment, procurement, or compliance advice.
• We do not claim to represent or speak for any organization listed in our maps or coverage.
• We do not publish unverified claims as fact.
• We do not run a pay-to-play network.

Related pages

• Full methodology -- source-confidence and signal-strength classification framework
• How it works -- signal handling, introduction routing, and what we track
• About Stack & State -- editor, thesis, and editorial firewall
• Bottleneck Map -- see the methodology applied across 25 constraints
• Privacy -- data handling and contact policy
• Send a signal or correction