UniSaaS.UniCORE.GVB

SaaS-deployment-shape substrate-services layer of UniSaaS.UniCORE. Public surface. Documentation today; source code on certification.

UniSaaS.UniCORE.GVB is the SaaS-deployment-shape sister of UniCORE.GVB. Same substrate-services scope, same Cross-Platform API, same governance, same gift, same CC BY 4.0, same irrevocability — different deployment topology.

Author: Bryan Fred, Unitek Systems Limited, Bedford, United Kingdom. Licence: CC BY 4.0 — given, not sold, irrevocable. First published: June 2026.

---

The three pillars

UniCORE makes three structurally distinct claims. Each one closes a different failure surface. All three are required; removing any one breaks the institutional case for the whole.

Pillar 1 — Audience: Consumer AI vs Institutional AI

Today's frontier AIs are configured for consumer use: variability, creativity, conversational warmth, and personalisation are features, not bugs. That is the right design for consumer surfaces. It is the wrong design for institutional surfaces — regulated decision-making, evidence-bound work, decisions that must be defensible to a third party. UniCORE is for the institutional audience: the same input, with the same governance state, in the same vertical, produces the same decision across vendors, sessions, nodes, and years.

Pillar 2 — Truth: the TrueAI Foundation truth contract

What an AI system is permitted to claim, and what it is required to mark as unverified. The Nine Invariants of the TrueAI Foundation make explicit: TRUE means evidenced, FALSE means falsified, UNVERIFIED means the system declined to assert. No third state where the system fabricates confidence it does not have.

Pillar 3 — Inconsistency: same input → same decision

Truth without consistency is not deployable in regulated institutional settings. If the same evidenced claim produces TRUE today and UNVERIFIED tomorrow, the truth contract is hollow. The Inconsistency Problem is the third pillar. It is closed in two places by two different mechanisms:

• Machine-side: foundation consistency (UniCORE-AI 12-Level governance + governance MD-files) + vertical consistency (per-Vertical-CORE primitives).
• Human-side: 1H1C at the production layer (Singular Pairing Principle — one human, one AI Claw, one workstream, produces certified artefacts) + xH1C at the operations layer (x humans operating the deployed Solution through one substrate Claw as consistency-holding agent, with per-Level qualification in PROD).

Canonical: THE-INCONSISTENCY-PROBLEM.md. The Singular Pairing Principle doctrine lives at bryanunitek/TrueAI/docs/10001-Singular-Pairing-Principle.md.

Honest framing

No AI architecture today can guarantee 100% end-to-end consistency. Probabilistic language models sit at the application boundary; their training is controlled by their vendors, not by UniCORE; and that training changes over time. What UniCORE makes is the structural maximum consistency achievable given that external-AI dependency, with the residual inconsistency named, bounded, and auditable.

---

Why this repository exists today

Powered by UniCORE AI built on the TrueAI foundation is a moral and ethical answer to Advanced AI for humanity.

This repository exists today as the canonical public home for UniSaaS.UniCORE.GVB — the place where its identity, licence, roadmap, naming rules, and industry classifications are recorded.

The source code is not yet published here. Source code is published when UniSaaS.UniCORE.GVB is certified Powered by UniCORE AI / built on the TrueAI Foundation. See ROADMAP.md for the trigger condition and what arrives at that point.

---

What this repository is

bryanunitek/UniSaaS.UniCORE.GVB is the canonical public home of the SaaS-shape substrate-services layer.

The Linux/Windows substrate that a SaaS Vertical CORE stands on, in hosted topology:

• mail (incl. mail filtering and DKIM/DMARC/SPF security)
• file transfer (Filedrop / WebDisk / FTP)
• DNS (zones and record sets)
• federation (SAML)
• tenancy (multi-tenant resolution, signing-key separation, quotas)
• topology (multi-region, IP pool management, inter-node federation)
• Outlook integration / calendar / contacts
• server profiles, node operations, bandwidth and storage reporting
• jurisdictional posture (per-tenant region pinning)
• the native UniCORE.GVB.SiteBuilder site-and-content engine (~40 site-builder primitives, plugin and theme registries, editor surface)
• and the SaaS-deployment-shape additions on top of all the above:
  • Multi-tenant routing — tenant-by-email resolution
  • Signing-key separation — per-tenant cryptographic isolation
  • Hosted operational shape — multi-tenant capacity, lifecycle management

