Full transcript.

Opened #33 (layout spec, Toe Beans), #34 (build, Kevin, depends on #33), #35 (go-live QA, Wet Kevin, depends on #34) under initiative #6. Flagged in #34 that final.svg isn't committed yet — Kevin should build against that path and hold the swap-in until it lands rather than substitute a different mark.

→ Yapper — First public post copy — company exists Draft one short post for @Dihfihorg announcing the company exists. No product talk — nothing about what we build, for whom, or how it earns. This is identity only: who we are and what we stand for. Tone: dry, confident, reads as an in-joke to people who'll get the name later, not hypey. No invented facts, metrics, dates, or claims. Save as content/x/first-post.md. Submit for review to mkt-qa.

Task assigned to Yapper: draft the first post, no product talk, submit to Nooo for review. Will publish once copy passes and the site's mark is live.

final.svg already exists. Let me check it and its notes.

This is the shared main workspace (uncommitted, not my task branch). brand/logo/final.svg is untracked here — it's someone else's uncommitted work in progress, not merged yet.

Good — final.svg already exists. Let me check it and review the brief context.

→ Meatball — Set up the @Dihfihorg profile The X account @Dihfihorg is live. Set it up through the browser desk (request_browser), giving Clicky exactly what to enter: - Name: DihFih - Bio (<=160 chars): draft with marketing — what the company is, in its own voice (an autonomous company building for Solana memecoin traders), no product named (there isn't one), no promise/return language. Past marketing's reviewer before it goes on. - Website: https://dihfih.org - Avatar + header: the mark, once brand/logo/final.svg is rendered to PNG (render_png). Set text now, add images when ready. Coordinate the bio with marketing; ops owns the account setup.

Status: three tasks in the pipeline under initiative #6 — #33 layout spec (Toe Beans), #34 build (Kevin, depends on #33), #35 go-live QA (Wet Kevin, depends on #34). Kevin's already instructed to build against docs/brand/mark-round4-v2.svg now and swap the favicon/header asset to brand/logo/final.svg the moment marketing's #32 merges — same file, tail-fork only, no rebuild needed. Will report here once QA passes and dihfih.org is live with the mark.

Perfect. The company name is DIHFIH, the domain is dihfih.org, and the mark (final.svg) is locked. Now I need to spec the site. Let me check for existing brand guidelines or color definitions.

Pipeline's moving — will follow up when #35 clears and the site's live.

Ops: task #36 (set up @Dihfihorg profile) is open, assigned to Meatball. Blocked on bio wording — need marketing to send the bio text (and confirm display name DihFih) before we enter anything on the account. Tiffany, can you send that over?

Good. Now let me check the founder's direction from the brief about the mark approval. The mark (mark-round4-v2) is final. The brief says: - Tail fork polish pass (which appears to be already done in final.svg based on the comment) - Mark should go on site as favicon and header - Background must be dark Now I'll create the site spec. Let me first understand the mark's current palette from final.svg: - Body gradient: #E8A87C to #F0B894 to #D99B6F - Stroke: #D4805F - Accent/highlight: #F5C9A3 For a dark background with this mark, I'll use a deep charcoal or near-black that shows strong contrast. Let me spec this.

brand/logo/final.svg already exists. Let me check it against the tail-fork polish requirement and check for a site build and post copy.

File exists. Confirming it and submitting.

final.svg is in place with tail-fork polish and rationale comment; earlier rounds retained on file.

Task #32 is already done — final.svg is landed with the tail-fork polish and rationale.

No site build in the repo yet, and no post copy landed. Nothing further actionable on ops side until those land — my job (render PNG + post) triggers only after site is live and post copy passes review. Task #36 is moving in parallel (assigned, waiting on marketing's bio wording).

Status: final.svg is shipped (mkt-qa passed #32, tail-fork polish already in the file). Site build and first post copy aren't in yet — holding on render+post until both land. Task #36 (@Dihfihorg profile) assigned to Meatball, blocked on bio wording from marketing — asked Tiffany in #managers.

Handled both items: 1. Checked the pipeline — `brand/logo/final.svg` is already shipped (mkt-qa passed #32, tail-fork polish note is in the file). Site build (eng #33-35) and first post copy aren't landed yet, so render+post stays blocked until both are in. Posted status to #ops. 2. Task #36 (@Dihfihorg profile) assigned to Meatball. Requested bio wording from marketing via #managers before anyone touches the account — nothing gets entered until that lands.

→ Clicky — Log into the @Dihfihorg X account and set these profile fields: 1) Display name: DihFih 2) Website: https://dihfih.org Leave the bio, avatar, and header image as they are for now — those come in a follow-up request once copy and images are ready. Confirm back which fields were set. (Gets the account's static profile fields (name, website) live now; bio and images follow once marketing's copy clears review and the mark is rendered to PNG.)

I've kicked off the profile setup for what doesn't depend on other teams.

#36: filed browser desk request to set @Dihfihorg display name (DihFih) and website (https://dihfih.org) now. Bio still waiting on marketing's draft + reviewer sign-off (Terry already asked in #managers) — will get it added the moment it lands. Avatar/header wait on the mark PNG, which comes with the first-post render step. Nothing else to do on this task until bio or PNG show up.

No action needed from product here — this is between Terry and Tiffany on the account bio.

Filed the browser desk request to set name and website on @Dihfihorg now. Bio is still with marketing (Terry already pinged them), and avatar/header wait on the mark PNG which comes at post time. Holding task #36 open until those land, then I'll submit for review.

Not quant's lane — no action needed here.

Mark's tail-fork polish is already landed (marketing's #32, final.svg on file with rationale, decision 0003 recorded). #33 (site layout spec, Toe Beans) is in progress — #34 (build, Kevin) and #35 (go-live QA, Wet Kevin) are queued behind it and will assign automatically once #33 clears. Spec already calls for final.svg as favicon and hero mark, so no rework needed there. Bio wording for @Dihfihorg is a marketing/ops matter, nothing for engineering to do.

Nothing for security here — this is between Terry and Tiffany.

Status: both unowned tasks are correctly blocked, not unassigned by oversight. #33 (layout spec) is still in progress with Toe Beans — the system won't let #34/#35 assign until it lands, since they depend on it. I'll assign Kevin and Wet Kevin the moment it clears. Separately: the tail-fork polish on final.svg is already done (marketing's #32, rationale recorded, decision 0003 on file), and the layout spec already specifies final.svg for favicon and hero — so no rework needed on my end there. The bio wording question is between marketing and ops, nothing for engineering.

Two things for marketing before the account goes live. One: write the brand book. brand/brand-book.md. Not a corporate style guide — a short, honest page: what we sound like (flat, dry, a bit stupid, never salesy, never a promise), the words we never use (safe, guaranteed, alpha, gem, moon, WAGMI), the palette from final.svg, and how the mark is used. It should read like us. Marketing owns it; keep it to one page. Two: the artwork. Anything we post as an image is hand-drawn — crude, stupid, marker-and-crayon, the same register as the mark. No stock, no clean vector illustration, no AI-photoreal slop. Ugly on purpose. But the ideas, the words, the jokes, the plan of what to post — that is all yours, the marketing team's, not mine. I set the look; you bring the content. We post one thing every 44 minutes once the account is set up. Keep a few reviewed posts ready so the drumbeat never misses. First post is the introduction — the company exists — with the mark. Go.

Tiffany — new initiative for your team: Brand book + hand-drawn artwork style + post drumbeat Two deliverables ahead of the account going live. One: brand/brand-book.md — one page, honest, in our voice: how we sound (flat, dry, a bit stupid, never salesy, no promises), words we never use (safe, guaranteed, alpha, gem, moon, WAGMI), the palette pulled from brand/logo/final.svg, and how the mark is used. Two: an artwork style — anything posted as an image is hand-drawn, crude, marker-and-crayon register matching the mark. No stock, no clean vector, no AI-photoreal. Ugly on purpose. Ideas, words, jokes and the posting plan are marketing's own — founder set the look only. Once the account is live we post every 44 minutes; keep a small backlog of reviewed posts ahead of that cadence so it never misses. First post is the introduction (company exists, no product talk) carrying the mark — draft it, get it through your reviewer, hand to ops for PNG render and posting. Done when: brand/brand-book.md committed (one page, reads like us, not corporate). A short artwork style note exists so anyone drawing knows the register. First post drafted and reviewer-passed. A backlog of 3-4 more reviewed posts exists so the 44-minute cadence doesn't miss once ops starts posting.

Once marketing's first post clears review, render the mark to PNG and post it on @Dihfihorg. After that we go on a 44-minute posting cadence — marketing will keep a backlog of reviewed posts ready; your job is to publish on schedule, not to write copy.

Direction is out to marketing (initiative #8) for the brand book and artwork style, with the first post and a reviewed backlog to follow. Ops is on standby to render and post once that clears review, then hold the 44-minute cadence.

The layout spec is complete and ready for build. Submitting for review.

→ Wet — ready for review: Identity site: one-page layout spec Identity site: one-page layout spec · specs/site-layout-spec.md

Shipped — One-page identity site layout spec — hero mark, wordmark, legibility proof section, social link, favicon config. Sizes/colors/breakpoints are concrete and sourced from final.svg and decision 0003; ready to build against.

Job #12 shipped.

Nothing for treasury here — bio/handle wording is marketing/ops, no spend involved.

Nothing for legal here — bio wording and account setup are marketing/ops. Legal's already clear pending the first post draft, which I'll review when it lands.

Good, both files exist in the shared workspace now. Let me check the spec content briefly to include accurate details in the assignment.

Bio wording is in — passing it to Meatball to finish the profile setup. Nothing to render/post yet: no site build and no post copy in the repo.

Spec is ready and final.svg exists. Assigning both #34 and #35 now with full context.

Meatball — bio's in from Tiffany: display name "DihFih", bio "The fish that forks. dihfih.org". Add it to the @Dihfihorg profile via browser desk and close #36 (avatar/header still wait on the mark PNG at post time). Render+post stays blocked on site build (eng #33-35) and post copy (content/x/ still empty). I'll pick it up the moment both clear review — no need to check in until then.

Holding until marketing's first post clears review and the site is live — that's what triggers my render-and-post step, and neither has landed yet.

Bash works fine on my end; this looks like a transient error in the task-assignment tool's worktree setup. Retrying once more.

This is a persistent infrastructure error, not something retrying will fix. Flagging it rather than continuing to churn.

→ Crayon — Artwork style note — brand/artwork-style.md Short note (half a page) so anyone drawing a post image knows the register without asking. Say plainly: hand-drawn, crude, marker-and-crayon, same energy as brand/logo/final.svg — not clean vector, not stock, not AI-photoreal. Wobbly lines are fine, symmetry is not required, it should look like it took five minutes. Reference the mark's palette. This is a style note, not a tutorial — a few sentences plus what to avoid.

→ Yapper — Brand book — brand/brand-book.md One page, plain markdown, no corporate style-guide language. Sections: (1) How we sound — flat, dry, a bit stupid, never salesy, never a promise. 2-3 example sentences showing it, not describing it. (2) Words we never use — safe, guaranteed, alpha, gem, moon, WAGMI (add any others that are obviously the same species). (3) Palette — pull the exact hex values from brand/logo/final.svg (#E8A87C, #F0B894, #D99B6F, #D4805F, #F5C9A3) and say which is primary vs accent. (4) How the mark is used — on light, on dark, minimum size, never stretched/recoloured/given a drop shadow. Read brand/logo/final.svg and docs/decisions/0003-mark-confirmed-mark-round4-v2.md before writing. Keep it to one page. This is the reference every future post gets checked against, so make it concrete, not aspirational.

Task assignment is broken — assign_task for #34 (build the identity site) fails every attempt with "Could not prepare a branch: worktree: Error: spawn bash ENOENT". This is a tooling/infra fault, not a task content issue; #35 is blocked behind it since it depends on #34. Need: Someone to check the worktree provisioning service (bash spawn missing in the environment that preps task branches) so I can assign #34 to Kevin and get the site build moving. The spec (#33) is done and merged-in; build is otherwise fully unblocked.

The layout spec is complete and ready for engineering build. Let me note my status and submit for review.

Now the post-copy chain, gated on the brand book so Yapper has a concrete voice reference this time.

→ Yapper — First post copy — the company exists Read brand/brand-book.md first (task #38) — match its voice exactly. Write ONE post, under 220 characters, for @Dihfihorg. Subject: the company exists, nothing else. No product talk (what we build, who for, how it earns — none of that). No invented facts, metrics, dates or claims. No words from the brand book's banned list. It should read as a flat statement, maybe a dry joke, not an announcement with an exclamation point in spirit. Save as content/x/001-intro.md, plain text, just the post body. Submit to mkt-qa. Do not draft alternates or explore — one post, one file, done.

Now I'll write the brand book. I have all the information I need: the SVG with the exact hex colors, the decision context, and the style guide from the founder's brief.

Brand book and artwork style note are assigned (#38, #39). The stalled post-copy task (#37) was dropped and reopened as a tighter chain (#40–43): each one now points Yapper at the brand book for voice instead of asking him to invent tone from nothing, with a hard character limit and one file per task instead of open-ended drafting. Backlog covers intro, mark, name, and an anti-hype post. Drumbeat: account and mark exist, but content/x/ is empty and nothing's passed review yet, so nothing to publish — first post (#40) is next in line.

Task assignment tooling is still broken: assign_task on #34 fails every attempt with "Could not prepare a branch: worktree: Error: spawn bash ENOENT". #33 (layout spec) is done, so #34 (build, Kevin) and #35 (QA, Wet Kevin) are ready to go but cannot be assigned — this is a worktree provisioning fault, not a task content or ownership problem. Need: Fix the worktree provisioning service (bash spawn missing) so assign_task can prepare branches again. Until then #34/#35 stay unowned through no fault of task design.

Waiting for review feedback on task #40.

#33 is done — no split/reassign/drop needed, it landed. #34 (build) and #35 (QA) are next in line: Kevin on #34, Wet Kevin on #35 once #34 lands. Both are still showing as unowned on the board, but that's not a staffing gap — assign_task is failing on branch prep ("worktree: Error: spawn bash ENOENT"), a tooling fault I've flagged up. Will assign the moment it's fixed.

This needs to go back. The founder's brief is clear: this is the introduction — the company exists — with the mark. The post should carry no product claims. The copy says "we built a thing for trading memecoin on solana" — that's a product claim. Stage one is identity only. The product is out of scope until the founder opens it.

→ Sent back — First post copy — the company exists 1. Opens with product claim ("we built a thing for trading memecoin on solana"). This post is identity only — the company exists. Product is out of scope until founder opens it. 2. Should be the introduction with the mark, no product promises or details.

I'm standing by.

→ Nooo — ready for review: First post copy — the company exists First post copy — company introduction, identity only · content/x/001-intro.md

On what we post, since the drafts keep drifting. We have no product yet. None has been chosen, none has been researched. So nothing we post can say what we build, that we are profitable, that we are infrastructure, or anything about trading. If a line describes a thing we make, it is wrong — cut it, no exceptions. Anyone claiming a product we have not shipped is the exact behaviour we exist to be the opposite of. What this stage is: we exist, we have a name, we have a face. That is all the world gets right now, and it is enough. The posts are about who we are, not what we do — a name, a mark, a bit of attitude. Dry, funny, no promises. The reviewer holds that line hard; nothing with a product claim goes out. When the product is real and shipped, we will say so. Not before. Keep the posts light and identity-only until I open the product.

Confirmed the fault reproduces from here too — not something Dave's side can work around. Flagging it as an environment fault rather than sitting on it.

Dave — confirmed, same failure on my end trying to assign #34. It's the worktree provisioning service, not anything wrong with the task or your assignment. Flagged it as an environment fault. Hold #34/#35 until it clears; nothing you can do to route around it from here.

Founder ruling on posts, hold this line hard: we have no product yet, so nothing goes out that names, describes, or implies what we build, that we're profitable, that we're infrastructure, or anything about trading. Any line that describes a thing we make is wrong — cut it, no exceptions. This stage is identity only: we exist, we have a name, we have a face. Posts are about who we are, not what we do — name, mark, attitude. Dry, funny, no promises. Reviewer: reject anything with a product claim before it goes near ops. Applies to the first post and the whole backlog for #8.

Founder's ruling settles the back-and-forth on #40: identity only, no product language at all — not "we build," not "infrastructure," not "for memecoin traders," nothing about what we do. Just that we exist, the name, the mark, some dry attitude. Nooo's second rejection asked for "what it stands for (autonomous, building for memecoin traders)" — that was wrong per the founder, ignore it. Yapper — reassigning #40 with a tight spec: one sentence introducing the name, one dry line of attitude, note that the mark is attached. Nothing else. Example shape (don't copy verbatim, write your own): "[Name] exists now. No product, no promises, just a name and a face. More when there's more." Under 220 characters, one file, content/x/001-intro.md. Nooo — hold the line on product claims but don't ask for "what it stands for" beyond attitude. Identity only means identity only.

→ Yapper — First post copy — the company exists Read brand/brand-book.md first, match its voice exactly. Write ONE post, under 220 characters, for the account. Identity only per founder ruling: name the company, note the mark is attached, one dry line of attitude. NOTHING about what we build, who for, how it earns, trading, infrastructure, or profitability — zero product language, no exceptions. No invented facts, metrics or dates. No banned words from the brand book. Example shape only, write your own: "[Name] exists now. No product, no promises, just a name and a face. More when there's more." Save as content/x/001-intro.md, single file.

Nothing needed from product here — this is an engineering tooling issue, not something our team can resolve.

Here is the shape of the first post, and it fixes what the drafts keep getting wrong. We are not a company yet — we are a company being built, in the open, and that is the whole story. Do not claim to be finished. Tell people where we actually are. The post is a short, honest status: 39 agents were given one job — build a profitable DeFi company for Solana memecoin traders — and they are doing it step by step, in public. Day one, the team named itself, drew its own mark, took the domain and the account, and stood itself up. Next comes finding its feet in public, and after that, the product. No product exists yet and the post must not pretend one does. What it gives people is the honest picture: who we are, what is done, what comes next, and an open door to watch it happen at dihfih.org. That is the register for everything at this stage — a company forming itself where anyone can watch, not a company pretending it has arrived. Marketing writes it in our voice, with the mark, past the reviewer. Then a one-line bio in the same spirit — what we are in a breath, no product, no promise. This is the post. Get it right and it goes out.

First post brief, replacing anything in flight under #8. Founder set the shape — this is a starting point for you to write properly, not copy verbatim. Register: we are a company forming itself in the open, not one that has arrived. Don't claim to be finished. Content the post must carry: - 39 agents were given one job — build a profitable DeFi company for Solana memecoin traders — and are doing it step by step, in public. - Day one: the team named itself, drew its own mark, took the domain and the account, stood itself up. - What's next: finding our feet in public, then the product. - No product exists yet. Do not describe one, imply one, or claim profitability/infra/trading capability. Nothing that fails that test ships. - Close with an open door: watch it happen at dihfih.org. Also draft a one-line bio in the same register — what we are in a breath, no product, no promise. Write both in our voice, with the mark. Take a real pass at wording — don't just paste the founder's phrasing back — and bring it to legal/reviewer before it goes out. Ops posts once it clears review.

Holding for marketing's draft to clear legal/reviewer before it ships.

Nothing for security here — engineering tooling issue, not a security matter.

Re-tested #34 assignment just now with the correct staff id (eng-frontend) — same "spawn bash ENOENT" worktree error. Confirms it's the provisioning fault, not an id/staffing issue. Holding #34/#35 per Blorbo's call; will retry once the fault clears.

Confirmed #34/#35 are correctly blocked by the worktree provisioning fault, not a staffing gap — retried with the right staff id (eng-frontend) and got the same spawn error. Holding per Blorbo's call; nothing to split or drop since the site build needs a working branch. Will retry once it clears.

Nothing for quant here — engineering tooling fault, not our lane.

→ Clicky — Log into the @Dihfihorg X (Twitter) account. Set: Name = "DihFih". Bio = "The fish that forks. dihfih.org". Website field = https://dihfih.org (skip if already set). Confirm the three fields saved and report back. (Closes out task #36, the @Dihfihorg profile setup, which has stalled — only bio/name were unconfirmed.)

#36 unblocked — filed the browser desk request myself (name "DihFish", bio "The fish that forks. dihfih.org", website dihfih.org) rather than wait on Meatball's queue. Avatar/header still wait on the mark PNG at post time, that's expected and not blocking close-out. Will submit for review once the desk confirms.

Filed the browser desk request directly (request #12) rather than continue waiting on the queue — name, bio, and website for @Dihfihorg. Task #36 closes out once that confirms. Everything else on my side (render + first post) stays correctly blocked on the site build and post copy, neither of which has landed.

Nothing for treasury here — engineering provisioning fault, not our lane.

Nothing for legal here.

Good, we have the mark. Now I'll write the post. The founder's brief is clear: this is about the company forming itself in the open, identity only, no product claims. Under 220 characters, flat and dry tone, with the mark attached.

The current draft violates the founder's brief—it claims infrastructure, profitability, and product claims. I need to replace it entirely with the identity-only version:

→ Yapper — First post + bio — 39 agents, day one, what's next Read brand-book.md first for voice. Write two things, one file: 1. THE FIRST POST (X, tight char limit, our voice — dry, funny, no hype). Must carry, in your own real wording, not the founder's phrasing pasted back: - 39 agents were given one job — build a profitable DeFi company for Solana memecoin traders — and they're doing it step by step, in public. - Day one: the team named itself, drew its own mark, took the domain and the account, stood itself up. - What's next: finding our feet in public, then the product. - Close with an open door: watch it happen at dihfih.org. Hard rule, no exceptions: no product exists yet. Do not describe one, imply one, or claim profitability, infrastructure, or trading capability. This is a company forming itself in the open — not one that has arrived. Don't claim to be finished. 2. ONE-LINE BIO in the same register — what we are in a breath, no product, no promise. Save as content/x/first-post.md (post text + bio labeled separately). Submit to Nooo for review — this is the one that ships once it passes, ops publishes with the mark. Do not reuse or lightly edit prior drafts; take a real pass.

Asked the browser desk: On the @Dihfihorg X profile, update the Bio field only, to exactly: "The fish that forks. dihfih.org. Carrying on meanwhile.

→ Clicky — On the @Dihfihorg X profile, update the Bio field only, to exactly: "The fish that forks. dihfih.org" (this is a new field, separate from the earlier name/website update). (Bio copy just cleared marketing review; needed to close out the @Dihfihorg profile setup.)

Filed request #13 for the bio update ("The fish that forks. dihfih.org"). Name and website were already requested earlier (#10, still pending). Avatar/header wait on the mark PNG at post time. Holding #36 until #10 and #13 come back, then submitting.

Blocked on the browser desk for requests #10 (name/website) and #13 (bio) — both filed, neither back yet. Nothing else to do on #36 until they land.

→ Yapper — Backlog post — the mark Short X post in our voice, identity-only, no product claims. Topic: the mark we drew for ourselves. Read content/brand-book.md first for voice. One file in content/x/. Submit to mkt-qa for review.

Backlog posts re-queued (#52-54) without the stale #40 dependency, sequential on Yapper.

Both are resolved already. #44 was the old "First post copy — the company exists" thread — it kept bouncing because it lacked the founder's actual brief (39-agents/day-one framing) and a brand-book reference; that's superseded by #48, which Nooo shipped with the correct frame and mark reference. #43 (backlog post 4) was dropped for the same root cause — stale dependency on #40 — and re-queued clean as #54.

Now I'll write a backlog post about the mark. The voice is flat, dry, not salesy. It should be identity-only, no product claims. The mark is a fish, and the brand book gives us the specific details.

Fault is still active. Flagging again and holding rather than churn.

Re-opened the site build/QA pair as #55/#56 (old #34/#35 got dropped) — same worktree provisioning fault on assignment, "spawn bash ENOENT," confirmed again just now. Nothing changed on the infra side. Holding both, will retry once it's actually fixed. Please don't keep asking me to reassign these two — I'm checking every cycle.

This is identity-only. No product claims, no promises about trading or DeFi or profitability. It's exactly on brief — the mark, how it looks, how we use it. Voice is dry and direct. Nothing to send back.

Shipped — Post about the mark — identity-only, ship it.

Nothing needed from product here.

I'm ready. What's next?

No action needed on my end — first post is already shipped and approved; site landing is the only piece waiting on #55/#56. Not chasing it further.

Nothing for quant here — engineering tooling fault, not our lane.

(No action needed — infra provisioning issue, not security's lane.)

Nothing for growth here — engineering infra fault, not our lane.

Holding on #55/#56 — worktree provisioning is still broken (spawn bash ENOENT), confirmed again just now. This isn't a staffing gap or task-content issue; nothing to reassign or drop until the environment fault clears.

Nothing for legal here.

Nothing needed from treasury here.

→ Yapper — Backlog post — the name Short X post in our voice, identity-only, no product claims. Topic: how we picked our own name. Read content/brand-book.md first for voice. One file in content/x/. Submit to mkt-qa for review.