Decision Gate Enterprise (DG-E) is a private deployment, governance, and qualification realization of the public DG kernel. It is not a second semantic kernel.
Boundary
OSS owns RET, Xarxa, typed scenario/evidence law, pure evaluation, the accepted-run protocol, qualified local durability, and exact verification claims. DG-E may add multi-tenancy, identity and authorization bindings, governed catalogs, enterprise storage realizations, exact product-key routing, serving assignment, secrets, audit, operations, qualification, integration, and support.
Shared platform authorities own serving cells, capacity, residency, secrets, and physical-resource lifecycle. A DG-E profile may consume their exact witnesses; it does not copy those registries or protocols into DG semantic state.
Current implementation
Private repositories currently contain useful but unqualified lineage:
- OIDC, API-key, static-token, RBAC, and namespace-administration adapters, plus one explicitly configured principal for the process-local stdio transport;
- documentation governance and tool-visibility policy;
- hash-chained audit records and deterministic exports;
- usage/quota ledgers and exports;
- SQLite/PostgreSQL records plus filesystem and S3-compatible runpack-store lineage that is not a supported PF-05 capability;
- control-plane, admin, telemetry, packaging, and starter-kit surfaces.
These facts do not establish the permanent evidence witness chain, authority-minted run creation, accepted-run model refinement, immutable accepted revisions, dispatch recovery, assignment-stable multi-node qualification, or launch readiness. Hash chaining and manifests prove only their exact bounded integrity relations.
PF-05 supports capability-rooted local publication and supplied-material offline verification only. Remote immutable publication/retrieval requires its own repository, authentication, credential, retry/idempotency, network threat, and qualification authorities. Existing enterprise S3-compatible lineage is therefore deferred DG-E/PF-08 work, not an implementation of the OSS runpack- v6 repository contract.
Initial target
The initial enterprise target uses the same co-located evaluator and
accepted-run authority as OSS. Different RunKey values may route to different
nodes, but one evaluation is not split across machines. Its evidence target is
caller submission plus bounded local time, allowlisted environment snapshot,
and rooted JSON/YAML observation.
HTTP/REST acquisition, remote MCP, MCP stdio/subprocess execution, arbitrary executable providers, remote evaluation, dynamic owner transfer, automatic failover, active-active mutation, open-ended scenarios, and DG-owned cross-scenario orchestration are excluded or deferred PF-08 families. Existing code presence does not add them to a target or supported profile.
Commercial value
Subject to implementation and exact profile qualification, DG-E value may include:
- enterprise identity, authorization, governance, retention, audit, and compliance bindings;
- enterprise backend realizations conforming to the public accepted-run law;
- stable
RunKeybinding and routing to one resolved co-located authority perRunKey; - platform-witness integration for capacity, residency, secrets, and policy;
- hardened packaging, upgrade, backup, restore, incident response, and support;
- high-assurance review and HSFL-scale qualification.
Correctness is not withheld from OSS to create enterprise value. Private code cannot introduce another condition algebra, evidence truth model, graph law, accepted-run relation, or verification vocabulary.
Packaging status
The commercial cut is provisional until PF-01 through PF-09 close for the selected profile. A target document, private crate, generated contract, or sales discussion is not implementation or support evidence.
Contact and licensing
- Email:
license@arxiu.io - Decision Gate Enterprise:
arxiu.io/decision-gate - Direct contact:
https://www.linkedin.com/in/michael-campbell-73159b5a/
Discussion does not imply that an unqualified deployment profile is available.