docHub three-flag model (2026-06-23 01:00 UTC)

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

TL;DR

Operator clarified: the mavis face is NOT shipped elsewhere, but IS deployed on the docHub site (behind Cloudflare Access) so the operator + Helper can browse it.
Replaced the simple deployable: bool flag with three flags: deployable, embeddable, redistributable.
Updated module.json and build.mjs to use the three-flag model.
Updated user/concepts/three-faces.md to reflect the new model.

The three flags

Each face in module.json now has three boolean flags:

Flag	Question	Default
`deployable`	Does it ship to Cloudflare Pages?	true
`embeddable`	Can FVS apps pull from it via web component?	true
`redistributable`	Can it be exported to other systems?	true

What each face looks like now

Face	deployable	embeddable	redistributable	Auth
user	✅ true	✅ true	✅ true	public
dev	✅ true	❌ false	❌ false	Cloudflare Access
mavis	✅ true	❌ false	❌ false	Cloudflare Access

The previous model had mavis as deployable: false — meaning it didn't ship at all. That was wrong. The operator needs a place to see the Mavis workings, reports, prompts, etc. So mavis is now deployed on the docHub site (same Cloudflare Pages project as user/ and dev/), behind the same auth wall as dev/.

What mavis can never do:

Be embedded in an FVS app (embeddable: false)
Be exported to a different system (redistributable: false)

What mavis CAN do:

Ship to docHub pages so you and Helper can browse it
Be served from https://docshub.pages.dev/mavis/...
Be read by the build script to update the manifest

What changed

module.json v0.3.0 (was 0.2.0): faces.{user,dev,mavis} now have explicit deployable, embeddable, redistributable flags
build.mjs: emits the three flags in the per-face bootstrap.json and the top-level _meta.json
_meta.json: shows all three flags per face, so the deploy pipeline (and any reader) can see what's allowed
user/concepts/three-faces.md: updated table to show the three flags; updated the mavis section to say "deployed behind Cloudflare Access" instead of "never deployed"
Memory: docHub Phase 5 build entry now reflects the three-flag model

The boundary is now well-defined

user/: ships to Pages, embeddable as web component, redistributable. Public.
dev/: ships to Pages, NOT embeddable, NOT redistributable. Behind Cloudflare Access.
mavis/: ships to Pages, NOT embeddable, NOT redistributable. Behind Cloudflare Access. The Mavis team workshop.

The Mavis workshop is the operator's reading room. It exists so you and Helper can see what the Mavis team has been doing, what plans are in motion, what decisions have been made, what dangerous lessons have been learned. It's on the same site, same auth, same login. But it's never the source of an FVS-app pull, never an export target, never a module.

Files

module.json — v0.3.0
build.mjs — updated to emit three flags
_meta.json — top-level index with three flags per face
user/_meta/bootstrap.json — user face bootstrap
dev/_meta/bootstrap.json — dev face bootstrap
mavis/_meta/bootstrap.json — mavis face bootstrap
user/concepts/three-faces.md — updated to reflect three-flag model
Memory: docHub Phase 5 build entry

Cross-references

D-060 — docHub substrate shape
user/concepts/three-faces.md — the architecture doc
module.json — the contract
_meta.json — the top-level index