Living styleguide

Seminar components

13 sections, 26 primitives, 73 tokens and every learner state render from the source buyers receive.

Foundations

Tokens

--background
--card
--field
--selection
--primary
--secondary
--muted
--accent
--positive
--warning
--critical
--info

Type scale at actual size

--text-caption

UTC · v2 · reviewed

--text-caption + --tracking-label

Course progress

--text-small

One concrete next move

--text-body

Trace the handoff and name its owner.

--text-lead

Build evidence a team can review.

--text-d1

Recovery trace

--text-d2

Make progress visible

--text-d3

Continue your work

--text-d4

Practice the real thing

Radius and border language

12px outer
8px inner
Square milestone

site-header

src/components/site-header.tsx

hero

src/components/hero.tsx

Live cohort

Practice the real thing

Build one service case through 12 studios, 5 critiques, and a final review you can show.

Cancel before the first studio for a full refund.

Hands arranging a blank service journey with wooden tokens on a sage studio table

Service systems in practice

Week 3 of 6

On track
  • 02Reviewed

    studio step

    Trace the handoff

    Seven-step actor map

    • 03In studio

      evidence check

      Is the failure evidenced?

      Five-step recovery trace

      Next handoff

      Submit your five-step recovery trace by Thursday, 22 Oct at 18:00 UTC.

learning-trail

src/components/learning-trail.tsx

Your route

Make progress visible

Every studio ends with an artifact, a critique, and one named next move.

One decision shown

  • 02Reviewed

    studio step

    Trace the handoff

    Seven-step actor map

    • 03In studio

      evidence check

      Is the failure evidenced?

      Five-step recovery trace

      • critique ready

        • CRThursday at 18:00 UTC

          mentor handoff

          Mara Bell reviews the trace

          Named next move

      • revise evidence

        • REReturn

          studio step

          Repair the evidence

          Trace ready to retest

          Loop to evidence check: retest after the missing evidence is repaired

Read the route as text
  1. Trace the handoff

    studio step · after frame

    Seven-step actor map

  2. Is the failure evidenced?

    evidence check · after Trace the handoff

    Five-step recovery trace

  3. Mara Bell reviews the trace

    mentor handoff · after Is the failure evidenced? via critique ready

    Named next move

  4. Repair the evidence

    studio step · after Is the failure evidenced? via revise evidence

    Trace ready to retest

course-shelf

src/components/course-shelf.tsx

Three courses

Choose the work

Each course starts with your case and ends with a review you can reuse.

Blank service map connected with green thread and wooden tokensIntermediate

Service systems in practice

Turn one live service problem into a reviewed case.

6 weeks

Blank research cards and an audio recorder on a sage worktableFoundation

Research that changes decisions

Plan, run, and synthesize a study with a real team.

4 weeks

Empty facilitation circle with blank boards and a speaking tokenAdvanced

Facilitation under pressure

Lead one tense decision without losing the room.

3 weeks

cohort-band

src/components/cohort-band.tsx

October cohort

Know the commitment

Cohort opens
7 October
Studios
Tue + Thu
Cohort
24 learners
Refund
Before studio 1

mentor-notes

src/components/mentor-notes.tsx

Critique

Feedback stays attached

Mentors respond to the artifact, name the gap, and leave one next move.

“Name the person who owns recovery step four. The map becomes useful when the handoff is explicit.”
Mara BellService designerRecovery trace 03
“Keep the failed call in the sequence. It explains why the customer repeats their story.”
Noah OkoroResearch leadActor map 02

course-index

src/components/course-index.tsx

Course library

Choose your studio

Every studio is artifact-led: start with a real case, then leave with reviewed work and a clear next practice.

4 studios listed.

Blank service map connected with green thread and wooden tokens
Intermediate6 weeks

Service systems in practice

Turn one live service problem into a reviewed case.

Blank research cards and an audio recorder on a sage worktable
Foundation4 weeks

Research that changes decisions

Run one study and make its decision path visible.

Empty facilitation circle with blank boards and a speaking token
Advanced3 weeks

Facilitation under pressure

Lead a contested decision and document the agreement.

Folded working paper with a token-based service route
Foundation3 weeks