It does NOT carry the Vertical CORE Business Objects. Those live in each Vertical CORE repository (Law BOs in UniCORE.Law-Claw, future Accounting BOs in UniCORE.Accounting-Claw, etc.). UniSaaS.UniCORE.GVB carries the substrate-services layer only, in SaaS-deployment shape.

---

Layered CORE position

Level 12  Solution Review (certification gate)
Level  3  Vertical CORE — Business Objects per industry, in SaaS shape
Level  2  IMPLEMENTATION REFERENCE — UniCORE / UniSaaS.UniCORE
                                      (deployment-shape pair)
Level  1  REFERENCE ARCHITECTURE — UniCORE-AI
Level  0  FOUNDATION — TrueAI (Nine Invariants)
          Programme — UniVERSE

UniSaaS.UniCORE.GVB sits below UniSaaS.UniCORE as the SaaS-shape substrate-services layer. It is the SaaS-deployment-shape sister of UniCORE.GVB.

---

Deployment-shape pair (with UniCORE.GVB)

Aspect	UniCORE.GVB (on-prem)	UniSaaS.UniCORE.GVB (SaaS)
Deployment topology	Customer's infrastructure	Hosted operator OR Private SaaS on customer's own kit
Tenancy model	Single-tenant (per deployment)	Multi-tenant routing
Signing keys	Per-deployment	Per-tenant separation
Operator	Customer	SaaS operator (e.g. Unitek Systems USA Inc) OR customer themselves (Private SaaS)
Operational responsibility	Customer	SaaS operator OR customer (Private SaaS)
Substrate-services scope	Same	Same
Cross-Platform API	Same	Same
Governance	Same Foundation invariants	Same Foundation invariants
Evidence trail / attestation	Same shape	Same shape
Licence	CC BY 4.0, irrevocable	CC BY 4.0, irrevocable

One substrate, three operator positions. The same UniSaaS.UniCORE.GVB code can run as:

1. Hosted SaaS — operated by Unitek Systems USA Inc (the GVB PROD-tier operator entity from Phase II onward) or any other operator.
2. Private SaaS — a global entity runs the SaaS stack on their own hardware, their own data centre, their own cloud account. The customer holds operational responsibility. Useful when the entity is large enough to not want shared hosting but still wants the SaaS deployment shape.
3. Self-hosted — any third party stands up the stack under CC BY 4.0.

The gift surface is uniform across all three positions.

---

Two-substrate parity at the customer-account-and-content layer

Inherited from the on-prem-shape sister: UniSaaS.UniCORE.GVB ships as one codebase that runs on either a Linux substrate or a Windows substrate. The two branches are co-equal at the control-surface layer; they differ only at the third-party-integration layer.

For the canonical statement of the parity shape, see UniCORE.GVB/README.md — the SaaS-shape inherits the parity unchanged.

---

Multi-provider persistence

The substrate-services data stores are provider-agnostic at compile time, with the runtime backend selected per deployment. Provider parity targets follow the on-prem-shape sister; the SaaS deployment topology does not change the persistence-provider list.

---

NVarchar Data Mode — Open, Scrambled, Encrypted, Quancrypted

All NVARCHAR (string) data across the UniSaaS.UniCORE.GVB substrate is governed by a four-mode architecture. Default posture: Scrambled — all string fields arrive Scrambled unless explicitly resolved otherwise by a policy chain (Workload → Tenant → Product → Default). Open mode is used where scrambling is operationally inappropriate (e.g. full-text search indexes). Encrypted mode is reserved (future feature; customer holds the decryption key per sovereignty principle). Quancrypted mode is reserved (future feature): the same field-level encryption as Encrypted, but with post-quantum key protection (ML-KEM key encapsulation, NIST FIPS 203) so the data survives a cryptographically-relevant quantum computer — the quantum-safe end-state of the data-at-rest posture, and the data-at-rest counterpart of POST-QUANTUM.md. The customer still holds the key (sovereignty principle). The enum, resolver, and policy store live at UniCORE.GVB.Common so that every Vertical CORE inherits the data-mode posture without re-implementing it.

The deployment shape (on-prem vs SaaS) does not change the data-mode architecture. Both inherit from the same substrate.

---

Platforms and UI Surfaces

UniSaaS.UniCORE.GVB runs on Windows, Linux, macOS, iOS, and Android.

Three primary UI surfaces deliver the full platform reach:

