infinitereality

Production operations

Production is versioned in jailbreaktheuniverse/infinitereality.cc and served by GitHub Pages. Generated ARTCUBE derivatives are committed; a visitor never causes a source-image conversion or GitHub API request.

Publish

  1. Pull main and make reviewed source changes.
  2. Preview with bundle exec jekyll serve.
  3. Commit and push to main.
  4. GitHub Pages builds the reviewed main branch once and publishes it.

No release ingestion or editorial draft is automatically pushed to main.

Service lifecycle

There is no long-running application process to start or restart. GitHub Pages serves a static artifact. The external dependencies are GitHub Actions, GitHub Pages, the infinitereality.cc DNS record, and third-party listening embeds.

Check the Pages build state with:

gh api repos/jailbreaktheuniverse/infinitereality.cc/pages
gh api repos/jailbreaktheuniverse/infinitereality.cc/commits/main/status

First failure checks

  1. Inspect the Pages build status and Jekyll error.
  2. Confirm CNAME still contains infinitereality.cc.
  3. Confirm the Pages source remains main at /.
  4. Confirm DNS still resolves to GitHub Pages.
  5. Check external embed status separately from the static site.

Rollback

Revert the production commit and push the revert to main. GitHub Pages will publish the preceding reviewed state. Do not rewrite main history.