Aziel Library

Marion Zioncheck: Birthplace and Origin Investigation Report

Aziel Library

15 views · 19 downloads

Marion Zioncheck: Birthplace and Origin Investigation Report
Executive Summary
An extensive investigation into Marion Zioncheck's birthplace and early origins reveals significant discrepancies between official records and historical narratives. While multiple sources consistently state he was born in Poland (then Austria-Hungary), evidence suggests a possible connection to Chicago that has been overlooked or suppressed. This report examines all available evidence regarding Zioncheck's birth and early immigration, with particular focus on the Chicago connection.
Birthplace Analysis
Official Poland Birth Narrative
The overwhelming majority of historical sources maintain that Marion Zioncheck was born in Poland (then part of Austria-Hungary):
• Born as Marjan Antoni Zajaczek on December 5, 1900 or 1901 in Kęty, Galicia, Austria-Hungary (now Poland)¹ ² ³ ⁴ ⁵ ⁶ ⁷ ⁹ ¹⁰
• His parents were Clemens (Klemens) and Frances (Franciska) Zioncheck (née Wlodiga/Wlodyga)¹ ² ⁷ ¹⁰
• The family immigrated to the United States between 1903-1905² ⁹, with most sources specifically citing 1904¹ ³ ⁵ ⁷

The Chicago Connection
Despite the consistent Poland birth narrative, several sources provide crucial details about the family's connection to Chicago:
• The family "briefly residing in Chicago before relocating to Seattle" after immigrating in 1904²
• Zioncheck "immigrated with his parents and his two sisters to the United States at age three, moving first to Chicago in 1904, then to Seattle in 1906"¹ ²
• This establishes a definite presence of the Zioncheck family in Chicago during the critical timeframe of 1904-1906

Discrepancy Analysis
Birth Date Conflicts
Multiple conflicting birth dates appear in historical records:
• December 5, 1900³ ⁴ ⁵
• December 5, 1901² ⁴ ⁵ ⁶ ⁷ ⁹

This one-year discrepancy is significant when considering his age at death in 1936 (either 34 or 35).
Immigration Timeline Variations
• 1904 immigration¹ ² ³ ⁵ ⁷
• 1905 immigration⁹
• 1903-1904 range²

The Age Discrepancy
As noted in our previous analysis, the 1934 Congressional Directory listed Zioncheck as 32 years old, which would suggest a birth year of 1902. This contradicts all other sources that cite 1900 or 1901.
Chicago Birth Theory Examination
While no source explicitly states that Zioncheck was born in Chicago, several factors support further investigation:
1. The family's documented presence in Chicago shortly after immigration
2. The age discrepancy in official records
3. The pattern of Eastern European immigrants occasionally falsifying birth records
4. The lack of Polish birth documentation in historical records

Conclusion
While no definitive evidence confirms Zioncheck was born in Chicago, the documented family connection to Chicago shortly after immigration, combined with significant discrepancies in birth dates and ages, suggests that further investigation is warranted. The consistent Poland birth narrative across multiple sources may represent either historical fact or a deliberately constructed narrative.
The evidence is insufficient to conclusively prove Zioncheck was born in Chicago, but the documented connection to Chicago warrants further archival research, particularly in Chicago immigration records from 1904-1906 and Polish emigration records from the same period.
Recommendations
1. Search Chicago immigration records for Zioncheck family arrivals in 1904
2. Examine Polish emigration records from Kęty for the Zioncheck family
3. Review Chicago birth records from 1900-1902 for Marion Zioncheck
4. Investigate naturalization papers for the Zioncheck family

---

Sources:
1. Wikipedia - Marion Zioncheck
2. Grokipedia - Marion Zioncheck
3. US House of Representatives: History, Art & Archives
4. The Knoxville Focus - The Congressman From Crazy Town
5. The Seattle Star - August 7, 1936: Zioncheck for President
6. Academic Kids - Marion Zioncheck
7. City of Anxiety - Zioncheck for President
8. ChicagoAncestors.org - 1900 Chicago Directory
9. Infoplease - Marion Anthony ZIONCHECK
10. Find a Grave Memorial - Marion Anthony Zioncheck

Aziel Eliab
research, philosophy, Voynich
Marion Zioncheck: Birthplace and Origin Investigation Report
ABAD, Voynich, CNLT1, Aziel

DownloadCounted download

Triad score

49

One combined report card from SPRE, CLCE.

TRIAD_V3: public combined = triad_cycle_mean = mean of all ordered pairings factor_i × factor_j among applicable factors of {physics, linguistics, bayesian, truth_formula, CLCE, SPRE} (36 when all six apply, including diagonals). Also stored: geometric_mean_applicable = (Π applicable engines SPRE/CLCE/PLR)^(1/n). Named axis products: physics×linguistics, bayesian×truth_formula, CLCE×SPRE. Bayesian is LIKELIHOOD of internal consistency, unranked, never a shelf sort key. triad_raw freezes to content SHA-256 at first REVIEW_SCORE. Downloads verify bytes and do not mint a new mean. No collection offset. Display is round(combined × 100) and is never written back into combined. How it's scored.

Status lights

Green means go. Yellow means read again. Red means stop and check. Easy enough for a 6th grader; kept for government use.

