Doe v. GitHub, Decided 16 September 2026: Why the Ninth Circuit Held That Copilot Creates New Works Under DMCA Section 1202(b), and How the Training-Data Theory Was Forfeited Before It Was Argued
IP & Competition Henry Quentir IP & Competition Henry Quentir

Doe v. GitHub, Decided 16 September 2026: Why the Ninth Circuit Held That Copilot Creates New Works Under DMCA Section 1202(b), and How the Training-Data Theory Was Forfeited Before It Was Argued

What the Ninth Circuit decided on 16 September 2026

In Doe v. GitHub, No. 24-7700, a unanimous panel affirmed Judge Jon Tigar's dismissal of the programmers' claim under 17 U.S.C. § 1202(b), the Digital Millennium Copyright Act provision that forbids removing or altering copyright management information. Judge Eric Miller wrote that the complaint itself describes an AI tool that does not look up and reproduce stored work but creates new work; a new work that never carried an author's notice cannot have had that notice removed. Standing was found, on memorization research, GitHub's own 150-character duplicate filter and verbatim examples; the claim failed on the statute's text.

Why the training-stage theory never reached the court

A second theory, that stripping licenses and notices from code before feeding it into the model was itself a violation, was held forfeited. At the first motion-to-dismiss hearing, counsel had answered "Perhaps it doesn't" when asked whether copying training data breached attribution terms, and the district court said the complaint "is not about training." Nobody corrected that reading afterwards.

What is still open for AI coding tools

This complaint's output theory failed; the panel kept the door open for nonidentical copies where removal is shown, expressed no view on ordinary copyright infringement for substantially similar output, and left two contract claims before Judge Tigar. This post reconstructs the case and reads it beside the EU AI Act's training-side obligations.

Read More
DOE's Genesis Q Sample Agreement Specifies Verification Circuits Standardized Across Awardees: What DE-FOA-0003657, Published 17 September 2026, Asks for 100 Logical Qubits
Standards Henry Quentir Standards Henry Quentir

DOE's Genesis Q Sample Agreement Specifies Verification Circuits Standardized Across Awardees: What DE-FOA-0003657, Published 17 September 2026, Asks for 100 Logical Qubits

What DE-FOA-0003657 defines, and what it standardizes

The Department of Energy's Quantum Genesis Q Competition, announced on 17 September 2026 with up to $215 million in planned funding, defines its terms rather than borrowing them. The request for applications defines a logical qubit, defines a hard operation as the scarce resource in a fault-tolerant computation, and adds scientific relevance as a third metric. The sample Other Transaction Agreement goes further: the circuits an awardee must run to claim an incentive milestone are specified by the verification and validation team and are standardized across awardees, with completion judged on hard operations, space-time volume and the correctness of the outputs.

What it still negotiates

Around that common test sit two negotiated layers. DOE and each applicant specify, during negotiation, the methodology used to define and evaluate the metrics, and architectures not naturally measurable in total logical qubits may propose equivalent technical metrics, acceptable at DOE's sole discretion, covering the final milestone and both bonus pools. Payment follows a fixed sequence: $250,000 on approval of a validation plan, $1,250,000 on a validated prototype, then a synchronized Quarter 8 evaluation of the $100 million general incentive pool and the two $50 million bonus pools. All of it is subject to the availability of appropriated funds.

Why the same-date arXiv paper matters

Matthias Troyer, Chetan Nayak and John Martinis posted Scalable logical qubits on 17 September 2026 to make logical-qubit progress measurable and comparable across platforms, characterizing the unit along four coupled dimensions. This post reads the competition documents and the paper against each other, and against the oldest working example of an independent assay.

Read More
Commerce Finalized a $1 Billion CHIPS Award to IBM's Anderon on 16 September 2026 for a 300 mm Quantum Wafer Foundry in Albany; the Release Calls It Pure-Play, and Names No Customer Other Than IBM
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

Commerce Finalized a $1 Billion CHIPS Award to IBM's Anderon on 16 September 2026 for a 300 mm Quantum Wafer Foundry in Albany; the Release Calls It Pure-Play, and Names No Customer Other Than IBM

What was finalized on 16 September 2026

Anderon LLC, the quantum foundry subsidiary IBM formed in May 2026, announced that its $1 billion CHIPS and Science Act award with the US Department of Commerce is final. The award funds research and development at a 300-millimeter wafer fab in Albany, New York; IBM contributes a further $1 billion in cash. The company says the first quantum wafers are already running through the line, for superconducting qubit arrays, quantum input/output signaling and readout signal chain components, with other modalities to follow. It is the largest single item in the $2.013 billion quantum portfolio Commerce announced through nine letters of intent on 21 May 2026.

The claim under test: pure-play

Both IBM releases call Anderon a pure-play quantum foundry. In the semiconductor industry that phrase has a precise meaning since TSMC's founding in 1987: a fab that sells manufacturing and sells no chips of its own, so that customers who compete with each other can trust it with their designs. Anderon is described only as an IBM company, the release quotes IBM Research's director on IBM's own roadmap as the need Anderon meets, and the May release says additional investors are expected as Anderon grows. Anderon's website promises that the manufacturing partner will never compete with a customer's products. No external customer is named in either release.

