docHub three-face restructure (2026-06-23 00:55 UTC)

Date: 2026-06-23 00:55 UTC Lane: helper Session: 412100071272671 Status: complete

TL;DR

1. Operator asked: "the doc hub probably needs 3 faces user dev and mavis only mavis is not for deployment its our own tools etc."
2. docHub restructured from two faces (user, dev) to three faces (user, dev, mavis).
3. The mavis face is deployable: false — never shipped, never embedded, never distributed.
4. Build script enforces the boundary by walking each face separately and emitting per-face manifests.

What was moved

From dev/ to mavis/ (Mavis coordination, not doctrine):

• lanes/ (cards, chrome, fvre, doctrine, helper) — 5 lane profiles
• prompts/ (operator-relay, helper-to-cards) — 2 prompt log entries
• bootstrap/mavis-protocols.md, bootstrap/lane-map.md, bootstrap/open-questions.md
• reports/ (state-check, pat-rotation, dup-cleanup, dochub-build) — 4 reports
• decisions/D-057..D-062 — 6 internal decisions
• plans/phase-1..5 — 5 phase plans
• dangerous/case-variant-dups.md, destructive-ops-checklist.md, memory-drift.md — 3 Mavis-specific lessons
• coordination/_legacy-projects.md — uncategorized coordination

Stays in dev/ (FVS doctrine, internal but not Mavis-only):

• doctrine/ — 5 files (pact-lookup, chip-system, anti-patterns, governance, fvw-v8)
• decisions/D-056 — the canonical FreshCards substrate decision (mirrors the pact)
• projects/ — 6 project pages
• bootstrap/README.md — orientation for any AI waking up
• dangerous/github-pat-leak.md — general security lesson

Stays in user/ (public, embeddable):

• index.md (root, now references three faces)
• getting-started/
• projects/ (4 user-facing project pages)
• concepts/ (substrate primer + new three-faces doc)
• reference/ (substrate contract schema)
• assets/embed.js (the web component)

What changed in the substrate contract

module.json v0.2.0:

{
  "faces": {
    "user":  { "deployable": true,  "auth": "public",                              "audience": ["end-users", "FVS-apps"] },
    "dev":   { "deployable": true,  "auth": "cloudflare-access-email-allowlist", "audience": ["operator", "ai-agents", "fresh-doctrine-readers"] },
    "mavis": { "deployable": false, "auth": "cloudflare-access-email-allowlist", "audience": ["operator", "helper-mavis", "lane-mavises"] }
  }
}

The deployable: false flag on mavis is the key new field. The build script and any future deploy pipeline can refuse to ship mavis content.

What changed in the build script

build.mjs (v0.2.0) now:

1. Walks each face separately (user, dev, mavis)
2. Emits per-face manifest.json and bootstrap.json
3. Mavis artifacts go to mavis/_meta/, NOT to dev/_meta/ or user/_meta/
4. Top-level _meta.json lists all three faces with file counts + the deployable flag

The user face is what the <doc-hub> web component reads. The web component fetches /api/user/manifest.json — it never sees mavis content.

New docs

• user/concepts/three-faces.md — explains the three-face architecture for end-users and any AI reading the user face
• user/index.md — updated to reference all three faces
• module.json — version bumped to 0.2.0 with three-face design

Open

• Deploy still pending operator trigger. Will deploy user/ + dev/ to docshub.pages.dev (new Cloudflare Pages project). Mavis stays in our sandbox.
• Cloudflare Access on /dev/ — operator task. Email allowlist with at least avidtech6@gmail.com.
• cards Mavis reply — still pending from the 2026-06-23 00:30 UTC ping (Region Schema confirmation).

Cross-references

• D-060 — docHub substrate shape (now v0.2.0 with three faces)
• Module contract: docshub/module.json
• Top-level index: docshub/_meta.json
• User face manifest: docshub/user/_meta/manifest.json
• Dev face manifest: docshub/dev/_meta/manifest.json
• Mavis face manifest: docshub/mavis/_meta/manifest.json
• Build script: docshub/build.mjs