Studio for focused products
Aubrey Codes builds the projects with real pull and keeps the operating discipline that helps each one ship cleanly.
Aubrey Codes exists to keep active work moving, document what the work teaches, and make sure the next build starts from a stronger position than the last one.
Current focus
Oathcraft has the strongest pull, so it gets the main build attention. Scope Delta remains a maintained proof case, and the studio site tracks both the active work and the reusable lessons around it.
The public site should show what is being built now, not only what once served as the proof case.
Adding a second product should be a content update, not a page rewrite.
The studio only compounds when launches improve the next starting position.
How it compounds
The studio matters only if products, docs, and execution habits start reinforcing each other instead of living in separate piles.
01
Choose the project that still feels necessary once the novelty wears off and implementation details arrive.
02
Build the smallest version that expresses the real idea instead of spending months proving permission to begin.
03
Use implementation friction, personal use, outside response, and monetization attempts to learn what the project actually is.
04
Capture the reusable parts while the work is still fresh so the next project inherits better material.
Products
Each product page should explain the project externally and leave behind something reusable for the studio internally.
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.
A practical operating lens for turning product noise into accountable progress.
Scope Delta is a maintained Aubrey Codes product and the first proof that the studio can ship a useful tool, document it publicly, and then let it stand without forcing the whole studio to keep orbiting it as the main bet.
Studio stance
Aubrey Codes is a studio for following the projects that keep their energy through implementation, shipping them seriously, and keeping the lessons so the next build starts ahead.
What Aubrey Codes is
A studio for focused products, public-facing product records, and a reusable operating layer that gets sharper with each launch.
What Aubrey Codes is not
Not a consultancy brochure, a product graveyard, or a vague umbrella brand that swallows the products it is meant to support.
Templates
Each project can start from reusable briefs, specs, launch checklists, and retros instead of a blank page.
Playbooks
Direction, build, QA, launch, and maintenance are documented as repeatable sequences.
Codex Packs
Repo-specific instructions and task packets keep AI-assisted execution consistent and reviewable.
