Silver Fern · Work Suite · internal — product + marketing leadership
fernie, alivelaunch kit
the character is approved and the assets exist. this page is the asset inventory, the rollout order, and the product requirements needed to put him in Work Suite.
Status: character study approved · 12 library cards + 2 booth pieces rendered · product work not yet scheduled · Owner: Kevin (COO)

01fernie, alive

live svg — he is blinking right now

What this is, and why now

one character, three jobs: product warmth, launch story, booth draw.

fernie is the face of Work Suite: the approved module squircle in deep soil, a fiddlehead antenna, and two spring-green LED eyes that read like a device display, not a cartoon. He earns his warmth through micro-motion — a blink at rest, a scan while thinking — and he keeps his credibility through restraint: he appears only where he literally speaks (launcher, chat, loading and empty moments), and he goes straight-faced whenever money is on the screen.

The marketing side is done: twelve library cards and two Cultivate booth pieces exist today, most cleared to ship. What does not exist yet is fernie in the product. Announcing a character who is not in the software would be a costume, not a launch — so the sequence below puts the product work first and the requirements brief in section 04 is the ask.

02The asset kit

idwhat it isformatclearance
fern-01Meet fernie — launch announcement1200×627SHIP-READY
fern-02The six states of fernie1600×900SHIP-READY
fern-03Placement rules — where fernie lives1600×1000INTERNAL
fern-04Booth standee — hi, i’m fernie800×2000SHIP-READY
fern-05Sticker sheet no. 11200×900SHIP-READY
fern-06Launch email header1200×400SHIP-READY
fern-07Avatar plate — fernie, cropped1200×900SHIP-READY
fern-08Just ask — launcher frame1600×900SHIP-READY
fern-09Three panels — how a save happens1600×700SHIP-READY
fern-10The straight-face rule1200×900INTERNAL
fern-11Wardrobe plate — little hats only1600×900SHIP-READY
fern-12Fourth of July stamp1080×1080SHIP-READY
sf-portrait-10Ask fernie — booth screen1080×1920SHIP-READY
sf-portrait-13fernie screensaver — booth loop1080×1920SHIP-READY
Renders live in the Creative Artifact Library (cards fern-01 – fern-12, batch dir batches/fern/) and the Cultivate portrait pack (sf-portrait-10-ask-fernie, sf-portrait-13-fernie-screensaver). The booth screensaver loops on a booth TV — a marketing surface. In the product a looping fernie is banned: on a loop it is a screensaver.
Full asset notes — what each piece is for
  • fern-01 — the LinkedIn announcement card: copy left, character on a mint stage right, one quiet “hi.” First public post of launch week; pin it for the duration.
  • fern-02 — lineup poster of all six LED-eye states with the trigger that earns each one. Hang it where product and design sit; attach it to any brief that puts fernie on a screen.
  • fern-03 — internal do/don’t sheet for placement: he appears where a person would greet you, never on grids, money, errors, or anything customer-facing.
  • fern-04 — near-lifesize floor standee for Cultivate ’26, Booth 1907: listening state, one welcome line, one question that starts the demo.
  • fern-05 — die-cut vinyl sticker sheet: six fernie heads with one-word captions plus the “just ask.” pill. Booth handout and onboarding welcome boxes.
  • fern-06 — header banner for the launch email: mint field, wordmark, character rising from the bottom edge mid-blink.
  • fern-07 — production spec for circle avatars at 512, 128, 48 and 24 px with clearance rings and crop rules; at 24 px the mouth and antenna drop.
  • fern-08 — product-theater frame of the launcher chat: fernie surfaces an overnight low-stock, drafts the restock, a person approves the send.
  • fern-09 — three-panel strip of the whole loop: flag the shortfall, approve the restock, the truck leaves full. Site, decks, LinkedIn carousel.
  • fern-10 — internal spec for the neutral state: money on screen → LEDs dim to #5F6F6A, glow and mouth drop, nothing animates.
  • fern-11 — the seasonal dress code: silhouette never changes, each season earns exactly one small hat, the 4th of July cone ships first.
  • fern-12 — square social stamp for the holiday: one-cone party hat, a greeting that respects the morning watering, nothing to sell.
  • sf-portrait-10 / -13 — 1080×1920 booth screens for the Cultivate portrait rotation: an “ask fernie” invitation panel and the idle screensaver loop.

