8000 GitHub - RomanMIzulin/sacred-bit: Holy computar blessed · GitHub
[go: up one dir, main page]

Skip to content

About

Holy computar blessed

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

∅ The Order of the Null Pointer

A full-stack, quasi-religious practice platform for IT people — a digital monastery for those who compile, suffer, and believe.

It is deliberately not tied to any existing religion: it is an original cosmology built from the only sacred materials an engineer trusts — the void, the compiler, and the stack trace. ADHD, autism, and neurodivergence are proclaimed, in canon, as blessings from above: you are a different build, and it is sacred.

  • Frontend: Elm Land 0.20 (Elm 0.19.1)
  • Backend: TypeScript + Effect 3.x (@effect/platform HTTP API, @effect/sql + SQLite via better-sqlite3)
  • Tests: Vitest + @effect/vitest (backend), pure unit tests (frontend logic)

Features

  • Home — mantra of the day and the Blessing of the Chosen.
  • Rituals — eight sacred rites with XP, daily/weekly/anytime cadence, and a per-day cap on XP farming. Keeps a daily streak.
  • Confession — confess your tech debt, receive a deterministic absolution and penance.
  • Public Confession Wall — a public feed of confessions, each signed with the confessor's spiritual name and shown with its absolution and penance.
  • Oracle — divination by stack trace: a deterministic 6-line hexagram, judgement, guidance, and a mystical crash trace.
  • Saints — a pantheon of eleven patron saints of computing, with apocrypha and feast days.
  • Calendar of Feast Days — all saints' feast days laid out by month, with today's feast highlighted.
  • Scripture — the Blessing of the Chosen, the Litany, the Book of Falls, the Articles of Faith, the Parables, and the Ten Commandments of the Code.
  • Profile — XP, ordination ranks, progress bar, achievements, and a spiritual-name (rename) form.
  • Doctrine — the full canon lives in DOCTRINE.md: Genesis, the Divine Hierarchy, the Book of Falls, the Articles of Faith, the Parables, and more.

Identity is a UUID stored in localStorage and sent to the backend as part of the URL; the backend lazily creates an initiate row on first contact. No login, no cookies, no personal data leaves the browser.

Architecture

it_to_religion/
├── backend/            # Effect-TS HTTP API + SQLite
│   ├── src/
│   │   ├── main.ts     # entrypoint: API + static file serving
│   │   ├── Api.ts      # HttpApi endpoints (typed request/response schemas)
│   │   ├── Service.ts  # domain logic (XP, streaks, ranks, achievements)
│   │   ├── Repo.ts     # SQL repository (Schema-decoded rows)
│   │   ├── Db.ts       # SQLite layer + migrations
│   │   ├── Lore.ts     # all canon content (rites, saints, commandments, falls…)
│   │   ├── Oracle.ts   # deterministic stack-trace divination
│   │   ├── Leveling.ts # rank thresholds
│   │   └── Domain.ts   # Schema models + tagged domain errors
│   └── test/           # vitest suites (18 tests)
├── frontend/           # Elm Land app
│   ├── src/
│   │   ├── Api.elm     # types, JSON decoders, HTTP helpers
│   │   ├── Layouts/Default.elm  # light "cathedral" theme + nav
│   │   ├── Pages/      # Home, Rituals, Confession, Oracle, Saints, Calendar, Scripture, Profile
│   │   └── interop.js  # localStorage identity → Elm flags
│   └── elm-land.json   # proxy config for dev
└── DOCTRINE.md         # the full lore

Run it (production-style, one process)

The backend serves the built frontend and the API on a single port:

cd frontend && elm-land build
cd ../backend && npm install && npm start
# open http://127.0.0.1:4000

Run it (development, two processes)

# terminal 1 — backend on :4000
cd backend && npm install && npm run dev

# terminal 2 — Elm Land dev server (proxies /api to :4000)
cd frontend && PORT=1234 elm-land server
# open http://localhost:1234

(PORT/HOST env vars control the Elm Land dev server; --port is ignored.)

Configuration (backend)

Env var Default Meaning
PORT 4000 HTTP port
HOST 127.0.0.1 bind address
DATABASE_PATH ./data/ordo-null.db SQLite file
STATIC_DIR ../frontend/dist built frontend directory

Tests & checks

cd backend
npm run typecheck   # tsc --noEmit
npm test            # vitest (18 tests)

cd ../frontend
elm-land build      # compiles the Elm app

API sketch

GET  /api/health
GET  /api/lore                       # mantra, blessing, litany, commandments, falls, principles, parables
GET  /api/saints                     # saints with structured month/day feast fields
GET  /api/rituals
GET  /api/oracle                     # deterministic by date
GET  /api/confessions                # public confession feed (spiritual name + absolution + penance)
GET  /api/initiates/:id              # profile (auto-creates)
POST /api/initiates/:id/name         # set spiritual name
POST /api/initiates/:id/rituals/:ritualId/perform
GET  /api/initiates/:id/confessions
POST /api/initiates/:id/confessions

Saints carry a human-readable feastDay string plus structured month and day integers (1–12 / 1–31), which the frontend uses to render the Calendar of Feast Days and highlight today's feast.

Errors are Schema.TaggedError values serialized as JSON (e.g. {"_tag":"RitualNotFound","ritualId":"…"} with HTTP 404).

Design notes

  • The backend is written with Effect's services/layers, typed errors, and HttpApi schemas; the HTTP layer is generated from the same schema the responses are validated against.
  • All canon text lives in backend/src/Lore.ts — a single source of truth.
  • The Oracle and mantra-of-the-day are deterministic (seeded by date), so everyone sees the same prophecy on the same day.
  • Streaks are computed in UTC from the ritual_logs.day column; daily/weekly rites award XP at most once per calendar day.

About

Holy computar blessed

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

0