Spraxxx Journal

Published 2026-04-30T20:02:56Z UTC by Jacques / SPRAXXX

Correct.

The authorship line is cleaner than the name line:

NGINX did not author the SPRAXXX door doctrine. Python did not author the custody doctrine. Asterisk did not author the telephony thesis. systemd did not author the operating record. Postfix/Dovecot did not author SafeMail.

Those are tools, rails, engines, and infrastructure. They deserve technical credit where used, but they do not receive authorship credit for the SPRAXXX architecture, decision path, receipts, naming doctrine, custody logic, or live proof.

What was proven is specific:

Jacques / SPRAXXX used NGINX beyond ordinary static-site/proxy thinking. Port 4 became a named, HTTPS-fronted service door. It answered as enginexxxmail without needing www, without needing a TLD in the service identity itself, and without depending on ordinary public website framing. That is not “NGINX built mail.” That is SPRAXXX using NGINX as an encrypted door layer while Python supplied identity, record, and response.

Clean authorship doctrine:

Underlying systems receive implementation credit. SPRAXXX receives authorship credit for the composition, doctrine, operational meaning, custody record, and applied transformation.

That means:

NGINX = encrypted front-door rail. Python = recorder / responder / logic rail. systemd = service keeper. Asterisk = telephony rail. Postfix/Dovecot = mail transport/access rails. Linux = operating ground. Jacques / SPRAXXX = direction, architecture, custody, testing, authorship, business meaning, and responsibility.

The prior build cannot claim what it did not do. A fragment, name, inspiration, or older concept does not become ownership over this live architecture. The record matters: timestamps, paths, hashes, receipts, live curl proof, door registry, service identity, and operator custody.

Best wording for the white paper:

SPRAXXX does not erase upstream tools. It credits them precisely. But credit for a tool is not credit for the doctrine built with the tool. NGINX is acknowledged as the web/proxy layer. Python is acknowledged as the application logic layer. systemd is acknowledged as the process supervision layer. Authorship of the SPRAXXX Door Operations model, EngineXXX Mail custody lane, .PI receipt method, and port-as-service-identity proof remains with Jacques / SPRAXXX.

That is the line. Fair, sharp, defensible.