Solutions

Regulatory Intelligence Platform

ArchAngel ingests any regulatory framework, parses every requirement, and classifies it as either a deterministic constraint or a probabilistic constraint. We translate regulation into code.

How It Works

Two Kinds of Truth

Not all compliance requirements are equal. ArchAngel knows the difference.

Protocol Context

Deterministic Engine

Enforce TLS 1.3

Verified Module
// CONSTRAINED_REQUIREMENT
require "tls" { min_version = "1.3" }
StateComputing Truth...

Probabilistic Engine

Vendor Risk Assessment

Human Verification Required

Ensure critical ICT third-party service providers undergo continuous risk assessment aligning with DORA Chapter V.

Signature Pending
Assignee: IT Risk Officer

Deterministic Concept

Rules that are binary and mathematically provable. Verified automatically via code analysis and state inspection, resulting in zero hallucination risk.

Probabilistic Concept

Requirements involving qualitative judgment or context. Escalated to humans with contextual evidence, requiring cryptographic signatures to proceed.

Applicability

Universal Capability

Industry examples illustrating how deterministic and probabilistic constraints apply across different regulatory domains.

Banking & Finance

DORAPSD2Basel III

The Context

DORA mandates continuous proof of ICT risk management and operational resilience. Banks must demonstrate that every architectural decision accounts for third-party dependencies and disaster recovery. Traditional quarterly reviews don’t meet DORA’s continuous evidence requirements.

Deterministic

  • TLS 1.3 enforced on all external-facing APIs.
  • Multi-region active-active failover configured for core ledgers.
  • Data at rest encrypted using AES-256.

Probabilistic

  • Sufficient third-party vendor risk assessment performed.
  • Adequate incident response plan documented and tested.
  • Business continuity strategy aligns with risk appetite.

Healthcare

HIPAAHITECHFDA 21 CFR Part 11

The Context

Patient data flows through increasingly complex microservice architectures. Every integration point is a potential HIPAA violation. Manual architecture review cannot keep pace with digital health innovation.

Deterministic

  • No direct internet ingress to PHI databases.
  • Session timeout configured to <= 15 minutes for clinical portals.
  • Audit logging enabled on all FHIR endpoints.

Probabilistic

  • Minimum necessary access principles applied to service roles.
  • Valid Business Associate Agreements (BAAs) exist for mapped vendors.
  • Anonymization protocols are statistically robust.

Government

FedRAMPNIST 800-53NIST AI RMF

The Context

Government systems operate under some of the most stringent compliance frameworks. AI adoption in government requires documented risk assessment and human oversight per NIST AI RMF.

Deterministic

  • FIPS 140-2 validated cryptographic modules used exclusively.
  • MFA enforced for all administrative control planes.
  • No unauthorized cross-boundary data flows detected.

Probabilistic

  • Continuous monitoring strategy effectively captures relevant metrics.
  • Supply chain risk management plan approved by authorizing official.
  • AI model transparency meets stakeholder requirements.

Energy & Utilities

NERC CIPIEC 62443NIS2 Directive

The Context

Critical infrastructure demands zero-tolerance for architectural drift. OT/IT convergence creates new attack surfaces that must be governed at the architectural level.

Deterministic

  • Strict network segmentation boundaries between OT and IT zones.
  • Default credentials changed on all enumerated ICS devices.
  • No outbound internet access from industrial controllers.

Probabilistic

  • Physical security perimeter controls are adequate for site classification.
  • Security awareness training program effectiveness metrics track positively.
  • Legacy system migration roadmap minimizes operational risk.

Insurance

Solvency IIDORAGDPR

The Context

Insurers face overlapping regulatory mandates across jurisdictions. Architecture documentation must satisfy multiple frameworks simultaneously.

Deterministic

  • Data residency restricted to approved geographic boundaries (e.g., EU).
  • Annual penetration testing scheduled and tracked.
  • User consent mechanisms integrated into all PII capture flows.

Probabilistic

  • Data minimization principles evaluated and deemed sufficient.
  • Legitimate interest assessments thoroughly documented and justified.
  • Algorithmic underwriting fairness metrics are within acceptable thresholds.

The Core Insight

"Regulations are written in natural language. ArchAngel translates them into the only language that doesn't lie: constraints."

Apply ArchAngel to Your Framework