Don's Canon and the 24-Week Content System

The opening

First call of 2026. Lou was back from three weeks in Thailand and visibly happier for it. The cohort caught up briefly. Lou opened the floor and Don jumped in.

Don’s holiday build

Don spent his Christmas going deep on something he had teased at the previous session. He wanted a content system that built GEO authority without him having to think about what to write each week. What he came back with was structured enough to be impressive and constrained enough to be sustainable.

The architecture he laid out:

• A central canon. The few things he believes are always true about his audience.
• Five supporting laws. Derived from the canon, used as anchors.
• Seven pillars. The container the work happens inside.
• A 2x2 ideal client matrix. Two axes, agency and academic affinity, four quadrants of audience to write to.
• A weekly cadence. Monday a long article aligned to one law. Tuesday a post amplifying it. Wednesday through Friday three short posts written from the perspective of the audience segments in three of the quadrants.

He had mapped twenty-four weeks of this in a spreadsheet. Each row had the law, the quadrant, the hook, the log line. The first two weeks were already drafted.

The drift question

Lou asked the question that mattered. How do you keep this from drifting into irrelevance after week eight? Don had already been thinking about it. He was tracking what he had said and where, in a spreadsheet, with the law and law alignment recorded for each piece. Lou pushed further, the metrics matter, when you do not check engagement until month three, you miss the inflection point at week two.

The cohort worked the tracking question. Start simple, two or three metrics, five minutes a day, manual, until the pattern is clear enough to automate. Do not build the dashboard first.

Bally’s reaction

Bally had been following Don’s posts. She confirmed the work was landing. The thing she noticed was that the consistency was already producing connection requests and comments at a rate his earlier sparser posting never had. The system was working, even if the LLM citation results were still nascent.

What the cohort took away

The frame the room left with, a content engine is not a calendar, it is a constraint structure that keeps you from wandering. Don’s canon was a constraint, the laws were constraints, the matrix was a constraint. The output looked like creativity from the outside because the constraints did the load-bearing work underneath.

Lou closed by saying he wanted to see the spreadsheet on the next call. Don agreed.