SamPlvs · SamPlvs · May 28, 2026 · May 28, 2026
@@ -1032,3 +1032,26 @@ GitHub-side changes (applied via `gh`, not in the PR):
 - **Keep the website's industry-detail origin story for "credibility"** — rejected. The eight-week constraint and budget framing carry the credibility without naming a domain; the named industry adds risk without proportionate signal.
 
 **Outcome:** Single conventional commit on a feature branch, PR opened against `main`. validate-docs 9/11 (2 pre-existing warnings, 0 failures — test badge warning re grep vs pytest count is structural, client-blocklist warning is intentional skip). No code or tests touched; no rebench needed. **No new PRIOR added** — this is a maintenance cascade closing out an earlier evolution-driven cleanup (session 025's honesty pass), not a novel failure mode. The generalisation worth recording for future cascades: when a documentation honesty pass ships, sweep all `grep -rn "<the-claim>"` hits across `docs/`, `README.md`, and `website/` in the same PR rather than trusting that the high-traffic surfaces are the only ones that matter. Closed under PR-005's enforcement spirit applied to documentation cleanup.
+
+---
+
+## Decision: 2026-05-28T00:00:00Z
+**Type:** COPY + STYLING
+**Title:** Extend hero byline with secondary collaborator credit (Callum Adamson)
+
+**Decision:** Extend the public website hero eyebrow byline from a single author credit ("by Samyakh (Sam) Tukra") to a two-line author + collaborator credit ("by Samyakh (Sam) Tukra / with Callum Adamson"), with the secondary clause visually downshifted via `display: block` + reduced font size + reduced opacity. Callum's name links to his LinkedIn (the same URL already in the footer Contributors list at `website/src/pages/index.html:1053`).
+
+Scope (single PR to `main`):
+- **`website/src/pages/index.html:84`** — eyebrow `<span>` extended with a nested `<span class="author-secondary">with <a href="...callumadamson/" ...>Callum Adamson</a></span>`. Both author links keep the existing `.author-link` underline + hover-opacity treatment.
+- **`website/public/styles.css:251`** — new `.author-secondary` rule: `display: block` forces the clause onto its own line below the main byline; `font-size: 0.9em` (renders at 9px against the eyebrow's 10px); `opacity: 0.55` (visually downshifts to "side credit"); `margin-top: 2px` for breathing room; `transition: opacity 0.18s var(--ease)`; `:hover { opacity: 0.85 }` so the link is still discoverable on intent.
+
+**Rationale:** Visual hierarchy carries the political signal that the source-code change doesn't need to spell out — Sam owns the byline (full coral, full opacity, 10px), Callum is acknowledged as a collaborator on a faded sub-line beneath it. The "with" framing word is intentional: softer than "and" / "&" (which imply co-equal billing), less obsequious than "with thanks to" (which implies one-off gratitude rather than active collaboration). The two-line layout was chosen after preview verification — an inline same-line credit ("by Sam, with Callum") wraps unpredictably at narrow viewports and strands "with" at the end of line 1, breaking the visual unit of "with Callum Adamson". `display: block` guarantees the clause reads as a single unit on its own line regardless of viewport width. Hover affordance preserved so external visitors can still reach Callum's LinkedIn from the byline (in addition to the footer link already at line 1053).
+
+**Alternatives considered:**
+- **Inline same-line credit with comma separator** ("by Sam, with Callum") — rejected after preview check: wrap behavior strands "with" at end of line 1, "Callum Adamson" alone on line 2, no clear visual hierarchy.
+- **Comma + smaller font without forced line break** — relies on natural text wrap; less predictable across viewports.
+- **Drop Callum from the eyebrow entirely, footer-only credit** — already present in the Contributors list at `website/src/pages/index.html:1053`, but user direction was explicit: add to the *opening* byline with subtle treatment. Honored.
+- **"with thanks to" framing** — too explicit, implies one-off gratitude rather than active collaboration; rejected as politically miscalibrated for an ongoing credit.
+- **Equal-billing treatment** ("by Sam & Callum") — rejected per user direction; Sam is the lead/creator and the visual hierarchy needs to reflect that without making it cringe-y to read.
+
+**Outcome:** Single conventional commit on branch `claude/website-byline-callum`, PR opened against `main`. validate-docs 9/11 (2 pre-existing warnings, 0 failures — identical state to session 029, unchanged by this PR). No code, tests, agents, commands, version, or model tiers touched. **No new PRIOR added** — this is a copy/styling decision, not a failure-driven self-evolution; design rationale captured in this DECISION_LOG entry is the auditable record.
@@ -8,7 +8,9 @@ status: complete
 
 ## Current Position
 
-**Session 029 hand-off — pick up here.** Launch-prep cascade (no code, copy + metadata only). Three external-review fixes shipped: (1) stale 70-80% token claims in `docs/quickstart.mdx:116`, `docs/cli/build.mdx:155`, `docs/COMMANDS.md:28` replaced with measured ~30% + 50-60% targeted + 70-80% roadmap framing (matches the cost-benchmark page already shipped in session 025); (2) stale test counts updated — `docs/installation.mdx:130` 675→743, `README.md` tests badge + line 508 735→743 (verified via `pytest -q`: 743 passed, 7 skipped); (3) website origin story at `website/src/pages/index.html:951` stripped of industry detail ("high-stakes client / power plant" → "eight-week production ML project") to remove confidentiality risk before broad launch push; (4) footer heading at `website/src/pages/index.html:1046` "The people behind it." → "Contributors." per user direction; (5) §03 headline at `website/src/pages/index.html:281` "Same six phases. *Now in days.*" → "Weeks of work. *Now in days.*" — the prior phrasing forward-referenced "six phases" four sections before §07 introduces them, and the §03 lede only enumerates five items, so the framing was both unearned and self-inconsistent. **GitHub repo metadata applied** via `gh repo edit`: description set, homepage `https://zerooperators.com`, 9 topics (ai-agents, claude-code, machine-learning, mlops, autonomous-agents, agent-orchestration, research-engineering, pytorch, devtools), Discussions enabled. **3 seed discussion threads posted** by SamPlvs: #80 "Show us your use case" (Show and tell), #81 "Roadmap: VS Code extension vs cost work" (Ideas, soliciting Tier 2 sequencing input), #82 "Help wanted: try the MNIST/CIFAR demos" (General). validate-docs 9/11 (2 pre-existing warnings, 0 failures). File changes shipped via PR (this session). Memory + DECISION_LOG updated per auto-protocol. **Next action when picking up:** monitor Discussions for early external-user signal on Tier 2 sequencing (extension vs cost), then resume the Tier 1 recommendation from session 028 (caveman ablation → onboarding hardening).
+**Session 030 hand-off — pick up here.** Single-file copy + styling tweak on the public website hero. `website/src/pages/index.html:84` byline extended from "by Samyakh (Sam) Tukra" to "by Samyakh (Sam) Tukra / with Callum Adamson" laid out as a two-line credit; Callum's name links to his LinkedIn (already present in the footer Contributors list at line 1053, now also surfaced in the opening eyebrow). Visual treatment in `website/public/styles.css:251` (new `.author-secondary` rule): `display: block` forces the secondary clause onto its own line below the main byline, `font-size: 0.9em` (renders at 9px against the eyebrow's 10px) + `opacity: 0.55` produce a subsidiary read while keeping the link discoverable (hover lifts opacity to 0.85, matching the existing `.author-link` hover affordance). The two-line layout was chosen over an inline same-line credit after preview testing — comma + "with" on one line wraps unpredictably at narrow viewports and can strand "with" at the end of line 1. Verified live in Astro 5 dev preview at 1280×720: Sam's name renders full coral oklch(0.58 0.16 35) at 10px, secondary line at 9px / opacity 0.55, both links underlined per `.author-link` rule. No code, tests, agents, commands, version, or model tiers touched — pure copy + styling, single PR scope. validate-docs 9/11 (2 pre-existing warnings, 0 failures — identical state to session 029). **Next action when picking up:** unchanged — monitor Discussions for early external-user signal on Tier 2 sequencing (extension vs cost), then resume the Tier 1 recommendation from session 028 (caveman ablation → onboarding hardening).
+
+**Session 029 hand-off (prior).** Launch-prep cascade (no code, copy + metadata only). Three external-review fixes shipped: (1) stale 70-80% token claims in `docs/quickstart.mdx:116`, `docs/cli/build.mdx:155`, `docs/COMMANDS.md:28` replaced with measured ~30% + 50-60% targeted + 70-80% roadmap framing (matches the cost-benchmark page already shipped in session 025); (2) stale test counts updated — `docs/installation.mdx:130` 675→743, `README.md` tests badge + line 508 735→743 (verified via `pytest -q`: 743 passed, 7 skipped); (3) website origin story at `website/src/pages/index.html:951` stripped of industry detail ("high-stakes client / power plant" → "eight-week production ML project") to remove confidentiality risk before broad launch push; (4) footer heading at `website/src/pages/index.html:1046` "The people behind it." → "Contributors." per user direction; (5) §03 headline at `website/src/pages/index.html:281` "Same six phases. *Now in days.*" → "Weeks of work. *Now in days.*" — the prior phrasing forward-referenced "six phases" four sections before §07 introduces them, and the §03 lede only enumerates five items, so the framing was both unearned and self-inconsistent. **GitHub repo metadata applied** via `gh repo edit`: description set, homepage `https://zerooperators.com`, 9 topics (ai-agents, claude-code, machine-learning, mlops, autonomous-agents, agent-orchestration, research-engineering, pytorch, devtools), Discussions enabled. **3 seed discussion threads posted** by SamPlvs: #80 "Show us your use case" (Show and tell), #81 "Roadmap: VS Code extension vs cost work" (Ideas, soliciting Tier 2 sequencing input), #82 "Help wanted: try the MNIST/CIFAR demos" (General). validate-docs 9/11 (2 pre-existing warnings, 0 failures). File changes shipped via PR (this session). Memory + DECISION_LOG updated per auto-protocol. **Next action when picking up:** monitor Discussions for early external-user signal on Tier 2 sequencing (extension vs cost), then resume the Tier 1 recommendation from session 028 (caveman ablation → onboarding hardening).
 
 **Session 028 hand-off (prior).** No code shipped — strategic roadmap pass synthesising three pieces of external user feedback into a tiered Q3/H2 roadmap. `docs/roadmap.mdx` rewritten (replaces prior 3-card "top priorities"); full internal plan at `~/.claude/plans/so-before-i-begin-peaceful-valley.md`. **Three workstreams:** (1) **cost** — caveman as scoped Claude Code skill in `--low-token` preset (target +10-20pp on the measured ~30% baseline); (2) **cross-phase autonomy (F3, DAG→weighted graph)** — Phase A = `RETURN_TO_PHASE` `GateDecision` backedge primitive (validates F3 hypothesis cheaply), Phase B = full graph refactor with `completeness` per node + revisit ranking + `zo nodes freeze`; (3) **accessibility** — **VS Code extension** chosen over fork (Cursor/Windsurf) and over from-scratch Tauri/Electron, with **headless tmux as engine + xterm.js webview as renderer** (zero changes to `wrapper.py`, Claude Code keeps real TTY, sub-agent panes render naturally, crash-recoverable); "ZO Studio" bundled installer (VS Code + extension + Claude CLI + uv) as optional follow-on for non-technical researchers. **Multi-provider** (CodeX/OpenCode) reframed as **worker-pool model** (Claude Code lead + single-agent workers via filesystem JSONL), NOT full peer-to-peer parity (would require rebuilding `TeamCreate` / `Agent` / `SendMessage` infrastructure on bare APIs). **Recommended next 2 PRs (Tier 1):** caveman ablation (~1 week) → onboarding hardening (~1 week, one-line installer + Homebrew formula + `zo doctor` command). **Recommended Tier 2 sequencing:** architecture-first (backedge primitive → SDK refactor → VS Code extension); visibility-first defensible if onboarding is the bigger growth lever. **Open questions still pending:** time horizon (Q3 vs H2), Tier 2 sequencing confirmation, audience weighting (research peers / paying customers / internal). Captured in DECISION_LOG entry 2026-05-05T12:00Z (ROADMAP + ARCHITECTURE). No new PR opened yet — roadmap doc + memory updates land in this commit; Tier 1 implementation deferred to user direction.
 

@@ -249,6 +249,15 @@ em, .it {
 .author-link:hover { opacity: 0.7; }
 .author-link em { font-style: normal; }
 
+.author-secondary {
+  display: block;
+  opacity: 0.55;
+  font-size: 0.9em;
+  margin-top: 2px;
+  transition: opacity 0.18s var(--ease);
+}
+.author-secondary:hover { opacity: 0.85; }
+
 .display {
   font-weight: 500;
   font-size: clamp(44px, 5.8vw, 78px);

@@ -81,7 +81,7 @@
       <div class="hero-copy">
         <div class="eyebrow reveal" data-delay="0">
           <span class="tick"></span>
-          <span>Zero Operators · v1.0.2 · by <a href="https://samtukra.com/" target="_blank" rel="noopener" class="author-link"><em>Samyakh (Sam) Tukra</em></a></span>
+          <span>Zero Operators · v1.0.2 · by <a href="https://samtukra.com/" target="_blank" rel="noopener" class="author-link"><em>Samyakh (Sam) Tukra</em></a><span class="author-secondary">with <a href="https://www.linkedin.com/in/callumadamson/" target="_blank" rel="noopener" class="author-link"><em>Callum Adamson</em></a></span></span>
         </div>
         <h1 class="display reveal" data-delay="120">
           An autonomous AI <em>research team.</em><br/>