docs(about-page): apply Daniel's copy decisions

Mark A,B,C,E,D-intro,F,G,H approved with verbatim text; redraft D
(no Octave One, live-hardware spirit) pending approval; resolve the
medium-card question; flag two COPY C typos for confirmation.

product-notes/about-page.md

@@ -1,13 +1,15 @@
 # About Page — DeepDrft public site — Design Spec
 
-Status: **proposed** (2026-06-17). Author: product-designer. Date: 2026-06-17.
+Status: **proposed — copy largely settled** (2026-06-17). Author: product-designer. Date: 2026-06-17.
 Implementer: staff-engineer (when approved). Surface: **public site only** (`DeepDrftPublic` /
 `DeepDrftPublic.Client`).
 
-> **All body prose in this spec is DRAFT, fenced as `[COPY — FOR APPROVAL]`. Daniel curates the
+> **Copy status (2026-06-17 review):** A, B, C, E, D-intro, F, G, H are **APPROVED** — Daniel's
-> band's public voice himself.** Section headers, eyebrows, and UI labels are proposed and may be
+> verbatim words, set. **D (Process card bodies) is a fresh DRAFT** pending Daniel's pass (redrafted
-> set; any *sentence or paragraph* of site copy is a placeholder pending Daniel's own words. Do not
+> per his "spice it up, no Octave One" direction). **Khabran's bio is still TODO.** Remaining open
-> ship the drafts as written without his pass.
+> items (Khabran's bio, final photos, image hosting path, hero title wording, "designed not
+> extracted" placement) are being resolved separately. Approved blocks ship as written; the one
+> remaining draft (D) does not ship without Daniel's pass.
 
 Cross-references: `Pages/Home.razor` + `Pages/Home.razor.css` (the visual language this page mirrors
 — inspected, not invented), `Controls/DeepDrftHero.razor` (hero type treatment),
@@ -144,9 +146,9 @@ under its hero. The bw/colour hover-crossfade pair (`Image1` + `Image2`) is the
 supply both a bw and a colour file per slot where available (Home pairs `dd-duo-hero-bw` +
 `dd-duo-hero`).
 
-> `[COPY A — FOR APPROVAL — standfirst]`
+> `[COPY A — APPROVED — standfirst]`
-> *Two people, all the hats. We bring the heart and soul of Midwest deep club house to Charleston —
+> Two people, many hats. We bring the heart and soul of Midwest deep house to Charleston — informed
-> informed by the founders of the style, and pushing it forward.*
+> by the founders of the style, and promising to push it forward.
 
 ---
 
@@ -159,10 +161,10 @@ origin/meeting hook; prose in the right column about how they met (exchanging sy
 they made and enjoyed similar music) and that both members wear every hat — music, sound design,
 arranging, producing, mixing, field recording, visual design, custom sound tools.
 
-> `[COPY B — FOR APPROVAL — People intro]`
+> `[COPY B — APPROVED — People intro]`
-> *We met trading synthesizers and found out we were chasing the same thing. Two of us, no fixed
+> We met trading synthesizers and found out we were seeking the same thing. Two of us, no fixed
 > roles — we both write, arrange, produce, mix, record in the field, build the visuals, and make the
-> tools when the tools don't exist yet.*
+> tools when the tools don't exist yet.
 
 ### 4.1 Member bio pair
 
@@ -186,12 +188,18 @@ Per card:
 > bio degrades gracefully (portrait + name + role line still compose; the body block simply absent) —
 > the same null-renders-nothing discipline `ReleaseDescription` uses.
 
-> `[COPY C — FOR APPROVAL — Daniel bio, drafted from transcript; Khabran's TBD]`
+> `[COPY C — APPROVED — Daniel bio, Daniel's words verbatim; Khabran's TBD]`
-> *Daniel started on drums at ten and found electronic music at seventeen — synthesizers first. A
+> Daniel started on drums at ten and embarked in electronic music at seventeen — synthesizers first.
-> metalhead at heart, he spent ten years as a Detroit artist, shaped most of all by modern
+> A metalhead at from a young age, he spent ten years as an engineer living near Detroit filling the
-> underground Detroit techno. He's also an engineer: custom plugins, hardware recording rigs, the
+> nights with synthesized tones and rhythms, shaped most of all by modern underground Detroit techno.
-> tools behind the tracks. To him the science and the math matter as much as the beauty — tension and
+> Art & engineering cannot be separated: custom plugins, hardware recording & performance rigs, the
-> release, built deliberately.*
+> tools behind the tracks are just as important as the finished sound. To him the science and the
+> math matter as much as the beauty — tension and release, built deliberately.
+
+> **Typo flags (for Daniel's confirmation — text preserved verbatim above, not auto-corrected):**
+> (1) "embarked **in** electronic music" reads as a likely slip for "embarked **on**"; (2) "A
+> metalhead **at from** a young age" reads as a likely slip for "A metalhead **from** a young age."
+> Both left as Daniel wrote them — his to confirm or keep.
 
 ### 4.2 Optional split — the meeting / origin
 
@@ -217,18 +225,23 @@ with a hand-rolled SVG icon in the existing `.feature-icon` slot:
 1. **Sketch** — start on the Akai Force or MPC Live 3.
 2. **Arrange** — into Ableton, or the whole thing in REAPER (heavy REAPER users).
 3. **Studio** — an arsenal of synths and pedals; digital and analog, hard and soft, some custom-made.
-4. **Live Rig** — DAWless live synthesizer rigs, sometimes fully improvised. Built for the warehouse.
+4. **Live Rig** — a big spread of hardware played 100% live, DAWless, sometimes fully improvised.
+   Built for the room / the warehouse.
 
-> `[COPY D — FOR APPROVAL — Process card bodies]`
+> `[COPY D — FOR APPROVAL — Process card bodies — REDRAFT per Daniel's "spice it up, no Octave One" note]`
-> 1. *Sketch — A loop starts on the Force or the MPC. The idea comes first.*
+> 1. *Sketch — A loop starts on the Force or the MPC, hands on the pads. The idea has to survive
-> 2. *Arrange — Sometimes into Ableton, sometimes start-to-finish in REAPER. Whatever gets the take.*
+>    first contact before anything else gets built around it.*
-> 3. *Studio — A wall of synths and pedals, digital and analog, some of it built by hand.*
+> 2. *Arrange — Sometimes into Ableton, sometimes start-to-finish in REAPER. The track gets shaped
-> 4. *Live Rig — DAWless rigs for the room. Sometimes composed, sometimes pure improvisation. Think
+>    wherever it wants to go — we follow the take, not the template.*
->    Octave One — big spread of gear, big tunes, meant for the warehouse.*
+> 3. *Studio — A deep bench of synths, drum machines, and pedals; digital and analog, hard and soft,
+>    some of it built by hand. If the sound we need doesn't exist yet, we make the thing that makes it.*
+> 4. *Live Rig — No laptop, no safety net. A full spread of hardware patched together and played
+>    100% live — sequenced, twisted, and pushed in the moment. Built for the room, the warehouse, the
+>    night that doesn't repeat.*
 
-> `[COPY D-intro — FOR APPROVAL — Process standfirst, optional]`
+> `[COPY D-intro — APPROVED — Process standfirst, optional]`
-> *It doesn't matter how — digital or analog, hard or soft, bought or built — as long as it moves
+> It doesn't matter how — digital or analog, hard or soft, bought or built — as long as it moves
-> the room. The soul in this music is designed, not extracted; assembled, not distilled.*
+> the room. The soul in this music is designed, not extracted; assembled, not distilled.
 
 (The "designed, not extracted / assembled, not distilled / constructed, not grown" line is the
 sharpest statement of the logos register and the soul-is-engineered thesis. Recommend it land here,
@@ -247,44 +260,34 @@ proof-of-effort image). Home's trailing `mixer.jpg` / `mixer-bw.jpg` pair is the
 Two-column `.section`: `.section-label` "The Output" + `.section-title` (e.g. *Classics, with a
 <em>Twist</em>*); prose framing the catalogue as the evidence — what the site is *for*.
 
-> `[COPY E — FOR APPROVAL — Product intro]`
+> `[COPY E — APPROVED — Product intro]`
-> *Everything ends up here, in the catalogue. We play the classics, with a twist — proof that
+> Everything ends up here, in the catalogue. It's proof people in Charleston are pushing the sound
-> someone in Charleston is still pushing the club sound forward.*
+> of the club.
 
-### 6.1 Medium triptych — should CUTS / SESSIONS / MIXES be explained here?
+### 6.1 Medium triptych — CUTS / SESSIONS / MIXES on About — **RESOLVED: yes, cards**
 
-**Open question (§8), recommendation below.** The three mediums already exist app-wide and the Home
+**RESOLVED (2026-06-17, per COPY F approval): use the cards.** The medium triptych reuses Home's
-page already carries a medium triptych (`.medium-grid` / `.medium-card`, the Studio / Live / DJ Mix
+`.medium-grid` / `.medium-card` grid, with a one-line frame of each medium, each linking to `/cuts`,
-cards). Two shapes:
+`/sessions`, `/mixes`. The About page is where a newcomer reading top-to-bottom learns *what a
+"Session" is* vs. a "Mix," and the medium cards are the established device for it. Copy is one line
+per medium (a frame, not a re-pitch) so it reads as *definition*, not a second sales section.
 
-- **(i) Reuse the `.medium-card` grid** with a one-line frame of each medium (CUTS = composed studio
+(Alternative considered and rejected: prose-only mention with no cards. Rejected because it loses the
-  work; SESSIONS = live, unrepeatable; MIXES = uninterrupted DJ sets), each linking to `/cuts`,
+concrete payoff at the end of the Product movement and pushes the taxonomy explanation off the page.)
-  `/sessions`, `/mixes`. **Pro:** ties the About narrative directly to the catalogue; reuses an
-  existing component; gives the Product movement a concrete payoff. **Con:** partial duplication of
-  the Home page's medium section.
-- **(ii) Prose-only mention**, no cards — name the three mediums in a sentence and let the catalogue/
-  nav do the explaining. **Pro:** avoids duplicating the Home triptych. **Con:** the About page is
-  the natural place a newcomer learns *what a "Session" is* vs. a "Mix."
 
-**Recommend (i) with a lighter touch than Home** — the About page is exactly where the taxonomy
+> `[COPY F — APPROVED — medium one-liners]`
-should be explained for someone reading top-to-bottom, and the medium cards are the established
+> - CUTS — studio work, composed and finished.
-device for it. Keep the copy to one line per medium (a frame, not a re-pitch) so it reads as
+> - SESSIONS — live, caught once, never the same twice.
-*definition*, not a second sales section. If Daniel finds it too repetitive next to Home, fall back
+> - MIXES — uninterrupted sets, start to finish.
-to (ii).
-
-> `[COPY F — FOR APPROVAL — medium one-liners, if cards used]`
-> - *CUTS — studio work, composed and finished.*
-> - *SESSIONS — live, caught once, never the same twice.*
-> - *MIXES — uninterrupted sets, start to finish.*
 
 ### 6.2 The live turn — "on the street, in the swamp"
 
 Close the Product movement with a `.section-split` (or a second short band) carrying the live/public
 identity — the part of the collective that isn't a release at all.
 
-> `[COPY G — FOR APPROVAL — live identity]`
+> `[COPY G — APPROVED — live identity]`
-> *But that's just the releases. We're also out there — on the street, in the swamp, with a PA, a
+> But that's just the releases. We're also out there — on the street, in the swamp, with a PA, a
-> generator, and a bunch of good vibes.*
+> generator, and a bunch of good vibes.
 
 ---
 
@@ -297,8 +300,8 @@ Reuse Home's `.cta-banner`. Headline with the `<em>` device; one primary + one g
   behaviour if a streaming CTA is wanted, or link to `/cuts`. (Home's CTA pairs "Explore the Archive"
   + a live-schedule button; About should point inward to the catalogue, the thing it just argued for.)
 
-> `[COPY H — FOR APPROVAL — CTA]`
+> `[COPY H — APPROVED — CTA]`
-> *Headline: "Hear the <em>Proof</em>" / sub: "The catalogue is the evidence. Start listening."*
+> Headline: "Hear the <em>Proof</em>" / sub: "The catalogue is the evidence. Start listening."
 
 Trailing full-bleed parallax (IMG SLOT E) to close, matching Home's structure.
 
@@ -351,13 +354,16 @@ is staff-engineer's call at implementation; named here so it isn't discovered mi
    placement is ready when files arrive (§8).
 3. **Image hosting path.** `wwwroot/img/` (recommended, Home-analogous) vs. the image vault. Flagged
    for staff-engineer; recommendation in §8.
-4. **CUTS / SESSIONS / MIXES — explained on About?** Recommend yes, via a one-line-per-medium reuse
+4. **CUTS / SESSIONS / MIXES — explained on About?** **RESOLVED (2026-06-17): yes, via the
-   of the `.medium-card` grid (§6.1); fall back to prose-only if it reads as duplicate of Home.
+   one-line-per-medium `.medium-card` grid (§6.1), per COPY F approval.**
 5. **Where does the "designed, not extracted" thesis land** — hero standfirst or the Process
-   movement? Recommend Process (§5).
+   movement? Recommend Process (§5). *(Still open — Daniel resolving separately.)*
 6. **Hero title wording** — "Who We Are" vs. "The Collective" vs. a Deep/DRFT masthead echo. Header
-   is proposed; Daniel's call.
+   is proposed; Daniel's call. *(Still open — Daniel resolving separately.)*
-7. **All `[COPY …]` blocks** are drafts pending Daniel's voice. None ship as written without his pass.
+7. **Copy status (2026-06-17 review):** A, B, C, E, D-intro, F, G, H are **APPROVED** (Daniel's
+   verbatim words). **D (Process card bodies) is a fresh DRAFT** pending Daniel's pass. **Khabran's
+   bio is still TODO** (item 1). Two suggested typo-fixes in COPY C are flagged inline for Daniel's
+   confirmation; his text is preserved verbatim.
 
 ---