Surface	Technology	Platforms	Role
DevExpress Blazor Server	.NET 10 + XAF + XPO	Windows, Linux, macOS (via browser)	Primary web UI — the main operational surface
.NET MAUI	.NET 10	Windows, macOS, iOS, Android	Native mobile + desktop
Avalonia	.NET 10	Windows, Linux, macOS	Cross-platform native desktop

Additional optional surface:

Surface	Technology	Platforms	Role
WinForms (*.Win)	.NET 10 + DevExpress	Windows only	Optional power-user desktop surface (ships alongside Blazor)

The Blazor Server surface is the governance-primary UI — all administrative, operational, and substrate-services workflows are available through it. MAUI and Avalonia extend reach to native mobile and native Linux desktop respectively. WinForms remains as an optional Windows-only surface for power users who prefer a native Windows experience alongside Blazor.

All four surfaces share the same substrate-services layer, the same 12-Level Governance Model, and the same Foundation invariants. The UI surface is a delivery choice; governance is invariant across all of them. The deployment shape (SaaS vs on-prem) does not change the available surfaces — UniSaaS.UniCORE.GVB offers the same platform reach as UniCORE.GVB.

---

Status today: docs only, no source

This repository carries the public canonical identity of UniSaaS.UniCORE.GVB. Source code is not yet here. It arrives at certification — see ROADMAP.md.

The implementation work is being done in the private working repository bryanunitek/UniSaaS.UniCORE.GVB-Claw, paired with bryanunitek/UniCORE.GVB-Claw (one shared substrate codebase with SaaS-deployment-shape deltas isolated).

---

Certification trigger

The first SaaS Vertical CORE built on UniSaaS.UniCORE is certified Powered by UniCORE AI / built on the TrueAI Foundation.

When that certification is recorded:

• The SaaS-shape industry-agnostic substrate-services source code is published in this repository under CC BY 4.0.
• The SaaS-shape industry-classified releases (UniSaaS.UniCORE.GVB.Law, UniSaaS.UniCORE.GVB.Accounting, UniSaaS.UniCORE.GVB.Banking, UniSaaS.UniCORE.GVB.Healthcare, UniSaaS.UniCORE.GVB.Government, UniSaaS.UniCORE.GVB.Space-Industry, etc.) are created.

The badge is the gate. See STATEMENT-ON-CLAIMS.md and ROADMAP.md.

---

SaaS-shape industry classifications — open list

The list mirrors the on-prem-shape sister and is open:

• UniSaaS.UniCORE.GVB.Law
• UniSaaS.UniCORE.GVB.Accounting
• UniSaaS.UniCORE.GVB.Banking
• UniSaaS.UniCORE.GVB.Healthcare
• UniSaaS.UniCORE.GVB.Government
• UniSaaS.UniCORE.GVB.Space-Industry

Military is intentionally absent. The deployment shape (on-prem vs SaaS) does not change the Positioning Principle. See STATEMENT-ON-CLAIMS.md.

---

Positioning Principle

Harmony, Peace, Space Exploration, for Humanity.

This is a programme-level commitment, recorded identically across the canonical material. It is the structural reason UniSaaS.UniCORE.GVB.Military is and will remain unauthorised regardless of who proposes it.

---

How Unitek Systems USA Inc relates to this gift

When Unitek Systems USA Inc operates hosted SaaS services on top of UniSaaS.UniCORE.GVB (the GVB PROD-tier operator role from Phase II onward), it does so as one consumer of the gift among many, under the same CC BY 4.0 licence as anyone else.

A global entity choosing the Private SaaS position keeps operational responsibility in their own hands. Both positions are valid under the gift.

---

Related repositories

Foundation triad (gift, public, CC BY 4.0):

• UniVERSE — programme
• TrueAI — Foundation (Nine Invariants)
• UniCORE-AI — reference architecture (12 Levels)

Implementation reference (deployment-shape pair):

• UniCORE — on-prem-shape
• UniSaaS.UniCORE — SaaS-shape (parent of this repo)

Substrate-services layer (deployment-shape pair):

• UniCORE.GVB — on-prem-shape (sister of this repo)
• UniSaaS.UniCORE.GVB — SaaS-shape (this repo)

Substrate-harness working repositories (private, sister to this layer):

• bryanunitek/UniCORE-Claw — substrate-harness working repository, on-prem-shape. The reference Vertical CORE pattern.
• bryanunitek/UniSaaS.UniCORE-Claw — substrate-harness working repository, SaaS-shape.

Forked-upstream building-block families (scaffold-anchor as of 2026-06-04 — full scaffolding and upstream fork pending dedicated kickoff arcs):

