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 the Justified Engine, Justified DeScribe, and our full catalog of C-ABI / WebAssembly (WASM) primitives execute 100% offline on physical host hardware and client browsers, traditional cloud SaaS compliance liabilities collapse:
| Framework | Status | Architectural Impact & Operational Rationale |
|---|---|---|
| SOC 2 Type II | CC6.6 EXEMPT | Customer data is never processed or stored on Justified servers. Zero cloud databases or multi-tenant hosting layers across all supported platforms. |
| PCI-DSS v4.0.1 (Client-Side) | ACTIVE CONTAINMENT | Primitives like jef-dom-guard provide deterministic, in-browser isolation against Magecart and supply-chain skimmers, neutralizing requirements 6.4.3 and 11.6.1 at the DOM level without cloud proxies. |
| Export Control (EAR) | ECCN 5D992.c (NLR) | Mass-market commercial software with standard cryptographic license verification. Eligible for No License Required (NLR) global export. |
| HIPAA / HITECH / GDPR | NO BAA REQUIRED | Zero Protected Health Information (PHI) ever traverses external network boundaries. Local runtime execution and inline SWAR PII redaction eliminate cloud Business Associate requirements. |
| NIST SP 800-171 / CMMC | AIR-GAP COMPLIANT | Controlled Unclassified Information (CUI) remains isolated within physical defense-industrial contractor hardware boundaries. |
| EU AI Act (Art. 50) | MINIMAL RISK | General-purpose local substrate with deterministic FSM logit clamping and zero autonomous biometric or subliminal manipulation vectors. |
Bring-Your-Own-Weights (BYOW) Legal Firewall
Justified Systems permanently decouples compiled execution engines (justified_engine.exe / justified_engine) from all model parameter matrices:
- Substrate Neutrality: Our distribution is an independent, unmanaged mathematical compute runtime across Windows PE32+, Linux ELF64, macOS Mach-O Metal, and WebAssembly (WASM). 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_bincompanion vaults. The licensing of the runtime engine does not claim ownership of or convey liability for user-supplied model outputs. - Zero-Brick Perpetual Attestation: Runtimes execute fully offline under a perpetual, zero-brick Ed25519 cryptographic attestation (
license.key). Zero hardware node fingerprinting, zero rolling expiration time-bombs, and zero network activation pings during inference cycles.
Perpetual Continuity & Founder Sunset Protocol
Enterprise software licenses require absolute operational certainty without vendor lock-in or shutdown risk. In accordance with the Sovereign Continuity & Vendor Sunset Covenant, Justified Systems guarantees continuous software availability through three immutable layers:
- 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. Our software continues running indefinitely in air-gapped environments regardless of company status.
- 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. - Nevada Custodial Escrow Contingency: An encrypted hardware recovery device containing execution scripts, repository blueprints, and signing recipes is held in escrow by the company's designated legal counsel in Nevada. In the event of formal corporate dissolution or confirmed founder incapacitation, the custodial executor is legally instructed to dispatch the master AES-256 decryption keys and Apache 2.0 open-source grant to all verified major-version licensees.
Cryptographic Signing, HSM Provenance & Gatekeeper Architecture
All Windows unmanaged runtime binaries (justified_engine.exe, justified_describe.exe), 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). Linux, macOS binaries, and .wasm modules maintain embedded cryptographic SHA-256 integrity digests verifiable against our on-chain version ledger.
CN=CLIGetDefaultPolicy, Thumbprint: 379A208A4223EE53525B0BBAE9FC4A7FCE76DE9C) with DigiCert RFC 3161 SHA-256 trusted timestamping. We deliberately operate independent of commercial retail Certificate Authorities (CAs), eliminating recurring annual certification overhead for bare-metal B2B infrastructure.
- Bit-Level Transit Integrity: Every distributed Windows binary is signed via AzureSignTool before staging. Integrators can programmatically verify Authenticode signatures via PowerShell (
Get-AuthenticodeSignature) or the Win32WinVerifyTrustAPI 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 → - 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.
- OEM In-Process Distribution: When OEM partners embed
justified_core.dll,libjustified_core.so,libjustified_core.dylib, or primitive.wasmmodules into their commercial applications, host loaders link directly in-process viaLoadLibrary/dlopenwith zero SmartScreen intervention. The partner's build pipeline signs their final application installer with their own commercial credentials.
Zero Behavioral Tracking & Telemetry Policy
We maintain an uncompromising privacy stance across our public web canvas (justified-systems.com):
- 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). Zero persistent cloud databases store your contact data.
- Merchant of Record Boundary: Commercial billing is governed exclusively by Polar.sh as Merchant of Record. Payment card information, VAT remittance, and address verification execute entirely on Polar's PCI-DSS Level 1 compliant infrastructure.
Enterprise Compliance Dossier
Download authoritative legal, compliance, and enterprise whitelisting artifacts for security review:
Executive Bridge Letter
Signed executive SOC 2 / ISO 27001 zero-egress architecture bridge letter for procurement teams.
WDAC Whitelist Policy
Pre-compiled Windows Defender Application Control XML whitelisting policy for enterprise IT rollouts.
Provenance Manifest
Machine-readable JSON manifest verifying permissive open-source training data and license hygiene.
EU AI Act Attestation
Formal Article 50 minimal-risk self-classification and technical transparency documentation.