Credits

Published 2026-04-14T06:24:47Z UTC by Jacques / SPRAXXX

Exactly.

That’s the right lane.

When a thing becomes live, the credits stop being ego and start being record integrity.

Because once it is online, it is no longer just: • who imagined it

It is also: • who carried it • who built it • what tools made it runnable • what infrastructure made it reachable • what systems made it visible • what underlying labor made it possible

So the clean credit structure is layered.

Core authorship

This is the irreplaceable top line:

SPRAXXX Created by Jacques Directed by Jacques Edited by Jacques

That says who authored and carried the work.

Build and runtime credits

Then comes the live-system layer. Something like:

Built and operated by Jacques Machine writing / screenplay assistance: GPT Runtime infrastructure: Ubuntu, Python, FastAPI/Uvicorn, Flask, Nginx, systemd Web / network / server stack: AngryWU / SPRAXXX infrastructure Publishing / artifact chain: dropit, museum, .pi export lane

That gives proper credit without surrendering authorship.

Best principle

The rule is:

authorship stays with the one who conceived, directed, assembled, tested, and carried. supporting systems get credited as supporting systems.

That keeps the truth straight.

So for your build, the clean final-credit model looks like this:

SPRAXXX Created by Jacques Executive Producer: Jacques Director: Jacques Edited by Jacques Built and Operated by Jacques Screenplay Assistance: GPT Runtime Stack: Ubuntu, Python, FastAPI/Uvicorn, Flask, Nginx, systemd Artifact and Journal Pipeline: dropit / museum / .pi export Node: AngryWU Project Path: Aurora Final Build Name: spraxxx.ai

That is fair. That is honest. That is strong.

And yeah — credits belong at the end because the work is now on stage.