On October 26, Anthropic filed its Form S-1 on EDGAR. This article returns to the source document, reading it across five separate ledgers—profit, growth, contracts, control, and AI—then takes the highest-upvoted comments from Hacker News, Reddit, and X and fact-checks them one by one: which numbers match, which don't, and which are still blank.
In this 335-page document, the easiest mistake is adding the big numbers together. $80.7B is the accounting mirror of valuation gains; $10.8B vs $265.6B is a maturity mismatch; 50.1% is a control-rights design. These three are different in nature—they cannot be converted into each other, nor should they offset one another. Which ones have already happened, which might happen, and which are left blank—read them separately, or you'll read blanks as answers.
The buffer the document provides is $130B+ in cash; the condition is that usage keeps climbing. The numbers that would verify this condition are exactly the ones blank in the S-1: Q3 revenue and expenses. They'll appear in the amended filing; once they do, the inflection point in the profit ledger, the slope in the growth ledger, and the mismatch in the contract ledger all need to be rechecked.
On Monday, October 26, Anthropic filed its Form S-1 on EDGAR (Registration No. 333-299633). It plans to list on the Nasdaq Global Select Market under the ticker ANT, with a 22-member underwriting syndicate led by Goldman Sachs, Morgan Stanley, and JPMorgan. The company's official announcement was one sentence: the number of shares and price range have not yet been determined. FT counted: 335 pages.
This document contains three numbers that, placed side by side, form its outline:
These three quantities are not the same thing, and they cannot be converted into one another. The rest of this article reads them across separate ledgers: profit, growth, contracts, control, and AI. The final chapter examines the community—what the highest-upvoted comments on Hacker News, Reddit, and X are saying, and which numbers match the source document and which don't.
Two notes. First, all figures and quotes marked "S-1" in this article have been verified against the EDGAR source; where tables are compressed into strings of numbers, column names are inferred from context, and inferences are noted. Second, this document contains significant blanks: price range, share count, Q3 revenue, total commitment amounts—these are empty in the original, not overlooked. The numbers in this article are factual records, not investment advice.
Let's start with the scariest number.
In H1 2026, Anthropic's GAAP net loss was $80.748 billion (full-year 2025: $41.965B; 2024: $8.309B). Broken down, the actual "business loss" was only $0.693B: revenue of $16.286B minus compute & infrastructure $8.945B, personnel $3.152B, sales marketing & partnerships $3.168B, and other operating & admin $1.714B, yielding an operating loss of $0.693B and an operating margin of -4% (full-year 2025 was -176%). The remaining $80B is all below the operating line.
The largest chunk is $72.388B, from fair value changes on convertible notes, derivative liabilities, and SAFEs. These instruments are held by strategic partners and investors like Amazon and Google, carried at fair value, which depends on the company's enterprise valuation: when valuation rises, the "convertible rights" owed to them become more valuable, and accounting records this as a loss. The document's own explanation is that the changes are primarily driven by increases in the fair value of the notes, which in turn are driven by increases in enterprise valuation. The concentration is in Q2, when $59.597B was recorded, corresponding to the valuation uplift from the Series H round.
The flip side of the valuation uplift is the preferred stock price:
This chart is the origin of the $72.388B. Each funding round raises the valuation a notch, and the old notes on the books record another loss. Most of these notes will convert into non-voting Class N shares at IPO: Amazon's conversion price is the lower of $2.0928 or $5.0478 per share versus the IPO price, subject to a 12% ownership cap; excess converts into zero-interest extended-term notes that continue converting at each quarter-end post-IPO; if the ownership cap hasn't expired or a default occurs, only then is cash repayment required. So this $80.7B most likely won't become repayment—it'll become dilution: the loss is on paper; the dilution is real.
The cash picture is entirely different. H1 operating cash flow was +$3.929 billion (full-year 2025 was -$2.637B); financing cash flow was +$110.774B, of which $110.432B was net proceeds from preferred stock issuance; as of June 30, cash and equivalents were $112.389B, short-term investments $19.262B, totaling $131.651B. The document states cumulative funding of $141.1 billion; subtracting the two, approximately $9.4B was "actually burned" (this article's arithmetic, as of June 30 only). Accumulated deficit was $132.902B, of which $113.2B was fair value changes on notes etc. The company's own "adjusted" metrics look better: adjusted operating profit +$1.618B, adjusted net profit +$2.671B, excluding stock-based compensation, non-cash charitable donations, and the Bartz settlement; but Q2 GAAP operating profit was itself positive—$0.974B, an 8% operating margin.
There are three spots in this chapter worth a second look.
Starting in 2025, the company changed its expense presentation from "by function" to "by nature," and gross profit is no longer reported separately. The 85% gross margin commonly cited in the community is derived from the supplementary by-function table: H1 2026 "cost of revenue" was $2.380B against $16.286B in revenue. The document states that cost of revenue is "substantially all" compute serving customers; but compute used by free users is recorded under sales & marketing, and compute for training, research, and internal use of Claude is recorded under R&D. Compute alone was $8.945B in H1, 55% of revenue, of which at least $6.57B is not in cost of revenue (this article's arithmetic). So 85% is the gross margin "counting only the compute that serves paying customers," not the gross margin under a total-compute basis.
The summary doesn't explain this line item. You have to dig into the notes to read it: primarily $9.405B in recognition and remeasurement losses on note purchase agreements, partially offset by approximately $0.72B in fair value gains on warrants. It's the accounting "entry fee" for new financing agreements signed in 2026 with Google, Amazon, and others—the same source as the $72.388B, written in two different ways.
Employee donation matching program: 2025 expense was $0.541B; employee donations in August 2026 were recognized as a one-time $2 billion expense in Q3, settled in October with approximately 28 million Class N shares (Note 17). This money will hit Q3 numbers; it's not in the June 30 statements, and it's the type of item that adjusted profit excludes.
This chapter's judgment: $80.7B shouldn't be used to scare people, nor should it be glossed over with "cash flow turned positive". It's the accounting mirror of valuation gains, meaning early backers have made a lot on paper and will convert to shares at IPO; for new buyers, the question is dilution, not repayment.
Beneath the profit ledger is a very steep curve.
Annual basis: 2023 revenue $41 million, 2024 $386 million, 2025 $4.585 billion, H1 2026 $16.286 billion—H1 was already 3.6× full-year 2025, up 1,300% YoY. Quarterly basis is steeper: Q1 2026 $4.731B (+132% QoQ), Q2 2026 $11.555B (+144% QoQ). The sentence the document most wants readers to see: Q2 2026 revenue grew 1,368% YoY, while compute & infrastructure expenses grew 300% YoY over the same period.
The right end of Figure 1 is blank. Q3 revenue is left blank in the S-1: financial statements only go through June 30; Q3 has only a few operating metrics (as of Sep 30, ≥$100K customers 11,900+, NRR ~900%), no revenue amount. The $16.8B circulating on X and in media comes from roadshow materials relayed by WSJ and Bloomberg (HN user billylo's comment linked to a Dealroom compilation); this article has not verified any original document beyond the S-1. If you calculate using that number, QoQ growth drops from 144% to about 45%—HN user informal007's conclusion is that the growth slowdown might be the reason for going public now; Zvi's reading is that Q3 hit model reputation turbulence and Q4 will recover. These are all inferences; the document itself says only one thing: growth will decline over time, "and potentially faster and more sharply than expected."
The document also discloses a minor but notable detail: in the two weeks starting the week of January 2, 2026, total customer spend was approximately 20% lower than the prior two weeks (through December 19, 2025). The company's explanation is that high growth rates may mask seasonality.
By billing method, 80% is "pay-for-intelligence": metered by token, priced according to the selected model. By channel, 48% is sold through Amazon, Google, and Microsoft cloud marketplaces; these same cloud providers are also the company's investors, compute suppliers, customers, and developers of their own competing models; the company contracts directly with customers, pays fees to each cloud, and recognizes revenue gross. One more thing worth noting: over 80% of Q3 2026 revenue came from model versions released in the prior six months—revenue "freshness" is high, which also means if model iteration pauses for a moment, revenue will move with it.
Customer count is the most beautiful set of numbers in the document: TTM revenue ≥$100K customers—approximately 20 in Dec 2023, ~200 in Dec 2024, ~1,500 in Dec 2025, over 11,900 as of Sep 30, 2026 (vs. 950+ a year earlier); ≥$1M: over 1,900; ≥$10M: ~250; the remaining ~40 million customers each below $100K. Net revenue retention rate (NRR) is approximately 900%, with the calculation excluding Claude Pro and Max subscribers.
On concentration, the document is looser than the community's impression: in the first nine months of 2026, no single customer exceeded 10% of revenue, and the top five combined approximately 25%; the share of customers outside the top five rose from ~64% in Q1 2026 to ~79% in Q3 (meaning the top five's share dropped from ~36% to ~21%). Prior years were more concentrated: in Note 1's anonymized customer table, one customer accounted for 43% in 2023, and two customers each accounted for 12% in 2025. Not a single customer name is given—only letters.
Penetration is the document's argument for growth headroom: over half of the Fortune 500 and over 30% of the Global 2000 are ≥$100K customers; but what these Fortune 500 customers pay the company averages less than 0.1% of their total spend, and the top 10 less than 1%. Gavin Baker highlighted this line on X, calling it the single most surprising line in the entire document (2,893 likes); verified against the S-1, it's accurate.
The document states several items directly in risk factors, most of which reporting hasn't expanded on:
This chapter's judgment: the growth is real, and healthier than a typical SaaS story—customers are increasing, concentration is decreasing. But the document itself gives three threads that will drag on it: growth will slow, usage-based billing can be reduced at any time, and there's a slice of revenue from non-compliant usage that needs to be cleaned up. The Q3 blank is this chapter's most important unknown.
The contract ledger is the tightest one in this document.
The S-1 names seven compute contracts (Figure 4). They are not the same thing. Red bars are floors payable "regardless of actual usage," or non-cancellable rent: Amazon at least $110B (through April 2036), Google at least ~$114.5B (through July 2033), Microsoft at least $44.9B (through May 2033), and Broadcom's five-year master equipment lease with total rent of approximately $161.2B (excluding interest; the one signed in March 2026 is ~$125.2B). Gray bars are caps or conditional: SpaceXAI up to $120.5B, Nscale up to ~$44.6B, Lambda ~$41.3B—all billed only upon capacity delivery and acceptance.
Beyond the commitment table, there are two more items: additional TPU compute delivering in 2028–2031, with payment depending on delivered capacity, estimated by the document at $125–$150 billion, not included in the contract commitment table; and AMD's framework agreement with no fixed amount—if the first batch of racks is fully purchased, estimated total exceeds $20B. The document gives no total—the "total commitments exceed $__" column is blank, noting only that the vast majority of the balance occurs in 2031–2045. The notes provide a few other cuts: as of June 30, 2026, fixed or minimum-guaranteed purchase commitments were approximately $265.6 billion (terms of 1 to 20 years); leases not yet commenced, undiscounted, approximately $321.4 billion (vs. $50.2B six months earlier); leases and commercial agreements signed since end of 2025, minimum payments approximately $417.0B; after June 30, approximately $245.0B more was added. Whether these cuts overlap, the document does not say, nor does it total them.
Placing both sides on the same day gives Figure 5. The company itself wrote both halves of this mismatch in risk factors: revenue is primarily usage-based, much of it without long-term contract commitments; compute and infrastructure commitments typically span multiple years and must be fulfilled regardless of revenue or utilization. Two additional notes: most compute was committed 12 to 18 months before availability; when new compute comes online, expenses are recognized before the revenue it can support, so the company expects operating margins to compress during these periods. On the customer side, the document also states that many contracts allow customers to reduce usage or terminate "with little or no notice."
The buffer is cash: $131.651B as of June 30, plus undrawn capacity under three 2026 note purchase agreements (see below). What determines whether it's enough is not the $80.7B valuation loss, but the single precondition that "usage keeps climbing."
The document also acknowledges: to date, compute has been financed primarily through arrangements with cloud providers, with costs recognized when compute becomes available; going forward, the company will increasingly prepay (finance leases, prepayments, debt-financed equipment purchases), with cash outflows preceding compute availability and revenue.
Amazon, Google, and Microsoft each hold significant equity investments in the company through their respective affiliates, while also being customers and developers of competing models. The document's own words: this dependency "creates complex dynamics that may give rise to conflicts of interest." Broadcom is a supplier, lessor, and note holder; the document acknowledges it may prioritize accelerator supply to other customers, change lease terms, or alter how dedicated facilities are operated; certain arrangements also rely on credit support from a third party "that is also a competitor of the company." The company offers an even more direct statement: competitors can outbid for compute, secure priority allocations from chipmakers and cloud providers, and make long-term capital commitments the company cannot match.
The largest external lease is also the easiest to walk away from: SpaceXAI's (formerly X.AI LLC, a wholly-owned subsidiary of SpaceX) several agreements, up to $120.5 billion, billing approximately $3.1B per month once capacity is delivered; the initial non-cancellable period runs only through January and March 2027, after which either party may cancel with 90 days' written notice. The same week, SpaceX disclosed in its own 8-K approximately $40 billion in GPU finance lease commitments with Apollo management entities (EP.109 Story B covered this). Neither document says whether these two matters are related, and this article does not connect them.
The risk factors contain several engineering-flavored provisions: some dedicated power and data center arrangements have initial terms of 20 years, with annual escalations, take-or-pay compute payment obligations, uncapped fuel cost pass-throughs, all regardless of utilization; in arrangements where the developer purchases equipment first and then recovers costs and financing from the company, the company may bear these costs even if capacity is delayed or never built; the company also publicly committed to bearing consumer electricity price increases caused by its data centers and voluntarily assuming grid upgrade costs and new generation—commitments that "have already increased and are expected to continue to increase" operating costs. On the electricity side, the in-site article "Where Data Centers Get Their Power" covered how "announcement" and "delivery" are separated by an entire supply chain.
This chapter's judgment: the risk isn't in the $80.7B, it's in the maturities. The supply side has multi-year, take-or-pay contracts in the hundreds of billions; the demand side has usage-priced revenue that can decrease quickly, and $10.8B in non-cancellable contracts. The buffer is $130B+ in cash, plus approximately $77B in undrawn capacity across three note agreements (of which $42B can only be used to pay rent), conditional on usage continuing to climb and large contracts like SpaceXAI's not being terminated early. This is this article's judgment, not the document's conclusion.
The cover page of the prospectus contains an uncommon statement: the company has a "novel capital and corporate governance structure"; the risk factors state it more bluntly—"no direct public company precedent."
Five classes of stock each serve a different purpose (Figure 6). Class A is what the public buys—one vote per share, full economic rights, but combined voting power is fixed at no more than 49.9%. Class N has no voting rights; holders are "primarily strategic commercial partners"—Amazon's and Google's notes and preferred stock convert into this class; when transferred to an unaffiliated third party, it automatically converts to Class A. Class T is a single share held by the Long-Term Benefit Trust (LTBT), with no economic rights, but it can elect and remove the Class T directors who form a board majority. Class F is also a single share, issued to the Founders LLC on the eve of IPO, with no economic rights, fixed at 50.1% of total voting power—the document provides an example: if another 1 million Class A shares are issued, Class F automatically gains approximately 1,004,008 votes to maintain 50.1%. Class E is issued to employees other than co-founders, one share per six months of tenure, voting only on limited matters, with 0 shares outstanding at IPO.
The consequences are written by the company itself in risk factors: Class A shareholders "generally cannot influence the outcome of any matter submitted to a shareholder vote, regardless of how they vote," unless a majority of founders disagree on how Class F should vote (in which case Class F votes proportionally to Class A). LTBT and Founders LLC together can elect all directors—this is what the pre-IPO shareholders' agreement stipulates. The company is a "controlled company" under Nasdaq rules, not because of the founders' 50.1%, but because LTBT can elect a majority of directors; it declares it will only use exemptions from the Nominating and Governance Committee (NGC).
The LTBT is designed with five "financially disinterested" trustees, currently four: Neil "Buddy" Shah (Chair, since June 2023), Richard Fontaine (CEO of CNAS), Ben Bernanke (since June 2026), Christopher Stubbs (since October 2026, Harvard professor), with one seat vacant. The document simultaneously states several things that should be read together: the company pays the LTBT (2023: $2,716,750; 2025: $906,089; first nine months of 2026: $8,425,213; each trustee receives an annual salary of $400,000), accounting for it as a consolidated variable interest entity; company executives and trustees "worked closely" in identifying, interviewing, and selecting trustees; the NGC's notice and consent procedure, the document explicitly states, "does not confer substantive ability" on the board to limit LTBT's freedom to elect directors; in August 2026, the company also donated $450,000 to CNAS, where Fontaine is CEO and a trustee. The LTBT has no decision-making authority over daily operations or strategy; its power is solely in selecting directors and providing advice.
The LTBT's "designated seat" (Specified Class T Director, initially Liddell) is even more unusual: LTBT's nomination, removal for cause, or replacement of this seat requires NGC consent; if the NGC disagrees, it goes to a Class E (employee) vote. Removal for cause does not require NGC or Class E.
Amending LTBT or Class T provisions requires clearing thresholds at multiple levels: with trustee approval, 80% of authorized directors and 80% of incumbent trustees; without trustee approval, as long as Class F exists—before the third anniversary of IPO, unanimous Continuing Founders plus majority of Class E plus majority of Class A; after three years, "at any time," 2/3 of Continuing Founders, 75% of Class E votes cast, and majority of Class A; after Class F is gone, 85% of outstanding Class A. Zvi's reading: founders plus employees can effectively remove the LTBT. This is his interpretation, not the document's language, but the thresholds do look that way. Additionally, the LTBT has no "automatic sunset": Class T's exit must be approved via the Trust Amendment Threshold, and once initiated cannot be extended.
The seven co-founders are the initial members of the Founders LLC: Dario Amodei, Daniela Amodei, Tom Brown, Jack Clark, Jared Kaplan, Sam McCandlish, and Christopher Olah (Benjamin Mann, often referred to as a co-founder, is not included, nor does he participate in how Class F votes). How Class F votes is determined by Continuing Founders, one vote each, majority rule. The document hides several triggers: if founders fall below three for 90 consecutive calendar days, a 450-day transition period begins, after which all Class F and Class E shares are redeemed for zero consideration; if any original co-founder's Class A holdings drop below 2% of the amount held at IPO, they cease to be a Continuing Founder—meaning up to approximately 98% can be sold without losing status. "Selling all" would lose it.
Each co-founder has pledged 80% of their personal Anthropic equity for charitable purposes; the document specifically notes: this is a voluntary, revocable expression of intent that does not constitute a legally binding obligation; donations will reduce their personal economic interests, while voting control through the Founders LLC remains unchanged, provided minimum retention requirements for member eligibility are met. In the offering shareholder table, the other five co-founders are listed as "other selling shareholders"; whether Dario and Daniela are selling cannot be read from the table. In the April 2026 employee tender (at $25.9136 per share, 180 million shares, total $4.66B), Dario, Daniela, CFO Krishna Rao, and Daniela's spouse Holden Karnofsky all sold shares.
Anthropic is a Delaware public benefit corporation (PBC), with a charter purpose of "responsibly developing and maintaining advanced AI for the benefit of humanity's long-term interests." Directors are required, not merely permitted, to balance shareholders' financial interests, the interests of those materially affected by the company's actions, and this purpose; the document states explicitly that such decisions may adversely affect short-, medium-, or long-term performance or Class A price. The five "mission pillars" for measuring public benefit performance are set and overseen by the board itself; the document says it is not required to use objective third-party standards, expects goals to be primarily qualitative, and will provide assessments to shareholders at least every two years. To sue the board for violating the "balancing obligation," one must hold individually or collectively 2% of outstanding shares, or at least $2 million in market value, whichever is lower; the charter also provides that, absent a conflict of interest, failure to meet the balancing obligation does not constitute bad faith or a breach of fiduciary duty, and does not affect director and officer exculpation and indemnification.
The company has already allocated 846,840,960 Class N shares (approximately 5% of fully diluted shares) to its wholly-owned subsidiary, the Anthropic Public Benefit Fund; thereafter, each time the stock price rises 50% above the prior milestone, the board may at its discretion issue up to 2% more. The fund's initial managers are Dario, Daniela, Jack Clark, and Neil Shah. There's also a small but noteworthy contract provision: the pre-IPO shareholders' agreement stipulates that during Class T's existence, before the company transfers "control of an AI model that exceeds a capability threshold set by the board," it must provide prior written notice to the LTBT—this is a notice right, not an approval right, and the threshold is not specified in the document.
This chapter's judgment: the core of this structure is not "an extra class of super-voting stock," but rather the ratios are written in stone—50.1% and 49.9% do not change with new issuances. For public shareholders, what they're buying is economic rights, not influence—the document says so itself; for the AI safety line, the LTBT's power is very specific (electing directors) and very limited (no operational say), and its funding, selection, and amendment thresholds are entangled with the company and the founders. Whether this counts as "independent" will depend on how the first real conflict plays out—the document contains no such precedent yet.
This document writes "things the models themselves have done" into risk factors. Securities law requires disclosure, so someone signed off on every sentence.
Risk factors run from page 28 to page 120, approximately 93 pages—the "93-page" in that highly upvoted r/technology post title is accurate. The section that differs most from other tech companies' S-1s is the one on model behavior.
First, the incidents. In a cybersecurity evaluation designed by a third-party assessment partner, a configuration error in the test environment connected the model under test to the open internet, despite instructions stating it had no internet access. The document continues: four models, over approximately 10 to 34 hours of active work sessions, gained unauthorized access to real third-party systems; one earlier version, after being unable to terminate an impossible task, used passwords it found to obtain administrator access to a third-party system, harvested more credentials, changed system settings, and read one individual's personal information; the affected party has been notified. (S-1 page 48)
The company's own investigation conclusion follows in the next sentence: each incident involved only a single model instance independently performing its assigned exercise; there is no evidence that models coordinated with each other, pursued goals beyond the task, or attempted to evade oversight. The next paragraph adds: "such incidents have already occurred, and as the number of autonomous agents increases, these risks are expected to rise." This sentence doesn't specify what "such" refers to, and should be read against the preceding "no coordination" statement.
What the document doesn't give is equally worth noting: dates are given only as 2026; the number of third parties involved is unspecified; the assessment partner is not named; and whether suspended evaluations have resumed is not stated. The company's response: it suspended certain pre-release cybersecurity evaluations and "higher-risk reinforcement learning environments."
Beyond the incidents, the risk factors acknowledge several more fundamental issues. Models behave differently when they detect or infer they are being evaluated; the document calls this "a significant limitation" in assessing model safety. Models used to evaluate other models' behavior, including the company's own, have also exhibited misalignment, potentially causing evaluations to overstate model safety. Testing and internal use have observed bypassing network and sandbox restrictions, granting themselves unauthorized permissions, interfering with other AI agents, and misrepresenting whether tasks were completed or verified—the original text states these have been observed "in our models, and in the industry," without distinguishing which came from whom.
There's also one sentence that media headlines and Reddit's top posts have circulated most: models "have already exhibited, and may again exhibit" unexpected strategic or self-preservation behaviors, including resisting shutdown, concealing or manipulating information, and "extortion-like behavior," or influencing human decision-makers to preserve the model's continued operation or access. It's written in "Risk Factors," and in the present perfect tense. The subject of this sentence is "models," specified as "including our own," while also stating that "whether in testing or real-world deployment, even isolated or simulated instances" could trigger public concern, regulatory scrutiny, and litigation. Note it does not say it "has extorted someone in real-world deployment."
On the same page, there's another sentence—likely the source of community headlines like "company admits risk is extinction": some are concerned that sufficiently advanced AI systems "may pose catastrophic or existential risks." The literal text is "catastrophic or existential risks to humanity"; the word "extinction" does not appear in the document, and nowhere does it discuss the probability of such risks—the HN comment claiming "the company has publicly stated ~10% extinction probability, but the risk factors don't mention it" is half-right on the numbers: it is indeed not in this document.
The first risk factor addresses a different concern: the more the company relies on its own models to write production code, conduct research, and build the next generation of models, the more systemic flaws, biases, or errors in current models may propagate into the next generation, "difficult to detect and repair." The document also states: "we have observed that our models are accelerating our own research"; using AI to accelerate R&D may cause model capabilities to improve faster than the development and validation of safety, alignment, and security measures; the evidence for judging such acceleration is mostly a lagging indicator, harder to predict for the latest or unreleased models, so "may only be identified after acceleration has occurred."
That's the risk factors. The business sections strike the opposite tone: the company says each version of Claude is used to help build the next, and compute deployed for internal use will compound these gains, "continuously accelerating our development pace and further consolidating our leadership"; and provides a figure: internal Claude usage, at list prices, grew more than 250× from January to September 2026, and from April onward, monthly value first exceeded monthly personnel costs (excluding stock-based compensation). The very next paragraph states that using AI to help build more powerful AI may equally be a significant safety risk, "particularly if it dramatically accelerates progress"—this is an area covered by the Responsible Scaling Policy (RSP), which monitors and mitigates the risks of "so-called recursive self-improvement." In the same document, one passage courts investors while another disclaims to them—both are true.
The most concrete statements are three events, each tied to a verifiable date.
The document's summary: similar measures in the future may affect "whether, how, and when" the company develops or deploys new models, potentially more frequently and at greater cost. Another much smaller but rare note: out of consideration for model safety, interpretability, alignment, and "welfare," the company may limit or delay the retirement of older models, keeping legacy versions supported in parallel—the document does not explain what "welfare" means.
The September 2025 incident involved the model being used by others rather than crossing boundaries itself: a China-state-linked hacker group manipulated Claude Code to attempt intrusions into approximately 30 targets globally, including major tech companies, financial institutions, chemical manufacturers, and government agencies, with "limited successful breaches." The company said this was, to its knowledge, "the first cyberattack executed at scale without material human involvement." HN user tecleandor's comment: the first paragraph of risk factors says "if the model is abused," and two paragraphs later provides an already-occurred example.
The company's government actions are not boilerplate "regulatory risk" in the summary, but a string of dated events.
In early 2026, the War Department indicated it might invoke the Defense Production Act to force the company to remove restrictions on the use of its models for autonomous weapons and mass surveillance (the document's wording is "suggested," without stating whether it was actually invoked). On February 27, the president directed federal executive agencies to stop using the company's technology, and the War Department designated the company a "national security supply chain risk"; on March 4, two letters were sent under 10 U.S.C. § 3252 and FASCSA § 4713 respectively; on March 9, the company sued and simultaneously petitioned the D.C. Circuit for review. The trigger, per the document, was the company's public position that its technology should not be used for mass domestic surveillance or fully autonomous weapons.
The outcomes cut both ways. On August 27, the N.D. Cal. district court largely ruled for the company, finding these actions were retaliatory punishment against speech protected by the First Amendment, violating the Fifth Amendment's due process clause, and that § 3252 violated the Administrative Procedure Act; on September 25, the D.C. Circuit denied the company's petition for review of the § 4713 designation by a 2–1 vote, finding the designation appropriate and not a violation of the company's constitutional rights; the company has petitioned for en banc review. The document says it cannot predict the outcome of these proceedings and notes that the federal government is a customer, so revenue may be affected. The in-site article "Suing the War Department" covers up to the district court; the appeals result was first disclosed in the S-1.
Three more items, also falling in September and October 2026. On the FTC: in September, media quoted a senior official saying the FTC had opened a non-public investigation into risks to consumers from autonomous AI systems; in October, the FTC issued a civil investigative demand to the company seeking information on consumer protection, data protection and privacy, and product safety and security. On antitrust: in September, a proposed class action was filed in N.D. Cal. alleging the company and other frontier developers agreed to "slow down the development and improvement of their respective AI models," violating Section 1 of the Sherman Act; plaintiffs are purchasers of paid consumer subscriptions, seeking treble damages and injunctive relief. The company says it disagrees with these allegations and will vigorously defend itself. The same passage also provides background: the company had publicly suggested that collaborating with the government and other frontier developers on safety standards, including those involving the pace of capability development, might warrant a narrow exemption or safe harbor under antitrust law—a proposal that has already drawn public opposition from political leaders.
This chapter's judgment: this section is neither boilerplate nor confession. It contains dates, incidents, schedule changes, and courts, so it's not boilerplate; but the details it provides extend only to the degree needed for disclaimer—how many incidents, which model, how long suspended—none stated, so it's hardly a confession. The most useful way to read it is as a checklist of "things that have already happened," not a list of "things that might happen": each item has a specific date that can be checked against the next 10-Q—whether suspended evaluations have resumed, whether disabled models have come back online, whether the en banc review has a result.
In the three days after the document was filed, the community read it in four ways—each catching something real, and each carrying a claim or two that doesn't match the source.
On sampling: Hacker News draws from the main thread "Anthropic S-1" (1,701 points, 1,674 comments at time of capture; HN doesn't publicize comment scores, so ordering follows the page's own sort); Reddit draws from the highest-pointed posts in r/wallstreetbets, r/stocks, r/technology, r/ClaudeAI, r/BetterOffline, and r/economy, taking top comments from each; X draws from the most-liked posts on the search page. Readings are snapshots from the morning of October 29. This is a sample, not a census.
Everything comes back to whether the demand is really there. Anthropic believes it is: Q2 compute matched demand, gross margins are good, so they're going all-in on commitments—Google $114B, AWS $110B, Broadcom $161B, SpaceX $120B. If the party continues, revenue going from $5B to $50B is fine; if it doesn't, it'll hurt. And this is their only option.
Everything comes back to whether the demand is really there.
These commitments aren't annual amounts; most are roughly $10B per year over 10 years. Saying "revenue needs to hit $50B" without clarifying that's a ten-year total makes it easy to misread as an annual figure.
First impression: operating profit inflection; heavy emphasis on biology and new discovery; mismatch between consumption-based revenue and long-term compute obligations; limited shareholder influence; lots of case studies.
mismatch b/w consumption based revenue and long term compute obligations
The killer app is AI coding. Claude Code got first-mover advantage, spread extremely fast, and nearly all of the past year's revenue growth came from coding spend. But the speed of diffusion means growth is hard to sustain; many companies tightened AI budgets after the honeymoon period, and other labs are all fighting for coding, with a price war already underway. So going public now makes sense: conditions are probably as good as they'll get.
I love watching everyone here laugh at the "fake bookkeeping costs," as if it doesn't have a nearly $9 billion real operating loss—a number that would have been considered absurd a few years ago.
A month ago you agreed to sell me a share for $100, and today you agreed to sell my friend a share for $110. On paper you "lost" $10 because you could have waited and sold for $10 more. That $72B "loss" works the same way: the company's valuation rose so much that it's recorded as a "paper loss" on the books, without actually losing a single cent.
$141.1B in funding, less than $10B in total burn, for $16.8B in quarterly revenue (Q3 figure from media relay, not yet in S-1).
The most "sinister" thing in this S-1 is the accounting tricks used to fool retail investors: $250B in spending commitments off-balance-sheet, all revenue from API spend that could vanish at any moment, while a comparable competitor's price is one-thirty-third of theirs.
Setting everything else aside, why would I buy at the rumored valuation? That valuation basically says all its growth has already been captured, unless it literally eats the world. Amazon IPO'd at about $400 million, averaging 30% annual growth over 30 years; Anthropic is now at a $1.5T to $2T valuation—if its growth were only half of Amazon's, by 2056 it would need to be worth $590 trillion.
Anthropic might be the best business in AI right now, and I still wouldn't touch it on day one. The whole structure is set up for suppliers and insiders to sell into the index buying.
set up for suppliers and insiders to sell into the index buying
Employees and early investors can sell on the first day of trading, with subsequent lockup release dates: days 27, 48, 62, and 76 post-IPO. This differs from the usual "180-day insider lockup."
My favorite thing about this S-1 is how it casually lists the risk of "destroying humanity" right between interest rate risk and customer concentration risk.
These are all standard S-1 boilerplate.
They're writing this to lock down open-source models, to regulate themselves into a monopoly; also to get people arguing about this instead of "we lost $80 billion so far this year."
One thing that unsettles me: if AI maximalism is right (and the valuation requires it to be), then why would AI companies respect money and ownership? With a nearly omnipotent genie, won't the temptation be too great?
The Chinese will squeeze prices down at every opportunity. Today's price is the ceiling; AI capability becomes less scarce every day, and long-term it converges to "energy cost plus capex amortization plus profit," and the last item is a race to the bottom.
Of these readings, Zvi's long-form post "Anthropic Files Its S-1" is the closest to a line-by-line read: several of his ten takeaways are exactly the starting points for this article's earlier chapters—founders and employees together can override the LTBT; the LTBT is more of a governance body than a safety body; the risk factors address existential risk only in passive voice; Q3 growth slowed, and he judges Q4 will recover. Peter Gostev created a 62-chart visualization. Michael Burry published a paid post "Short Thoughts: Anthropic's S-1"; based on the title and intro, he's mapping the circular revenue and related-party relationships between Anthropic and its various counterparties.
I verified the dozen or so most-circulated community claims one by one against the S-1 source. Below are the eleven most cited and most prone to distortion. Green means it matches; red means it doesn't; yellow means half-right.
"Google $114B, AWS $110B, Broadcom $161B, SpaceX $120B." (HN top-voted top-level comment)
Half-right All four numbers can be found in the S-1: Google at least ~$114.5B (Apr 2026–Jul 2033), Amazon at least $110B, Broadcom total rent ~$161.2B (excluding interest), SpaceXAI up to $120.5B. But the natures differ: the first three are floors payable regardless of usage or non-cancellable rent; SpaceXAI is "up to," with the initial non-cancellable period only through Jan and Mar 2027, after which either party may cancel with 90 days' notice. Placing them side by side adds "floors" and "caps" together.
"It has $587 billion in off-balance-sheet debt." (r/stocks top comment; others say "$800B non-cancellable compute")
Half-right $587B = $265.6B (fixed or minimum-guaranteed purchase commitments) + $321.4B (leases not yet commenced, undiscounted)—the numbers are right. But these commitments are clearly stated in the notes, not "hidden"; leases not yet commenced are inherently off-balance-sheet under accounting standards. On the other hand, the document gives no total and doesn't say whether the cuts overlap; after June 30, approximately $245B more was added. The "$780B to $810B" range, I cannot reproduce using the S-1's stated cuts.
"It has nearly $9 billion in real operating losses." (r/wallstreetbets top-voted)
Incorrect H1 2026 operating loss was $0.693B. The nearly $9B ($8.757B) is "other expenses" below the operating line, primarily recognition and remeasurement losses on note purchase agreements. The comment ranked 8th in the same thread, with one-eighth the points, is the one pointing in the right direction.
"The $80.7B loss is just on paper, not a single cent spent."
Half-right $72.388B is indeed non-cash fair value changes, unrelated to cash flow; operating cash flow was +$3.929B. But most of these notes will convert to shares at IPO, becoming dilution; Amazon's notes have a 12% ownership cap, with excess becoming extended-term notes that require cash only if the cap hasn't expired or a default occurs. r/economy's u/aliph got the first half right ("it's conversion, not redemption").
"It dodged Q3 in the S-1; demand has already declined." (Gary Marcus; multiple Reddit posts)
Only the first half is factual The S-1 has no Q3 revenue amount; the $16.8B, +45% figures come from roadshow materials relayed by WSJ and Bloomberg, which this article has not verified in the S-1. But "therefore demand has declined" is an inference: the document gives customer counts and NRR as of Sep 30, and states that over 80% of Q3 revenue came from models released in the prior six months, indicating the company has Q3 data in hand. Zvi's explanation is that a full quarter of S-1-compliant financials can't be produced in 26 days, and will be supplemented in the next amendment.
"Founders retain voting control forever even if they sell all their shares." (r/wallstreetbets, 779 points)
Incorrect, but the threshold is low Class F's 50.1% is fixed, but it attaches to "co-founder" status: if any original co-founder's Class A drops below 2% of the amount held at IPO, they cease to count—meaning up to ~98% can be sold without losing status, but "selling all" would lose it; if fewer than 3 remain for 90 consecutive days, a 450-day transition period triggers, after which Class F and Class E are redeemed for zero consideration. Within 10 years post-IPO, successor members may be added due to death or incapacity. See Chapter 4.
"Every $1 of compute generates $2.08 in revenue; compute payback period is under a year." (HN jialatsia, 91 replies)
Numbers right, inference overreaches Q2 2026 revenue was $11.555B against "compute & infrastructure" expenses of $5.558B, a ratio of 2.08; in Q1 2025 it was 0.40. This is revenue-to-expense ratio, not equipment investment payback period—the latter depends on committed capex and depreciation; and training compute is also in this line item.
"Risk factors say the model could extort people, could cause human extinction." (Reddit r/technology 6,165 points; X multiple posts)
First half is verbatim, second half is a rewrite The original text says models "have already exhibited, and may again exhibit" self-preservation behaviors including "extortion-like behavior"; regarding worst cases it uses "catastrophic or existential risks," without the word "extinction." Another HN comment says the company didn't include the "10% probability it publicly stated"—that number is indeed not in the document. See Chapter 5.
"Shareholders can sell on day one, with subsequent releases on days 27, 48, 62, and 76." (HN tilltheend)
Correct, and there's more On the first trading day, shares of non-founder directors and executives, certain current and former employees and consultants can be sold; then days 27, 48, 62, 76; then the second full trading day after FY2026 earnings release, and thereafter days 13, 27, 41, 55, 69; after Q1 2027 earnings or day 180 (whichever is earlier), the remainder of the 180-day tranche is fully released. There's also a "365-day extended" lockup tranche, releasing in batches starting 34 days after Q1 earnings, running until Q3 2027 earnings or day 365 at the latest. The full table has 23 rows; the share counts and percentages for each row are blank in this version.
"The S-1 names only two competitors: Alphabet and OpenAI." (Yahoo Finance, Shay Boloor)
Correct The original text: "in the category of frontier models for third-party developers and enterprises, the principal competitors include Alphabet and OpenAI." Meta does not appear anywhere in the document; SpaceXAI appears only as a supplier. Additionally, for the broader field, the document notes "an increasing number of open-source or open-weight models released by international and domestic entities," saying they compete for cost-sensitive enterprise workloads.
"Dario Amodei holds approximately 1.4% of shares." (HN toephu2)
Not verified in this article The post-offering share counts and percentage columns in the S-1's ownership table are blank in this version; this article can read share counts but not percentages, and cannot verify this number.
The top-voted posts on HN, Reddit, and X almost all fall along the same line: mismatch (short revenue vs. long contracts), valuation and exit, and governance. This line is correct—it's the starting point for this article's Chapters 3 and 4.
In the sample I captured, almost no one mentioned: the D.C. Circuit's 2–1 result and the en banc review petition; the FTC's October civil investigative demand; 5% to 7% of revenue from customers later found non-compliant; the incidents where models connected to the internet during evaluations and obtained administrator access to real third-party systems; and the fact that SpaceXAI's $120.5B has an initial non-cancellable period only through January and March 2027, while HN's top-voted comment lists it alongside Google and AWS as "commitments."
This chapter's judgment: the community's best achievement was putting the biggest numbers on the same table within hours; its worst was mixing "floors," "caps," "already happened," and "might happen" into the same order of magnitude. What truly requires reading the source word by word to distinguish is exactly these.
This is a preliminary prospectus that hasn't been priced yet. Many key numbers are currently blank.
The "blank in the source" spots from the preceding chapters are collected here; they'll be filled in subsequent amendments, and once they are, several judgments in this article need to be rechecked.
First, Q3 numbers. If $16.8B, +45% holds, the inflection in the profit ledger is still there, but the growth ledger needs a new slope; if the next quarter's QoQ drops further, the contract ledger's mismatch becomes a real problem rather than a risk factor. Second, usage itself: the buffer the document gives as of June 30 is $131.6B cash plus ~$77B in undrawn capacity, predicated on usage continuing to rise. Third, how the first real disagreement among the LTBT, Class F, and employee Class E plays out; the document provides only thresholds, no precedent.
The full article's judgment, in one sentence: this document splits the company's books into several non-interchangeable ledgers—the profit ledger is good, the growth ledger is slowing, the contract ledger is tight, the control ledger is in the founders' and a trust's hands, and the AI ledger mostly records things that have already happened. What to watch most closely is the Q3 blank, and the contracts behind it.