← Corpus / chroma-decks / sitemap
Slot 05 — Bottleneck (decompose-stub only — Play-UI renders empty section)
Decompose-stub generated by `/api/slide-decompose` during the Phase A.6 smoke-test. Empty `<section data-slot="05" data-variant="enhanced-v3"></section>`; never recreated. /play/pitch/enhanced-v3/05/ renders this empty section rather than falling back to DecomposeFirstPlaceholder, because the file *exists* even though it has no content. Distinct from slots that have no file at all (those fall back correctly).
- Path
- sitemap/slides/enhanced-v3/05-bottleneck.md
- Authors
- @dididecks/shell (generated)
Slot 05 — Bottleneck (stub)
Edge case worth flagging
A stub file exists on disk but has no body content. The shell’s render path treats this as “file present → render the component.” Result: Play-UI renders an empty <section>. The DecomposeFirstPlaceholder fallback only fires when the file is absent.
If founder-facing UX wants “decompose-stub-but-not-yet-recreated” to render as a distinct placeholder, that’s a small shell-side enhancement: check for component emptiness (or a data-stub marker on the section) and substitute the placeholder. Tracked here as an open question; the framework today is consistent if not maximally helpful.
Related
- [[01-cover]], [[15-ask]] — fully recreated siblings.
- [[../../../../../../ai-labs/dididecks-ai/context-v/sitemap/routes/api-slide-decompose]] — origin endpoint.
- [[../../../../../../ai-labs/dididecks-ai/context-v/sitemap/components/DecomposeFirstPlaceholder]] — fallback that this stub prevents from firing.