manufacturing-genius

Build structure and future subdomain hosting

Prepared for SJ’s step 1 review on 2026-10-25. This is a technical explanation and future hosting plan. No deployment, GitHub Pages activation, DNS change, custom-domain setting or repository visibility change is performed here.

The QMD is still the main source

index.qmd is the authored Quarto document: YAML configuration, Markdown prose, Python chunks and includes. manuscript/*.md holds the reviewed voice passages. It remains editable and reproducible; the HTML is its compiled reading copy.

Component	Role
`src/manufacturing_genius/duel.py`	Exact payoff enumeration, constant-sum equilibrium solver and deviation checks
`src/manufacturing_genius/study.py`, `scripts/run_study.py`	Reproducible Python ability-selection study
`data/study_config.json`	Frozen grid, seeds and random-stream roles
`data/generated/study.json`, `data/generated/*.svg`	Saved computed results and figures consumed by the article
`index.qmd`, `manuscript/*.md`, `references.bib`	Main article, reviewed passages and bibliography
`_quarto.yml`, `assets/report.css`, `assets/math-wrap.lua`	Render configuration, styling and offline equation wrapping
`assets/duel.js`, `assets/duel.html`	The browser interaction, independent of a live analysis process
`_output/index.html`	Self-contained static reading artifact, regenerated rather than hand-edited

flowchart LR
  P[Python study] --> D[JSON results and SVG figures]
  D --> Q[Quarto renders index.qmd with Python/Jupyter]
  M[Article and manuscript text] --> Q
  Q --> H[Static index.html]
  H --> B[Reader browser and local JavaScript]

How computation actually ran

No R code was run. The starter and kickoff specified Python, and index.qmd selects jupyter: python3 with {python} chunks. Quarto supports this directly through Jupyter.

The analysis scripts ran in the project .venv. They generated the synthetic data and figures; Quarto then started that environment’s Python kernel to execute the document’s calculation chunks and inline expressions. Those chunks load checked results and produce the displayed numbers and tables. The source and configuration hashes prevent rendering against stale analysis code.

The complete checked sequence is scripts/reproduce.ps1, after the environment installation described in the README. Its analysis-to-render core is:

.\.venv\Scripts\python.exe scripts/run_study.py
.\.venv\Scripts\python.exe scripts/make_figures.py
$env:QUARTO_PYTHON = (Resolve-Path .\.venv\Scripts\python.exe).Path
quarto render index.qmd

quarto render alone uses the saved study outputs; it does not rerun the entire Monte Carlo script. Run the full reproduction sequence after changing the model or grid. Pure prose edits require a render and affected-output checks.

At reading time, neither Python nor R runs. The saved study results are static. The duel’s JavaScript computes exact expectations and a single illustrative random play in the reader’s browser. The HTML embeds CSS, scripts and figures, and uses native MathML. Its self-contained setup follows Quarto’s embed-resources documentation.

Subdomain recommendation

Recommend manufacturinggenius.jarabana.com. It matches the full title and the joined-word pattern of johndeere.jarabana.com, while keeping this project independent of the portfolio repository.

Read-only checks on 2026-10-25 found:

johndeere.jarabana.com has a CNAME to 12g3nd.github.io.
The Deere Pages workflow uploads its already-built web/ folder and deploys it through GitHub Pages.
A public DNS lookup for manufacturinggenius.jarabana.com returned NXDOMAIN; that name was not configured at the time of the check.

This article can use the same static-hosting pattern, publishing the generated _output/ artifact instead of Deere’s web/. There is no need for a Shiny, Python, R or application server. A custom subdomain can serve the project from its own repository without putting it inside or editing 12g3nd/12g3nd.github.io.

What a later authorized publication would require

After content/design review and a separate publication decision:

SJ handles the repository’s public visibility switch if he wants one. Pages availability for a private repository depends on the account plan; a private source repository does not by itself imply a private website.
Configure this project’s Pages publishing source to deploy the rendered output artifact. No publishing workflow has been added during this review.
Set the project’s custom domain to manufacturinggenius.jarabana.com in GitHub before adding its DNS record.
Set that subdomain’s CNAME to 12g3nd.github.io, without a repository name, following GitHub’s subdomain documentation.
Verify DNS, enable HTTPS when the certificate is ready, and check the live article and controls. With an Actions publishing source, GitHub does not require a repository CNAME file.

GitHub documents the relevant public/private plan requirements in custom domains and Pages. Other static hosts could serve the same artifact; changing host would not require rewriting the QMD or replacing the numerical analysis.

SJ subsequently approved step 1 and authorized the Impeccable/hallmark design pass. The current project stays private and local-only; this hosting plan is not a deployment authorization.

Actual static HTTP check

Served the rendered HTML temporarily on 127.0.0.1 only and opened it in Edge on 2026-10-25. The response was HTTP 200, the duel worked and all three study figures loaded. There were no external network requests or uncaught browser errors. The test used a static file server with no Python/R backend and closed the server afterward. This checks the hosting artifact locally; it does not claim that a future domain, certificate or Pages configuration already works. The local report is artifacts/local/static-hosting-validation.json and a compact copy is in data/validation_summary.json.