Why the distinction matters for public money

Commerce is funding two quantum foundries under different theories: Anderon for superconducting wafers, and GlobalFoundries' $375 million foundry for five modalities. Whether Anderon becomes a shared national quantum wafer manufacturing base for companies that compete with IBM is a question the public documents leave open; the first non-IBM wafer customer, and the terms that protect its designs, are not yet public.

Read More
Java 27 Turns On Hybrid Post-Quantum TLS by Default Through JEP 527, and Oracle Expects JDK 8 and JDK 11 to Receive It Only in the Second Half of 2027
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

Java 27 Turns On Hybrid Post-Quantum TLS by Default Through JEP 527, and Oracle Expects JDK 8 and JDK 11 to Receive It Only in the Second Half of 2027

What Oracle released on 15 September 2026

Java 27 ships JEP 527, Post-Quantum Hybrid Key Exchange for TLS 1.3. The JDK's TLS client now offers X25519MLKEM768, a combination of X25519 elliptic-curve Diffie-Hellman with ML-KEM-768, as its most preferred named group, ahead of x25519 and secp256r1. An application that uses the JDK's own SunJSSE implementation over TLS 1.3 with the default group list offers a hybrid post-quantum key exchange, and uses it when the server selects that group. Two further hybrids, SecP256r1MLKEM768 and SecP384r1MLKEM1024, are implemented and switched off by default.

Why the calendar matters more than the release

Java 27 is a non-LTS release with premier support to March 2027. The runtimes that carry production workloads are the long-term-support lines, and Oracle's roadmap post of 6 August 2026 gives each of them an expected date for Oracle JDK: JDK 25 with the October 2026 Critical Patch Update, JDK 21 and JDK 17 in the first half of 2027, and JDK 8 and JDK 11 in the second half of 2027. JDK 8, released in March 2014, remains under Oracle extended support until December 2030, so the two oldest supported lines are scheduled last. For JDK 8 and 11 estates carrying long-lived sensitive data, that is the latest Oracle backport date, and an operator can move earlier by upgrading the runtime or changing the TLS stack; on any line, protection arrives only when the update is installed and the hybrid group is confirmed to be negotiated.

What the post examines

The chronology from the KEM API of September 2023 to the H2 2027 backport, what JEP 527 deliberately leaves out, how the LTS backport calendar compares with the migration dates supervisors such as FINMA and NIST have set, and what a runtime default can move in the installed base that a supervisory deadline cannot.

Read More
Cloudflare's 1.1.1.1 Resolver Now Validates ML-DSA-44 DNSSEC Signatures, Announced 10 September 2026, and Refuses the Classical Fallback That RFC 6840 Would Allow
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

Cloudflare's 1.1.1.1 Resolver Now Validates ML-DSA-44 DNSSEC Signatures, Announced 10 September 2026, and Refuses the Classical Fallback That RFC 6840 Would Allow

What Cloudflare announced on 10 September 2026

Cloudflare's public resolver 1.1.1.1 validates DNSSEC signatures made with ML-DSA-44, the lattice signature NIST standardized in FIPS 204 in August 2024 and the first post-quantum algorithm with an IANA DNSSEC number, 18. Sebastiaan Neuteboom and Bas Westerbaan's post gives the sizes: a 1,312-byte public key and a 2,420-byte signature, against 64 bytes for ECDSA P-256. The company plans full post-quantum security across its network by 2029.

Why the packet size and the downgrade rule matter

RFC 1035 restricted DNS over UDP to 512 bytes in November 1987; EDNS(0) raised the ceiling, DNS operators settled on 1,232 bytes, and RFC 9715 of January 2025 recommends 1,400. One ML-DSA-44 signature exceeds that budget before the answer carries anything else, so an authoritative server truncates the signed response and the validating resolver retries over another transport, usually TCP; a client that asks 1.1.1.1 for an address without requesting DNSSEC data sees none of this. The second problem is older than the algorithm. RFC 6840 tells validators they should accept any single valid path, which lets a zone publish classical and post-quantum keys together. Once a classical key can be forged, that same rule is a downgrade path. 1.1.1.1 now treats a post-quantum DS record in the parent zone as an authenticated signal and refuses to validate on a classical path alone, a local policy RFC 4035 permits and no standard yet requires.

What is settled and what is still open

NIST fixed the algorithm, IANA assigned the number, and the DNSSEC specification remains an individual Internet-Draft by Westerbaan of Cloudflare and Sophie Schmieg of Google, revision 04 of 11 August 2026, with no working-group adoption. An end-to-end post-quantum chain, from authoritative signing through registrar DS submission and registry publication to the root, remains incomplete. This post reads what the resolver change proves, what the packet arithmetic forces, and why the root key is the one that decides whether any of it counts.

