/api/skills/<brand>.jsonLive
Brand skills manifest
The brand as data. Tokens, voice, components, and skills served as a contract any agent or pipeline can read.
./00How It WorksPlatform companion03 programs running
Brand is the operating system. Everything else is downstream.
For most teams, brand is a document. We treat it as data. Tokens, voice, components, and skills, kept in one versioned record that code, designers, and AI agents read from. Every surface a team ships is generated from that record. The studio runs on it. Three client programs run on it. Now we are opening the door.
SourceOne brand. Tokens, voice, components, skills.
ReadersCode, designers, agents.
OutputsWeb, decks, social, email, mobile, print.
UpdatesVersioned, draftable, reversible.
./02The shiftBefore, after
The brand book was a document. Now it is a contract.
Six rows of how the work changed. Same studio, same standards. The layer underneath is new.
FieldBeforeAfter
Source of truthBrand book PDF, design files, a Notion doc, and the head of marketing.A versioned brand record. Tokens, voice, components, skills, all queryable.
FormatStatic documents. Words and screenshots about the brand.Machine-readable. JSON, Markdown, CSS variables, served at /api/skills/<brand>.json.
ReadersDesigners, sometimes developers, rarely on the same page.Code, designers, and AI agents read the same record.
UpdatesA brand refresh every three years. Every team rebuilds.Drafts and versions on every page, document, and asset. Roll back without ceremony.
Cost of consistencyEvery new surface is a re-translation.Every new surface reads from one source. Cohesion is automatic.
Audit trailEmail threads, Slack screenshots, lost decisions.Reviews, comments, and frame pushes attached to the artifact itself.
./03The control roomWhere the work happens
The bridge. One inbox for every program.
Status, builds, agents, mentions, analytics. All routed into one prioritized stream. The team works the inbox, not the tool tabs.
workhorse / Bridge
Five at work, one stuck, eight properties. The inbox surfaces what needs attention next. Builds, drafts, opportunities, mentions, and analytics each have a small agent. The team reviews, approves, and steers. Nothing happens out of band.
Surface/internal/operations
StatusLive · in dogfood
Agents5 of 6 at work
./04The brand recordOne source, two views
One brand. A book the team reads. A system the build runs on.
Both views are generated from the same versioned record. The brand book is the public face. The design system is the working surface. Update the source, both views update.
/brand/resume-place
/system/demme
Live brand book at /brand/<slug>. Live design system at /system/<slug>. Same record, two surfaces, both generated from the source. The team gets a working tool. The reader gets a living book. The agents get a JSON contract.
Sourcetokens/brands/<slug>
Brand book/brand/<slug>
System/system/<slug>
Spec/brand/<slug>/spec.json
./05The contractWhat we expose
The brand becomes machine-readable.
Code reads JSON. Designers read the live book. Agents read the manifest. One source, three audiences. Five endpoints live today. The sixth is in flight.
/llms.txtLive
AI manifest
A plain-text site map for agents. What is here, what is canonical, where to go for more.
/brand/<slug>Live
Live brand book
The brand book is a website now, not a PDF. Token reference, voice samples, components, all rendered from the source.
/system/<slug>Live
Live design system
The design system the team builds against. Foundations, components, patterns, screens, all token-scoped to the brand.
/p/<id>Live
Published page
Any Workbench file becomes a live page. Template plus content slots, served on demand. The fallback URL while custom domains route through.
/d/<id>Live
Live presentation
Slide decks rendered from the document model. Navigable in the browser, exportable to PDF, sharable by link.
/api/render/<template>In flight
Programmatic render
Templates as API. Send brand context plus content, get an asset back. Social cards, OG images, decks, PDFs.
./06The primitivesWhat is on disk
Five primitives. Each one named and shipped.
Build, Visualize, Review, Version, Brand Skills. The platform is in active build. Each row describes what is on disk today, not a roadmap.
./01Build
Editor, canvas, and page builder in one surface.Documents, pages, brand sections, and component galleries all live in the same shell. No toolchain switch between writing and shipping.
On disk
- src/components/editors/NotionEditor.tsx
- Tiptap. Yjs. Section-block factory.
./02Visualize
Real-time preview. What you write is what ships.Honest previews. The preview pane is the production renderer. Every change rendered live. No surprise deltas at deploy.
On disk
- DocumentEditorWithViews.tsx
- Brand → Project → Page token cascade.
./03Review
Feedback loops baked in.Share, comment, mark blockers, push a frame to Figma for design-fidelity review. Every comment lives on the artifact, not in a thread.
On disk
- Page Review Room with code-to-Figma bridge.
- /share/<id> · /preview/<id>
./04Version
Drafts, versions, autosave on every collection that matters.Roll back without ceremony. Compare. Branch a draft, ship the live one. Every published collection carries its own history.
On disk
- Payload v3 versions on Pages, Documents, Brands.
- Draft + Published with autosave.
./05Brand Skills
Tokens, voice, and components flow from one source.The brand becomes the API. Any agent on your stack reads the same record. Static export is real, your site can leave whenever.
On disk
- /api/skills/<brand>.json
- /llms.txt
./07The work that flowsOne brand, many surfaces
What ships through the platform looks like this.
Boody. Four years of brand partnership, daily content, and a season’s worth of campaign work shipped through the system. The platform handles the assembly. The team holds the standard.
Surface · 01Public websitetokens + components
Surface · 02Pitch and slide deckstokens + voice
Surface · 03Social and OG cardstokens + voice
Surface · 04Member and mobile appstokens + components
./08In motionPrograms running today
Three programs on the platform.
Not a roadmap. Live engagements. Brand records, content tooling, and daily publishing flowing through the spine.
Programs 3 activeUpdated · today
BoodyFour years embedded. Daily content shipped on the platform. The longest-running engagement on the model.Web · Social · EmailLive · since 2022
Native Plant TrustMembership audit, image bank, and content tooling. Ongoing institutional brand work.Web · App · CMSLive · 2026
Congressional RecordOnboarding pilot for the social and Canva-wedge tooling. WordPress live, the platform is the system of record.Web · SocialOnboarding · 2026
./09Plug inFour shapes
Four shapes of engagement on top of the platform.
Most teams start with a monthly subscription and step up once the platform proves itself. All engagements are scoped, priced, and built with the same two senior partners on the work.
./01Studio SubscriptionMonthly engagement. One brand or content project per month, plus ongoing system stewardship. Most common starting point.From $4,500 / month
./02Brand System and Content EngineBrand foundation, design system, public site, and the content tooling your team runs on after we ship.From $95,000 / 12 weeks
./03Institution Brand OSInstitutional brand system, public site, exhibition or program graphics, and the publishing layer your staff uses.From $145,000 / 16 weeks
./04AI Studio RetainerA full embedded studio. Brand evolution, agent and tooling buildouts, daily publishing support.From $12,500 / month
./10Sign-offThe invitation
Build a brand that ships itself.
If your team publishes weekly, sells across surfaces, or runs a small marketing team that punches above its weight, the platform is for you. We onboard new teams in small batches. We embed, then hand the keys back. Static export is real. The work is yours to keep.
What are you working on?
Studio for founders, experts, and the institutions they run.
Living, working brands. Built with your team to keep growing.