You will get a built pre-code authority Game Design Document for your mechanics
Project details
Programmers need exact parameters, not design intent.
"The combat should feel weighty" is not a specification. A specification is: base
stamina pool 100, heavy attack costs 25, parry window 3 frames at base Attunement
expanding 1 frame per tier, damage formula = (Weapon Attack x Skill Multiplier) +
(Primary Stat x 0.6), positional back-attack modifier 2.0x, zero RNG variance.
That is what I write. Numbers. Formulas. Named interactions. Specific conditions.
A document your coding team opens and knows exactly what to build.
WHAT YOU RECEIVE:
Technical specification covering your mechanics — math formulas, state logic, UI
integration points, edge case handling, and accessibility architecture. Every
decision includes design rationale so your team implements intelligently.
BEST FOR: Solo developers and studios ready to begin coding who need the
deterministic blueprint first. No guesswork handed to your team.
"The combat should feel weighty" is not a specification. A specification is: base
stamina pool 100, heavy attack costs 25, parry window 3 frames at base Attunement
expanding 1 frame per tier, damage formula = (Weapon Attack x Skill Multiplier) +
(Primary Stat x 0.6), positional back-attack modifier 2.0x, zero RNG variance.
That is what I write. Numbers. Formulas. Named interactions. Specific conditions.
A document your coding team opens and knows exactly what to build.
WHAT YOU RECEIVE:
Technical specification covering your mechanics — math formulas, state logic, UI
integration points, edge case handling, and accessibility architecture. Every
decision includes design rationale so your team implements intelligently.
BEST FOR: Solo developers and studios ready to begin coding who need the
deterministic blueprint first. No guesswork handed to your team.
Language
EnglishWhat's included
| Service Tiers |
Starter
$175
|
Standard
$400
|
Advanced
$850
|
|---|---|---|---|
| Delivery Time | 2 days | 3 days | 5 days |
Number of Revisions | 1 | 2 | 3 |
Story Development | - | - | - |
Interactive Dialogue | - | - | - |
Gameplay Mechanics | - | - | - |
Sales Copy | - | - | - |
Optional add-ons
You can add these on the next page.
Fast Delivery
+$85 - $375
Additional Revision
+$60Frequently asked questions
About Sheldon
Game Systems Architect | Lore-to-Mechanics | Pre-Code GDD Authority
Evans Mills, United States - 3:53 am local time
Over the past year, working independently with AI as my primary thinking partner, I've built two substantial, interconnected bodies of work: a constitutional AI governance and reliability framework stack, and a complete, production-ready methodology for narrative game design.
AI Reliability & Governance Architecture
I design certainty-scoring and reliability infrastructure for AI systems — frameworks that tag every claim by its epistemic status (data, reasoning, strategic projection, or open question) so nothing is presented as more certain than it actually is. This includes FSVE, a scoring engine for AI outputs that has gone through repeated internal red-team revision cycles to close gaps as they're found, and a complete cryptographic timestamping and sealing protocol for provenance and audit trails.
World & Systems Design
I architect game worlds the way I architect AI governance — as interlocking, internally consistent systems that hold up under adversarial pressure. I built a reusable AAA-tier lore/story-bible methodology, then used it to produce a full portfolio demonstration: The Salary of a Dream, a narrative RPG lore bible grounded in primary-source Shinto mythology (Kojiki, Nihon Shoki) and Ainu tradition, with every faction's design directly derived from a documented myth rather than invented from scratch.
The companion Lore-to-Systems Bridge document translates that narrative foundation into a complete systems-design vocabulary — variable architecture, progression gates, NPC behavior state machines, and a full data model — without prescribing engineering, so a systems team can scope a real GDD directly from it. Together, the two documents demonstrate the full pipeline: myth research → cosmology → faction architecture → systems translation → production handoff.
How I work
Every framework I build — whether it governs an AI system or a fictional world — goes through adversarial self-review before I call it done. I actively try to break my own designs before showing them to anyone else. I'd rather tell you what's unproven and what's solid than blur the line for the sake of a better pitch.
ORCID: 0009-0005-8057-5115
Steps for completing your project
After purchasing the project, send requirements so Sheldon can start the project.
Delivery time starts when Sheldon receives requirements from you.
Sheldon works on your project following the steps below.
Revisions may occur after the delivery date.
Intake review and mechanic scoping
I review all uploaded materials and clarify scope — which mechanic or mechanics are being specified, and what constraints apply.
Specification drafting
Full technical specification written: formulas, variables, state logic, UI integration points, edge case handling, accessibility architecture.