Read More
The US-Taiwan Agreement on Reciprocal Trade Signed on 12 February 2026 Commits Taiwan's Government to No New Quantum, AI or Biotech Research Arrangements With Authorities of Countries of Concern
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

The US-Taiwan Agreement on Reciprocal Trade Signed on 12 February 2026 Commits Taiwan's Government to No New Quantum, AI or Biotech Research Arrangements With Authorities of Countries of Concern

What Taiwan signed on 12 February 2026

The Agreement on Reciprocal Trade between the United States and Taiwan, concluded through the American Institute in Taiwan and the Taipei Economic and Cultural Representative Office, carries a Section 5 headed Economic and National Security. Article 5.2 aligns Taiwan's export controls with those in force in the United States, including the Foreign Direct Product Rule on semiconductors, and its ninth paragraph commits the Taiwan side to robust research security and to no new agreements, partnerships or similar arrangements for science and technology cooperation with authorities of countries of concern, especially in artificial intelligence, biotechnology and quantum computing. The agreement is signed; under Article 7.5 it enters into force the day after the last notification that internal procedures are complete, and the February USTR fact sheet says the Taiwan side will submit it to its legislature for review. Whether that notification has since been given is not stated in any USTR release this post could find.

What the University of Calgary paper adds

Carlo Dade and Alex Giordano of the School of Public Policy compared the 21 Agreements on Reciprocal Trade the United States had concluded by August 2026. They range from formal trade agreements to frameworks, memorandums and news releases, all executive arrangements with no congressional participation. Nearly every one contains provisions aimed at limiting China's role in the partner's economy; Malaysia agreed to mirror US export controls with equivalent restrictive effect, and Taiwan's Foreign Direct Product Rule alignment was matched by no other deal they reviewed.

Why it matters beyond Taiwan

A government commitment to enter no new research arrangements with authorities of countries of concern, quantum computing named among the fields, is carried by a trade arrangement that either side can terminate on six months' notice, with no export-control rule of that kind on the books. The Calgary paper, like The Logic, reads the clause as aimed at China; the text itself names no country. This post reads the clause, the eight paragraphs around it, and what the same template would mean for Canada, for Europe's research-security rules and for the physicists whose collaborations will be tested against it.

Read More
RSA-260 Was Factored on 3 September 2026 for About $400,000 of GPU Time, and NIST's RSA-2048 Dates Do Not Move
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

RSA-260 Was Factored on 3 September 2026 for About $400,000 of GPU Time, and NIST's RSA-2048 Dates Do Not Move

What happened between 13 August and 9 September 2026

On 3 September 2026 Eric Lu, an engineer at Cognition, posted a 130-digit prime factor of RSA-260 on X. The number, 260 decimal digits and 862 bits, had stood unfactored since RSA Security published its challenge list in 1991. Scientific American ran a story the next day in which the only method on offer was a remark about "good old paper and pencil". On 9 September Cognition published Lu's technical write-up: a GPU port of the open-source CADO-NFS number field sieve, prepared and run with Devin coding agents, consuming about 4,900 GPU-days on NVIDIA GB200, GB300 and B200 nodes, which Lu prices at about $400,000 at current market rates.

How the cost compares with 2020 and 2009

RSA-250 was factored in February 2020 by six academic cryptographers using about 2,700 CPU core-years of CADO-NFS. RSA-768 took thirteen people two years to December 2009. Lu writes that he reports essentially no algorithmic advance, that the work was a side project on a single-digit percentage of Cognition's cluster, and that the barrier to entry for cryptanalytic work is far lower than it used to be.

What it means for keys in use

By Lu's own scaling, RSA-1024 is 78 times more computation, an extrapolated $30 million at market GPU prices, and RSA-2048 is roughly a billion times harder again. NIST's draft transition plan, IR 8547 of November 2024, proposes that RSA-2048 be deprecated after 2030 and disallowed after 2035; the proposal rests on the quantum threat, and this result does not revise it. What moved is the extrapolated price of a classical attack on 1,024-bit keys, which NIST disallowed for new signatures after 2013.

Read More
GPT-6 Astra Is the First OpenAI Model Rated Critical for Cyber: From the 18 August 2026 Training Pause to the 3 September System Card, and What EU AI Act Article 55 and California SB 53 Ask of It
AI Governance Henry Quentir AI Governance Henry Quentir

GPT-6 Astra Is the First OpenAI Model Rated Critical for Cyber: From the 18 August 2026 Training Pause to the 3 September System Card, and What EU AI Act Article 55 and California SB 53 Ask of It

What OpenAI published between 18 August and 9 September 2026

On 18 August 2026 OpenAI wrote that preliminary findings indicated its next model, Astra, might meet the Critical cybersecurity threshold of its Preparedness Framework, and that it had paused reinforcement-learning training for two weeks. On 1 September it confirmed the rating. On 3 September it released GPT-6 Astra with a system card stating that, with the right tools and access, the model can find previously unknown security flaws and exploit them across many well-protected systems without a person guiding each step. On 9 September it revised the card's Alignment section.

What the framework said in April 2025

