Codex — docHub

The final codex entry for docHub the App. Per FVW v6 §11, every Recipe Book at every fractal level has a codex.md that records the final shape of the scope.

Identity

Name: docHub
Brand: fv-dochub
URL: https://fv-dochub.pages.dev/
Repo internal name: freshvibe-dochub
Cloudflare project: fv-dochub
Version: 0.4.0 (Q1 prompt archive shipped 2026-06-23)

Shape

docHub is a two-view substrate (FWV v7 §23). It is BOTH:

A standalone workspace the operator browses at fv-dochub.pages.dev
A substrate FVS apps pull chips and modules from via web components

It has three faces (D-060):

┌─────────────────────────────────────────────────┐
│ fv-dochub.pages.dev                              │
├─────────────────┬───────────────┬───────────────┤
│   user/         │   dev/        │   mavis/      │
│   public        │   doctrine    │   coordination│
│   embeddable    │   gated       │   gated       │
│   9 files       │   16 files    │   38 files    │
└─────────────────┴───────────────┴───────────────┘

Chips (level 1 — atomic, reusable)

Chip	Source	Used by
`<anchor-bar>`	user/assets/anchor-bar.js (11.6KB)	docHub sidebar, prompt viewer breadcrumb, future FVS chips
`<doc-hub>`	user/assets/embed.js (5.5KB)	FVS app integration (embedded docs)
Tabler-style SVG icons	inline in anchor-bar.js	nav items, section headers

Modules (level 3 — cluster, aspirational)

Per D-066, these are folder-shaped today but cluster-of-feature-shape in principle:

Module	Path	Cluster
prompt-archive	mavis/prompts/	browse, search, filter-by-project, filter-by-tag, view-detail, link-to-source
decision-log	mavis/decisions/	view-list, view-detail, mark-superseded, link-related, group-by-topic, trace-atlas
lane-coordination	mavis/lanes/	spawn-mavis, ping-lane, watch-lane, report-state, archive-lane
plan-tracker	mavis/plans/	list-plans, view-phase, mark-phase-done, link-reports, track-blockers
report-feed	mavis/reports/	list-reports, view-report, link-decisions, link-plans, filter-by-lane

Substrate adoption (FWV v7 §23 view 2)

From FreshCards substrate: card geometry (4/8/12/16/24 padding, 6/8/12 radius, 1px border), semantic roles (focus/action/navigation/status/filter/info), lifecycle states (dormant/active/expanded/peeked/filtered/grouped), CardChipSystem
From Vibe Hub substrate (Q2): TBD

Cross-references

recipe.md — the human-readable recipe
lineage.json — the machine-readable lineage
mavis/decisions/D-066-anchor-bar-is-a-chip-not-a-module.md — the level-classification decision
pact/freshvibe-way-v7/23-two-view-substrate.md — the two-view substrate doctrine
pact/freshvibe-way-v6/10-modules-as-clusters.md — the 5-level hierarchy
pact/freshvibe-way-v6/11-recipe-book.md — the recipe book fractal
pact/platform/cards/cards.md — the FreshCards substrate