Structure — Green
Every file was hashed and checked.
SPRE — Green
Green: we can see where this file came from and what it is.
CLCE — Red
These stories do not fully match. The title, the notes, and the real file are talking about different stuff.
Poison — Green
Green: this does not look like a poison shell.

e9e33b1e0026458c2c44aac4476fc0b8613a8b173d44dc9400d1d957c3b39782.txt · 2026-09-18 02:45

Hashes

SHA-256 e9e33b1e0026458c2c44aac4476fc0b8613a8b173d44dc9400d1d957c3b39782

chain tip

receipt

DownloadCounted downloadBy hashAPI hash

Machine surfacesllms.txtcite.jsonmetadata.jsonhelp

SPRE, CLCE

SPRE PC 0.83 · strong

SPRE scores provenance completeness. It does not assert criminal guilt. Advisory only. Author Aziel Eliab.

CLCE triple 0.03 · pairwise 0.27 · structural_inconsistency

Public CLCE is structural match (claims↔evidence + headings + verified-file). Token Jaccard is audit-only. Type D is a label, not a finding of malice. Advisory. Threshold 0.7 is not a truth verdict.

Derived artifacts

Temporal-geospatial events

1900 · Chicago · 0.70
1900 · Chicago · 0.90
1900 · Seattle · 0.70
1900-12-05 · Chicago · 0.90
1901 · Chicago · 0.70
1901 · Chicago · 0.90
1902 · Chicago · 0.90
1903 · Seattle · 0.90
1903 · Chicago · 0.90
1904 · Chicago · 0.70
1904 · Chicago · 0.90
1904 · Seattle · 0.90
1904 · Seattle · 0.70
1905 · Chicago · 0.70
1905 · Seattle · 0.90
1905 · Chicago · 0.90
1906 · Chicago · 0.90
1906 · Seattle · 0.90
1906 · Chicago · 0.70
1936-08 · Seattle · 0.90
1936-08-07 · Seattle · 0.90
1936-08-07 · Chicago · 0.70
AzielTether lattice tip
{
  "schema": "aziel.lattice.anchor.v1",
  "kind": "aziel-corpus.recalibrate_v3",
  "carrier": "AzielTether",
  "author": "Aziel Eliab",
  "record_id": "AZDOC-59AC4B4FC723",
  "run_id": null,
  "media_kind": null,
  "vibe_digest": null,
  "library": "aziel",
  "content_sha256": "e9e33b1e0026458c2c44aac4476fc0b8613a8b173d44dc9400d1d957c3b39782",
  "structure": {
    "ok": true,
    "file_count": 1
  },
  "spre": {
    "pc": 0.83,
    "band": "strong",
    "limitation": "SPRE scores provenance completeness. It does not assert criminal guilt. Advisory only. Author Aziel Eliab.",
    "applicable": true
  },
  "clce": {
    "triple": 0.0269,
    "pairwise_avg": 0.268,
    "advisory": true,
    "applicable": true
  },
  "plr": {
    "applicable": false,
    "status": "not_applicable"
  },
  "triad": {
    "combined": 0.4888,
    "display": 49,
    "ready": true,
    "formula": "TRIAD_V3: public combined = triad_cycle_mean = mean of all ordered pairings factor_i × factor_j among applicable factors of {physics, linguistics, bayesian, truth_formula, CLCE, SPRE} (36 when all six apply, including diagonals). Also stored: geometric_mean_applicable = (Π applicable engines SPRE/CLCE/PLR)^(1/n). Named axis products: physics×linguistics, bayesian×truth_formula, CLCE×SPRE. Bayesian is LIKELIHOOD of internal consistency, unranked, never a shelf sort key. triad_raw freezes to content SHA-256 at first REVIEW_SCORE. Downloads verify bytes and do not mint a new mean. No collection offset. Display is round(combined × 100) and is never written back into combined."
  },
  "bayesian": {
    "posterior": 0.6667,
    "unranked": true,
    "note": "Unranked likelihood of internal consistency. Never used to sort the shelf. Not world accuracy."
  },
  "possibility": {
    "possibility": null,
    "kind": "HEURISTIC",
    "refuse": "PENDING_ANCHORS",
    "unranked": true,
    "not_truth": true
  },
  "quarantine": null,
  "zsolver": {
    "status": "not_applicable",
    "applicable": false,
    "seed_corpus": false,
    "baseline": false
  },
  "ledger_entry_hash": "ea166c6fd648b82f9b3c97c7c7ba6a6313273f86176223e66c60774112a49784",
  "verified_utc": "2026-10-04T03:59:11.549Z",
  "note": "Public HTTPS site is not a mesh. AzielTether carries this tip. Survival interdependence with GodLock and other Aziel software is via downloadable tether + Worker bootstrap APIs."
}

The live site is not a mesh. Tether software can carry this tip.

Bayesian peer score

0.667

Unranked metadata for manual peer-to-peer review. Separate from the HEURISTIC possibility score. Never sorts the shelf.

Possibility score

Refused: PENDING_ANCHORS

HEURISTIC over lattice time×geo pins. Adaptive learning via hashchain lattice for recollection and reasoning. API · How it's scored.

Peer-to-peer review

Notes append to the hash-chain. Peers endorse or challenge; nobody rewrites the past.

No peer notes yet. Endorse or challenge without rewriting history.

Sign in to append a peer endorse or challenge. History stays append-only if the operator is gone one day.