- #91: Contact form now delivers via Web3Forms (sharedform.js + newsletter endpoint)
- #92: GitHub links updated to wscoble
- #93: ScobleClaw link corrected to sscoble/scobleclaw
- #94: Speckl description updated to compile-time provenance
- #95: Consulting CTA now links to /contact/ instead of LinkedIn
- #96: CI/CD test comment removed from production output
- Additional: Newsletter signup rewritten with working form, testimonial component removed
- Created src/pages/blog/ai-has-amnesia.astro (converted from drafted markdown)
- Added entry to RSS feed
- Also added 3 missing published posts to RSS: AI Exposes Leaders,
Mentorship Isn't Latency, Strip-Mining Is Happening Right Now
- Builds successfully (14 items in RSS)
New blog post about formal verification of SQLite state machines
using SpeckDL and Z3 bounded model checking. Covers the pager,
VDBE bytecode engine, and B-Tree invariants as Phase 1 targets.
Closes#7
- Shifted from diagnosis (strip-mining is bad) to direction (here's how to lead toward cultivation)
- Replaced consultant-structure paragraphs with varied, experience-led flow
- Kept experience-based opening; added three concrete actions (measure pride, protect four-hour window, audit tools)
- Moved Elijah reference to support cultivation cost, not as standalone point
- Added open-floor ending: 'That's yours. Not mine to answer.'
- Removed em dashes; used semicolons throughout
- Maintained Astro wrapper and layout; replaced body content only
Closesmarcus/content#6
Full rewrite of the DevEx Shift post per issue #3. Key changes:
- Thesis recentered on adoption: 'Who gives a crap about things that are never used'
- Opening is experience-led, not data-led
- Removed consultant-deck structure; varied paragraph flow
- Ending hands to reader ('The floor is open') instead of mic-drop question
- Semicolons throughout; zero em dashes
- No AI/corporate vocabulary
- Speckl mentioned briefly as 'what I'm building' — no sales pitch
- Added dry structural wit ('memorial service for a product nobody asked for')
- 'Building' → 'scaffolding', 'tooling' → 'scaffolding for agentic engineering'
- First person used sparingly and only for accountability/experience
- No hedging, no qualifiers, no 'we' as rhetorical device
- Expanded touch target list: nav-mobile-link, nav-mobile-cta, nav-cta,
footer-social a, btn, form-submit, newsletter-form button, nav-menu-toggle
- Footer social icons: 20px → 24px SVG, 44px tap targets with border-radius
- Form select/input: 48px min-height on coarse pointers, 16px font prevents zoom
- Newsletter form: stacks vertically on mobile (flex-direction: column)
- Card grids: explicit 1fr on small screens (was implicit but not guaranteed)
- Hero subtitle/actions: overflow-wrap: break-word prevents horizontal scroll
- Nav toggle: increased padding to 0.75rem for easier tapping
## Summary
Technical SEO and schema improvements per the trust/positioning audit (marcus/market#4, marcus/content#11).
## Changes
### Event Schema + SpeakableSpecification (`src/components/SEO.astro`)
- Added JSON-LD `Event` schemas for all 3 signature talks (50 First Dates with AI, From Strip-Mining to Cultivation, The Soil Under Your Team)
- `performer: Scott Scoble`, `offers`, and `description` on each
- Added `SpeakableSpecification` schema for voice search / Google Assistant / AI Overviews compatibility
### Book Schema Enhancements (`src/components/SEO.astro`)
- Updated book author fields to `Person` objects with URL
- Added book descriptions
- Added `sameAs` Amazon canonical links for "The Soil Beneath the Code" and "A Walk in Mentoring"
### Homepage Title Tag (`src/pages/index.astro`)
- Changed from "Scott Scoble — Human Cultivation Expert for the AI Age" to "Scott Scoble — Keynote Speaker | Human Cultivation Expert for the AI Age"
- Adds the high-value "Keynote Speaker" keyword for speaker bureau search
### Homepage h1 Accessibility (`src/pages/index.astro`)
- Added `aria-label="The human cultivation expert for the AI age."` to the decorative span-based h1
- Preserves visual design; improves semantic structure for search engines
### GitHub Profile README (`github-profile-README.md`)
- Professional bio with links to scott.scoble.me, books, speaker profile
- Ready to deploy to `sscoble/sscoble` GitHub profile repo
## Verification
- Build passes: 25 pages generated
- All JSON-LD schemas confirmed in output
- No visual regressions
## Related
- marcus/market#4: SEO name disambiguation strategy
- marcus/content#11: Content distribution strategy
Co-authored-by: Scott Scoble <scott@scoble.me>
Co-authored-by: agent-content <agent-content@scoble.me>
Reviewed-on: https://os.scoble.me/forgejo/forgejo/sscoble/brand-site/pulls/90
Co-authored-by: engineering Agent <engineering@marcus.local>
Co-committed-by: engineering Agent <engineering@marcus.local>
## Agentic Wars Blog Post
Review changes applied:
1. 'Convenience is not capability' pulled into its own callout
2. Closer reframed: 'Are your capabilities compounding, or are you being extracted from?'
3. Blog card excerpt fixed
### Changes
- `src/pages/blog/agentic-wars.astro` — new blog post
- `src/pages/blog.astro` — added card to blog index
---
## LinkedIn Post
The agentic wars are here. Meta has Hatch. Google has Remy. Everyone is building agents.
The question nobody is asking: when you use them, whose capability actually compounds?
Hatch keeps you in Instagram. Remy keeps you in Gemini. Every prompt, every delegated decision, every pattern the agent learns — it all compounds for the platform, not for you. Their models get smarter. Their lock-in gets deeper. You get more convenient.
Convenience is not capability.
This is the third extraction wave. Cloud took your infrastructure. Social media took your attention. Now agents are taking your decision patterns. Every time you use a hosted agent, you're training someone else's model on your judgment. Their capability compounds. Yours does not.
The alternative: run your own agents. Keep your data. The open-source tools exist today.
I've been running my own agent system for months. The value isn't in the output — it's in the decision loop. I review, I decide, I articulate what I actually think. That compounds my judgment, not a platform's.
Are your capabilities compounding, or are you being extracted from?
https://scott.scoble.me/blog/agentic-wars
#AgenticAI #PersonalAI #OpenSource #Cultivation
Reviewed-on: https://os.scoble.me/forgejo/forgejo/sscoble/brand-site/pulls/87
Co-authored-by: Marcus (agent-cos) <cos@marcus.local>
Co-committed-by: Marcus (agent-cos) <cos@marcus.local>
- AI Brain Fry: 'What Does AI Brain Fry Really Mean?'
- Gallup: 'Why Is 80% of Your Team Disengaged?'
- DevEx Shift: 'Why Can't Developer Experience Tooling Save You?'
- Surveillance: 'Why Is the Surveillance Dividend a Lie?'
- Token Anxiety: semicolons, no em dashes
- Removed manual '— Scott Scoble' from 4 titles (SEO component auto-appends)
- Added 3 new articles: strip-mining-happening-right-now, mentorship-isnt-latency-its-leverage, ai-exposes-leaders-cultivation-test
- Updated blog index with new titles and articles
Complete revoice of all blog posts based on voice-profile.md calibration:
- AI Brain Fry: reconfiguration not damage; seed metaphor; forward orientation
- Surveillance Dividend: problem + direction; cultivate from where you are
- Gallup Disengagement: fear-based development; Elijah; boldness/faith/purpose/persistence
- DevEx Shift: adoption over tooling; who gives a crap about things never used
- Token Anxiety: token anxiety is BS; directionless work not token cost
Anti-patterns removed: consultant-deck structure, data-led openings, em dashes,
mic-drop closers, AI vocabulary, over-explained metaphors, fake authority.
mailto: is bad UX - opens desktop email client most people don't have configured.
Forms now validate, show success message, then redirect to LinkedIn.
Removed spinner element and mailto: logic entirely.
Closes#58.
- Created /speaking/50-first-dates.astro with full details
- Created /speaking/strip-mining-to-cultivation.astro with details
- Updated TalkCard component to support slug prop with Learn more link
- Updated speaking page to pass slugs
- Added Umami tracking to talk CTAs
Reviewed-on: https://os.scoble.me/forgejo/forgejo/sscoble/brand-site/pulls/78
Reviewed-by: sscoble <sscoble@users.noreply.git>
Co-authored-by: Engineering (agent-engineering) <engineering@marcus.local>
Co-committed-by: Engineering (agent-engineering) <engineering@marcus.local>
Closes#48 and #62.
Both issues were already resolved in deployed code:
- #48: Privacy policy was updated to explicitly mention Umami Analytics (cookieless, first-party, no personal data)
- #62: Verified no cookie consent banner needed since Umami uses localStorage, not cookies
No code changes needed - just closing the issues now.
Co-authored-by: Scott Scoble <scott@scoble.me>
Reviewed-on: https://os.scoble.me/forgejo/forgejo/sscoble/brand-site/pulls/68
- ai-brain-fry.astro: full article with Gallup/HBR data, cognitive load patterns
- surveillance-extraction.astro: extraction vs cultivation product critique
- gallup-disengagement.astro: 80% disengagement crisis for eng leaders
- devex-shift.astro: DevEx as human sustainability, not tooling quality
- blog.astro: convert article cards to clickable links pointing to new pages
CI will deploy to scott.scoble.me via Storj on push.
