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.
The omega_2 bookkeeping iteration for MA
Definition
Assume ground-model GCH. At each stage choose, as part of the recursion, a coherent dense coded suborder of size at most using Size bound for finite-support ccc iterations. Fix a well-order of and a bookkeeping map on that repeats every relevant canonical nice code over an earlier cofinally often. The MA iteration is the finite-support iteration in which bookkeeping selects a coded candidate name for an order on a subset of . Choose a maximal antichain deciding whether that candidate is a ccc order of the required size. On each positive branch, use its top-adjoined version as in Martin's Axiom reduces to small ccc orders; on each negative branch, use the one-point order. Mix those branch names into the single name , including a branchwise name for its largest condition. Thus forces that the iterand is nonempty, ccc, and has as a largest condition. A candidate already forced ccc is used, with its adjoined top, on every branch. Cohen forcing, with a top adjoined, is selected at cofinally many stages.
The local mixed top name need not lie in the prescribed set-sized carrier . Apply the AC/maximal-antichain mixing clause of Two-step forcing iterations at to choose forced equal to . Recursively choose these representatives as part of the set-indexed stage data, so the all-top condition and literal top padding required by Finite-support forcing iterations are defined at every stage.
The bookkeeping enumerates canonical codes, not arbitrary raw -names. Given a name which a condition forces to be a ccc order of size at most , first use ambient AC to name an isomorphic presentation on a subset of . Encode its domain and order relation as a subset of the fixed ground set . Below a coded -condition, apply Nice-name reduction and the ccc counting bound using countable deciding antichains from the dense ccc suborder ; this gives an equivalent nice code over . By GCH there are at most such codes at each stage. The coherent coding and schedule revisit each earlier canonical code later, while the raw presentation may have unboundedly many forced-equal names. AC chooses the master well-order, deciding antichains, carrier representatives, and scheduling map. The branch mixture makes “ is ccc” forced by rather than merely decided by some conditions; it never discards a positive branch merely because the top condition did not decide it.
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
- Karagila, Forcing & Symmetric Extensions, Theorem 7.10 and Lemmas 7.11–7.13 (standard reference, not scraped)