Plain-language definitions for the vocabulary behind Sixfold OS — from Framework-as-a-Service and multi-tenancy to design tokens, grounded AI, maturity scoring, and governance. 122 terms, filterable by category and letter, in English and German.
Search across every term and definition, narrow by category, or jump by letter. Each definition links to the related terms around it.
Structured notes on roles, states, and behavior that make components accessible.
Accessibility annotations are structured, documented notes on a component's roles, states, keyboard behavior, and semantics that specify how it must work for assistive technology. They turn accessibility from an afterthought into a first-class part of the component's specification. HexaQence captures accessibility documentation so it is auditable against standards like WCAG.
An AI system that plans and takes multi-step actions toward a goal using tools.
An agent is an AI system that pursues a goal by planning, calling tools, and taking multiple steps, rather than producing a single one-shot answer. Agents are powerful but require strong guardrails and scoping to stay safe. In Sixfold OS, agents operate within tenant scope and grounded orchestration so their autonomy never bypasses governance.
A system structured so AI agents can act on it safely and within scope.
Agent-ready describes a system whose data, contracts, and permissions are structured so AI agents can operate on it safely, predictably, and within scope. It requires clear API contracts, provenance, and enforced scoping — exactly what governance-by-design provides. Sixfold OS is agent-ready because its layers of truth and tenant scoping give agents a safe surface to act on.
The agreed, typed interface between a service and its consumers.
An API contract is the explicit, typed agreement describing how a service may be called and what it returns, so producers and consumers can evolve independently without breaking each other. Stable contracts are the basis of composability and agent-readiness. Sixfold OS keeps API contracts typed and validated so modules connect predictably.
Logic that determines which standards and rules apply to a given context.
An applicability engine is the logic that decides which standards, policies, and rules apply to a given context — a product, region, or workspace — so teams are held only to what is genuinely relevant. It turns a large body of standards into a precise, contextual checklist. HexaNorm's applicability engine is what makes its governance scalable rather than one-size-fits-all.
A tamper-evident, chronological record of who did what and when.
An audit trail is a chronological, tamper-evident record of actions and changes — who did what, when, and to which resource. It is the backbone of accountability and compliance, letting any state be traced back to its cause. Because Sixfold OS captures evidence continuously, the audit trail is a byproduct of normal work rather than a separate effort.
An early release to a limited, invited group before general availability.
A closed beta is an early release of a product to a limited, invited group of users before general availability, used to gather real-world feedback and harden the product under controlled conditions. It balances real usage against risk. Sixfold OS uses closed beta phases to validate modules with committed early customers before wider rollout.
A group sharing a trait or start point, analyzed together over time.
A cohort is a group of users or entities that share a defining characteristic or start point — for example, everyone who onboarded in a given month — analyzed together to reveal patterns over time. Cohort analysis exposes retention and behavior that aggregate averages hide. HexaSight supports cohort views so trends are read within comparable groups, tenant-scoped.
Conforming to applicable laws, standards, and internal policies, provably.
Compliance is the state of provably conforming to the laws, standards, and internal policies that apply to your context, backed by evidence rather than assertion. It is only sustainable when it is continuous and evidenced, not a periodic scramble. HexaNorm makes compliance a byproduct of governed work through its standards and applicability engine.
Fields where continuous, evidenced compliance is a core operating cost.
Compliance-heavy sectors are fields where meeting and proving conformance is a continuous, expensive part of operating — think regulated finance, health, energy, or critical infrastructure. Manual, periodic compliance does not scale for them. Sixfold OS lowers this cost by making compliance a byproduct of governed, evidenced work through HexaNorm.
The structured breakdown of a component into its parts, states, and rules.
Component anatomy is the explicit breakdown of a UI component into its constituent parts, states, variants, and the rules that govern them. Documenting anatomy turns a component from an opaque artifact into a shared, teachable specification. HexaCore surfaces component anatomy so implementers and reviewers work from the same structure.
Rules and review that keep components consistent, accessible, and up to standard.
Component governance is the set of rules, ownership, and review that keeps a component library consistent, accessible, and aligned with the design system as it evolves. Without it, components drift, duplicate, and decay. HexaGrid provides component governance by keeping the authoritative component structure in sync with Figma and standards.
Independent modules combine cleanly into larger systems without hidden coupling.
Composability is the property that well-bounded parts can be combined and recombined through clear contracts, so the whole is more capable than any single piece. It depends on stable interfaces and single ownership of each concern. Sixfold OS modules are composable: each owns a distinct layer of truth and connects to the others through defined contracts rather than tangled dependencies.
Informed, recorded permission to collect or process a person's data.
Consent is the informed, freely given, and recorded permission for data to be collected or processed, a legal and ethical prerequisite under regimes like GDPR. Respecting consent means honoring it in every downstream use, not just at collection. Sixfold OS treats consent as a governed signal that gates telemetry and analytics throughout the platform.
The structured schema that defines how a piece of content is shaped.
A content model is the structured schema that defines the fields, types, and relationships of a kind of content, separating what content is from how it is presented. Modeling content explicitly makes it reusable, validatable, and localizable. Sixfold OS keeps content models distinct from read models and source-of-truth models so each stays clean.
The cockpit that lets you enter and orchestrate across all workspaces and modules.
The Control Room is the top-level cockpit and workspace chooser for Sixfold OS — the launcher through which people enter the right workspace and move across modules. It provides a single, access-controlled entry point to the whole platform. From the Control Room, the coherence of the operating system becomes tangible rather than abstract.
Control over the geographic location where data is stored and processed.
Data residency is the requirement and ability to control where data is physically stored and processed — for example, keeping EU customer data within the EU. It is a legal and trust concern for regulated and international buyers. Sixfold OS treats data residency as a governed configuration so tenants can meet their jurisdictional obligations.
A durable record of a decision, its context, options, and rationale.
A decision record — often an Architecture Decision Record (ADR) — captures a significant decision along with its context, the options considered, and the rationale for the choice. It makes decisions durable and reviewable long after the meeting is forgotten. In HexaQence, decision records are structured evidence that feeds the evidence loop and audit trail.
Accumulated inconsistency and shortcuts that make design harder to change later.
Design debt is the accumulated cost of inconsistent, duplicated, or off-standard design work that makes future change slower and riskier — the visual analogue of technical debt. It grows when there is no single source of design truth. Sixfold OS reduces design debt by making tokens and components governed data rather than repeatedly re-created artifacts.
A governed set of tokens, components, and rules for building consistent products.
A design system is the shared, governed set of design tokens, components, patterns, and usage rules that lets many teams build consistent products. It is more than a component library: it encodes decisions and standards so consistency is the default. In Sixfold OS the design system spans HexaGeist, HexaGrid, HexaKit, and HexaCore as one connected chain.
Named design decisions (color, spacing, type) stored as data for reuse.
Design tokens are named, structured values — colors, spacing, typography, radii — that capture design decisions as data instead of hard-coded styles. Because they are the single source for these decisions, changing a token updates every product that consumes it. In Sixfold OS tokens are authored in HexaGeist and delivered at runtime through HexaKit.
Companies where design quality and consistency are strategic priorities.
Design-led organizations treat design quality, consistency, and accessibility as strategic priorities rather than a finishing layer, and they invest in design systems accordingly. They feel design debt acutely and need a single source of design truth. Sixfold OS serves them through the HexaGeist to HexaGrid to HexaKit to HexaCore chain.
Docs authored, versioned, and reviewed with the same rigor as source code.
Documentation-as-code treats documentation as structured, versioned artifacts that are authored, reviewed, and validated with the same discipline as software. Docs become linkable, testable, and portable instead of stale prose in a wiki. HexaQence embodies this approach so that knowledge stays current, governed, and exportable.
Software sold to large organizations with demanding security and scale needs.
Enterprise SaaS is software sold to large organizations that expect single sign-on, role-based access, strong isolation, SLAs, and data-residency options. These buyers demand governance and scale that consumer tools never face. Sixfold OS is built for enterprise SaaS realities: multi-tenant, RBAC-gated, and governed from the first click.
A scoped runtime context (e.g. dev, staging, production) within a module.
An environment is a scoped runtime context — such as development, staging, or production — that isolates configuration and data at a level below the module. It lets teams test and promote work safely without contaminating live data. Environment is the fourth level of the Sixfold OS scoping hierarchy, between module and project.
A structured check of the ethical implications of a decision or feature.
An ethics review is a structured, documented assessment of the ethical implications of a decision, feature, or use of data or AI, before it ships. It brings foreseeable harms and fairness concerns into the decision explicitly rather than by accident. HexaNorm supports ethics review as a governed workflow, with its outcome captured as evidence.
Systematic tests that measure whether AI outputs meet quality and safety bars.
Evals are systematic evaluations — test suites and scored checks — that measure whether an AI workflow's outputs meet defined quality, accuracy, and safety bars. They make AI behavior measurable and regression-testable instead of anecdotal. HexaMind treats evals as first-class so AI changes are validated the way code changes are.
An ordered flow of recorded events that other parts of the system react to.
An event stream is an ordered, durable sequence of recorded events describing what happened in the system, which other components consume to react, build read models, or trigger jobs. It decouples producers from consumers and provides a natural audit substrate. Sixfold OS uses platform event contracts so modules communicate through events rather than tight coupling.
A durable, traceable record that backs a claim, decision, or standard.
Evidence is any durable, traceable record — a decision, a document, a measurement, an asset — that backs a claim and can be audited later. Treating work products as evidence is what lets governance be continuous rather than reconstructed. Sixfold OS captures evidence at the moment of work so that every claim is defensible.
Decisions and work continuously produce evidence that feeds back into governance.
An evidence loop is the closed cycle in which every decision, design, and workflow leaves a durable, traceable record that then informs analytics, maturity scoring, and the next decision. It turns governance from periodic audits into a continuous, self-documenting flow. Sixfold OS is built around the evidence loop: work is captured as evidence at the moment it happens, not reconstructed afterward.
The collaborative design tool that HexaGrid links to for design-system truth.
Figma is the widely used collaborative interface-design tool where teams create and maintain visual designs and component libraries. In Sixfold OS, HexaGrid links to Figma so that design decisions made there are captured as governed, structured data rather than left as disconnected files. This link keeps the design tool and the design-system truth aligned.
Banking, payments, and finance products under heavy regulatory scrutiny.
Financial services, including fintech, covers banking, payments, lending, and investment products operating under intensive regulatory scrutiny and demanding audit requirements. Trust, traceability, and controlled change are existential rather than optional. Sixfold OS suits fintech teams that must move quickly while keeping every decision governed and evidenced.
Analytics you collect and own directly, not via a third-party service.
First-party analytics is measurement collected and owned directly by the platform, rather than routed through third-party trackers that also serve their own interests. It gives you control, privacy, and provenance over your own data. HexaSight is the first-party intelligence layer of Sixfold OS, keeping analytics governed and tenant-scoped.
The map of the whole framework: modules, layers, and how they relate.
The Framework Atlas is the explanatory map of Sixfold OS: it lays out the modules, their layers of truth, and the connections between them so newcomers and buyers can grasp the whole. It is the conceptual counterpart to the Sixfold Cube's visual model. The Atlas is how the operating model is made legible before you ever log in.
A delivered operating model, not just software: the framework itself is the product.
Framework-as-a-Service (FaaS) delivers an opinionated operating model — how work is structured, governed, and evidenced — as a hosted, continuously maintained product. Instead of buying isolated tools and assembling process yourself, you adopt a coherent framework whose modules, standards, and guardrails are versioned and kept current by the vendor. Sixfold OS is a FaaS: the framework, not a single feature, is what you subscribe to.
A backend layer that assembles session, scope, and read models for the apps.
A gateway or backend-for-frontend (BFF) is a server layer tailored to the needs of the front-end apps, resolving session, tenant and workspace context, scopes, read models, and events in one place. It keeps clients simple and enforces scoping centrally. In Sixfold OS the gateway is the trusted point where tenant context is established for every request.
The EU regulation governing how personal data is collected and processed.
The General Data Protection Regulation (GDPR) is the European Union regulation governing how personal data may be collected, processed, stored, and transferred, with strong rights for individuals and significant penalties for breaches. It makes consent, purpose limitation, and data residency concrete obligations. Sixfold OS builds consent handling and tenant scoping to support GDPR alignment.
Rules, roles, and audit are built into the system, not bolted on afterward.
Governance-by-design means standards, access rules, and auditability are structural properties of the platform rather than manual processes layered on top. Because scoping, roles, and evidence capture are enforced by the software itself, compliance is a default outcome instead of an afterthought. Every Sixfold OS module inherits this posture: you cannot easily do the ungoverned thing.
Coordinating AI steps over the platform's own governed sources of truth.
Grounded orchestration is the coordination of AI steps and tools where every step is anchored in the platform's own governed data rather than the model's unverified recall. Because outputs derive from real sources, they are traceable, evaluable, and safer. HexaMind is built on grounded orchestration so AI enhances the operating model without undermining its governance.
Constraints that keep AI behavior within safe, allowed boundaries.
Guardrails are the constraints — input filters, output checks, allowed tools and scopes — that keep AI behavior within safe and permitted boundaries. They ensure the system fails safe rather than doing something harmful or out of scope. HexaMind enforces guardrails as part of grounded orchestration, alongside evals and safety boundaries.
When an AI states something plausible-sounding but false or unsupported.
A hallucination is when an AI model produces output that sounds plausible but is factually wrong or unsupported by any source. It is the central reliability risk of generative AI in serious settings. Grounding techniques like RAG and strict provenance are how Sixfold OS reduces hallucination and keeps AI outputs traceable and trustworthy.
Health products handling sensitive data under strict safety and privacy rules.
Healthcare and healthtech cover products that handle sensitive personal health data under strict safety, privacy, and accessibility requirements. Errors carry human and legal consequences, so evidence, provenance, and access control are paramount. Sixfold OS gives healthtech teams a governed, accessible, and auditable way to build and document their products.
Component implementation and the design-system viewer.
HexaCore is the module that owns component implementation and the design-system viewer — the built, inspectable components that realize the tokens and structure defined in HexaGrid. It closes the gap between designed intent and shipped code by making the live component library browsable and connected to its lineage. HexaCore is where the design system becomes something you can actually build with.
Design-token studio where token values are authored and governed.
HexaGeist is the design-token studio: the module where token values, themes, and their relationships are authored, organized, and prepared for export. It sits at the head of the token pipeline that feeds runtime tokens into products. HexaGeist is where the raw material of the design system — its tokens — is defined and kept coherent.
Design-system truth and Figma-linked governance for tokens and components.
HexaGrid is the module that owns design-system truth: the authoritative structure of tokens, components, and their relationships, kept in governed alignment with Figma. It is where design decisions become structured, versioned data rather than scattered files. Downstream modules consume HexaGrid as the single source of design truth.
Runtime tokens, themes, and CSS variables consumed by products.
HexaKit is the runtime layer of the design system: the packaged tokens, themes, and CSS variables that products actually consume at runtime. It is the delivery end of the token pipeline, translating authored tokens into live styling. HexaKit is how design decisions made upstream reach real screens without manual restyling.
Grounded AI workflow orchestration with prompts, evals, and safety.
HexaMind is the module for grounded AI: it orchestrates AI workflows over the platform's own governed data, managing prompts, evaluations (evals), and safety boundaries. Because it is grounded in real sources of truth, its outputs are traceable and evaluable rather than free-floating. HexaMind is how Sixfold OS applies AI without giving up governance or provenance.
Governance, standards, compliance, and the applicability engine.
HexaNorm is the governance module: it owns standards, compliance, ethics and audit workflows, and an applicability engine that determines which standards apply to which context. It turns policy from static documents into rules that are enforced and evidenced across the platform. HexaNorm is how governance-by-design becomes concrete and auditable.
Structured documentation, evidence, decisions, and accessibility docs.
HexaQence is the module for structured documentation, evidence, and decisions — including accessibility documentation and portable knowledge flows. It turns docs from static prose into governed, versioned, and linkable records that participate in the evidence loop. HexaQence is where product knowledge is captured so it can be trusted, audited, and moved.
Environmental impact intelligence: standards, impact, and maturity.
HexaSeed is the module for environmental impact intelligence — environmental standards, measured impact, and sustainability maturity. It brings the same governed, evidenced approach to environmental performance that the other modules bring to design and decisions. HexaSeed lets sustainability be tracked and scored as rigorously as any other product concern.
Analytics, KPIs, maturity scoring, and the intelligence cockpit.
HexaSight is the analytics and intelligence module: it owns KPIs, maturity scoring, and the intelligence cockpit that reads across every other module. As the first-party intelligence layer, it turns evidence and telemetry into decisions rather than raw dashboards. HexaSight is where the organization sees how mature, healthy, and aligned its product practice actually is.
Brand and creative visual-evidence runtime.
HexaVision is the brand and creative module: a visual-evidence runtime that captures and governs brand and creative assets as first-class, traceable evidence. It ensures that visual and brand work is not an ungoverned side channel but part of the same evidence loop. HexaVision keeps creative output aligned with the design system and brand standards.
Organizations with many teams that need shared truth to stay coherent.
High-scale product teams are organizations large enough that coherence stops being automatic — many teams, products, and decisions risk drifting apart without shared truth and governance. They need one operating model rather than many local conventions. Sixfold OS gives them shared sources of truth so scale does not become fragmentation.
A person reviews or approves consequential AI actions before they take effect.
Human-in-the-loop means a person reviews, approves, or corrects an AI system's output at defined checkpoints before consequential actions take effect. It keeps accountability with people for high-stakes decisions. Sixfold OS places human-in-the-loop review gates where AI meets governance-critical steps, complementing automated evals and guardrails.
The authenticated representation of a person or system in the platform.
An identity is the authenticated representation of a person or system — established via single sign-on — that memberships and roles attach to. Separating identity from membership lets one authenticated identity hold different access across tenants and workspaces. Sixfold OS authenticates identities through Auth0 and resolves their access via the RBAC chain.
The unified view that reads across modules to surface decisions and health.
The intelligence cockpit is HexaSight's unified, cross-module view that turns KPIs, maturity scores, and telemetry into a coherent picture for decision-making. Rather than isolated dashboards, it reads across the whole operating system to show health, alignment, and what needs attention. It is where analytics becomes decision support.
A key metric chosen to track progress against a specific objective.
A key performance indicator (KPI) is a deliberately chosen metric that tracks progress against a specific objective, distinguishing signal from the noise of all measurable things. Good KPIs are few, owned, and tied to decisions. HexaSight defines and computes KPIs across modules so performance is measured consistently and tenant-scoped.
A distinct concern (design, docs, AI, analytics) owned authoritatively by one module.
A layer of truth is a bounded concern — design, documentation, components, AI, analytics, or governance — for which exactly one module is the authoritative owner. Separating layers of truth prevents overlap and contradiction, and lets each module go deep without stepping on the others. The Sixfold Cube is essentially a stack of clearly separated layers of truth.
A content model that carries per-locale variants of translatable fields.
A localized content model is a content model designed to hold per-locale variants of translatable fields, keeping structure shared while text differs by language. It keeps localization first-class instead of retrofitted, so multiple languages stay in sync. This glossary itself uses a localized model: each term carries both English and German.
A staged framework describing levels of capability from ad-hoc to optimized.
A maturity model is a staged framework that describes levels of capability for a practice — typically from ad-hoc, through defined and managed, to optimized — with explicit criteria per level. It gives organizations a shared, defensible way to assess where they stand and what improving looks like. HexaSight scores practices against maturity models rather than opinion.
A computed rating of where a practice sits on its maturity model.
A maturity score is the computed rating that places a practice at a level on its maturity model, based on evidence rather than self-assessment alone. Because it is derived from captured evidence, it can be tracked over time and compared across workspaces. HexaSight computes maturity scores continuously so progress is visible and defensible.
The link binding an identity to a workspace with one or more roles.
A membership is the link that binds an identity to a specific workspace and carries the roles that identity holds there. It is what scopes a person's access to the right place, so the same person can have different rights in different workspaces. In the Sixfold OS RBAC chain, membership connects identity to role within a workspace.
The information given to a model at inference: instructions, data, and history.
Model context is the full set of information a language model has available when generating a response — system instructions, retrieved data, conversation history, and tool results. Curating context well is what separates reliable AI from guesswork. In grounded orchestration, Sixfold OS fills the model context from governed sources so answers stay accurate and scoped.
A self-contained Sixfold OS product surface that owns one layer of truth.
A module is a bounded product surface within Sixfold OS — such as HexaGrid or HexaMind — that owns a single, well-defined concern and its authoritative data. Modules are workspace-aware, individually access-controlled, and connect to one another through defined contracts. This composition is what lets the platform grow without becoming a tangle.
One repository holding many apps and packages with shared tooling.
A monorepo is a single version-controlled repository that holds many applications and shared packages together, with unified tooling for building, testing, and releasing them. It makes sharing code and enforcing consistency across products far easier than many separate repos. Sixfold OS is built as a pnpm and turbo monorepo so every app draws from the same shared packages.
One system instance serves many isolated customers (tenants) from shared infrastructure.
Multi-tenancy is an architecture in which a single running system securely serves many customers, called tenants, while keeping each tenant's data and configuration logically isolated. It lowers cost and speeds updates because everyone runs the same maintained code, yet no tenant can see another's data. Sixfold OS is multi-tenant by default, with tenant scope enforced in every query, API, and job.
The single metric that best captures the core value delivered to customers.
A north-star metric is the single measure a team agrees best captures the core value it delivers to customers, used to align many efforts behind one direction. It is chosen for causal proximity to real value, not vanity. In HexaSight, a north-star metric anchors a KPI tree so supporting metrics ladder up to what matters most.
The guided process of getting a new customer set up and productive.
Onboarding is the guided process of getting a new customer or team set up, configured, and productive with the product. Good onboarding is the largest lever on time-to-value and on whether adoption sticks. In Sixfold OS, provisioning and sensible defaults make onboarding fast while preserving correct tenant scoping from the start.
How an organization structures work, roles, and decisions to deliver value repeatedly.
An operating model describes how a company actually runs: how teams are organized, how decisions are made and recorded, and how standards flow across functions. It is the connective tissue between strategy and day-to-day execution. Sixfold OS encodes an operating model as software so that the intended way of working is the enforced way of working.
Coordinating multiple steps, tools, or models into one reliable workflow.
Orchestration is the coordination of multiple steps, tools, models, or services into a single reliable, observable workflow. It handles sequencing, retries, and control flow so complex processes behave predictably. HexaMind orchestrates AI workflows and, when grounded, keeps every orchestrated step tied to governed data.
A single granular right to perform a specific action on a resource.
A permission is the atomic unit of access: a specific right to perform a defined action on a defined resource, such as reading a module or approving a decision. Permissions are bundled into roles rather than granted individually. In Sixfold OS every module surface is gated on explicit permissions like module:read, always within tenant scope.
A time-boxed initial deployment to prove value before full rollout.
A pilot is a time-boxed, limited deployment run with a real team to prove value and fit before committing to a full rollout. It de-risks adoption and produces concrete evidence for the business case. A Sixfold OS pilot typically focuses one workspace on a few modules to demonstrate governed value quickly.
A hosted platform to build and run apps without managing the underlying infrastructure.
Platform-as-a-Service (PaaS) provides a managed environment — runtimes, databases, build and deploy pipelines — on which teams develop and operate their own applications. It abstracts away servers and operating systems while leaving application logic to the customer. FaaS sits a layer higher: it delivers the working model and its governance, not just the platform to build one on.
A stated rule of conduct or configuration the organization commits to.
A policy is a stated rule of conduct or configuration that an organization commits to and expects to be followed — for access, data handling, or ethics. A policy delivers value only when it is enforceable and evidenced rather than a document nobody checks. In Sixfold OS, policies become governed rules that HexaNorm can apply and audit.
The ability to move your knowledge and evidence out in open, usable form.
Portability is the property that your data, knowledge, and evidence can be exported in open, usable formats and moved elsewhere without loss of meaning. It is the practical antidote to vendor lock-in. HexaQence prioritizes portability so that what you capture in Sixfold OS remains yours and stays useful outside it.
Raw base values versus references that point at them by purpose.
Primitive tokens hold raw base values (for example, a specific hex color), while alias tokens are references that point at primitives by purpose and can be remapped per theme. This two-tier structure lets you change what a purpose resolves to without touching the base palette. It is the mechanism behind clean theming and semantic naming.
The captured, governed understanding of how and why a product works.
Product knowledge is the accumulated, governed understanding of how a product is built, why decisions were made, and how it must behave — including standards, decisions, and accessibility docs. When it lives only in people's heads, it is fragile and non-portable. HexaQence turns product knowledge into structured, owned, and portable records.
How far a product practice has evolved from ad-hoc toward governed and evidenced.
Product maturity measures how consistently and defensibly an organization designs, decides, and governs its products — from ad-hoc improvisation to a repeatable, evidenced practice. It is assessed against explicit maturity models rather than gut feel. Sixfold OS scores maturity continuously so that progress is visible and every claim is backed by evidence.
The coherent system that runs how a product organization designs, decides, and governs.
A product operating system is the integrated layer that connects design, documentation, decisions, AI, analytics, and governance into one coherent way of working. Rather than stitching point tools together, it gives every function a shared source of truth and a shared set of rules. Sixfold OS is a product operating system delivered as Framework-as-a-Service.
The structured instruction and context given to an AI model to produce output.
A prompt is the structured input — instructions plus context — supplied to a language model to elicit a desired output. In a governed system, prompts are versioned, reviewed, and tested rather than typed ad hoc. HexaMind manages prompts as controlled assets so their behavior is consistent, evaluable, and auditable.
The traceable origin and lineage of a piece of data or a decision.
Provenance is the documented origin and lineage of an artifact — where a value, decision, or asset came from, and how it was derived and changed over time. It lets you trust data because you can see where it came from. Sixfold OS preserves provenance across modules so a token, decision, or metric can always be traced to its source.
Setting up a tenant, workspace, or environment with its initial state.
Provisioning is the automated setup of a new tenant, workspace, or environment — creating its records, roles, and initial configuration so it is ready to use. Reliable provisioning is what makes onboarding fast and multi-tenancy operable at scale. In Sixfold OS provisioning establishes correct scoping and defaults from the very first moment a customer exists.
Government and public bodies with mandates for accessibility and transparency.
The public sector comprises government agencies and public bodies that must meet legal mandates for accessibility, transparency, procurement, and accountability to citizens. Their work must be defensible and open to scrutiny by design. Sixfold OS supports public-sector teams with WCAG-aligned accessibility documentation, audit trails, and portable knowledge.
Access granted through roles that bundle permissions, not per individual.
Role-based access control (RBAC) grants permissions through roles rather than assigning them to individuals one by one, so access stays consistent and manageable at scale. In Sixfold OS the chain is User to Identity to Membership to Role to Permission, always resolved within tenant and workspace. This makes who-can-do-what auditable and hard to get wrong.
A query-optimized projection of data shaped for reading, not writing.
A read model is a projection of data optimized for reading and display, derived from the source of truth rather than authoritative itself. Separating read models from write/source models keeps queries fast without compromising the integrity of the canonical data. Sixfold OS distinguishes read models, source-of-truth models, and localized content models by design.
Fast derived views versus the authoritative record they are built from.
This distinction separates the authoritative record (source of truth) from the query-optimized projections built from it (read models). Writes and audit go to the source of truth; reads are served from fast, possibly denormalized read models derived from it. Keeping them separate protects data integrity while keeping the interface responsive.
Sectors where law mandates auditability, controls, and compliance.
Regulated industries are sectors — finance, healthcare, public services, and others — where law and oversight mandate strict controls, auditability, and provable compliance. They cannot adopt tools that leave governance to chance. A governance-by-design, evidence-first operating system like Sixfold OS is aimed squarely at their needs.
Grounding an AI answer in retrieved source documents before it responds.
Retrieval-augmented generation (RAG) is a technique where relevant source documents are retrieved and supplied to a language model so its answer is grounded in real, citable material rather than parametric memory. It reduces hallucination and makes outputs traceable to sources. Sixfold OS applies RAG over its own governed knowledge so AI answers carry provenance.
A required approval checkpoint that work must pass before proceeding.
A review gate is a required approval checkpoint that work must pass before it can proceed — a governed stop where a person or rule confirms readiness. Gates make quality and compliance mandatory at the right moments rather than optional. Sixfold OS places review gates where governance-critical steps occur, capturing each approval as evidence.
A named bundle of permissions assigned to members within a scope.
A role is a named collection of permissions that expresses a job function — such as admin, editor, or viewer — and is assigned to members rather than individuals directly. Roles keep access consistent and let you reason about permissions at a human level. In the Sixfold OS RBAC chain, roles sit between memberships and permissions.
A precomputed aggregation of raw data into summary metrics.
A rollup is a precomputed aggregation that summarizes raw events or records into higher-level metrics — daily totals, per-workspace scores — so dashboards stay fast and consistent. Rollups are produced by scheduled jobs and, in a multi-tenant system, must be computed within tenant scope. Sixfold OS runs rollups in its background jobs to feed KPIs and maturity scores.
Recurring subscription pricing, typically per seat, tier, or usage.
SaaS pricing is the recurring subscription model by which software is sold — commonly per seat, per tier, or by usage — aligning cost with ongoing value rather than a one-time licence. Clear pricing helps buyers reason about total cost of ownership. Sixfold OS is priced as a subscription that reflects its role as a whole operating framework, not a single tool.
An explicit limit an AI system must not cross, enforced by the platform.
A safety boundary is an explicit, enforced limit on what an AI system is permitted to do — which data it can touch, which actions it can take, which scopes apply. Unlike a guideline, it is structurally enforced, not merely requested. HexaMind defines safety boundaries so AI capability never exceeds what governance and tenant scoping allow.
The boundary that limits what an action or token may access.
A scope is the boundary that constrains what a given action, token, or session is permitted to reach — a tenant, a workspace, a module, or a specific permission. Scopes are the mechanism through which least-privilege and tenant isolation are actually enforced. In Sixfold OS every request carries a scope resolved from context, and nothing operates outside it.
A typed client library that makes calling the platform's APIs simple and safe.
A software development kit (SDK) is a typed client library that packages the platform's API contracts into convenient, safe calls, so consumers do not hand-roll requests. It centralizes correctness — auth, scoping, serialization — in one place. The Sixfold OS internal SDK gives every app a consistent, tenant-aware way to talk to the gateway.
A single licensed user in a subscription, billed individually.
A seat is one licensed user within a subscription, the common unit by which per-user SaaS pricing is counted and billed. Seat-based pricing is simple but can penalize broad collaboration. Sixfold OS can combine seats with workspace-based pricing so cost tracks the value delivered, not just headcount.
Tokens named by purpose (e.g. surface, danger) rather than raw value.
Semantic tokens are design tokens named for their intent — such as color-surface or color-danger — rather than for a raw value like blue-500. Because they express meaning, they can be remapped per theme without touching components, and they document why a value is used. Semantic tokens are the layer that makes theming and consistent intent possible.
A commitment to defined levels of availability, performance, and support.
A service-level agreement (SLA) is a formal commitment to defined levels of availability, performance, and support, often with remedies if targets are missed. It is a core expectation of enterprise buyers who depend on the service operationally. Sixfold OS commercial terms include SLAs appropriate to its role as an operating system teams rely on daily.
One authentication that grants access across many connected applications.
Single sign-on (SSO) lets a user authenticate once and gain access to many connected applications without logging in again to each. It centralizes authentication, improving both security and experience. Sixfold OS modules use SSO via Auth0 so one identity carries securely across the whole operating system.
One authoritative place for tokens and components that all products derive from.
A single source of design truth is one authoritative repository of tokens, components, and rules from which every product and surface derives, rather than each team maintaining its own copy. It is the specific application of the source-of-truth principle to design. HexaGrid is this source in Sixfold OS, keeping design decisions consistent everywhere.
One dedicated instance per customer versus a shared instance serving many customers.
A single-tenant deployment gives each customer its own dedicated instance and data store, maximizing isolation at higher operational cost and slower updates. A multi-tenant deployment shares one maintained instance across many customers with logical isolation, gaining efficiency and faster delivery. Sixfold OS is multi-tenant, but its strict scoping model gives each tenant single-tenant-grade separation.
The visual model of how the modules combine into one coherent system.
The Sixfold Cube is the signature visual model of the platform: it represents the modules as faces of a single object, expressing that they are distinct yet inseparable parts of one operating system. It communicates composability and coherence at a glance. The Cube is both a brand device and an accurate mental model of how the layers of truth fit together.
The product operating system that unifies design, docs, AI, analytics, and governance.
Sixfold OS is a multi-tenant product operating system delivered as Framework-as-a-Service, combining a set of governed modules into one coherent way of working. Each module owns a distinct layer of truth — design, documentation, components, AI, analytics, governance — and they connect through the Sixfold Cube. It is workspace-aware and governed by design from the first click.
Software delivered over the web on subscription, hosted and maintained by the vendor.
Software-as-a-Service (SaaS) is application software hosted centrally and accessed over the internet, typically on a recurring subscription. The vendor runs the infrastructure, applies updates, and manages availability, so customers avoid installing or operating the software themselves. FaaS builds on the SaaS delivery model but sells an operating framework rather than a single application.
The single authoritative place a fact lives, from which all copies derive.
A source of truth is the one authoritative record for a given fact — a token value, a decision, a standard — from which every other view is derived rather than independently maintained. It eliminates the drift and contradiction that come from duplicated data. Sixfold OS assigns each kind of fact a clear owning module, so there is always exactly one place that is right.
The shared accent palette that gives each Sixfold OS module its identity color.
The spectrum is the coordinated set of accent colors that runs across Sixfold OS, assigning each module a distinct hue while keeping the whole visually coherent. It is defined once in shared tokens and reused everywhere, so brand and product stay in sync. The glossary categories reuse the same spectrum accents as the modules they describe.
A defined, agreed rule or specification that work is measured against.
A standard is a defined, agreed rule or specification — internal or external — against which work is measured for consistency, quality, or compliance. Standards are only useful when their applicability and conformance are tracked. HexaNorm owns standards as governed data and, via its applicability engine, maps them to the contexts where they apply.
Automatically collected signals about how a system is used and behaves.
Telemetry is the automatically collected stream of signals about how a system is used and how it behaves — events, timings, and states — gathered to inform analytics and operations. Responsible telemetry is consented, tenant-scoped, and privacy-respecting. Sixfold OS collects telemetry first-party so the data stays governed rather than leaking to third parties.
A single customer organization with fully isolated data and configuration.
A tenant is the top-level customer boundary in a multi-tenant system — typically one organization or account whose data, users, and settings are kept separate from every other tenant. It is the root of the scoping hierarchy: tenant, then workspace, then module, environment, project, and resource. In Sixfold OS the active tenant is stamped from authenticated context and never read from the request body.
The guarantee that one tenant can never access another tenant's data.
Tenant isolation is the architectural guarantee that data and actions belonging to one tenant are inaccessible to any other, even though tenants share infrastructure. It is enforced structurally through scoping, not left to careful coding alone. Tenant isolation is what makes multi-tenancy safe enough for regulated and enterprise customers.
Restricting every query and action to the caller's tenant and workspace.
Tenant scoping is the discipline of restricting every database query, API call, search, analytics read, and background job to the caller's tenant and workspace, so scope is never widened silently. The tenant is stamped from authenticated context, never trusted from the request body. In Sixfold OS tenant scoping is non-negotiable and enforced on every data-access path.
A named set of token values (e.g. light/dark) applied across a product.
A theme is a coherent, named set of token values — such as light, dark, or a brand variant — that can be applied consistently across a product. Themes work by remapping semantic tokens to different underlying values without changing component code. HexaKit delivers themes at runtime as switchable CSS variable sets.
How long from first adoption until a customer realizes tangible benefit.
Time-to-value is the elapsed time between starting to use a product and getting measurable benefit from it. Shorter time-to-value reduces adoption risk and strengthens the business case. By delivering a ready operating model rather than a toolkit to assemble, Framework-as-a-Service is designed to compress time-to-value.
The defined format that carries authored tokens from HexaGeist to runtime.
The token export contract is the defined, versioned format by which design tokens authored in HexaGeist are exported and handed to the runtime layer in HexaKit. It is the seam that keeps the token pipeline reliable across module boundaries. Because the contract is explicit, authoring and runtime can evolve independently without breaking design consistency.
The path tokens travel from authoring through export to runtime styling.
The token pipeline is the governed path a design token travels from authoring, through transformation and export, to the runtime where products consume it. It ensures a change made once propagates reliably to every surface. In Sixfold OS the pipeline runs from HexaGeist (authoring) through the export contract to HexaKit (runtime).
The full lifetime cost of a solution, not just its purchase or licence price.
Total cost of ownership (TCO) sums every cost of a solution over its life: licensing, integration, operations, maintenance, training, and the hidden cost of drift and rework. A tool that is cheap to license can be expensive to own. By consolidating design, docs, AI, analytics, and governance into one maintained framework, Sixfold OS aims to lower TCO versus a stack of separately owned point tools.
Dependence on one vendor that makes switching costly or impractical.
Vendor lock-in is the condition where an organization becomes so dependent on a supplier's proprietary formats or processes that moving away is prohibitively expensive. It is mitigated by open standards, exportable data, and clear provenance. Sixfold OS counters lock-in through portability and documentation-as-code, so your knowledge and evidence remain yours and can leave with you.
The standard for making web content accessible to people with disabilities.
The Web Content Accessibility Guidelines (WCAG) are the internationally recognized standard for making digital content perceivable, operable, understandable, and robust for people with disabilities. Conformance is often a legal as well as ethical requirement. Sixfold OS documents accessibility annotations in HexaQence so components can be audited against WCAG.
A scoped work area inside a tenant that groups people, modules, and projects.
A workspace is the second level of the scoping hierarchy: a bounded area inside a tenant where a team collaborates across modules on a shared set of projects. It carries its own membership, roles, and configuration, so different parts of an organization can work independently under one tenant. All Sixfold OS surfaces are workspace-aware, meaning access and data are always resolved within a workspace.
Every operation resolves data and access within a specific workspace.
Workspace-aware means that every operation — reads, writes, permissions, analytics — is resolved within the context of a specific workspace, not just a tenant. It gives teams inside one organization independent, scoped areas to work in. All Sixfold OS product surfaces are workspace-aware so collaboration and isolation coexist.
Pricing tied to workspaces rather than counting every individual seat.
Workspace-based pricing ties cost to the number or capability of workspaces rather than counting every individual seat, so collaboration is not penalized per person. It aligns naturally with a workspace-aware, multi-tenant platform. Sixfold OS can price by workspace so teams grow participation without a per-head tax.
Runtime schema validation that turns untrusted input into typed, safe data.
Zod validation is the use of Zod schemas to validate data at runtime, ensuring untrusted input matches a defined shape before it is trusted, while inferring matching TypeScript types. It closes the gap between compile-time types and runtime reality. Sixfold OS uses Zod for all runtime validation, keeping read, source-of-truth, and localized models cleanly separated.