Writing useful service standards

Turn policy language into instructions teams can test.

Need a team format? Every studio can run privately for 8–16 people with the same critique rhythm.

course-overview

src/components/course-overview.tsx

6 weeks studio

Intermediate

Service systems in practice

Map one live service, test its weakest handoff, and present a case your team can act on.

$480 once. Cancel before the first studio for a full refund.

lesson-shell

src/components/lesson-shell.tsx

Studio lesson

In progress

Test the failure

Follow one failed handoff, then write the recovery path a team can rehearse.

Hands building a service journey with blank paper and wooden tokens
Video lesson42 min

Mara traces a missed library return from the first call to the final apology.

The recording is not part of this template.

Exercise

Build the recovery trace

Critique opens Thursday at 18:00 UTC.

Exercise

2 of 3 checked

learner-studio

src/components/learner-studio.tsx

Studio states

Current

Sample cohort snapshot

Wed 21 Oct 2026, 16:40 UTC

Learner studio

Continue your work

Priya Nair · October cohort · Tuesday + Thursday

On track

Course progress

Service systems in practice

Week 3 of 6

03

Current lesson

Milestones

2 of 5 reviewed

Lesson 03 holds the current artifact and its critique handoff.

  • 02Reviewed

    studio step

    Trace the handoff

    Seven-step actor map

    • 03In studio

      evidence check

      Is the failure evidenced?

      Five-step recovery trace

      • critique ready

        • CRThursday at 18:00 UTC

          mentor handoff

          Mara Bell reviews the trace

          Named next move

      • revise evidence

        • REReturn

          studio step

          Repair the evidence

          Trace ready to retest

          Loop to evidence check: retest after the missing evidence is repaired

Next action

Finish version 2

Complete the customer response, then submit five-step recovery trace by Thursday, 22 Oct at 18:00 UTC.

Submission queue

Five-step recovery trace

Due Thursday, 22 Oct at 18:00 UTC

Draft

Private draft version 2

priya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdf

2.8 MB · PDF · local preview

PDF or PNG up to 12 MB. Selection stays until this preview reloads.

Submission check

Critique thread

Version 1 feedback

2 messages

Mara Bell

Mentor · submitted v1

Name who owns recovery step four. The handoff becomes testable when one person holds the next move.

Leila Santos

Peer · submitted v1

Unread

Keep the failed call in the sequence. It shows why the customer repeats the same story.

This reply stays until this preview reloads. Connect delivery and persistence in your backend.

Feedback remains open until you mark it addressed.

Frontend fixture: connect auth, storage, messaging, and calendar sync in your backend.

Waiting

Next action

Wait for Mara's review

Version 2 is queued for the Thursday at 18:00 UTC handoff.

Feedback pending

Submission queue

Five-step recovery trace

Due Thursday, 22 Oct at 18:00 UTC

Submitted

Submitted version 2

priya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdf

2.8 MB · PDF · local preview

This local state models the handoff. Connect storage and review delivery in your backend.

Submission check

Late

Late-state sample snapshot

Thu 22 Oct 2026, 18:20 UTC

Course progress

Service systems in practice

Week 3 of 6

03

Current lesson

Milestones

2 of 5 reviewed

Due Thursday, 22 Oct at 18:00 UTC. The artifact is still a draft.

  • 02Reviewed

    studio step

    Trace the handoff

    Seven-step actor map

    • 03Late

      evidence check

      Is the failure evidenced?

      Five-step recovery trace

      • critique ready

        • CRThursday at 18:00 UTC

          mentor handoff

          Mara Bell reviews the trace

          Named next move

      • revise evidence

        • REReturn

          studio step

          Repair the evidence

          Trace ready to retest

          Loop to evidence check: retest after the missing evidence is repaired

Cohort calendar

Cohort moments

UTC

Test the failure

Studio

Tue 20 Oct, 16:00–17:30 UTC

Recovery trace due

Deadline

Thu 22 Oct, 18:00 UTC

Mara's critique room

Now

Thu 22 Oct, 18:00–18:45 UTC

Peer practice room

Conflict

Thu 22 Oct, 18:15–19:00 UTC

