Six indexed capabilities — prose, not cards.
We build the structural document that states who you are for, what you refuse, and what proof supports the claim. Written before visual work.
Frameworks include a refusal column and a proof ladder — claims must climb from observable fact to market promise.
Long-form story architecture — origin, tension, resolution — adapted for board, web, and field teams.
Narrative work starts as numbered scenes on index cards before it becomes investor copy or homepage hero text.
Primary, secondary, and proof messages ranked so every channel knows what leads.
Sales one-pagers inherit the same rank order as the website — proof lines never lead before the promise.
Quarterly editorial arcs with named themes — not a content calendar of filler.
Each quarter ties to a business milestone: launch, expansion, or category shift — not a posting quota.
Voice principles, sample rewrites, and forbidden phrases — held in the vault document.
Rewrites use your actual live copy as the before sample — invented examples are not permitted in vault voice guides.
Documentation bundle: positioning, narrative, hierarchy, voice — indexed for handover.
The system index lists owner, version date, and next review — agencies paste it into your wiki unchanged.
Framework documents carry a refusal column listing claims the brand will not make in market.
Narrative drafts circulate as numbered scenes before they become website copy or investor slides.
Hierarchy sheets use green pencil markup on paper proofs — digital comments come after physical read.
Editorial arcs tie each quarter to a business milestone, not a posting quota or channel calendar.
Voice guides include before-and-after rewrites from actual client copy, not invented examples.
System bundles ship as a folder index with owner names — your wiki team knows where to start.
Capability numbers stay fixed so email references like “Archive 03” match what you see here.
We cross-link documents internally: narrative cites positioning page; voice cites hierarchy page.
Archive entries note typical rhythm — sprint weeks versus residency months — in the footer of each doc.
Drift audits use anonymised screenshots stored with client permission — never published as case studies.
Rain on the studio window appears in our photos; the work itself stays dry, written, and filed.
New capabilities get a seventh index slot only when we have run three engagements using the method.
Agency partners receive read-only vault copies — they annotate, they do not rewrite the spine.
Revision history lives in the margin of every framework — version 1.3 replaces 1.2 with a dated note.