FullStack VC v0.1.0 — June 24 Readiness, a Two-Perspective How-To Engine, and a Registry That Grew Up
Everything between the May 27 all-hands and the June 24 session: we turned a thin poll into rendered pre-session data, built and revised the 'Dealflow into Second Brains' deck, corrected the record on who actually presented, bumped the whole toolchain onto Astro 6.4.8, grew the tool + participant registries with real sourced profiles, and — the forward-looking bet — started a documentation engine that lets VCs enter how-to content two ways: by the problem they're solving or the tool they've heard about. 26 commits, 37 files.
Contents
Why Care?
v0.0.9 cut on May 27, the day of the Monthly All-Hands. This release is everything between that session and the next one — June 24's "Dealflow into Second Brains" — plus a bet on what comes after the sessions themselves.
The immediate work was getting June 24 ready: a session page, a section-composed slide deck, and — the part that matters most — turning last month's small poll into something legible. Only a handful of people answered the May 27 survey, but they answered well (a perfect +100 NPS, and concrete asks like "wire Claude into Affinity/Notion/Drive"). Rather than fake analytics over seven responses, we rendered the reflection and the asks as data, and let them frame the next session.
The forward-looking work was bigger: the Dojo keeps generating one-off sessions, but knowledge from them evaporates. So we started a documentation engine — how-to content reachable from two doors (the problem you're solving, and the tool you've heard about) — to turn ephemeral session demos into durable, navigable guides. This release is where that engine takes its first breath.
What's New Since v0.0.9
| Surface | v0.0.9 | v0.1.0 |
| June 24 session | did not exist | full session page + RSVP + a ported, revised slide deck |
| May 27 survey data | two raw CSVs in a folder | one session-keyed JSON rendered on the session page + an April→May satisfaction trajectory on the deck |
| Docs / how-to content | none | a two-perspective engine: /recipes, /use-cases/*, /guides/*, internal /tools/*, all LFM-rendered |
| Toolchain | Astro 6.3.1, Tailwind 4.2, Svelte 5.55 | Astro 6.4.8, Tailwind 4.3.1, Svelte 5.56 (verified by a clean full build) |
| Tool registry | — | +Composio, +Granola, and every tool now has an internal /tools/<handle> page |
| Participant registry | several stubs | David Rolf + Abhinaya Konduru added with real profiles; Lylan Masterman stub repaired; headshots committed locally |
Key Features
1. The June 24 session, end-to-end
The "Dealflow into Second Brains" all-hands got a full session post (/sessions/2026-06-24_dealflow-into-second-brains) with a Zoom RSVP, and a section-composed deck at /slides/2026-06-24_monthly-all-hands (cover, theme, pre-session signals, network, agenda, three demo slides, town hall, close). Presenters: Marcus Brotman (intake → Notion), Toby Rush (his personal-automation second-brain stack), and Michael Staton (a markdown-notebook primer). The /slides "Today" highlight moves forward to it automatically.
2. May 27 survey rendered as data — with a trajectory
The post-session reflection survey (insightful 9.6/10, NPS +100) and the open poll's Setupathon/curiosity asks now live in one session-keyed JSON that the session page composes (mirroring the April 29 shape). The deck adds an April → May satisfaction trajectory (insightful 9.1→9.6, NPS +75→+100) as deck-local markup — no shared component changes.
3. A two-perspective how-to engine (the new thing)
Built on @lossless-group/lfm, deliberately not Astro Starlight. One body of how-to content, two navigation doors:
/use-cases/<slug>— start from the problem (the first hub: Automate Dealflow, straight from the survey's #1 ask)./guides/<slug>— follow the steps (the first guide: Put Hermes Agent on Your Dealflow), each wired to itsuse_cases:andtools:./recipes— an umbrella index in the header listing both perspectives as cards./tools/<handle>— every registry tool now has an internal page (info + body + the guides/use-cases/people that reference it), and wikilinks prefer it over the tool's external homepage.
LFM features render live: callouts, [[wikilinks]] (via a site resolver), citations, video/GIF embeds — all through the copied AstroMarkdown component. The spec (context-v/specs/Two-Perspective-How-To-Docs-Engine-on-LFM.md) records the model and, deliberately, leaves the final tree shape to settle from real content.
4. Registry maturation
Tools: Composio (tool-calling + auth layer for agents) and Granola (AI meeting notepad).
Participants: David Rolf (Head of Visa Ventures, Class 12) and Abhinaya Konduru (Partner at M25, Class 28) added with sourced bios + local headshots; Jules Miller added earlier in the window; Lylan Masterman's stub repaired (real name, Whipsmart Ventures, local headshot). Stack relations wired (e.g., Composio → Michael's aspirations, Granola → Abhinaya's).
5. Toolchain currency
In-major bumps across the board — Astro 6.3.1→6.4.8, Tailwind 4.2→4.3.1, Svelte 5.55→5.56, plus @astrojs/db, sitemap, vercel, jose, svelte-dnd-action. Resolved in standalone mode to match Vercel's build context; verified by a full local libSQL build. Surfaced (and flagged for a future migration) the upstream @astrojs/db deprecation.
Bug Fixes & Housekeeping
/people/[handle]SSR with a Turso fallback — DB-only signups stopped 404ing (and afcamposanostub patched a specific 404).The record kept honest — Marcus and Toby removed from the April 29 / May 27 lineups they were slated for but didn't present (and Toby off the May 27 deck), counts and copy adjusted to match.
context-v/extra/fully untracked — a registrant CSV with real emails (committed before the ignore rule) removed from tracking.db.timestamp-*.mjsignored — Astro DB bundler temp artifacts no longer clutter the tree.Zero new type debt —
astro checkheld at its pre-existing baseline (16 errors, all in older files) across every change in this release.
The Story
The arc of this release is ephemeral → durable. v0.0.9 was about the machinery of a live session (auth, polls, stacks). This release used that machinery for one more session (June 24) — but the bigger realization was that the sessions keep producing knowledge that nobody can find afterward. A founder demos an OpenClaw-into-Obsidian pipeline; three weeks later, someone asks "how do I even start a second brain?" and there's no answer to point them at.
That's the gap the how-to engine fills. And the design fell out of the audience itself: VCs say both "I need to automate dealflow" and "I've heard I need Hermes Agent." Two doors, one room. We resisted the urge to fully architect it on paper — wrote a provisional spec, then let the structure emerge from authoring one real slice. It did: use-cases/ + guides/, tool angle on the existing registry, "recipe" as the cross-nav idea. The wikilink resolver flip (internal-first) turned the content into a navigable loop instead of a set of exits to other people's sites.
Operational Hand-Off
Tag this release
v0.1.0ongithub.com/lossless-group/fullstack-vc— a minor bump from v0.0.9, reflecting the new how-to-engine surface (new routes, not just content). Plain three-part semver, since the changelog is public-facing and a single readable number reads clearer than a four-part scheme.Bump
package.jsonfrom0.0.9→0.1.0to match the tag when cutting the release.The how-to engine is content + raw render only. No left-nav / TOC / pager yet (specced, not built). Guides are
publish: falsedrafts; the Hermes guide's[!todo]blocks need a real run to fill in before publishing.@astrojs/dbdeprecation is the one looming dependency risk — a Drizzle/libSQL-direct migration of the poll/session/stack layer is the documented next step before the Astro major that removes it.
What's Next
Docs chrome: left-hand navigation, right-hand table of contents, prev/next pagination — the furniture that turns the raw render into a real docs site.
More guides: the survey's other named asks (accelerate memo drafts, wire Claude into the VC stack, diligence + portfolio tracking) are the obvious next content, each pressure-testing the two-perspective structure.
June 24 itself — and the post-session survey that will, in turn, frame the session after.