UniCORE is the public foundation for advanced AI.
We design the governance, write the code, and train the people who can do both. The foundation is gifted to humanity under permissive licences. The producers who maintain it earn their authority through a 30-year apprenticeship: not bought, not granted, earned.
The result is infrastructure no single company can monopolise, built and maintained by people from every background.
The future is coming. Advanced AI will shape the world ahead, whether we are ready or not. The question is who builds it, who controls it, and who benefits. UniCORE answers all three the same way: humanity does.
If you want to spend a career building advanced AI for humanity rather than for shareholders, UniCORE is the path.
A 30-year programme from apprentice to certified producer. A public foundation given away under permissive licences. No monopoly. The work belongs to everyone, including you.
This is UniCORE, the implementation reference layer of the programme. It is the working code substrate that satisfies the UniCORE AI (mirror: GitHub) 12-Level reference architecture, which itself satisfies the TrueAI (mirror: GitHub) Foundation. Sister repositories: UniVERSE (mirror: GitHub) (the programme), TrueAI (mirror: GitHub) (the immutable Foundation), UniCORE-AI (mirror: GitHub) (the 12-level reference architecture).
New to producing on the public gift surface? Start with UniVERSE/GETTING_STARTED.md (mirror: GitHub).
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.
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.
What an AI system is permitted to claim, and what it is required to mark as unverified. The Nine Invariants of the TrueAI Foundation (mirror: GitHub) 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.
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 (mirror: GitHub). The Singular Pairing Principle doctrine lives at bryanunitek/TrueAI/docs/10001-Singular-Pairing-Principle.md (mirror: GitHub).
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.
The implementation reference for governed, human-sovereign artificial intelligence.
Author: Bryan Fred, Unitek Systems Limited, Bedford, United Kingdom First published: May 2026 Status: Public. Given, not sold. Irrevocable.
UniCORE is the implementation reference for the programme — the working code substrate that any Vertical Solution may build upon when it is built to satisfy the TrueAI Foundation invariants and the UniCORE AI 12-Level reference architecture.
It sits in the Layered CORE model at Level 2 ↔ Level 3 — between the universal architecture (UniCORE AI) and the Vertical CORE specific to a sector (e.g. UniCORE.Law, UniCORE.Accounting, UniCORE.Banking). UniCORE is what a Vertical CORE inherits FROM. The Vertical CORE then carries the industry-specific Business Objects on top.
When a Vertical Solution is certified Powered by UniCORE AI / built on the TrueAI Foundation, the UniCORE substrate it stands on is published here, on this repository, under CC BY 4.0. The Vertical CORE remains in its own repository (e.g. bryanunitek/UniCORE.Law-Claw for the Law sector) and carries its industry-specific Business Objects there.
UniCORE is the gift layer. The Vertical Business Objects are the commercial layer. Both can co-exist; the gift can never be enclosed.
Institutional AI fails the moment the same input produces a different output. Different vendors give different answers. The same vendor gives different answers in different sessions. Even the same session can drift. Acceptable for a recipe or a bedtime story. Structurally unsafe for a credit decision, a clinical triage, a tax classification, or a privilege ruling.
UniCORE answers this with a two-layer architecture:
- Foundation consistency — the UniCORE AI (mirror: GitHub) 12-Level governance stack and the per-level governance MD files. Same input + same governance state → same output.
- Vertical consistency — each Vertical CORE (Law, Banking, Healthcare, Accounting, …) inherits foundation consistency and adds industry-specific consistency primitives on top.
Truth without consistency is not deployable in regulated institutional settings. The Inconsistency Problem is the third pillar — sitting alongside the audience pillar (Consumer vs Institutional AI) and the truth pillar (TrueAI Foundation truth contract).
Full doctrine: THE-INCONSISTENCY-PROBLEM.md (mirror: GitHub).
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 UniCORE — the place where its identity, licence, roadmap, and naming rules are recorded.
The source code is not yet published here. Source code is published when the first Vertical CORE that uses UniCORE — UniCORE.Law-Claw — is certified Powered by UniCORE AI / built on the TrueAI Foundation. See ROADMAP.md (mirror: GitHub) for the trigger condition and what arrives at that point.
What is published here today:
- The licence — CC BY 4.0, irrevocable, the same terms as the rest of the programme. See LICENSE.md (mirror: GitHub).
- The licensing reference with worked scenarios — plain-English guidance for Partners, Clients, and Software Providers, with worked examples per industry. See LICENSE_EXAMPLES.md (mirror: GitHub).
- The naming and claims rules — what can and cannot be claimed about the UniCORE name. See STATEMENT-ON-CLAIMS.md (mirror: GitHub).
- The roadmap — what arrives at certification and in what shape. See ROADMAP.md (mirror: GitHub).
- The AI authorship disclosure — same disclosure form as the Foundation triad. See AI-AUTHORSHIP.md (mirror: GitHub).
- The agent rules — how Claws working on this repository conduct themselves. See AGENTS.md (mirror: GitHub).
The repository will accumulate documentation between now and certification. Source code arrives at certification.
UniCORE sits within the Layered CORE model (UniVERSE/docs/00057-Layered-CORE-Model.md (mirror: GitHub)).
Level 1 CORE — TrueAI Foundation (universal, immutable, gift)
↑
Level 2 CORE — UniCORE AI (universal architecture, gift)
↑
Level 2 ↔ 3 — UniCORE (THIS REPO — implementation reference, gift)
↑
Level 3 CORE — Vertical CORE (industry-specific reference, gift)
(e.g. UniCORE.Law, UniCORE.Accounting,
UniCORE.Banking, UniCORE.Healthcare,
UniCORE.Government, UniCORE.Space-Industry)
↑
Solutions tier — Working implementations (services-built, sellable)
A derivative of CORE is itself CORE and is itself gifted. This is gift propagation. Vertical COREs are CORE. The Solutions tier is not CORE; Solutions are services-built deliverables produced by Generation IT pairs on top of the relevant CORE layers.
The trigger that moves UniCORE from this repository's documentation-only state to documentation-plus-code state is:
The first Vertical CORE built on UniCORE —
UniCORE.Law-Claw— is certified Powered by UniCORE AI / built on the TrueAI Foundation.
When that certification is recorded, the UniCORE substrate inside UniCORE.Law-Claw is extracted and published here under CC BY 4.0. The Law Business Objects remain in UniCORE.Law-Claw as the commercial Vertical CORE layer.
The same gift principle then applies to every future Vertical CORE: when a Vertical CORE is certified, its UniCORE-conformant substrate is already published here for everyone, and the vertical's industry-specific Business Objects sit in the vertical's own repository.
The certification is the gate. The gate exists because the gift must mean something; the badge cannot be self-applied.
UniCORE 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 Vertical CORE business-object 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 (UniCORE.GVB), 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.
UniCORE.Desktop provides the desktop client applications for the UniCORE family. These applications connect to services running on UniCORE.GVB and/or UniCORE. They are not products for sale — they are included with the UniCORE licence (CC BY 4.0), part of the same gift.
UniCORE.Desktop must independently pass the "Powered by UniCORE AI / built on TrueAI Foundation" certification gate.
Client applications (scope):
- File transfer client — secure file send/receive, filedrop upload, filelink management, download tracking
- FTP / SFTP client — file access to GVB-hosted storage, bookmark management, transfer queue
- Mail configuration — auto-configuration of desktop mail clients against GVB mail services
- Calendar and contacts sync — CalDAV/CardDAV client integration, offline sync, conflict resolution
- Office integration — document workflows connecting desktop productivity suites to UniCORE services
- AI Chat — governed AI assistant operating under TrueAI governance, connected to UniCORE AI services
- Identity and authentication — desktop-side identity provider, certificate-based authentication, 2FA integration
- GVB API client — typed HTTP client for the UniCORE.GVB substrate API, used by all other desktop applications
- VPN / tunnel client — secure connectivity to GVB nodes, jurisdictional routing
- Backup client — desktop-side backup agent connecting to GVB backup services
- Admin console — desktop administration interface for node operators and tenant administrators
- VM management client — desktop interface for hypervisor operations (VM lifecycle, snapshots, migration)
- DNS management client — zone and record management interface
- Monitoring dashboard — desktop-side observability client (bandwidth, storage, service health)
UniCORE.Desktop is documented in both this repository and bryanunitek/UniCORE.GVB (mirror: GitHub) because the applications serve both layers. At certification, UniCORE.Desktop publishes as its own repository (bryanunitek/UniCORE.Desktop) with cross-references from both.
The working repository is bryanunitek/UniCORE.Desktop-Claw (private until certification).
UniVIEW and UniREPORT follow the same pattern as UniCORE.Desktop. They are application surfaces that serve both UniCORE and UniCORE.GVB:
- UniVIEW — view-layer applications, presenting governed data from the substrate-services and Vertical CORE layers. Read-mode user surface; no business-logic mutation.
- UniREPORT — reporting-layer applications, generating governed reports across the same data. Evidence-bound output suitable for regulated reporting contexts.
Like UniCORE.Desktop, both:
- Are not products for sale — they are included with the UniCORE licence (CC BY 4.0), part of the same gift.
- Must independently pass the "Powered by UniCORE AI / built on TrueAI Foundation" certification gate.
- Are documented in both
bryanunitek/UniCOREandbryanunitek/UniCORE.GVBbecause they serve both layers. - Publish as their own repositories at certification (
bryanunitek/UniVIEW,bryanunitek/UniREPORT) with cross-references from both.
The working repositories are bryanunitek/UniVIEW-Claw and bryanunitek/UniREPORT-Claw (private until certification).
All NVARCHAR (string) data across the UniCORE substrate is governed by a four-mode architecture:
| Mode | Default | Description |
|---|---|---|
| Scrambled | ✅ Yes | Reversibly scrambled storage. Prevents casual database inspection. The owning system’s scramble key is required to read. |
| Open | Plain text. Used where scrambling is operationally inappropriate (e.g. full-text search indexes). | |
| Encrypted | Field-level encryption. Future feature (reserved). The customer holds the decryption key (sovereignty principle). | |
| Quancrypted | Field-level encryption with post-quantum key protection. Future feature (reserved). The same field cipher as Encrypted, but the key-management/envelope layer uses post-quantum cryptography (ML-KEM key encapsulation, per NIST FIPS 203) so the protection survives a cryptographically-relevant quantum computer. The customer still holds the decryption key (sovereignty principle). This is the quantum-safe end-state of the data-at-rest posture. |
Default posture: Scrambled. All string fields arrive Scrambled unless explicitly resolved otherwise by a policy chain. The resolution cascade is: Workload → Tenant → Product → Default (Scrambled).
Encrypted and Quancrypted are reserved future modes: the enum values exist so that fields can be tagged for them and the persistence seam can carry them, but the cryptographic implementations are not yet shipped. Quancrypted is the data-at-rest counterpart of the substrate post-quantum posture — see the UniCORE.GVB POST-QUANTUM.md (mirror: GitHub) for the threat model, standards, and migration timeline.
This is a substrate-level concern. Both the on-prem UniCORE and the SaaS UniSaaS.UniCORE deployments enforce the same posture. The enum, resolver interface, policy store, and default resolver live at the GVB substrate layer (UniCORE.GVB.Common) so that every Vertical CORE inherits the data-mode posture without re-implementing it.
The SaaS deployment shape includes a 10-level bootstrap seeder that provisions the foundational user and role hierarchy per UniVERSE Foundation Document 45/54:
| Level | Code | Name | AI Mode |
|---|---|---|---|
| 1 | 0001 | UniCORE-Global | GlobalAIMode |
| 2 | 0002 | UniCORE-GlobalVirtualBridge | GlobalVirtualBridgeAIMode |
| 3 | 0003 | UniCORE-Continental | ContinentalAIMode |
| 4 | 0004 | UniCORE-Regional | RegionalAIMode |
| 5 | 0005 | UniCORE-State | StateAIMode |
| 6 | 0006 | UniCORE-DataCentre | DataCentreAIMode |
| 7 | 0007 | UniCORE-Platform | PlatformAIMode |
| 8 | 0008 | UniCORE-Product | ProductAIMode |
| 9 | 0009 | UniCORE-Deployment | DeploymentAIMode |
| 10 | 0010 | UniCORE-Tenant | TenantAIMode |
Each level seeds one bootstrap user and one paired role. The seeder is idempotent. Default NVarchar posture for all seeded data: Scrambled.
Levels 11 (RoleAIMode) and 12 (UserAIMode) remain in the per-tenant operational database — they are not bootstrap-level.
The Intelligent Integration Controller (IIC) is the integration and data-movement subsystem of UniCORE. It provides secure messaging, secure file transfer manifests, and governed data exchange between systems — the integration spine that a Vertical CORE uses to connect to external systems (practice management, document management, billing, etc.) without exposing raw data paths.
The IIC is built as a standalone service layer within the Vertical CORE working repository. At certification, the IIC interfaces and contracts become part of the UniCORE gift surface (CC BY 4.0).
Integration / Import from 3rd-party systems:
The IIC includes a connector architecture for importing data from established practice-management and billing systems. The first production connector is Aderant Expert — a legacy system used by global law firms. The connector provides:
AderantIntegrationTransactionAdapter— transaction-level data importAderantRunProjectionService— run-projection and workload planningAderantWorkloadHandler— workload execution for governed import pipelines
The connector pattern is repeatable: future connectors for other systems (Elite, Aderant iManage, 3E, etc.) follow the same interface shape.
The working code lives in bryanunitek/UniCORE.Law-Claw (the first Vertical CORE), structured as:
UniCORE.Law.IntelligentIntegrationController.Abstractions— contracts and DTOsUniCORE.Law.IntelligentIntegrationController.Core— interfaces, services, resolverUniCORE.Law.IntelligentIntegrationController.Persistence— store implementationsUniCORE.Law.IntelligentIntegrationController.Service— the hosted service entry pointUniCORE.Law.IntelligentIntegrationController.Connectors.Aderant— Aderant Expert connector
The programme is positioned as Harmony, Peace, Space Exploration, for Humanity.
Industries and uses that align with this positioning are welcome. Those that do not are not. Military uses are intentionally absent from the programme and will not be added.
The "Powered by UniCORE AI" and "built on TrueAI Foundation" certifications must not appear on any military use. The badge is part of the gift, and the gift is meant for Harmony, Peace, Space Exploration, for Humanity — using the badge to brand weapons-class systems would invert the gift principle. The positioning closes that route.
This is a structural choice, not a marketing choice. The programme exists to keep critical decision systems available to humanity as gift.
The Foundation triad:
UniVERSE(mirror: GitHub) — The civilisational-scale programme. Whitepapers, governance, outreach.TrueAI(mirror: GitHub) — The immutable Foundation. Nine Invariants. Small. Stable. Never commercial.UniCORE-AI(mirror: GitHub) — The 12-Level reference architecture.
The substrate-services layer:
UniCORE.GVB(mirror: GitHub) — Global Virtual Bridge — the substrate-services layer (mail, file transfer, DNS, federation, tenancy, topology). Sister to this repository. Same certification gate. Same gift principle.
The SaaS-deployment-shape sisters:
UniSaaS.UniCORE(mirror: GitHub) — The SaaS-deployment-shape sister of this repository. Same governance, multi-tenant topology. CC BY 4.0 gift surface.UniSaaS.UniCORE.GVB(mirror: GitHub) — The SaaS-deployment-shape sister of UniCORE.GVB. Substrate-services layer for the SaaS topology. CC BY 4.0 gift surface.
The Vertical CORE family (working repositories — private until certification):
bryanunitek/UniCORE.Law-Claw— First Vertical CORE, Law sector. Working repository. Certification pending.- Future:
UniCORE.Accounting-Claw,UniCORE.Banking-Claw,UniCORE.Healthcare-Claw, etc., as additional verticals are produced. The industry list is open and is defined as the programme expands. Military is intentionally absent — the UniCORE Positioning Principle is Harmony, Peace, Space Exploration, for Humanity.
Substrate-harness working repositories (private, deployment-shape pair):
bryanunitek/UniCORE-Claw— on-prem-shape substrate-harness working repository. The reference Vertical CORE pattern (Module / UniVIEW / UniREPORT / hosts) that every concrete Vertical CORE inherits from. Currently being factored out ofUniCORE.Law-Claw.bryanunitek/UniSaaS.UniCORE-Claw— SaaS-shape substrate-harness working repository. SaaS-deployment-shape sister ofUniCORE-Claw.
Forked-upstream building-block families (scaffold-anchor as of 2026-06-04 — full scaffolding and upstream fork pending dedicated kickoff arcs):
UniCORE.Avalonia(mirror: GitHub) — Cross-platform .NET UI substrate. Fork of MIT Avalonia + UniCORE CC BY 4.0 additions (Pro-equivalent controls + Avalonia XPF).UniSaaS.UniCORE.Avalonia(mirror: GitHub) — 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(mirror: GitHub) — Web CMS / portal building block. Fork of MIT Dnn.Platform + UniCORE CC BY 4.0 modules.UniSaaS.UniCORE.DNN(mirror: GitHub) — 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(mirror: GitHub) — VoIP/PBX telephony engine. Fork of GPL-2.0 Asterisk + UniCORE additions. Full upstream history (34,425 commits).UniSaaS.UniCORE.Asterisk(mirror: GitHub) — 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(mirror: GitHub) — Video conferencing (Meet + Videobridge). Fork of Apache-2.0 Jitsi + UniCORE additions. Multi-upstream (13,956 commits).UniSaaS.UniCORE.Jitsi(mirror: GitHub) — 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(mirror: GitHub) — Secure messaging platform. Fork of AGPL-3.0 Signal Server + UniCORE additions. Full upstream history (5,010 commits).UniSaaS.UniCORE.Signal(mirror: GitHub) — 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(mirror: GitHub) — 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(mirror: GitHub) — 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.
Powered by UniCORE AI. Built on the TrueAI Foundation.
Attribution required wherever UniCORE, UniCORE AI, the TrueAI Foundation, or the 12-Level Governance Model is referenced, implemented, or extended.
Given, not sold. The architecture is public, open, and free. The TrueAI Foundation cannot be modified, forked, commercialised, patented, or proprietarily captured. See LICENSE.md for full terms; see the canonical UniVERSE/IRREVOCABLE-LICENCE-DECLARATION.md (mirror: GitHub) for the formal irrevocability declaration that covers the whole programme.
— Bryan Fred, Unitek Systems Limited, Bedford, United Kingdom, May 2026.
This repository is produced with AI assistance operating under TrueAI governance. The full disclosure is at AI-AUTHORSHIP.md (mirror: GitHub).
Programme-level debate, adoption questions, translation, and corrections belong in GitHub Discussions. What is in scope: questions about UniCORE's role in the Layered CORE model, the certification gate, the relationship to Vertical COREs, the gift principle as it applies to substrate code. What is out of scope: implementation specifics that belong inside a particular Vertical CORE's own repository.
For Foundation-level debate (the invariants themselves, the architecture, civilisational governance), use UniVERSE Discussions, TrueAI Discussions, or UniCORE-AI Discussions as appropriate.
UniCORE is the implementation reference for governed AI. It is not a product, platform, SaaS offering, tool category, or brand for sale. See STATEMENT-ON-CLAIMS.md (mirror: GitHub) for binding rules on how the UniCORE name may and may not be used.
- Public discussion: GitHub Discussions (see DISCUSSIONS.md (mirror: GitHub))
- Private contact / connection request: LinkedIn