Trace — docHub Recipe Book
The recorded history of changes to docHub the App. Per FVW v6 §11, the 5th piece of a Recipe Book.
Chronological history
2026-06-23T17:00:00Z — D-066 corrects anchor-bar classification
- What changed:
<anchor-bar>was framed as a "reusable module" in D-065. D-066 corrected this to "reusable chip" per FWV v6 §10 (a module is a cluster of features; anchor-bar has only one capability, so it's a chip). - Why: The doctrine says a module must be a cluster where removing one feature breaks the module. anchor-bar's icon, count, and active-state features are all independently removable without breaking the component. Therefore chip.
- Impact on docHub App: docHub adopts 2 chips (anchor-bar, doc-hub) and has 5 aspirational modules (folder-shaped, not yet cluster-promoted).
2026-06-23T16:14:00Z — Q1 prompt archive shipped
- What changed: 238 prompts (237 from
avidtech6/AvidCreation+ 3 docHub top-level) live atfv-dochub.pages.dev/mavis/prompts/_viewer/. Build pipeline:pact/scripts/build-prompt-archive.pyemits 268KB manifest. Brand updated to "fv-dochub" with Tabler chat-bubble icon in sidebar. - Why: Operator asked to include the AvidCreation prompt archive into docHub (Q1 deliverable per spec).
- Impact on docHub App: the
prompt-archivemodule has its data + viewer. Still needs: formal module-register entry, per-module recipe book.
2026-06-23T15:46:00Z — D-064 clean Cloudflare URLs
- What changed: Created
fv-dochub.pages.dev(clean) andfv-vibehub.pages.dev(clean) Cloudflare Pages projects. Deleteddocshub-1pi.pages.devandvibe-hub-5k3.pages.dev(the auto-suffixed duplicates). - Why: Operator asked for clean URLs. Cloudflare auto-suffixes only when the bare name is taken by another account; both
fv-dochubandfv-vibehubwere unclaimed, so we got them clean. - Impact on docHub App: brand, URL, and Cloudflare project name all unified to
fv-dochub. Repo internal name staysfreshvibe-dochubper operator directive.
2026-06-23T15:55:00Z — anchor-bar + breadcrumb shipped
- What changed:
<anchor-bar>web component (11.6KB) extracted touser/assets/anchor-bar.js. Wired into docHub SPA shell sidebar AND prompt viewer breadcrumb. - Why: Operator asked for a reusable nav module that FVS apps can lift.
- Impact on docHub App: sidebar uses anchor-bar instead of inline HTML; prompt viewer has breadcrumb back to docHub home; FVS apps can now
<script src="https://fv-dochub.pages.dev/assets/anchor-bar.js">to get the same nav primitive.
2026-06-23T15:00:00Z — D-063 prompt archive migration
- What changed: 237 prompts copied from
avidtech6/AvidCreationinto docHub'smavis/prompts/<project>/. Viewer SPA ported as-is. Build script adapted. - Why: Operator Q1 deliverable.
- Impact on docHub App: mavis face grew from 8 to 38 files (most of it prompt content).
2026-06-22T22:30:00Z — docHub Phase 5 build (initial scaffold)
- What changed: FreshCards substrate shape + 3-flag model + 64 files across 3 faces.
- Why: Initial Phase 5 implementation per D-060.
- Impact on docHub App: full structure built, deployable, awaiting operator trigger.
2026-06-22T20:00:00Z — D-060 substrate shape
- What changed: docHub adopted FreshCards substrate shape with three-flag model extension.
- Why: Operator asked for substrate that mirrors FreshCards + can be embedded in FVS apps.
- Impact on docHub App: shape defined, all subsequent decisions reference D-060.
Forward-looking delta
Things to add to this trace as they happen:
- [ ] Cloudflare Access setup on
/dev/*and/mavis/*(operator task) - [ ] Q2 Vibe Hub ships at
fv-vibehub.pages.dev— adds Vibe Hub substrate adoption - [ ] Per-module Recipe Books for the 5 docHub modules
- [ ] Module-register.json entries for each module (so FVS apps can adopt them)
- [ ] Cookbook docs at
cookbook/for common adoptions (FVS Vibe Chat integration, FVS VibeScope integration, third-party app integration)