03Go-to-market sequence

Internal reveal everyone learns the rules before anything is public

Product, design, and support meet fernie first. The gate to move on: the placement rules and the straight-face rule are understood by everyone who puts pixels on a screen, and the section 04 requirements are accepted into the backlog.

fern-02 · fern-03 · fern-10 · fern-11

Product beta surfaces fernie exists in Work Suite before we say his name in public

Launcher greeting and chat states ship behind a flag to beta tenants. fern-08 already mirrors the target launcher frame; the avatar plate governs every export. The gate: real growers have seen him and the kill switch works.

fern-07 · fern-08 · requirements 1–5, 7–8

Site silverfern.com introduces the face

The site gets fernie in the same places the product does — launcher-style hero moments and loading states — plus the three-panel save story as a page asset. No fernie on pricing pages; the straight-face rule applies to marketing too.

fern-08 · fern-09

Social “meet fernie” announcement week, in order

fern-01 goes up first and stays pinned. fern-08 is the second post — the character earns his keep by showing a save, not by being cute. fern-09 exports panel-by-panel as a carousel. The launch email carries the fern-06 header and goes out with the first post.

fern-01 · fern-08 · fern-09 · fern-06

Cultivate booth Cultivate ’26, Columbus, Booth 1907

The standee greets at the open corner, sticker sheets go into hands, and the portrait screens rotate the “ask fernie” panel with the screensaver loop. Demo stations show the real launcher greeting — the booth promise and the product must match.

fern-04 · fern-05 · sf-portrait-10 · sf-portrait-13

Seasonal wardrobe cadence starting with the 4th of July

Per leadership direction: little hats and such — small tradeoffs only, the silhouette never changes. Each season earns exactly one small hat; the 4th of July cone is first (fern-12 is the social stamp, fern-11 is the dress code). Hats appear in product only after requirement 6 ships; until then the wardrobe is social-only.

fern-11 · fern-12 · requirement 6

04Product requirements brief

This is the ask. Ten requirements, each with the acceptance criterion that makes it done. The character rules are already settled by the approved study — the work here is enforcement, wiring, and plumbing, not design.

R1

Surface registry + placement-rule enforcement

A central registry of surfaces where fernie may render. Allowed: launcher greeting, chat, loading and empty moments. Banned: data grids and documents (invoices, POs, pick lists), any error involving money, and every customer-facing surface (Portal included). Placement is not per-feature discretion — a component that isn’t registered cannot draw the face.

accepts whenRendering fernie requires a registered surface id; an unregistered surface renders nothing and logs a warning in dev builds; grid, document, and customer-facing surface types cannot be registered at all.
R2

Six-state machine with defined triggers

One component, six states, transitions only through named events. At rest the only motion is the blink, every 4–5 seconds. The done face plays once per completion and returns to rest — it never loops.

rest
listening
thinking
working
done
straight
accepts whenGiven a scripted event stream, the component reproduces the full trigger table below; at rest the blink is the only motion; done never replays without a new completion event.
Trigger table — event to state
stateentering triggermotionexits to
restdefault / any state settlesblink every 4–5 s, nothing elseany
listeningchat input focused or user typingeyes brighten and widen, faster blinkthinking on submit; rest on blur
thinkingrequest submitted; fernie reading dataeyes scan side to side, antenna pulsesworking or done
workinglong-running job or draft generationhalf-lidded eyes, antenna pulses harddone on success; rest + plain-type error otherwise
doneanswer shipped, plan saved, draft acceptedthe grin, oncerest
straightfinancial context flag (R3)none — LEDs dim to neutralprior state when flag clears
R3

Straight-face context flag

A financial-context flag settable at route or component level. When set, LEDs render neutral #5F6F6A, the glow and mouth drop, and all animation stops — it overrides every other state. Covers invoices, pricing, credits, and any failure with money attached.

accepts whenWith the flag set, zero animations run and incoming state events are ignored until the flag clears; a screenshot of any financial screen shows the neutral face or no face at all.
R4

Launcher greeting slot with person-aware copy