Overlaps Mara's critique room from 18:15–18:45 UTC.

The deadline hands directly into Mara's critique room. Connect calendar sync in your backend.

Artifact history

Recovery trace

Version 1priya-nair_library-return-recovery-trace_v1.pdfChanges requestedPDF2.4 MB20 Oct, 14:12 UTCOlder than 48 hoursSubmitted evidence
Version 2Currentpriya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdfDraftPDF2.8 MB21 Oct, 16:32 UTCCurrent snapshotPrivate draft

Complete

Course progress

Service systems in practice

Week 3 of 6

05

Course complete

Milestones

All 5 reviewed

All five milestones are reviewed.

  • 02Reviewed

    studio step

    Trace the handoff

    Seven-step actor map

    • 03Reviewed

      evidence check

      Is the failure evidenced?

      Five-step recovery trace

      • critique ready

        • CRReviewed

          mentor handoff

          Mara Bell reviews the trace

          Named next move

      • revise evidence

        • RENot used

          studio step

          Repair the evidence

          Trace ready to retest

          Loop to evidence check: retest after the missing evidence is repaired

Next action

Review the course trail

Your artifact is accepted. Revisit the course trail or sample lesson from this frontend fixture.

Submission queue

Five-step recovery trace

Due Thursday, 22 Oct at 18:00 UTC

Accepted

Accepted version 2

priya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdf

2.8 MB · PDF · local preview

Version 2 is accepted in this local specimen. Review the lesson or course trail.

Submission check

No enrollment

Open public navigation

Public sample

Learner studio

Choose a course first

This sample has no enrollment, so progress, submissions, and critique stay hidden.

Browse courses

Mentor view

Submission queue

Five-step recovery trace

Due Thursday, 22 Oct at 18:00 UTC

Changes requested

Submitted version 1

priya-nair_library-return-recovery-trace_v1.pdf

2.4 MB · PDF · submitted evidence

Mentors can review submitted versions. They cannot attach or submit as the learner.

Submission check

Critique thread

Version 1 feedback

2 messages

Mara Bell

Mentor · submitted v1

Name who owns recovery step four. The handoff becomes testable when one person holds the next move.

Leila Santos

Peer · submitted v1

Unread

Keep the failed call in the sequence. It shows why the customer repeats the same story.

This mentor specimen can read submitted evidence and add buyer-connected review tools. Learner reply controls stay hidden.

Empty queue

Submission queue

Your artifacts

No draft or returned artifact is waiting here.

Open the lesson

Critique thread

No feedback yet

0 messages

Feedback appears after a version enters the critique handoff.

Missing version

Artifact history

Recovery trace

Version 1priya-nair_library-return-recovery-trace_v1.pdfChanges requestedPDF2.4 MB20 Oct, 14:12 UTCFile unavailableSubmitted evidence
Version 2Currentpriya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdfDraftPDF2.8 MB21 Oct, 16:32 UTCCurrent snapshotPrivate draft
The unavailable version keeps its record and has no action. No file transfer is simulated here.

Attachment error

Submission queue

Five-step recovery trace

Due Thursday, 22 Oct at 18:00 UTC

Draft

Private draft version 2

priya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdf

2.8 MB · PDF · local preview

PDF or PNG up to 12 MB. Selection stays until this preview reloads.

Submission check

Submitted success

Next action

Wait for Mara's review

Version 2 is queued for the Thursday at 18:00 UTC handoff.

Feedback pending

Submission queue

Five-step recovery trace

Due Thursday, 22 Oct at 18:00 UTC

Submitted

Submitted version 2

priya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdf

2.8 MB · PDF · local preview

This local state models the handoff. Connect storage and review delivery in your backend.

Submission check

priya-nair_library-return-recovery-trace_revised-owner-and-response_v2.pdf submitted locally for Thursday at 18:00 UTC.

Layout variants

mentor-roster

src/components/mentor-roster.tsx

Working critics

Meet your critics

Each mentor reviews a different kind of decision, leaves one concrete next move, and replies within 48 hours.

Blank service-recovery map, ruler, wooden tokens and orange marker
Artifact critique

Mara Bell

Service recovery

Finds the owner missing from the handoff.