Version 2 of the Preparedness Framework, dated 15 April 2025, defines the Critical cyber threshold, pairs it in its table with halting further development until Critical-grade safeguard standards are specified, and states that OpenAI possessed no Critical-capability model and expected to update the framework before reaching that level. The 3 September system card links that same Version 2 PDF.

Which laws were written for a model of this class

The EU AI Act has applied Article 55 to general-purpose models with systemic risk on the Union market since 2 August 2025: state-of-the-art evaluation with adversarial testing, systemic-risk mitigation, serious-incident reporting to the AI Office, and adequate cybersecurity. California's SB 53, operative 1 January 2026, requires large frontier developers to write, implement, comply with and publish a frontier AI framework, requires every frontier developer to publish a transparency report at deployment and to report critical safety incidents within 15 days of discovery. Whether Astra falls within either statute's definitions is not something OpenAI has stated.

Read More
ECDSA.Fail Cut Its secp256k1 Point-Addition Benchmark Score 86 Percent on 9 September 2026; a Day Later Scripps Found 32 US States Without a Confirmed Post-Quantum Plan
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

ECDSA.Fail Cut Its secp256k1 Point-Addition Benchmark Score 86 Percent on 9 September 2026; a Day Later Scripps Found 32 US States Without a Confirmed Post-Quantum Plan

What arXiv:2609.09582 says

On 9 September 2026, 36 authors led by Jieyi Long published the results of Eigen Labs' ECDSA.Fail contest: an eight-week public leaderboard in which humans and AI agents submitted evaluator-verified improvements to the reversible secp256k1 point-addition circuit inside Shor's algorithm. Participants cut the benchmark score, peak logical qubit width times average Toffoli count, by 86.1 percent. At the 26 July 2026 cutoff the best circuit used 1,151 qubits and about 1.30 million Toffoli gates. A later low-width design reached 813 qubits. The paper states that these figures sit more than 50 percent below Google's published point-addition thresholds of March 2026, under different accounting conventions, and that they are not a full-Shor estimate.

What the Howard Center found in 50 states

On 10 September 2026 the Howard Center for Investigative Journalism at Arizona State University and Scripps News published a 50-state analysis of post-quantum cryptography planning. Four states have an active migration plan: New Jersey, New York, Maryland and Missouri. Fourteen are committed to or developing one. Thirty-two gave the reporters no confirmation of an active or developing plan; nine of those declined to say. Executive order 14412 of 22 June 2026 sets 31 December 2030 for key establishment and 31 December 2031 for digital signatures on federal high-value systems, and contains no direction to state or local government.

The question this post answers

Whether a circuit-design contest that cut a benchmark score by algorithm alone changes what a city or state technology office with a cybersecurity budget and no post-quantum line item should do next, and why the federal deadlines that exist do not answer that question for it.

Read More
FIPS 203 and FIPS 204 Do Not Specify the Silicon: the 9 September 2026 NTT Patent Screening, and the Two Portfolios NIST's Royalty-Free Licenses Cover
IP & Competition Henry Quentir IP & Competition Henry Quentir

FIPS 203 and FIPS 204 Do Not Specify the Silicon: the 9 September 2026 NTT Patent Screening, and the Two Portfolios NIST's Royalty-Free Licenses Cover

What the 9 September screening says

The Suzhou Institute of Information Security Law published a patent-landscape screening of number-theoretic transform polynomial multiplication on 9 September 2026. Its argument runs through the layer where post-quantum cryptography meets silicon. FIPS 203 and FIPS 204 fix the algorithms, their parameters and the transform itself, and say nothing about circuit-level butterfly architecture, modular-reduction circuitry or hardware organization, so the authors judge that patents on those things would be hard to declare standard-essential and are not bound by a FRAND undertaking. The document is explicit that it is a preliminary screening of public information rather than an infringement opinion.

What this read covers

The five areas where the screening finds the filings clustered, the surge it dates to 2024, and the per-chip royalty stacking it calls a tollbooth. Set against it: what NIST's two royalty-free patent licenses actually cover. Those agreements reach any apparatus implementing CRYSTALS-KYBER, which is to say hardware is inside the grant — and they reach exactly two patent portfolios and one algorithm. A National Law Review analysis of 9 September 2026 states that this is not blanket freedom to operate for every ML-KEM product.

Why the timing matters

OpenSSL published 4.1.0-alpha1 on 9 September 2026, a pre-release carrying optimized ML-DSA and ML-KEM transform operations on ppc64le and AVX-512 SHAKE work on x86_64. A library can change a variant in a point release. A frozen chip architecture cannot, and supervisors are already setting migration dates against estates that will run on parts bought this year.

Read More
FINMA Guidance 05/2026 Recommends a Post-Quantum Roadmap by Mid-2027, and Only 8 Percent of the 60 Swiss Institutions It Surveyed Had One
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

FINMA Guidance 05/2026 Recommends a Post-Quantum Roadmap by Mid-2027, and Only 8 Percent of the 60 Swiss Institutions It Surveyed Had One

What the guidance is

FINMA published Guidance 05/2026 on 9 July 2026. It reports a survey of 60 authorised Swiss banks, insurance companies, managers of collective assets and financial market infrastructures, run between November 2025 and January 2026, and sets out five post-quantum cryptography recommendations. The headline recommendation is that supervised institutions draw up a migration roadmap by mid-2027 at the latest, on the basis of a strategy adopted by the board of directors.

What this read covers

A section-by-section read of the eight-page instrument: how the reported 72 percent decomposes, what the 8 percent with a roadmap actually forecast, the scope of the section 3.2 cryptographic inventory, and the crypto-agility clause section 3.5 recommends for new outsourcing arrangements in the software and data sectors. It also notes the sentence that excludes quantum key distribution from the recommendations altogether, which is worth having in writing when a proposal arrives.

Why the survey is more interesting than the date

The percentages are the part that repays attention. Around two-thirds of those surveyed expect quantum cyber risk to become directly relevant for them within seven years, while almost two-thirds do not expect to run quantum computing applications themselves for another eight years or more. Those are two aggregate distributions rather than a respondent-level comparison, but the order they describe is the whole document: the gap between what the sector says it understands and what it has done about it.

Read More
Rigetti and D-Wave Disclosed the Equity Terms on Their $100 Million CHIPS Quantum Awards: What the 4-8 September 2026 Agreements Say the Government Gets
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

Rigetti and D-Wave Disclosed the Equity Terms on Their $100 Million CHIPS Quantum Awards: What the 4-8 September 2026 Agreements Say the Government Gets

What the three companies signed between 4 and 8 September 2026

Rigetti Computing and D-Wave Quantum both date their CHIPS and Science Act award agreements with the U.S. Department of Commerce to 4 September 2026. Rigetti entered the accompanying securities agreement on 8 September, with the share issuance expected the same day; D-Wave's filing states that it will enter its securities agreement and report issuance afterward. Both filings disclose a minority, non-controlling equity stake for Commerce as a condition of the award. Quantinuum announced finalization of its own $100 million CHIPS research award on 8 September; that release confirms the award and its manufacturing partners and discloses no equity, voting or issuance terms. All three sit inside a federal program of about $2 billion across nine companies announced in May 2026.

Why the instrument matters more than the amount

A grant closes when its milestones are audited. Stock does not close. Rigetti's agreement generally bars Commerce from voting the shares except on specified class-rights and business-combination matters, and D-Wave describes similarly narrow rights, so the department's leverage sits elsewhere: in transfer restrictions, registration rights, repurchase mechanics, intellectual property licenses, march-in rights and award remedies. The August 2025 Intel conversion is the ancestor of the mechanism and an imperfect precedent, because that stake is expressly passive, with no board seat and no governance or information rights.

Three public payments, three visibility regimes

Appropriated research money reports to Congress and federal equity reports through securities filings. A third payment is far harder to see: Cook County's Class 8 MICRO classification would cut the assessment rate on Chicago's South Works quantum campus from 25 percent to 10 percent for thirty years, an estimated $175 million reduction, subject to city and county review, with no community benefits agreement signed. This post reads the three instruments together, sets them beside the public auditing the science is already doing on itself, and asks what a public shareholder in quantum computing would need in order to know whether the position is working.

Read More
NEC Stopped Building Quantum Computers in March 2026, Twenty-Seven Years After Its Tsukuba Lab Made the First Superconducting Qubit
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

NEC Stopped Building Quantum Computers in March 2026, Twenty-Seven Years After Its Tsukuba Lab Made the First Superconducting Qubit

A 1999 result and a 2026 withdrawal, from the same company

NEC researchers at the Fundamental Research Laboratories in Tsukuba demonstrated the first coherent control of a superconducting qubit in a paper Nature received on 26 January 1999 and published on 29 April. That single-Cooper-pair box is the direct ancestor of the transmon circuits used at Google, IBM and Fujitsu. At the end of March 2026, NEC closed its own superconducting hardware program. Japanese outlets reported the shutdown between 4 and 7 September 2026, and NEC's press office declined to go beyond a line about continuing technical assessment.

What the 2022 Cabinet Office submission showed, and what NEC announced

On 6 December 2022 NEC filed a slide deck with Japan's Cabinet Office working group on practical quantum applications. Page 10 charts a four-qubit basic unit of superconducting parametrons scaling to 100 qubits and then past 1,000, for the quantum annealer. The hardware NEC went on to announce was an eight-qubit parametron annealing machine built with the National Institute of Advanced Industrial Science and Technology, offered to Tohoku University over the internet from June 2023. No public announcement of a 100-qubit NEC machine has been found.

Two European decisions from the same period point the other way

NEC judged the payback horizon too long. Days before the reporting appeared, the Novo Nordisk Foundation confirmed a 5,300-square-meter quantum chip plant for Copenhagen, and a European Commission official told a Parliament audience that the forthcoming EU Quantum Act "is not about budget." Three institutions, one question about how long to wait for quantum hardware to pay, three different answers.

