Company workspaces
The shared operating surface for one company. A tile hierarchy governs what exists: each company — and each person — sees their authorized tiles and child tiles, and nothing beyond them.
The Framework
One congruent framework with consistent behavior across the parent firm, its subsidiaries and acquisitions, and participating clients. Consistency of structure — never pooling of data.
What a company knows, written down once, owned by that company, and findable forever.
Every company gets a consistent, private, numbered knowledge structure. Every record in a Vault carries its company, its owner, its source, its version, its approval, and its review date. Inherited templates stay distinguishable from company-specific records, so a company always knows what it adopted and what it wrote itself.
AI over a Vault is permission-scoped retrieval with citations — lookup, not invention. "Doesn't know" is a valid answer, and the Vault is never silently used to train anything shared. The full discipline, including AI cost and model rules, is on the Knowledge & AI Efficiency page.
A generated crosswalk that gives every company, asset, and person a stable reference — and links websites, forms, proposals, documents, and audits into the Vault structure.
Because the Index is generated from the registry rather than hand-maintained, it cannot quietly drift from the records it describes. When something is corrected, the correction is documented, the superseded reference is preserved as an alias, and retired references are never reused.
The shared operating surface for one company. A tile hierarchy governs what exists: each company — and each person — sees their authorized tiles and child tiles, and nothing beyond them.
The owner's view over their whole company: pipeline, knowledge, reporting, and the cost ledger, in one place.
Role-scoped personal views over the same records — not duplicate databases. A person can hold several roles and memberships; access is verified per action, not assumed from a job title.
Aggregate-level visibility across the group: counts, status, health. Record-level detail only under an explicit, logged grant from the company owner — revocable by that owner. The full model is stated on the Security & Data Handling page.
No. Each company keeps its own records in its own workspace. Parent oversight is aggregate-level visibility, or record-level access only under an explicit, logged grant from the company owner. Consistency of structure is not pooling of data.
A generated crosswalk that gives every company, asset, and person a stable reference and links websites, forms, proposals, documents, and audits into the Knowledge Vault structure. It adopts established Business Hub OS numbering through an explicit crosswalk rather than replacing it; that crosswalk is still being reconciled.
A consistent, private, numbered knowledge structure for one company. Every record carries its company, owner, source, version, approval, and review date. AI retrieval over a Vault is permission-scoped lookup with citations, and "doesn't know" is a valid answer.
Start with a single workspace and a single workflow. The framework proves itself there first.