Thu 18:00 UTC

Audio recorder and three groups of blank research cards
Study review

Noah Okoro

Applied research

Tests whether evidence changes a decision.

Wed 16:00 UTC

Blank facilitation cards arranged around a wooden speaking piece
Session replay

June Park

Group facilitation

Names the moment agreement became unclear.

Fri 15:00 UTC

cta

src/components/cta.tsx

October cohort

Bring one real problem

Start with a live service case and leave with a reviewed story your team can use.

  • $480 once
  • 12 live studios
  • Full refund before studio 1

site-footer

src/components/site-footer.tsx

Fieldnote

Cohort studios for people who learn by making, showing, and revising real work.

Frontend scope

Connect your own auth, course data, payments, and video host.

© 2026 Fieldnote Studio

Instrument Sans · Karla · Spline Sans Mono

ui/dashboard-layout

src/components/ui/dashboard-layout.tsx

mode=sidebar

Menu

Week 3 · Test the failure

The work surface stays fluid; this primitive decides which navigation plane is showing and nothing else.

mode=rail

Menu

Week 3 · Test the failure

The work surface stays fluid; this primitive decides which navigation plane is showing and nothing else.

mode=topbar

Menu

Week 3 · Test the failure

The work surface stays fluid; this primitive decides which navigation plane is showing and nothing else.

ui/wire-figure

src/components/ui/wire-figure.tsx

The learning trail

  • 01Reviewed

    starting work

    Frame the service

    One-page service claim

    Choose one live service and write the claim the team needs to test.

    • 02Reviewed

      studio step

      Trace the handoff

      Seven-step actor map

      Map the seven moments where responsibility changes hands.

      • 03In studio

        evidence check

        Is the failure evidenced?

        Five-step recovery trace

        The trace must name the failed handoff, its owner, and the customer-facing response.

        • critique ready

          • CRThursday at 18:00 UTC

            mentor handoff

            Mara Bell reviews the trace

            Named next move

            A mentor checks that every recovery step has one owner and one observable result.

            • 04Next

              studio step

              Prototype the fix

              Working service script

              Turn the reviewed recovery path into a service script the team can rehearse.

              • 05Locked

                course outcome

                Present the case

                Recorded case review

                Show the evidence, the changed handoff, and the result in one ten-minute review.

        • revise evidence

          • REReturn

            studio step

            Repair the evidence

            Trace ready to retest

            Name the missing owner or replace the unsupported step before critique.

            Loop to evidence check: retest after the missing evidence is repaired

A learner frames a service, traces its handoffs, and tests one failure. Critique-ready work moves to a mentor; missing evidence loops back through repair before the test runs again.
Read the route as text
  1. Frame the service

    starting work · starts the trail

    One-page service claim

  2. Trace the handoff

    studio step · after Frame the service

    Seven-step actor map

  3. Is the failure evidenced?

    evidence check · after Trace the handoff

    Five-step recovery trace

  4. Mara Bell reviews the trace

    mentor handoff · after Is the failure evidenced? via critique ready

    Named next move

  5. Prototype the fix

    studio step · after Mara Bell reviews the trace

    Working service script

  6. Present the case

    course outcome · after Prototype the fix

    Recorded case review

  7. Repair the evidence

    studio step · after Is the failure evidenced? via revise evidence

    Trace ready to retest

ui/progress

src/components/ui/progress.tsx

nothing reviewed yet, because the cohort has not started

Milestones

0 of 5 reviewed

mid-course: two reviewed, and the one you are standing in

Milestones

2 of 5 reviewed

every milestone reviewed

Milestones

All 5 reviewed

size=sm, the rail that rides beside a lesson checklist

Exercise

2 of 3 checked

live. The only count on this page you can move yourself

Evidence

1 of 3 checked

ui/avatar

src/components/ui/avatar.tsx

secondary, size=sm — the critique thread, where a primary fill would outrank the message

Priya Raghunathan

Mentor · submitted v1

primary, size=md. The roster's meta row on --card, where it can afford the deepest ink

Tomas Berg

Service recovery

Primitives

buttons

fields

The resting control, with its instruction.

Choose a PDF or PNG.