One greeting card in the launcher: first name, one number-first observation from the tenant’s own data, one action. The pattern: “Morning, Adam. 4 stores ran low on 1-gal perennials overnight. Want the draft? I already did the math.” Charm rides on competence — the face and the number arrive in the same breath.

accepts whenThe greeting renders name + a real observation + one action button; when no observation is available it falls back to a plain hello with no invented numbers; the observation is traceable to a tenant data query.
R5

Loading-spinner replacement component

Inside fernie surfaces only, the thinking and working states replace the generic spinner — visibly reading, then visibly building. Everywhere else in Work Suite the existing spinner stays. No global swap.

accepts whenChat and launcher loading moments show thinking→working; a grep of non-fernie surfaces shows the standard spinner untouched.
R6

Seasonal accessory layer — the wardrobe slot

A date-ranged wardrobe slot that renders hat overlays only. Per leadership direction: little hats and such, small tradeoffs only, the silhouette never changes. Default-on with a per-tenant kill switch. The 4th of July cone ships first. A hat never renders on the straight face.

accepts whenInside a configured date range the hat appears on every fernie instance except straight-face; the per-tenant switch removes it everywhere; the base character geometry is byte-identical with the wardrobe layer on or off.
Wardrobe config shape
  • overlay — an SVG group anchored above the squircle; it may not touch or clip the squircle, eyes, mouth, or antenna.
  • date range — start and end date; outside the range the slot renders nothing.
  • one at a time — the slot holds at most one accessory; no stacking, no full costumes.
  • approval — each accessory is a reviewed asset (fern-11 is the dress code), not a runtime free-for-all.
R7

Reduced motion + accessibility

Under prefers-reduced-motion the face goes fully static — no blink, no scan, no pulse (the CSS on this very page already does this). The face itself is decorative: greeting and chat text is the real content and reads normally; the character never traps focus or announces its own state changes.

accepts whenWith reduced motion set, an animation audit shows zero running animations on fernie; a screen reader reads the greeting copy and action, and the face is skipped as decorative.
R8

Global kill switch

Tenant-level and user-level setting: turn fernie off. Off means plain Silver Fern surfaces — standard spinner, plain-text greeting — with no feature loss and no layout shift. Some operations will not want a character near their numbers; that has to be one toggle, not a request to support.

accepts whenToggling off removes the character from every registered surface in the same session; all underlying features (greeting content, chat, drafts) keep working; toggling back on requires no reload gymnastics.
R9

Telemetry

If fernie is worth shipping he is worth measuring. Three event families, each carrying surface id and tenant, so we can answer the only question that matters: does the face make people use the help more?

accepts whenAll three event families land in the analytics pipeline with surface + tenant dimensions, and a query can report greeting-to-chat-open conversion per tenant.
Event fields
  • fernie_state_transition — from, to, surface_id, trigger event, financial_flag.
  • fernie_greeting_impression — surface_id, had_observation (bool), action_taken (draft / dismissed / ignored).
  • fernie_chat_open — source (greeting card, launcher face, other entry point), surface_id.
R10

Asset pipeline — one SVG source of truth

One canonical character file — squircle, antenna, six faces, wardrobe anchor — that both the product component and marketing exports build from. The avatar plate (fern-07) defines the crops: 512, 128, 48, 24 px; at 24 px the mouth and antenna drop. Today the geometry lives in the library cards; hand-copying it into the app guarantees drift.

accepts whenA single repo-owned SVG is the build input for the product component, the avatar exports, and marketing renders; changing the geometry once lands everywhere without manual copying.

05Open questions for leadership

  1. Portal. Customer-facing surfaces are banned today, which includes Portal. Confirm that stands permanently, or define what a grower-approved exception would even look like.
  2. The financial-context list. Invoices, pricing, credits are clear. Do dashboard tiles that show revenue count? R3 needs the definitive surface list before it ships.
  3. Wardrobe default. Default-on with a kill switch is the current call. Comfortable shipping hats on by default to enterprise tenants, or should the wardrobe be opt-in above a certain tier?
  4. Source-of-truth ownership. Does the canonical SVG live with design (marketing repo) or product (worksuite-pwa)? R10’s pipeline direction follows from this.
  5. The mark. The character study writes fernie™; the library cards ship without it. Pick one treatment for public assets before the announcement post.