Five top-level axes. The vault is the platform's multi-tenant shape. Every Cloudworkz tenant carries the same Box pattern. Items marked * are open for the Werner walk.
Every company carries the same four-Box pattern. Cloudworkz operates itself by the model it sells, so the structure proves the product. The Brain-Box is the canonical source the rest of the system relationally pulls from.
One shape, every company. The Data slot is open and decides at CF-3 with Werner.
CLOUDZ is the operating model that runs on top of the Box pattern. Brain-Box is the source of truth; CLOUDZ Individual Cloud is the per-seat surface that pulls from it.
Five tenants on the structure. The reference tenant (Cloudworkz) dogfoods the platform.
Individual Cloud, Team / Executive Cloud, Agents / Roles. The cascade that turns the Brain-Box plan into daily tasks. Per-seat CLOUDZ in the context of the whole model.
The chain that turns vision into daily tasks: each agent is Responsible at its own tier and collaborates with the tiers above and below.
Same tier owners appear in the cascade (Individual Cloud) and the schema (Role table). Mapping these to the current personas, Roxi Lexi NEO is open. Decided at CF-6 with Werner.
The relational model the 2020 deck called a "transactional database", reconstructed from the sheet columns. Hover an entity to trace its relationships. Source: Individual Cloud + Executive Cloud + Service Design (Cloudworkz, 2020).
What's settled and what Werner is deciding. Plus the reconciliation log from combining the three source artefacts (5-axis V2 + Werner mock + CLOUDZ model). Anything starred is open.
Three artefacts combined into this Walk. Notable inconsistencies surfaced and resolved during the merge.
The 5-axis V2 structure and the Werner mock use "Brain-Box" (hyphenated). The original CLOUDZ operating-model file used "Brain Box" (no hyphen).
Resolved: "Brain-Box" is canonical, following the 2026-05-31 V2 structural decision. Every reference in this Walk uses the hyphen.
The 5-axis structure and Werner mock enumerate four Boxes per tenant (Brain-Box / Brand-Box / Biz-Box / Data slot). The CLOUDZ operating-model file only referenced Brain-Box as a canonical source, with no mention of the broader pattern.
Resolved: Tenant pattern view makes the four-Box pattern explicit. CLOUDZ model view names Brain-Box as one slot inside that pattern, so the two reconcile.
The 5-axis V2 structure uses L0 = BOSS, L1-L4 = layers, L5 = Services. The V2.1 product taxonomy (Product Map, 2026-05-28) uses an 8-layer hierarchy: BOSS, CLOUDZ, Boxes, ACID Suite, Agents, Services, Modules, OS infrastructure.
Open. These models answer different questions, vault organisation (V2) versus product taxonomy (V2.1). But both use "L0..." vocabulary. Werner walk should land the naming reconciliation: are these compatible expressions of the same hierarchy, or two parallel hierarchies that share vocabulary?
The 5-axis structure positions CLOUDZ inside the Products axis as "the operating model" (flagship). The CLOUDZ operating-model file deep-dives into its Individual / Team / Agents internals.
Resolved: No real conflict. CLOUDZ is a flagship product under Products axis, and the operating-model view shows how it works internally. Both expressions are consistent.
The CLOUDZ Agents view names cascade roles (Business / Campaign / Project / Account / Customer Service Manager). Mapping to current personas (Roxi / Lexi / NEO) is open. The Werner mock flags CF-6 as the decision point for "NEO / agent-persona mapping".
Open. Both source artefacts agree this is open. Werner walk lands the mapping.
This Walk combines three rebuilds. Each is preserved at its own deploy path for direct reference.