Read-only: version 1 is with the mentor, and still has to be read.

Disabled: no attachment while the version is in review.

submitting

Inert until the reply lands.

compound states

Selected + focused

Selection remains inside the focus outline.

Feedback pending
Mentor view is read-only

status roles

Accepted
Schedule risk
Needs attention
Local only

badges

IntermediateReviewedCritique Thu
DraftWith your mentorChanges requestedAccepted

brand and mode

Section label

Make progress visible

Every section says what the learner gets and how the work proves it.

ui/accordion-disclosure

src/components/ui/accordion-disclosure.tsx

the syllabus row, closed

Week 3 · Test the failure4 tasks
Map one service you use weekly, then find the step where it breaks for someone who is not you.

open, and Escape closes it

Week 4 · Bring it to critique2 tasks
One artifact and one paragraph. The paragraph is what your mentor argues with.

live: the FAQ, keyboard-operable

What do I hand in each week?Week 3
One artifact and one paragraph saying what you tested. The paragraph is what the mentor argues with.
Can I resubmit after a critique?Any week
Yes, until the cohort closes. Every version stays readable, so the critique keeps its context.

ui/dialog

src/components/ui/dialog.tsx

the panel, with no layer around it

the real layer. Escape, focus trap, focus return

ui/confirm-dialog

src/components/ui/confirm-dialog.tsx

the alertdialog panel, gate unsatisfied

Withdraw from Service systems?

October cohort · Seat 12 of 18

Your seat is released to the waiting list and the three submissions you have made stop being critiqued.

Cancel takes focus, and the gate unlocks Withdraw

ui/dropdown-menu

src/components/ui/dropdown-menu.tsx

the list, including a refusal that says why

the real menu: arrow keys, type-ahead, Escape

ui/tooltip

src/components/ui/tooltip.tsx

the bubble, with no intent gate in front of it

A version a mentor can argue with: one claim, one test, one artifact.

hover after 80ms, or focus instantly

ui/popover

src/components/ui/popover.tsx

the surface, unanchored

anchored, with light dismiss

ui/toast

src/components/ui/toast.tsx

all five tones, each with its own word, not only its ground

DoneVersion 4 submitted to Priya.

Critique returns by Thursday.

In progressUploading the artifact.

CheckThe studio starts in ten minutes.

FailedThat file is larger than 25MB.

Split the artifact or link it instead.

NoteDraft saved locally.

press one and a card stands, then goes

ui/tabs

src/components/ui/tabs.tsx

arrow keys move, selection follows focus

Map one service you use weekly, then test where it fails.

a view that is not available yet, and says which

Available once the studio has run.

ui/date-picker

src/components/ui/date-picker.tsx

a chosen studio date, with today ringed

October 2026

nothing chosen yet

October 2026

the cohort runs 6–23 October; the rest is not offered

October 2026

the trigger carrying the field's verdict

Studio slot

Choose a date inside the cohort.

the real grid. Arrows, Home/End, PageUp/PageDown

Studio slot

ui/skeleton

src/components/ui/skeleton.tsx

no shimmer, and the wait is said in words

Loading the submission history

what arrives when the wait is over

Submission history

Four versions, the oldest from twelve days ago, each still readable beside the critique it drew.

ui/sort-head

src/components/ui/sort-head.tsx

a real head row, one sorted column and one with no comparator

Submissions in the October cohort, sortable by learner, version, week and status
Status
Chen Weiv54Accepted
Amara Okaforv43With mentor
Ben Ridleyv23Changes requested

ui/pagination

src/components/ui/pagination.tsx

page two of six, with the range read aloud

the first page. Previous is out of moves and says so

ui/toggle-group

src/components/ui/toggle-group.tsx

one tab stop, arrow keys, selection follows focus

a topic with nothing in it this cohort

ui/search-input

src/components/ui/search-input.tsx

empty, with no clear control to press

3 of 3 courses

with a word in it, and a clear control

1 of 3 courses

a word nothing matches, said politely

No course matches that word

the catalog is not searchable before a cohort opens

Search opens with the cohort

live: the count follows what you type

3 of 3 courses

  • Service systems in practice
  • Research that changes a decision
  • Writing the failure test