Enterprise Security, Trust & Legal Shield

Justified Systems operates on a foundational architectural principle: zero remote data egress. We do not host your model weights, we do not ingest your proprietary codebase, and we do not route execution payloads through remote multi-tenant cloud APIs.

Enterprise Compliance & Exemption Rationale

Because both the Justified Engine (justified_engine.exe / justified_engine_setup.msi) and Justified DeScribe (justified_describe.exe) execute 100% offline on physical host hardware, traditional cloud SaaS compliance liabilities collapse:

Bring-Your-Own-Weights (BYOW) Legal Firewall

Justified Systems permanently decouples the compiled execution engine (justified_engine.exe) from all model parameter matrices:

• Substrate Neutrality: justified_engine.exe is an independent, unmanaged mathematical compute runtime[cite: 1]. It contains zero copyrighted, proprietary, or fine-tuned model weights embedded within its executable binary headers.
• License Isolation: Users supply their own open-weights models (such as standard GGUFv3 formats from Apache 2.0 or MIT repositories) or unlock proprietary encrypted .jef_bin companion vaults[cite: 1]. The licensing of the runtime engine does not claim ownership of or convey liability for user-supplied model outputs.
• Zero-Brick Perpetual Attestation: The runtime engine executes fully offline under a perpetual, zero-brick Ed25519 cryptographic attestation (license.key)[cite: 1]. Zero hardware node fingerprinting, zero rolling expiration time-bombs, and zero network activation pings during inference cycles[cite: 1].

Perpetual Continuity & Founder Sunset Protocol

Enterprise software licenses require absolute operational certainty without vendor lock-in or shutdown risk. In accordance with [JUS-ENG-ADD-05.01.000] and [JUS-WEB-SPEC-v1.0.0-ADDENDUM-24], Justified Systems guarantees continuous software availability through two immutable layers[cite: 1]:

• Zero-Brick Air-Gapped Operation: Because licenses are contractual Ed25519 digital signatures verified entirely in unmanaged RAM, active client binaries never connect to a central server[cite: 1]. Our software continues running indefinitely in air-gapped environments regardless of company status[cite: 1].
• Deterministic Sunset Protocol: Automated cloud dead-man switches have been replaced by the controlled Founder Sunset Protocol (scripts/trigger_sunset_release.ps1), eliminating false-positive releases caused by external cloud outages[cite: 1].
• Source Escrow Release: If commercial operations ever formally sunset, the protocol triggers an automated escrow directive, releasing clean C++ compilation sources and verification manifests to contracted enterprise partners for perpetual internal builds[cite: 1].

Cryptographic Signing, HSM Provenance & Gatekeeper Architecture

In accordance with [JUS-WEB-01.06.000], all unmanaged runtime binaries (justified_engine.exe, justified_describe.exe), Windows installers (justified_engine_setup.msi), and dynamic C-ABI libraries (justified_core.dll) distributed by Justified Systems are compiled directly from source and cryptographically authenticated against a dedicated Microsoft Azure Key Vault Hardware Security Module (HSM)[cite: 1].

• Bit-Level Transit Integrity: Every distributed binary is signed via AzureSignTool before staging[cite: 1]. Integrators can programmatically verify Authenticode signatures via PowerShell (Get-AuthenticodeSignature) or the Win32 WinVerifyTrust API to confirm zero byte-level corruption or unauthorized modification in transit.
• Windows SmartScreen Demarcation: Because our root certificate is a self-contained private authority rather than a commercial retail CA certificate pre-bundled into consumer Windows images, browser downloads receive the standard NTFS Mark-of-the-Web (Zone.Identifier = 3) and display an "Unknown Publisher" prompt. This is expected, by-design behavior for direct B2B infrastructure. Developers can unblock the binary in one command (Unblock-File .\justified_engine.exe) or pull via terminal (curl / Invoke-RestMethod). See the full SmartScreen & Authenticode Demarcation Guide →[cite: 1]
• Enterprise Fleet Whitelisting (WDAC): For locked-down enterprise environments, security teams deploy the pre-compiled justified_wdac_policy.xml rule to authorize our cryptographic thumbprint globally across their Windows Defender Application Control policies[cite: 1].
• OEM In-Process Distribution: When OEM partners embed justified_core.dll into their commercial desktop applications, host loaders link directly in-process via LoadLibrary with zero SmartScreen intervention[cite: 1]. The partner's build pipeline signs their final application installer with their own commercial credentials[cite: 1].

Zero Behavioral Tracking & Telemetry Policy

We maintain an uncompromising privacy stance across our public web canvas (justified-systems.com)[cite: 1]:

• Zero Behavioral Tracking: Zero Google Analytics, zero Meta/LinkedIn tracking pixels, zero marketing cookies, and zero client fingerprinting scripts.
• Edge Telemetry Purge: Inbound submissions from the Technical Intake portal are formatted into encrypted emails dispatched directly to engineering channels and immediately purged from edge memory (V8 isolates)[cite: 1]. Zero persistent cloud databases store your contact data.
• Merchant of Record Boundary: Commercial billing is governed exclusively by Polar.sh as Merchant of Record[cite: 1]. Payment card information, VAT remittance, and address verification execute entirely on Polar's PCI-DSS Level 1 compliant infrastructure[cite: 1].

Enterprise Compliance Dossier

Download authoritative legal, compliance, and enterprise whitelisting artifacts for security review: