Alphabeta Math
TheoremStatement: Literature-sourcedProof: AI-adaptedPipeline-generatedjudge pass (gpt-5.6-terra)audited 2026-09-14
How statement and proof provenance work

The first chip identifies the source of the statement or construction; the second identifies the source of its local proof or verification.

  • Literature-sourced: the exact statement appears in a cited source; only wording and notation differ.
  • AI-adapted: a semantically identical restatement of literature-sourced material, modulo indexing, notation, and boundary cases adopted by the library.
  • AI-generated: a genuinely novel statement formulated by AI, with no source for the claim itself.

These labels describe origin, not correctness: citations and verification chips remain separate evidence.

Finite-support iterations of ccc forcing are ccc

Statement

In ZFC, if every Pα forces Q˙α ccc, then every Pβ of the finite-support iteration is ccc.

Facts & Assumptions

Given: AC and the stated finite-support iteration.

[F2]

Restriction maps and complete embeddings in an iteration supplies restriction maps and complete top-padding embeddings. Normalization of off-support names and disjoint-tail amalgamation at limits are verified directly from the iteration order below; F2 makes no claim about arbitrary restrictions.

Proof

1.1

First normalize any pPβ without changing its forcing condition up to equivalence. At every ξsupp(p) replace p(ξ) by the distinguished literal top name 1˙ξ; retain p(ξ) on its finite support. Induction on ξβ shows that the original and normalized prefixes force each other below themselves. At an off-support coordinate the original prefix forces p(ξ)=1˙ξ by the definition of support, and forcing-equivalent prefixes preserve that assertion; at a support coordinate the names coincide. Consequently the normalized function is a valid condition with the same support and is equivalent to p in both order directions. If its support lies below α<β, it is literally the top-padding of its Pα restriction. Replacing members of an antichain by equivalent normalized conditions preserves incompatibility. This normalization uses the supplied top names of the finite-support definition, not a property claimed by F2.

F2given
2.1

Induct on β. The trivial initial stage is ccc and F1 gives every successor step. If cf(β)=ω, write β=supnβn. Normalize an alleged ω1-antichain by step 1.1. Every finite support is contained in some βn, so one n captures uncountably many normalized members. They are literal top-paddings of Pβn-conditions. Induction makes two compatible in Pβn, and F2 carries that compatibility to their paddings in Pβ, contradicting the antichain.

F1F2step 1.1
3.1

At a limit of uncountable cofinality, normalize an alleged ω1-antichain by step 1.1. If one finite support occurs uncountably often, choose α<β above it; the corresponding normalized conditions are literal paddings from Pα, contradicting induction and F2. Otherwise thin to uncountably many distinct supports and apply F3 to obtain a delta system with finite root r. Choose α<β above r. By induction two restrictions to α are compatible. Their support petals above α are disjoint. Let sPα extend both restrictions and form the function whose prefix is s, whose coordinates above α on the two disjoint petals are those of the respective normalized conditions, and whose other coordinates are literal top names. At a tail coordinate belonging to one petal, the new prefix extends that condition's original prefix, so its forced iterand membership and order comparison persist by monotonicity; at coordinates of s, validity is already checked in Pα. Hence this finite-support function is a valid condition extending both normalized conditions. The disjoint-tail amalgamation is proved from the iteration order; F2 is used only for the literal padded prefix. This contradicts the antichain, and equivalence transfers the contradiction to the original conditions. AC is used for thinning.

F2F3step 1.1step 2.1

Depends on

Used by

Dependency tree · two levels

17 results within two dependency steps of this one, each drawn at its shortest distance from it. An arrow runs from a result to what uses it, so the chart reads left to right and ends at this result, which carries a heavier outline. Every node is a link to that result. Click elsewhere on the chart to enlarge it.

Sources