What I build
A record of the work this studio is capable of, not a list of services on offer. I am not taking client work, and nothing on this page is a quote or an invitation to commission anything.
Custom software development
Systems where the rules are complicated and the cost of a wrong answer is high. That usually means a calculation engine, a set of business rules, or an internal process that has outgrown the spreadsheet it lives in.
The approach is a fixed scope at the start: read the code and the process, then write down what gets built, what gets left out, and what could go wrong. From there it runs in milestones, with working software at each one.
The shape of this work
- A calculation engine that has to match a specification exactly.
- A reporting layer that reconciles several upstream systems.
- An internal tool replacing manual work that breaks at the end of every month.
- An integration between systems that were never meant to talk.
- Rescue work on a codebase that lost its original author.
How it was scoped
- Discovery
- One to two weeks
- Build
- Monthly, milestone by milestone
- Ongoing
- Retainer for support and changes
AI consulting
The useful question is whether a task can be made reliable enough to depend on, and what the system should do when it cannot. That gets answered with measurements rather than opinions.
I do not sell access to a model or a platform. The work is the surrounding system that makes a model safe to put in front of real work.
What that looks like
- A workflow review that ends in a written recommendation, including "do not use a model here".
- Document extraction where every field has a confidence score and a review path.
- Retrieval over a private document set, with citations back to the source.
- An evaluation suite that catches regressions before your users do.
- Cost and latency budgets, with a defined fallback when a provider is down or slow.
What I will not do
- Promise accuracy numbers before measuring anything.
- Put a model in a decision path that has no human review.
- Build a chatbot when a form solves the problem.
Games
This is the part that is still running. Hagane to Shijima is in development.
Games are a different set of constraints with the same engineering underneath: hard frame budgets, state that changes sixty times a second, and players who will find every edge case you left in.
What the work covers
- Gameplay and systems programming.
- Tools and pipelines for teams of one to ten.
- Prototypes built to answer a single design question.
- Performance work on a build that has stopped keeping up.
- Technical review of a design document before it becomes code.
Also
Brand and interface work for games, including title art, loading screens, and store assets, using a mark designed to hold up at every size.