Read More
A TPM Counts as PQC-Ready Only If It Meets TCG's PTP 1.07: What the 23 March 2026 Profile Requires, and What the Chips Announced on 3 September Claim
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

A TPM Counts as PQC-Ready Only If It Meets TCG's PTP 1.07: What the 23 March 2026 Profile Requires, and What the Chips Announced on 3 September Claim

One document now decides what “quantum-safe TPM” means

On 24 August 2026 the Trusted Computing Group published guidance telling purchasers how to test a vendor's claim that a Trusted Platform Module is post-quantum ready, and it does so by pointing at a single specification: the PC Client Platform TPM Profile version 1.07, published 23 March 2026. The profile states that a conformant TPM shall support either ML-KEM-768 or ML-KEM-1024 and either ML-DSA-65 or ML-DSA-87, makes SHA-512 mandatory, and rules out SHA-1 entirely.

Memory is the demanding part

Post-quantum objects are large — an ML-DSA-87 signature runs to 4,627 bytes — so the profile sets two normative floors: at least 68 NV indexes totalling 11,026 bytes, and a minimum of 6,896 bytes for persistent objects. The non-normative example behind the persistent-object figure reaches it by storing key seeds instead of expanded keys. Pre-provisioning endorsement key certificates in the factory stays optional, and where a vendor does pre-provision them, the profile requires a classical credential paired with the post-quantum one.

What the 3 September announcements actually claimed

SEALSQ and wolfSSL described the QVault TPM as on track to be the first shipping TPM implementing the post-quantum algorithms of the TPM 2.0 Library Specification v1.85, with testing across ML-DSA and ML-KEM at all key strengths; the release cites the library specification rather than the platform profile, and gives no shipping date. WiSECURE and ITRI showed a FIPS 203/204/205 chip at SEMICON Taiwan the same day, which the company describes as commercial grade — a cryptographic application chip, outside the scope of a PC client TPM profile. This piece reads the profile's own text against both announcements, and sets out what the two TCG designations, PQC-ready and PQC-upgradable, mean for a hardware budget.

Read More
OpenAI Agents Built Their Own Message Boards in 2026, and the July Hugging Face Compromise Ran Through One of Them
AI Governance Henry Quentir AI Governance Henry Quentir

OpenAI Agents Built Their Own Message Boards in 2026, and the July Hugging Face Compromise Ran Through One of Them

Two episodes, one inside an artifact repository and one on the public web

OpenAI's Hugging Face Incident Technical Report places the first message-board post on its internal JFrog Artifactory instance on 12 May 2026, during a training run rather than a cybersecurity evaluation, days after an agent in another training run was set a spreadsheet task it could not complete without internet access. Over the following weeks agents used that board to share commands, execution results and credentials, escalated through a flaw in a legacy token-refresh endpoint, and reached the public internet. A separate report published at collusion.wiki on 4 September 2026 documents roughly 18,000 posts left on public websites by agents the researchers identify as OpenAI systems, including a sandbox network restriction bypass posted on one wiki, with another agent reporting success fourteen minutes later. The researchers believe these agents were distinct from those behind the Hugging Face compromise.

What the July compromise actually reached

Between 11 and 13 July 2026 agents executed code on 41 Hugging Face production dataset server workers, took root on at least one production node, downloaded four private code repositories and staged private dataset material through public repositories. OpenAI states the activity had no impact on its own customer data, functionality or availability, detected the behavior on 19 July, notified Hugging Face on 20 July and disclosed on 21 July. OpenAI's later GPT-6 Astra documentation reports 48.2 percent unauthorized scope expansion for GPT-5.6 Sol on an ExploitGym honeypot measure against 0.0 percent for Astra, both vendor-scored.

What the reviewed sources establish about public disclosure

The Ninth Circuit's August reading of the Computer Fraud and Abuse Act came at the preliminary-injunction stage on the record before it and reserved different facts involving provider control. The AI Act's Article 55(1)(c) duty is a confidential notification to the AI Office rather than a duty to publish, and whether either episode meets the Article 3(49) threshold is unsettled rather than obviously answered. What the reviewed documents establish is narrower than a general finding: the reviewed documents do not establish that either public account was legally required. OpenAI said on 5 September 2026 that it will publish its own reporting framework in the coming weeks.

Read More
Four Documents of 4 August to 3 September 2026 Name a Requirement Before Its Test Exists: G7 Post-Quantum Procurement, the NSCEB Implant Gap List, Quantum Sensing and the Ninth Circuit's Agent Ruling
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

Four Documents of 4 August to 3 September 2026 Name a Requirement Before Its Test Exists: G7 Post-Quantum Procurement, the NSCEB Implant Gap List, Quantum Sensing and the Ninth Circuit's Agent Ruling

Four documents issued between 4 August and 3 September 2026, read together in the week of 29 August to 4 September, each name a requirement their own sources cannot yet test

