Why it exists
Most self-improvement software drifts toward vague tracking, motivational theater, or soft accountability. Oathcraft is trying to support a stricter daily practice without self-deception or moral inflation.
In DevelopmentPublic product record
Oathcraft
A disciplined software system for keeping oaths, closing the day honestly, and progressing without theater.
Oathcraft is the current primary Aubrey Codes project. It turns the Oathcraft system into software, with the mobile product now taking precedence while the studio documents the rules, decisions, and implementation patterns around it.
DisciplineMobileSystems
Public build not linked yetBack to products
How it is being approached
Build from the canon outward, keep the language exact, and let the software stay subordinate to the discipline it is meant to support rather than inventing a looser product category around it.
What it proves
It is now the primary build focus inside Aubrey Codes.
The backend, admin surfaces, and first mobile shell already exist, so the project is being shaped through real implementation instead of planning alone.
Its manuscript and spec force the studio to work from a strong canon rather than improvising product meaning late.
What the studio can reuse
Canon-first product development where manuscript and spec outrank implementation
Tighter alignment between product language, rule system, and software behavior
Using the studio site as a public record of active work instead of only completed proof