ch · context-v
Context-V
Specs, explorations, plans, prompts, and reminders across the ai-labs tree. Parent-authored docs live alongside the rolled-up child docs; provenance is on every card.
specs 15 explorations 17 plans 26 prompts 1 blueprints 3 reminders 4 issues 1 issue-resolution 1 sitemap 14 context-v 15
specs 15
-
ai-labs In-App Agent Chat — Core Package Spec
Concretizes the chat-as-agent-surface exploration into a shippable package: capability registry schema, BYOK storage and proxy contract, chat UI component API, transcript schema, and a v1 acceptance scenario for dididecks. One shared package under ai-labs/packages/, per-app capability definitions, three guards that keep the agent inside our methods.
-
dididecks-ai Dididecks-AI: DD-Ready Citation and Source-Access System
Every claim in a Due Diligence deck must be backable — by an academic-grade citation, a sourceable artifact, and a downloadable trail that a receiving decision-maker can pull on without asking the sender for permission.
-
dididecks-ai Dididecks-AI: Slide Decks as Code
A code-first paradigm for slide deck generation, iteration, and management — where AI coding assistants treat slides as components, decks as repositories, and presentations as living, versioned software rather than artifacts trapped in proprietary binary formats.
-
dididecks-ai Dididecks-AI: Visual and Diagram Component Library
DD-grade decks lean on a wide universe of recurring visual primitives — concept diagrams, mental models, classification schemes, frameworks. A reusable, AI-composable library of these primitives is what lets each new deck reach 'wow' without re-drawing from scratch.
-
memopop-ai Character Cast for Live Agent Indication
Personify the orchestrator's agents as a cast of named, faced characters. A row of portraits sits above the run panel; the ones currently doing work glow, with a live caption underneath describing what each is up to right now.
-
memopop-ai An Onboarding User Journey for memopop-native
Experiences win on Onboarding. This spec outlines a user journey for onboarding users to memopop-native.
-
memopop-ai/memopop-orchestrator Interactive Terminal Application — Easy Interface for Casual Users
A guided CLI application that walks users through memo generation, export, and iteration without requiring knowledge of individual commands, flags, or file paths.
-
memopop-ai/memopop-orchestrator Introducing Investigate Capital Syndicate with Detailed Artifacts
A research agent that investigates every investor, fund, family office, and financial institution on a company's cap table and in the current round — producing detailed profiles, pattern analysis, and signal extraction for investment decision-making.
-
memopop-ai/memopop-orchestrator Introducing a One-Pager Cover Sheet and Export
A post-pipeline agent and CLI tool that distills the full investment memo into a single-page visual summary, usable as both a standalone deliverable and a cover sheet prepended to the full memo export.
-
memopop-ai/memopop-orchestrator Introducing a Competitive Landscape Research and Evaluation System
Two coordinated agents—a Competitive Landscape Researcher and a Competitive Landscape Evaluator—that produce accurate, validated competitor analysis by combining multi-query web research with structured relevance screening.
-
memopop-ai/memopop-orchestrator Introducing a Table Generator Agent
A post-writer enrichment agent that identifies tabular data opportunities in memo sections and generates markdown tables with overflow anchor linking, configurable column schemas, and firm-specific customization.
-
memopop-ai/memopop-orchestrator Introducing a Diagram Generator Agent
Add a diagram_generator.py agent that identifies opportunities to create visual diagrams explaining complex business concepts, starting with TAM/SAM/SOM market sizing and expanding to common finance and consulting visuals.
-
memopop-ai/memopop-orchestrator PDF Parser Agent Specification
A small specification for an agent and script to parse PDFs and convert them to markdown with properly formatted citations.
-
memopop-ai/memopop-orchestrator Deck Analyzer Agent
A specialized agent for extracting structured data and visual screenshots from pitch decks (PDF and PowerPoint) to bootstrap investment memo generation.
-
memopop-ai/memopop-orchestrator Dataroom Analyzer Agent System Plan
A comprehensive plan for implementing a multi-agent dataroom analysis system that intelligently recognizes, categorizes, and extracts information from diverse document types in investment datarooms.
explorations 17
-
ai-labs Memory Layers for the In-App Chat Package
The chat surface in dididecks-ai, memopop-ai, and augment-it will only feel 'within our system' if the agent on the other side has fast, cheap, accurate access to our patterns, prior decisions, project state, and what it already learned about this specific client. This explores how the eight memory systems pinned in studies/memory-layers-for-agents map onto roles in the chat package, what we'd pick for v1 given that we already lean on Chroma, and what to defer.
-
ai-labs In-App Chat as the Agent Surface for Client Apps
Instead of trying to fit dozens of anticipated client requests — 'redesign this slide', 'run the writer agent on the updated research', 'export in my brand kit' — into navigation, buttons, and command menus across dididecks-ai, memopop-ai, and augment-it, wire up a single chat surface inside each app that calls an LLM with our patterns, skills, and project context already loaded. Paying clients use our keys; lingering post-engagement clients bring their own. The chat is the menu.
-
ai-labs Shared Auth for Applied AI Labs
We're about to need a real auth story across three sibling apps in ai-labs — memopop-ai, dididecks-ai, and the just-arriving augment-it. None of them is at the scale that justifies Auth0/Clerk pricing or robustness. We want a small, owned auth system that handles OAuth (GitHub + Google Workspace), pre-shared invites delivered by WhatsApp or 1Password, organization-scoped permissions, and a viewer-tier for memos and decks published on client subdomains — with a roll-up seam stubbed from day one so we can wire cross-app dashboards later without rewriting clients.
-
dididecks-ai Plans Inventory 2026-05-16 — Post-DeckOverlay, Post-/play-Chooser-Fix, Post-Status-Sweep
Snapshot of `dididecks-ai/context-v/plans/` as of 2026-05-16, four days after Phase A+ shipped and two days after the Restore-Calmstorm-Nav-Elegance partial landed. Supersedes `Plans-Inventory-and-Phase-A-Outcome.md` (which froze at 2026-05-12 and predates the Scroll-UI/Play-UI framing correction). Designed for a cold-start future-session land: what shipped, what's running, what's actively partial, what's deferred, and three reasonable directions for the next iteration.
-
memopop-ai Curating Only Valid Sources Across Runs
The memo pipeline ran ChromaDB seven times and emitted seven source catalogs. Merging them produced 392 'unique' entries that were mostly the same dozen URLs recycled across sections, half of them dead pages returning HTTP 200. Here's what's broken and how curation has to handle it.
-
memopop-ai Separating Retrieval from Generation in Agent Pipelines
When the same LLM agent both searches the web and writes the prose that cites those searches, it can't help fabricating URLs. This is not a bug — it's the predictable failure mode of asking one cognitive process to do two different jobs. Here's the agent topology that makes citation hallucination structurally impossible.
-
dididecks-ai Chroma-Decks Parity with Calmstorm-Decks, and the Path to a Shared Deck UI Module
Calmstorm-decks carries roughly forty UI feature-surfaces that chroma-decks does not yet have. Initial framing weighed three paths (verbatim port, abstract-while-porting, full monorepo split); dialog landed on a fourth and lighter shape — the wrapping UI becomes `@dididecks/shell`, an Astro integration published to a private pnpm-scoped npm registry, consumed by each client-site's `astro.config.mjs`. Each client-site stays a standalone repo with its own Vercel deploy; content stays put; only the chrome travels. Phase A is the TOC + slide-ranking UI inside the shell, which doubles as the Phase 1 → Phase 2 tooling from the `deck-iteration-workflow` skill.
-
dididecks-ai Plans Inventory and Phase A Outcome — What Shipped, What Remains, and the Three Gaps the Founder Surfaced on First Smoke-Test
Four plans live in `dididecks-ai/context-v/plans/`. Two have been fully executed (the dididecks-ai monorepo init and the chroma-decks scaffold). One is partly executed (Phase A of `@dididecks/shell` — A.1 through A.6 working in workspace-link mode; A.7 publish is administratively blocked). One is fully deferred (the slide componentization sweep, which now retargets into the shell). After landing the shell today, the founder smoke-tested the running surface and named three concrete gaps: no global navigation chrome, no in-scroll-deck slide-rank UI (a feature neither calmstorm nor chroma has today), and no per-slide static HTML files to feed a `/play` runtime. The next plan — Phase A+ — closes those three in a single coherent slice.
-
context-vigilance-kit Code-Comment Sections as Context-V Source
JSDoc treats code comments as the source of truth for API documentation. The same move might work one level up — treating *certain section-level comment blocks* in a codebase as the source of truth for context-v entries that today live as standalone markdown. The question is which kinds of context belong embedded in source files versus floating beside them.
-
dididecks-ai Chroma Brand & Deck Notes (pre-scaffold)
Source-of-truth design tokens, typography, and content-source notes for the upcoming `chroma-decks` client-site. Extracted directly from trychroma.com's production CSS bundle and the Alpha Partners investment memo. Lives in dididecks-ai/context-v/explorations/ until Phase 2 of [[../plans/Init-Chroma-Decks-Client-Site]] scaffolds the chroma-decks repo — at which point this file's substance is promoted into `chroma-decks/DESIGN.md` (Stitch-spec format).
-
dididecks-ai Dididecks-AI: Business Model Exploration
Build in public, copyleft where we can, copyright where it matters, hosted + Forward Deployed humans as the real growth engine. This is the option-space; sign-off on a model is downstream of usage signal.
-
memopop-ai Where Investor-Firm Rosters Live
When a deal artifact bundle includes the investor's team roster, where does that roster live? Inside the deal folder it duplicates on every co-investor; in a global firms index it loses deal context. Stub for a real exploration.
-
ai-labs ChromaDB as Context Improvement Across Everything, Everyone
Skeptical of vector databases at our scale until a founding-team demo showed me the product is no longer 'a place to put embeddings' — it is an ingestion layer for agent traces, session transcripts, and ambient developer signal that a small team can bend toward almost anything.
-
ai-labs Collate Context Files into Context Vigilance as Repo & Project
A long-running, everywhere-distributed practice — context-v/ across a tree of pseudomonorepos — finally graduates into a project of its own, with a collator, a splash, and a vector index.
-
memopop-ai Crawl for Better Team Structured Output
Building a team slide takes analysts 1–2 hours of clicking. The orchestrator already writes prose about teams; what it doesn't do is hand back the structured roster — names, titles, durable photo URLs, professional socials — that the MemoPop app needs to render cards. Here's the option space for closing that gap.
-
memopop-ai Moving an Agent Orchestrator to an API
The orchestrator is a Python CLI today. To plug it into memopop-native, we need an HTTP-shaped surface. Three options, ranked by effort and time-to-value.
-
ai-labs explorations/When-Claud-Code-and-When-Pi
plans 26
-
ai-labs In-App Agent Chat — Walking Skeleton Plan
Starter kit for tomorrow's session. Three days of conversation have produced an exploration, a spec, a memory-layers exploration, and a tenancy decision. This plan turns all of it into one session's worth of concrete work: scaffold the package, do the Chroma tenant migration, settle two open questions that block everything downstream, and ship slide.read end-to-end as the proof the abstractions hold.
-
dididecks-ai Redesign TOC as a Deck-Level Dual-Surface Review Matrix
Today's `/toc/[deck]/[variant]/` answers a build-system question ('which slot has a Play-UI file?') when the deck-iteration-workflow centers on a workflow question ('where am I in the review cycle, and which variant is closest to shippable?'). The calmstorm-decks `/index` shows the right shape: variants as columns, slides as rows, a review-status chip per cell. We go one step further than calmstorm: each cell carries TWO chips, one per surface — scroll-review and play-review — because the workflow reviews each slide twice (once during scroll-iteration, once after porting to Play-UI). The goal the matrix should make obvious at a glance: find a single column where every slide is ≥ passable on both surfaces, with as many ★s as possible. Drift between scroll-rating and play-rating is itself a workflow signal (the port may have lost fidelity). This redesign migrates the audits schema from one rating per (slot, variant) to two ratings, makes the SlideRankPill surface-aware, builds a new `/toc/[deck]/` deck-level matrix route, and keeps the per-variant `/toc/[deck]/[variant]/` route alive as the variant landing/index — distinct purpose from the matrix. [Original lede said "folds the per-variant TOC into a redirect"; revised 2026-05-17 in-flight when in-browser review made clear the two surfaces serve different workflow needs.]
-
dididecks-ai Componentize Slides and Establish Component Library
Walk the calmstorm-decks slide deck page-by-page, extracting raw inline HTML+CSS into a properly-taxonomized Astro component library while simultaneously building the design system that backs it. The end state: every slide variant composes from named, reusable parts; `components/basics/` stops being a dumping ground; and the work doubles as the first concrete proof of the sibling Visual-and-Diagram-Component-Library spec.
-
dididecks-ai Init Chroma Decks Client-Site
Stand up `client-sites/chroma-decks` for an early-growth-stage portfolio company raising a round — radically improve the founder's existing materials, marry them with MemoPop-generated investment memos and market research, and use the engagement to harden the calmstorm-decks template into a reusable client-site baseline.
-
dididecks-ai Init DidiDecks as Core Submodule of AI-Labs
Carve out dididecks-ai as its own repo and re-attach it to ai-labs as a git submodule, following Lossless pseudomonorepo discipline — branch-aligned tiers, rollup-friendly context-v, splash-page on day one, and the parent's gitlink as the single point of truth.
-
memopop-ai/memopop-orchestrator Trustworthy Citations: Source Harvester Rollout
Where we are after the ChromaDB curation post-mortem, why the existing anti-hallucination work hasn't held, and the concrete six-phase plan to make fabricated URLs structurally impossible — starting with cheap fixes that block the bleeding and ending with a Source Harvester / Section Writer split.
-
dididecks-ai Phase A+ — In-Deck Ranking, Shared Nav Chrome, and a Working /play Runtime
After Phase A landed `@dididecks/shell` with a working TOC + slide-ranking API + decomposition-stub generator, three concrete gaps surfaced on first founder smoke-test: no global navigation chrome connecting Scroll · TOC · Play, no way to rank a slide *from within* the scroll deck (you have to leave for a separate route), and nothing to verify the /play runtime works because the shell injects no /play route yet and chroma has no per-slide files for one to render. Phase A+ closes all three together — shell-injected global nav, a shell-exported `<SlideRankPill>` floating overlay the founder drops into the scroll deck via data-attrs, a minimum-viable `/play/[deckSlug]/[variantSlug]/[slot]?` route with ← / → keyboard nav, and two seeded per-slide files in chroma so the whole loop (rank → decompose → recreate → present) is provable end-to-end. All in workspace-link mode; Phase A.7's publish step is orthogonal.
-
dididecks-ai Phase A++ — Play Fidelity, In-Play Ranking, and Variant URL Safety
Phase A+ shipped the global nav, the floating in-scroll rank pill, a working `/play` runtime, two seeded per-slide files, and the TOC `[view →]` link — all the surfaces the founder asked for. Day-of smoke-test surfaced three concrete gaps: `/play/pitch/proto/` 404s because the proto variant has no `SLOTS[]` entry yet (the index-redirect was unconditional), the Play runtime doesn't yet have the elegant UI of calmstorm-decks (chrome feels like a dev tool, not a presentation surface), and the `<SlideRankPill>` is mounted in `/scroll` but not in `/play` even though the founder is reading-and-judging slides there too. Phase A++ closes all three without touching Phase A.7's still-blocked publish step, and seeds the calmstorm-primitive lift the larger Phase B will continue.
-
dididecks-ai Port Enhanced-v2 Scroll Slides to Static 16:9 Play Slides for PDF Export
The scroll deck for chroma's pitch/enhanced-v2 is shippable by the founder's design eye, but its sections live in a scroll-flow context — `min-h-screen` heights, brand-orb gradients that bleed across section boundaries, the customer marquee animation — that won't export cleanly to PDF. This plan ports each of the 16 v2 sections, non-destructively, into static 16:9 per-slide files under `src/components/slides/enhanced-v2/{slot}-{slug}.astro` so the existing /play/[deck]/[variant]/[slot]/ runtime renders them at a predictable aspect ratio. Then a one-shot print route stacks all 16 vertically, ⌘P saves as PDF, deck ships to founder tonight. Tomorrow's Phase A++ (calmstorm-grade /play chrome + SlideCanvas/ContentFit lift) is orthogonal and not blocked by this.
-
dididecks-ai Stand Up @dididecks/shell and Ship the Chroma TOC + Slide-Ranking UI
Phase A of the exploration that landed on `@dididecks/shell` as the path to chroma-↔-calmstorm parity. Scaffold `apps/deck-shell/` inside the dididecks-ai monorepo as an Astro integration; ship two seed routes (TOC + slide-ranking pills) and one decomposition-stub generator that bridges the deck-iteration-workflow Phase 1 → Phase 2 transition; install in `client-sites/chroma-decks/` first via local link, then via a v0.1.0 publish to a private pnpm-scoped npm registry. Each client-site stays a standalone repo on its own Vercel project; the shell is the only thing that travels.
-
context-vigilance-kit Tidy Context Vigilance Files Across All
A phased, manifest-driven plan to bring every context-v file in the corpus to a state we are proud of — starting with the most-developed docs, fanning out to idea-started ones, with concurrent duplicate detection and ruthless decisions on merge / kill / relocate as we go.
-
memopop-ai Add People Crawl Command to MemoPop Native
Wire the orchestrator's `extract_team_roster` command into the MemoPop Native UI as a per-investor button — and as a batch action that runs it 5–20 times per memo, once for each co-investor in the round.
-
ai-labs Add a Chroma Local UI Interface
Local Chroma in PersistentClient mode is an embedded SQLite library with no UI of its own. Three paths to a browseable surface — from a 30-line inspect script tonight to a /chroma route in the splash later — laid out in increasing commitment.
-
ai-labs Context Vigilance Splash Page — Narrative Brief
Designer brief for the Context Vigilance splash. The functional plumbing exists; the structural skills are codified elsewhere. This doc is only about the *story* — the four-act narrative arc and the emotional move each act should produce.
-
ai-labs Track and Ingest Lossless Content into Chroma (with Change Detection)
A second ingestion pipeline parallel to the context-v corpus — for the ~5K Lossless content files scattered across the monorepo. Driven by its own sources map, with content-hash-based change detection so re-runs only re-embed what actually changed.
-
ai-labs Write Custom Chroma MCP Server (v0: a session-transcript ingester)
Defer the community djm81/chroma_mcp_server. Roll our own session-transcript ingester that writes into the same Chroma instance our corpus already lives in — preserving the metadata alignment that lets us cross-query corpus and conversation history together.
-
memopop-ai Team and People Metadata Ingestion
Six phases to take any company URL → structured TeamRoster JSON the MemoPop app can render as cards. Each phase ships independently and is verifiable on its own.
-
memopop-ai Upgrade the MemoPop AI splash with three-mode theming, context-v rollup, peer-aware discovery, and Pagefind
The current memopop-site shipped fast but pre-dates the conventions astro-knots/splash settled into a few days later. This plan brings memopop-site up to that bar — three-mode toggle on a two-tier token system, a context-v archive alongside the existing changelog, peer-directory rollup that walks the monorepo (apps/* and packages/*) instead of children, and Pagefind across both archives — without touching the design language. Implementation is free to invent its own visual identity; this plan only locks down the mechanics.
-
memopop-ai/memopop-orchestrator Generic competitor analysis enhancement, post-hoc and re-runnable
Move competitor research/evaluation from a one-shot pipeline step into a re-runnable, configurable enhancement — driven by `.md` + frontmatter schemas, applicable to any version of any memo, surfaced in memopop-native.
-
memopop-ai/memopop-orchestrator Generic scorecard generation across firms and outlines
Refactor the scorecard agent + CLI from hardcoded Hypernova/fund-only to a generic renderer driven by `.md` + frontmatter scorecards, then surface it in memopop-native on the deal page.
-
memopop-ai/memopop-orchestrator Wire memopop-native to the FastAPI sidecar
End-to-end plan for closing the loop from Tauri click to live log stream — Rust dispatcher forwards JSON, browser EventSource handles SSE, sidecar spawns lazily.
-
dididecks-ai Refactor scroll-ported slides into true static play-format slides (per-client, repeat for every deck)
Operational plan, reusable across every dididecks client engagement, for converting per-slide files that were COPIED from scroll-deck sections (and therefore still carry scroll-mode idioms — vw/vh/clamp viewport units, IntersectionObserver-driven reveals, marquees, transitions, breakpoint media queries) into the static-only HTML/CSS/Tailwind form @dididecks/shell's /play and /print routes require. The calmstorm-decks `src/slides/by-title/` fileset is the reference implementation; this plan extracts its discipline so any client deck (chroma-decks today, future engagements tomorrow) can be ported the same way. Includes the rationale, the checklist, the per-slide procedure, the verification loop, and the anti-patterns to flag during code review.
-
dididecks-ai Restore Calmstorm's nav-chrome elegance as themable shell primitives (separate structure/behavior from styling)
@dididecks/shell v0.1's PlayChrome solved the navigation contract but discarded calmstorm-decks' deliberately elegant chrome — floating bottom-right capsule, glassy white/grey/black, fade-on-idle, two-axis nav (variant cycling + section walking), custom tooltips, tabular-num counter — and replaced it with a heavy dark bottom bar that always claims viewport real-estate. This plan lifts the calmstorm chrome forward as package-level primitives in apps/deck-shell/, with structure and behavior cleanly separated from visual styling via a CSS-custom-property theming contract. Consumers (chroma-decks today; future client sites tomorrow) inherit a sensible neutral default (calmstorm's plain white/grey/black) when client-specific tokens aren't supplied, and override with their own design system when they are. Hybrid of port-and-replace + re-skin: port the bones, ship the calmstorm look as the universal fallback, then let chroma-decks (and others) light them up with their own brand.
-
memopop-ai/memopop-orchestrator Migrate `studies/open-specs-and-standards/` into its own pseudo-monorepo
-
memopop-ai memopop-ai/plans/Generate-DD-Questions-&-Checklist
-
memopop-ai memopop-ai/plans/Include-Validation-Analysis-as-Action-Items
prompts 1
blueprints 3
-
memopop-ai/memopop-orchestrator Git Submodules for Private Data and Exports
Configure git submodules to enable private GitHub repositories for sensitive company data inputs and branded memo exports, while keeping the main orchestrator repo public/shareable.
-
memopop-ai/memopop-orchestrator Model Scorecard Agent and Template System
Add proprietary investment scoring frameworks to memo generation, enabling VC firms to systematically evaluate and communicate their differentiated investment thesis.
-
memopop-ai/memopop-orchestrator memopop-ai/memopop-orchestrator/blueprints/Ideal-Information-Hierarchy-Applied-to-Markdown-Headings
reminders 4
-
ai-labs Preferred Stack — uv over pip, and other defaults
-
memopop-ai/memopop-orchestrator Format Memo According to Outline Input
Refactor the investment memo system to use YAML-based content outlines that agents can reference for structure, guiding questions, and vocabulary.
-
memopop-ai/memopop-orchestrator Generate Investment Memo for Portfolio Company
Create investment opportunity briefs that match Hypernova's analytical voice, format, and depth using AI-assisted generation with structured inputs and validation.
-
memopop-ai/memopop-orchestrator memopop-ai/memopop-orchestrator/reminders/The-Voice-and-Purpose-of-Changelogs
issue-resolution 1
sitemap 14
-
dididecks-ai DeckChrome — themable floating navigation capsule for Play-UI (and eventually Scroll-UI variant cycling)
Floating bottom-right capsule with paginator, ← / → slot nav, TOC link, optional ↑ ↓ variant cycling, and the full keyboard contract (← → Space PageUp/Down Home End F C T Esc). Replaces v0.1's heavy dark PlayChrome bar. Structure / behavior / styling are separated by discipline: structure is the Astro template, behavior is the inline keyboard script and `ddd:section-*` event dispatch, styling reads only `--ddd-chrome-*` CSS custom properties (neutral defaults inline; consumer overrides at any wrapping element). Lives inside `DeckOverlay--Play-UI` as the default `nav` slot today; will also serve as the variant-cycling element of `DeckOverlay--Scroll-UI` under Phase 2.
-
dididecks-ai DeckOverlay--Play-UI — the floating overlay layer for Play-mode decks
Single mount point for /play/[deck]/[variant]/[slot]/ that composes DeckChrome (paginator + slot-step nav + keyboard contract) and SlideRankPill (classifier) above the active slide, plus named slots for Phase 3 presenter notes and Phase D telemetry. Wraps the slide in a `<section data-slot data-variant>` so SlideRankPill's existing IntersectionObserver finds exactly one section — the play-mode adapter is the section-wrap itself, no special play-mode prop required. Sets `data-play-root` + `data-chrome-hidden` so DeckChrome's `C` keypress fades the whole overlay together.
-
dididecks-ai DeckOverlay--Scroll-UI — the floating overlay layer for Scroll-mode decks
Single mount point that composes the persistent overlay affordances riding over a Scroll-UI deck: the classifier pill (today), variant-cycling nav + counter (Phase 2 via PageAsDeckWrapper), presenter notes (Phase 3), and engagement telemetry (Phase D). Each is a named slot so consumers can rearrange or omit. The overlay element itself is layout-neutral (`display: contents`) — its children own their own fixed/absolute positioning. The Scroll-UI variant of this paired family; see DeckOverlay--Play-UI for the slot-per-route sibling.
-
dididecks-ai DecomposeFirstPlaceholder — empty-slot fallback rendered when a per-slide file doesn't exist yet
Rendered by `/play/[deck]/[variant]/[slot]` when the resolved per-slide file at `{slidesComponentsRoot}/{variant}/{slot}-{slug}.astro` does not exist. Communicates the next action — open the TOC at `?focus={slot}`, rank as redo-worthy, click scaffold to create the stub — without sounding like an error state. The instructive-helpful tone is deliberate: this is the framework's invitation to begin the rank → decompose → recreate loop, not an Astro 404.
-
dididecks-ai DididecksNav — shell-injected global header linking Scroll · TOC · Play · Changelog
Top-of-page nav auto-mounted on every shell-injected route (/toc/*, /play/*) and importable into consumer-owned routes (homepage, scroll-deck variants). Links derive from the consumer's deck registry — Scroll → first deck slug, TOC and Play → first deck + first variant. Brand slot lets each client deck drop in its own wordmark; default is a text wordmark sourced from the integration's `client` option. Reads `Astro.url.pathname` to flag the active link with `aria-current="page"`.
-
dididecks-ai SlideCanvas — pure-CSS 16:9 wrapper that scales a 1920×1080 stage to fit any canvas
Per @dididecks/shell contract, rendered play decks must be static HTML + CSS — no JS in the scaling pipeline. SlideCanvas uses CSS container queries (`container-type: size`) to compute a unitless scale ratio from canvas size to the design size (1920×1080 by default), then applies `transform: scale()` to a `position: absolute` stage. `min(100cqw/designW, 100cqh/designH)` picks whichever axis is the binding constraint so the slide letterboxes correctly when canvas aspect ≠ 16:9. The route's `[slot].astro` is responsible for sizing the canvas; this component just translates that size into a scaled stage.
-
dididecks-ai SlideRankPill — floating five-button classifier for the active slot (rename pending → SlideClassifierPill)
Bottom-right floating pill that shows the active slot's number + title and exposes five enum buttons — Urgent / Could-be-better / Passable / Perfect / Pending. In Scroll-UI it discovers the active slot via IntersectionObserver over `section[data-slot][data-variant]` tags; in Play-UI the DeckOverlay--Play-UI wraps the slide in such a section so exactly one is in view. Hydrates ranks from `GET /api/slide-rank` on mount, posts optimistically on click, fails-soft in production builds. Rename to `SlideClassifierPill` is queued — 'classify' matches the cognitive act more accurately than 'rank' (the enum is a finite tag set, not an ordering).
-
dididecks-ai Sitemap — Living Map of the DidiDecks Universal-Frontend-over-Client-Decks Architecture
A living mini-spec per artifact (route, component, per-slide component) across the dididecks-ai shell and its client-site consumers. Splits across two levels: this directory describes the *universal* shell artifacts inherited by every client deck; per-client overrides and consumer-authored artifacts live in each `client-sites/<client>/context-v/sitemap/`. Each entry is short, kept up-to-date with the running code, and cross-linked so an agent reading any one file can trace composition, theming inheritance, and the plan-of-record that produced it.
-
dididecks-ai /api/slide-decompose — non-destructive stub generator for the Phase 1 → Phase 2 transition
Dev-only API route that writes an empty per-slide stub file at `{slidesComponentsRoot}/{variant}/{slot}-{slug}.astro` in the consumer's working tree. Non-destructive: refuses to overwrite, returns 409 if the file already exists. The stub is a minimal `<section data-slot data-variant></section>` with a generated-by header comment instructing the recreate-do-not-extract discipline (Phase 2 of the deck-iteration-workflow). Static Vercel builds never carry this route; file writes only happen against a local working tree.
-
dididecks-ai /api/slide-rank — read + write per-slide classifier state into the consumer's audits file
Dev-only API route (`prerender = false`) that reads + writes the audit registry at the consumer's `data/audits/slides.json` (default path; configurable via the integration options). GET returns the full ranks map; POST upserts a single `{deckSlug, variantSlug, slot, status}` entry with `rankedAt` ISO timestamp + `rankedBy: 'founder'`. Status `'pending'` is the implicit default — never persisted; a POST with `status === 'pending'` deletes the existing entry. Fails-soft in production static builds (the route doesn't exist there, both GET and POST 404 — SlideRankPill catches and degrades to read-only).
-
dididecks-ai /dev/icons — recurring design-review workbench
Originally a one-off Phase 4 review surface for the dual-surface icon pair on the TOC redesign. Founder picked Pair B 'Frameless glyphs' on 2026-05-17; rather than delete the route, the pattern was kept: a single /dev/* page per project that renders every candidate for a visual-primitive decision side-by-side at multiple sizes, on multiple backgrounds, inside the real composed context (chip-next-to-icon, drift case, missing-file dimmed case). Alternates live one directory deeper at `apps/deck-shell/src/components/icons/alternates/` and remain importable so the design history stays legible. Future icon families, chip variants, badge styles, button states extend this route with additional sections rather than spawning a new /dev/* route per decision.
-
dididecks-ai /play/[deckSlug]/[variantSlug]/ — variant-index redirect to slot 01
Enumerates every (deck, variant) pair from the consumer's deck registry and 302s to /play/{deck}/{variant}/01/. Today the redirect is unconditional; A++.1 will gate it on `SLOTS[variantSlug]?.length` and render a friendly 'no slots yet' panel for variants without entries (currently chroma's proto, enhanced-v1, enhanced-v2 — all return 404s after the redirect because `[slot]` only emits paths from SLOTS).
-
dididecks-ai /play/[deckSlug]/[variantSlug]/[slot]/ — single-slot Play-UI renderer with keyboard nav
Static route emitted for every slot in `SLOTS[variantSlug]`. Resolves the slot's `slug` from the registry, then dynamic-imports the per-slide component at `/src/components/slides/{variant}/{slot}-{slug}.astro` via `import.meta.glob` and renders it inside SlideCanvas; falls back to DecomposeFirstPlaceholder if the file doesn't exist. Today the route directly composes DididecksNav + DeckChrome + SlideCanvas inline; the target shape composes them via `DeckOverlay--Play-UI`, which also wraps the slide in `<section data-slot data-variant>` so SlideRankPill mounts work (closes A++.2 structurally).
-
dididecks-ai /toc/[deckSlug]/[variantSlug]/ — bird's-eye-view audit dashboard with rank pills + scaffold buttons
Static table-of-contents route emitted for every (deck, variant) pair in the consumer's `DECKS` registry. Renders one row per slot from `SLOTS[variantSlug]`, each row showing the slot number, title, five rank pills (mirroring SlideRankPill's enum), a scaffold button that POSTs to /api/slide-decompose, and — when the per-slide file exists — a `[view →]` link to `/play/{deck}/{variant}/{slot}/`. The TOC is the read-only-on-deploy / read-write-in-dev audit surface; it complements (does not replace) the in-place SlideRankPill on scroll-deck routes.
context-v 15
-
augment-it context-v for augment-it
Living documentation for augment-it — specs, habits, prompts, reminders, explorations, issues.
-
dididecks-ai ChromaDB · Deck Outline · Enhanced-v1
The first enhanced variant of Chroma's Series A pitch — diverging from Proto by integrating founder call notes (2026-04-29), live-checked primary sources (2026-05-12), and a tightly-screened layer of analyst-cited category framing. Adds three substantive new slides (Market, Backed by, Capital Efficiency) plus a reframed Use of Funds; locks in the funding picture, the syndicate, the enterprise ASP, and the Q4 2026 revenue milestone. Authored as one coherent through-line so design improvisation can reason about the deck holistically. Management (Jeff Huber) screens before send.
-
dididecks-ai ChromaDB · Deck Outline · Proto
The faithful-recreation baseline of Chroma's live Series A pitch — 13 slides ported from the management-supplied PDF (2026-05-11_Chroma-Series-A_MS-Resort.pdf) into the chroma-decks codebase. This is the substrate every subsequent whole-deck variant (Enhanced-v1, etc.) diverges from.
-
memopop-ai MemoPop AI — Ideogram OG Image Brief
Creative brief for generating OpenGraph and changelog hero images via Ideogram. A house-style prefix and suffix that any per-image scene description plugs into so the family stays coherent across the splash page, changelog entries, and context-v notes.
-
memopop-ai/memopop-orchestrator Introducing a Content Density Mode System
A system-level content mode toggle (redundant vs concise) that alters the behavior of the writer, table generator, and quality agents to match different firm preferences for information density and repetition.
-
memopop-ai/memopop-orchestrator Introducing a Legal Doc Comparator
An agent that compares deal-specific legal documents (SAFEs, convertible notes, term sheets, incorporation docs) against firm-maintained standard templates, surfacing deviations and flagging common legal risks using a shared reference document.
-
memopop-ai/memopop-orchestrator Introducing an Augment Research Writer Agent
A two-phase post-hoc enrichment system that first enhances research files with authoritative third-party citations via Perplexity Sonar Pro, then runs an augmentation writer that weaves those new citations into existing section prose without rewriting content.
-
memopop-ai/memopop-orchestrator Introducing an Enrich Visualizations Agent
An enrichment agent that discovers and embeds publicly accessible charts, graphs, diagrams, and infographics from web sources to visually reinforce key claims in investment memos — the automated equivalent of grabbing charts from Google Image search.
-
memopop-ai/memopop-orchestrator Multi-Agent Orchestration for Investment Memo Generation
An exploration into using AI supervisors and specialized agents to generate high-quality content and documents.
-
memopop-ai/memopop-orchestrator Portfolio Listing Agent and Current Portfolio Section
Design notes for the portfolio_listing_agent that builds a Current Portfolio subsection and structured JSON for LP-commit emerging manager fund memos.
-
memopop-ai/memopop-native memopop-ai/memopop-native/Issues-after-First-Run
-
memopop-ai/memopop-orchestrator memopop-ai/memopop-orchestrator/Getting-Started-with-Tauri
-
memopop-ai memopop-ai/Preferred-Format-for-Changelog
-
memopop-ai memopop-ai/Tasks
-
memopop-ai memopop-ai/Up-and-Running-with-Tmux