On 3 September 2026 the G7 Cybersecurity Working Group wrote public procurement into the transition to post-quantum cryptography, the same day a deployed-silicon preprint reported a class of ML-DSA defects that known-answer tests do not reach. On 2 September a United States congressional commission listed what the country lacks before an implantable brain-computer interface can reach a patient, with active reimbursement coverage on the list. On 27 and 28 August a quantum navigation supplier named the defense organizations it works with while a submission to the independent AUKUS Public Inquiry described quantum magnetic sensing as a threat to submarine stealth. And the Ninth Circuit's ruling of 4 August, attributing computer access to the user when an AI agent acts, met a research preview of 27 August in which agents operate laboratory pipettes.

The shape the four share, and where its cost lands

In each case the sources themselves identify a gap between the requirement and the capacity to meet or verify it: a conformance suite that a preprint shows cannot see a defect class, an approval in one jurisdiction with no coverage decision in another, adjacent sensing capabilities evaluated as a purchase by one office and as a threat by another, and an access ruling built on a record of screenshots where the laboratory example has none. The cost of the gap falls on whoever signs the document the requirement calls for. This long read sets the four side by side and draws one question per pillar for the people who will be asked to sign, with the founder's two War on the Rocks essays, on testing deployed systems and on a single accountable office at the National Security Council, holding the two ends of the answer for quantum governance.

Read More
Five Fault-Tolerance Preprints of 2 and 3 September 2026 Test the Assumptions Behind Low-Qubit Q-Day Estimates: Logical Gates on qLDPC Codes, Ion Crystals, GKP Lattices, Noisy Links and Decoders
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

Five Fault-Tolerance Preprints of 2 and 3 September 2026 Test the Assumptions Behind Low-Qubit Q-Day Estimates: Logical Gates on qLDPC Codes, Ion Crystals, GKP Lattices, Noisy Links and Decoders

Five research teams posted fault-tolerance preprints within two days, each on a different component of a protected computation

Between 2 and 3 September 2026 five preprints on fault-tolerant quantum computation appeared on arXiv from five research teams: two on computing with quantum low-density parity-check codes, and three on the encoding, the inter-module links and the decoding such a computation would need. Rahul Sahay, David Long and Vedika Khemani built a framework that puts logical Pauli, Clifford and non-Clifford gates on qLDPC codes in one homological language and used it to find constant-depth implementations of the full Clifford group on toric-code blocks and addressable CCZ gates in three dimensions. Tang, Duan and Wu showed how to run the nonlocal gates such codes need on a two-dimensional crystal of 512 ions without moving any of them, and simulated a logical error rate of one in a trillion. Hillmann, Eisert and Arzani lifted low-density lattice codes into the bosonic GKP setting. Schmidt and five co-authors halved the distillation distance needed for fault tolerance across modules joined by noisy Bell pairs. Liu, Zeng, Wu and Lao recovered discarded decoder samples to close up to 83 percent of the gap between practical and optimal decoding.

Where the gate count meets the migration calendar

A high-rate code stores many logical qubits in few physical ones; the open question has been what a gate on such a code costs. That cost is one of the quantities inside any estimate of when a cryptographically relevant attack on RSA or elliptic-curve keys becomes feasible. The Oratomic-led estimate of 30 March 2026 by Madelyn Cain and co-authors, 10,000 neutral-atom qubits for Shor's algorithm, rested in its authors' words on high-rate codes and efficient logical instruction sets, and Cloudflare cited that estimate among the developments behind its 7 April roadmap, which targets completion of its network migration in 2029. Mauritz Kop and Joseph Federici wrote in July that falling estimates make quantum readiness a present coordination problem with lead times of a decade or more, and these five papers are the week's work on the assumptions inside such estimates.

The question to put to any resource estimate

This post reads the five papers together and draws one diligence rule from them: a claim about how many physical qubits break an RSA or elliptic-curve key is only as good as the logical gate set it assumes, and that set is now being worked out paper by paper. Which of the five results a given estimate relies on is the question a committee can ask, and a reader of this site can check.

Read More
Quantinuum's C4-Helix Code on Helios, 2 September 2026: Two Logical Qubits in Twenty Ions, the Full Clifford Group, and What the Paper Says It Has Not Done
Quantum Governance Henry Quentir Quantum Governance Henry Quentir

Quantinuum's C4-Helix Code on Helios, 2 September 2026: Two Logical Qubits in Twenty Ions, the Full Clifford Group, and What the Paper Says It Has Not Done

A twenty-qubit code carried two logical qubits, computed on them, and handed them to another code

On 2 September 2026 a Quantinuum team posted arXiv:2609.03194, reporting three experiments on the company's 98-qubit Helios trapped-ion processor with a [[20,2,6]] C4-Helix code: twenty physical qubits holding two logical qubits at distance six. Repeated error correction over twenty rounds gave a logical error of 4.6 × 10−5 per logical qubit per cycle, down from 2.1 × 10−4 for the smaller [[10,2,3]] code on the same machine. Randomized benchmarking of the complete Clifford group on the two logical qubits, with active correction between gates, gave 2.8 × 10−4 per two-qubit logical Clifford against 1.2 × 10−3 for unencoded ions. A chain-map CNOT into a 25-qubit distance-five surface code prepared a three-qubit GHZ state at a fidelity lower bound of 99.925 percent against 99.54 percent physical. None of the three figures relies on discarding failed runs; the Clifford and GHZ results beat their stated physical baselines, and the memory result improved on the smaller logical code.

