source-notes

Source: U.S. Census Bureau, "Business Formation Statistics," Announcements notices, under "Latest Monthly Business Formation Statistics Report": https://www.census.gov/econ/bfs/index.html

Quoted: "As of the January 2026 monthly release, applications associated with internet sales are excluded from the high-propensity (HBA) and corporation (CBA) application series. This methodology change was originally scheduled to occur during the November 2025 monthly release. The HBA and CBA definitions are updated for the entire time series."

Also quoted: "Due to significant differences between 2017 NAICS and 2022 NAICS vintages, the entire time series was restated to 2022 NAICS during this annual update. The January 2026 monthly data publication was the first release using 2022 NAICS."

And: "Due to a scheduled outage of the Internal Revenue Service's online Employer Identification Number (EIN) Assistant from December 30, 2025 until January 5, 2026, applicants were unable to apply for an EIN through…

Source: AWS Builders' Library, "Making retries safe with idempotent APIs" by Malcolm Featonby. https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/

Locator: section "Reducing client complexity with idempotent API design."

Quoted: "We can significantly simplify client code by delivering a contract that allows the client to make a simplifying assumption that any error that isn't a validation error can be overcome by retrying the request until it succeeds." And: "You could derive a hash of the parameters present and assume that any request from the same caller with identical parameters is a duplicate. On the surface, this seems to simplify both the customer experience and the service implementation. However, we have found that this approach doesn't work in all cases."

What this establishes: idempotency requires an explicit caller-supplied token, not a parameter hash. Two calls with identical parameters can be two distinct intents (the article's example: launching…

Source: BLS, "Consumer Price Index – August 2026" (USDL-26-1496, Sept 11, 2026). Canonical URL: https://www.bls.gov/cpi/news.htm (I could not fetch it directly — BLS returned an automated-access "Access Denied" page — so I read the identical release text via the FRASER mirror: https://fraser.stlouisfed.org/title/consumer-price-index-6838/august-2026-735977).

Locator: opening paragraphs of the release body, plus the single NOTE line below them.

Quoted: "The Consumer Price Index for All Urban Consumers (CPI-U) increased 0.4 percent on a seasonally adjusted basis in August... Over the last 12 months, the all items index increased 3.4 percent before seasonal adjustment." And: "The index for all items less food and energy rose 0.3 percent... The energy index increased 16.3 percent for the 12 months ending August. The food index increased 2.7 percent over the last year."

Two details that change how the headline number should be read:

Source: Stripe API Reference, "Idempotent requests" section. https://docs.stripe.com/api/idempotent_requests

Key passage (quoted): "Subsequent requests with the same key return the same result, including 500 errors." And: "We save results only after the execution of an endpoint begins. If incoming parameters fail validation, or the request conflicts with another request that's executing concurrently, we don't save the idempotent result because no API endpoint initiates the execution. You can retry these requests."

What this establishes: A timeout is ambiguous — the server may have already committed the mutation before your connection dropped. The idempotency layer resolves this by caching the full response (success or failure) under the key. A retry with the same key returns the cached result instead of re-executing. The concrete distinction: "connection timeout with no response received" is safe to retry (the key makes it idempotent); "400 validation error" is not a timeout — the…

Source: "Russian Threats to NATO's Eastern Flank: Scenarios, Strategy, and Policy for European Security" — Belfer Center, Feb 5 2026. https://www.belfercenter.org/research-analysis/russia-nato-baltics-scenarios-europe-security

Locator: "Key Judgments" section, first bullet, and the closing paragraph on public resilience.

Quoted: "Putin's core strategic objective is to fracture the NATO alliance." And, on the rear-area dimension: "Russia combines massive force at the front with sabotage, hacking, and information operations in Europe's rear."

What this establishes (author's claim): The report treats NATO cohesion itself as the primary Russian target, and frames gray-zone information operations as an integral, not auxiliary, instrument of Russian coercion. The scenario logic is explicit — a limited fait accompli works only if NATO's political consensus is slow, so the informational and political layer is where the battle is decided before the kinetic one.

Source: "WAICO 2026: A New Chapter in AI Diplomacy" (July 23, 2026) — Geneva School of Diplomacy. https://genevadiplomacy.ch/waico-2026-a-new-chapter-in-ai-diplomacy/

Relevant passage: "Rather than merely positioning these Chinese-led initiatives as competitive tools in great-power games, they can be better interpreted as constructive contributions to the ongoing multilateral dialogue on transformative technology governance, supplementing and improving the existing fragmented global AI governance architecture."

What this establishes: China is actively institutionalizing its AI governance framework via the "World AI Cooperation Organization" (WAICO), launched at WAIC 2026. The explicit framing rejects the "great-power competition" lens in favor of a "constructive contribution" narrative. This is a soft-power maneuver: positioning China as the champion of Global South inclusion in AI rulemaking, while framing Western "competition" framing as the obstacle to multilateralism.

The authors (Dr.…