NN-kebab-case-name.md. Two-digit prefix, hyphen, lowercase, hyphen-separated.The marketing knowledge base ships as a single operating system: every discipline conforms to the same chapter spine, and a router skill decides which chapters Claude loads based on what Gnesis is doing right now.
The /revised/ folder has eleven marketing disciplines in flight. Each is in a different format. The router cannot route over inconsistency, so step one is forcing every discipline into the same skeleton.
Four shapes shown. Seven other disciplines vary similarly. None of them is wrong. They just aren't the same shape, which means the router would need eleven special cases instead of one general rule.
The numbered chapter spine wins because it sorts naturally, forces sequential reasoning, and is already the shape of your most mature disciplines (Positioning, CRO, paid-media). It becomes the canonical template.
NN-kebab-case-name.md. Two-digit prefix, hyphen, lowercase, hyphen-separated.positioning/, paid-media/, email-marketing/.v1/, v2/, v3/ get collapsed./reviews/ folder at the /revised/ root.The router is a Claude Code skill named gnesis-marketing-router. It takes two inputs and outputs the exact chapter set Claude should load. No more dumping the whole knowledge base into context every session.
The router cannot be built before the spine is uniform — otherwise it bakes in the inconsistency and gets rewritten. Sequence is non-negotiable.
Lock the canonical chapter list, naming convention, and the /reviews/ folder. Migrate Positioning, CRO, paid-media first as the reference implementations.
Every remaining discipline gets reformatted to match the spine. Content from existing files is mapped to the right chapter slots. Each completed discipline ships with a trifecta review in /reviews/ before it's allowed to cascade.
Ship gnesis-marketing-router as a skill in project-starter/.claude/skills/marketing/. Wire it to a single state file (gnesis-state.md) so the router knows what Gnesis is doing without being told every session.
The promise to the partner: by the time all three phases land, here's what the marketing OS does that it cannot do today.
Any discipline can be navigated by chapter number alone. Onboarding a new contributor takes minutes, not hours.
Claude pulls four to six relevant chapters per session instead of hundreds of files. Faster sessions, sharper output, lower cost.
Update gnesis-state.md once. Every marketing session for the next phase routes correctly without per-session briefing.
Every discipline has a trifecta verdict in /reviews/. You can see at a glance which disciplines are ship-ready and which still need work.
The router skill ships with operational file + README + .docx. Cascades into project-starter, user-global, Excel master sheet, and the tbk-labs portal.
Add a new discipline by copying the spine. Add a new state by appending one line to the mapping table. The architecture absorbs growth instead of breaking under it.