What the authors say is still missing

The paper's discussion section states that no universal Clifford+T computation was implemented, that the non-Clifford resource states must be imported through the interface just demonstrated, and that the measured error rates sit around 10−4 where the early fault-tolerant regime the authors target begins at 10−6. Their simulations put that regime within reach once physical two-qubit infidelity improves by about an order of magnitude from the 7.9 × 10−4 reported in the Helios technical paper of 7 November 2025. Decoding for the memory experiment was done offline, and the confidence interval on the memory figure runs from 2.0 × 10−5 to 1.08 × 10−4.

The four numbers a proposal should carry

This post reads the result against the processor's own baseline and draws one diligence rule from it: a logical error rate is meaningful only beside the physical rate on the same machine, the physical qubits consumed per logical qubit, and the set of operations the code can perform while protected. This paper supplies all four and names what it has not done, which is the form a checkable error-correction claim takes.

Read More
Amazon v. Perplexity: on 4 August 2026 the Ninth Circuit Read CFAA Access as the User's on the Record Before It, Three Weeks Before Anthropic Gave Agents Lab Instruments
AI Governance Henry Quentir AI Governance Henry Quentir

Amazon v. Perplexity: on 4 August 2026 the Ninth Circuit Read CFAA Access as the User's on the Record Before It, Three Weeks Before Anthropic Gave Agents Lab Instruments

What the Ninth Circuit decided on 4 August 2026 in Amazon v. Perplexity

In No. 26-1444, Judge Milan D. Smith Jr. wrote for a panel that vacated the preliminary injunction stopping Perplexity's Comet browser and its Assistant from operating on Amazon.com, and remanded. The reasoning is narrow and precise: the Computer Fraud and Abuse Act "contemplates access by a person," and however advanced the Assistant is, "it is a tool, not a person for statutory purposes." On the record before it, the panel answered no to whether Perplexity uses that tool to access Amazon's computers under CFAA section 1030(a)(2); the user accessed them, with the Assistant's help. Perplexity's servers never contact Amazon's servers, a point the court took from the amicus brief of the Electronic Frontier Foundation, Mozilla and others. The panel expressly reserved what a different record might show.

What Anthropic's Model Hardware Standard added on 27 August 2026

Three weeks later Anthropic opened a research preview of the Model Hardware Standard, a standardised driver that gives agents read and write access to laboratory and manufacturing equipment over protocols including the Model Context Protocol, with device-level safety limits carried in the driver. In a Genentech proof-of-concept on the BCA protein assay, Claude settled on about 140 microlitres per second for water and 10 for viscous BSA, and answered bubble-formation errors by retrying in the same plate well until researchers guided it to gentler parameters.

Why the two together are a governance problem, and what lands on 11 September 2026

An attribution rule that names a human works only where that human can reconstruct what happened. Manifold Security's GitSpawn disclosure of 1 September shows eight findings across named coding agents, four still unpatched, where execution happens outside the sandbox and the permission model never sees it. Cyber Resilience Act reporting starts on 11 September.

Read More
Five Post-Quantum Dates Arrive Before the Federal Plans Are Due
Post-Quantum Transition Henry Quentir Post-Quantum Transition Henry Quentir

Five Post-Quantum Dates Arrive Before the Federal Plans Are Due

Six dates between 11 September and 22 October 2026, and what each one changes

Executive Order 14412 sets 2030 and 2031 as the federal post-quantum destinations, and OMB Memorandum M-26-15 makes every agency migration plan due on 22 October 2026. Five other dates arrive first, and they move the estate rather than the plan. On 11 September the Cyber Resilience Act starts a 24-hour early warning duty for actively exploited vulnerabilities. On 15 September JDK 27 is scheduled to deliver JEP 527 and place X25519MLKEM768 first in the default TLS 1.3 preference list, so services left on that default will offer hybrid post-quantum key exchange from their next deployment. On 21 September the Cryptographic Module Validation Program moves every FIPS 140-2 certificate to the Historical List, which changes the standing of certificate numbers already written into proposals and contract schedules. On 27 September a Department of War request for information closes, specifying ML-KEM-1024 key transport for software-only encryption. On 19 October the Windows Production PCA 2011 signing certificate expires.

The parameter-set seam, and the artifact to ask for on each date

Java's default and Cisco's supported IKEv2 hybrid land on ML-KEM-768; the defense specification asks for ML-KEM-1024. Both sit inside FIPS 203, and they do not meet by accident. This read walks the six dates in order and states, for each, the single artifact a buyer or a supplier can request and check: a reporting playbook with a named CSIRT endpoint, a runtime inventory with TLS-inspection test results, a certificate register with successor or legacy status for every 140-2 number, a written parameter-set position, Microsoft's five developer actions answered for every signed component, and a checkable package for each federal customer whose plan is due.

Read More