Week 1

Personalise your Codex

This is the first step. Skip it, and everything downstream is generic.

Works.

Concept

A folder full of files is not a brain. It's a storage unit.

The brain is the thin layer Codex actually reads, distilled out of the dump.

We turn your team into AI operators.

Week 1 is an identity, not a feature list.

Constitution. Work. Goals.

By the end of the week, Codex knows all three.

Gather. Read. Interview. Synthesise.

The four-step method, run on each person's own real material, not a blank page.

Concept

Three files barely move. One changes every week.

about-me, voice-reference, and working-preferences are slow. current-context is fast.

Concept, previewed now

One home per topic. Never stacked on top of each other.

Previewed now, enforced from Week 4 once the recording layer lands.

Tool choice

Tool-agnostic, by design.

We're tool-agnostic. The architecture works on Claude, Codex, Gemini. We default to Claude because it's the best fit for most engagements. For specific principals or workflows we pick the right tool for that slot. The architecture stays the same.

Concept, the spine of the course

One long chat burns context exponentially. Short sessions are the fix.

Short sessions only work if the chain behind them holds.

Site team, mini-track

Bruce and Jai learn a different way. Voice in, voice out.

One 45 to 60 minute session, landing alongside this week. No keyboard exercises.

Governance, every week

We read from Jack and Databuild once the read-only exports land. We never write into either.

Rob's rule, standing for the life of this course.

Before next session

This week's work

Lachlan (CEO): his own proposal templates plus his own working estimate, about 60 admin days a year, straight into the interview.
Rob (CFO/COO): the governance and fitness-for-purpose lens, drawn from his own CFO planning documents.
Susan (Design Lead): her design brief templates and the roughly 40 past reverse-briefs already on file.
Mollie and Grace (Project Leads): their own resourcing model, the planner view the sales system doesn't have.
Kat (Construction Manager): her own cost-code tool build and her site-reporting habits.
Mel (Contracts Administrator): a drafted context file to review and correct, not built cold, one win first.
Michael, James, Trent, and Steve: their own role documents, through the same interview method.

Exit criteria

You're done when

You open a fresh chat and ask Codex what you should work on and how it should talk to you, and the answer sounds like you, not generic AI.
You can point to where your Constitution, Work, and Goals layers live.
You can name the four-link chain, sessions to files to structure to context routing, and where each piece lands in the course.
You can state the three homes rule in your own words, even though nothing enforces it yet.
You've run the two-minute end-of-session debrief habit at least once this week.
Protected weekly time for the course is confirmed on the calendar.