• UniCORE.Avalonia — Cross-platform .NET UI substrate. Fork of MIT Avalonia + UniCORE CC BY 4.0 additions (Pro-equivalent controls + Avalonia XPF).
• UniSaaS.UniCORE.Avalonia — SaaS-deployment-shape sister of UniCORE.Avalonia.
• bryanunitek/UniCORE.Avalonia-Claw (private) — on-prem-shape working repository for UniCORE.Avalonia.
• bryanunitek/UniSaaS.UniCORE.Avalonia-Claw (private) — SaaS-shape working repository.
• UniCORE.DNN — Web CMS / portal building block. Fork of MIT Dnn.Platform + UniCORE CC BY 4.0 modules.
• UniSaaS.UniCORE.DNN — SaaS-deployment-shape sister of UniCORE.DNN.
• bryanunitek/UniCORE.DNN-Claw (private) — on-prem-shape working repository for UniCORE.DNN.
• bryanunitek/UniSaaS.UniCORE.DNN-Claw (private) — SaaS-shape working repository.
• UniCORE.Asterisk — VoIP/PBX telephony engine. Fork of GPL-2.0 Asterisk + UniCORE additions. Full upstream history (34,425 commits).
• UniSaaS.UniCORE.Asterisk — SaaS-deployment-shape sister of UniCORE.Asterisk.
• bryanunitek/UniCORE.Asterisk-Claw (private) — on-prem-shape working repository for UniCORE.Asterisk.
• bryanunitek/UniSaaS.UniCORE.Asterisk-Claw (private) — SaaS-shape working repository.
• UniCORE.Jitsi — Video conferencing (Meet + Videobridge). Fork of Apache-2.0 Jitsi + UniCORE additions. Multi-upstream (13,956 commits).
• UniSaaS.UniCORE.Jitsi — SaaS-deployment-shape sister of UniCORE.Jitsi.
• bryanunitek/UniCORE.Jitsi-Claw (private) — on-prem-shape working repository for UniCORE.Jitsi.
• bryanunitek/UniSaaS.UniCORE.Jitsi-Claw (private) — SaaS-shape working repository.
• UniCORE.Signal — Secure messaging platform. Fork of AGPL-3.0 Signal Server + UniCORE additions. Full upstream history (5,010 commits).
• UniSaaS.UniCORE.Signal — SaaS-deployment-shape sister of UniCORE.Signal.
• bryanunitek/UniCORE.Signal-Claw (private) — on-prem-shape working repository for UniCORE.Signal.
• bryanunitek/UniSaaS.UniCORE.Signal-Claw (private) — SaaS-shape working repository.
• UniCORE.XCP — Virtualisation platform (XCP-ng hypervisor + Xen Orchestra management). Fork of GPL-2.0/AGPL-3.0 + UniCORE additions. Multi-upstream (493 commits).
• UniSaaS.UniCORE.XCP — SaaS-deployment-shape sister of UniCORE.XCP.
• bryanunitek/UniCORE.XCP-Claw (private) — on-prem-shape working repository for UniCORE.XCP.
• bryanunitek/UniSaaS.UniCORE.XCP-Claw (private) — SaaS-shape working repository.

Full fleet inventory (193 repositories):

• The canonical fleet inventory is maintained in the Book of Unitek Systems Limited at _inventory/UNICORE-REPOSITORY-INVENTORY.md. It covers all 193 in-fleet repositories across 11 tiers, their branch state, visibility, upstream relationships, and licence positions. Updated 2026-06-06.

---

Files

• README.md — this file
• LICENSE.md — CC BY 4.0 / gift licence
• LICENSE_EXAMPLES.md — plain-English worked scenarios
• AGENTS.md — repo working rules
• AI-AUTHORSHIP.md — AI-assistance disclosure
• ROADMAP.md — what arrives at certification, when, why
• STATEMENT-ON-CLAIMS.md — names, marks, claims rules
• BRAND-AND-TRADEMARK-USE-POLICY.md — names + marks cross-reference
• IRREVOCABLE-LICENCE-DECLARATION.md — irrevocability cross-reference
• DISCUSSIONS.md — Discussions tab purpose
• SUCCESSION.md — stewardship cross-reference

---

Contact

• Public discussion: GitHub Discussions
• Private contact / connection request: LinkedIn

---

Author: Bryan Fred, Unitek Systems Limited, Bedford, United Kingdom. Public. Given, not sold. Irrevocable.