Unified Lattice Solver Technologies

ArchenFrame™ Guardian

Resilience Engineering for Integrated Cyber-Physical Subsystems Through Evaluation, Design, and Runtime Governance

Unified Lattice Solver Technologies develops ArchenFrame™ Guardian, a deployable resilience-engineering platform for complex systems where failure, drift, outage, cyber intrusion, fragmentation, or degraded recovery can create serious consequences.

ArchenFrame™ Guardian helps organizations answer one central question:

Can the system remain coherent, resilient, and decision-ready under stress?

Traditional cybersecurity tools help detect, block, or investigate threats. ArchenFrame™ Guardian focuses on what happens next:

What still works?
What is degraded?
Which nodes and edges are unsafe?
What should recover first?
What evidence supports the decision?

ArchenFrame™ Guardian maps critical systems as living node-edge mission graphs. It evaluates system behavior before failure, supports resilience design before deployment, and provides runtime governance during disruption.

The result is decision-grade resilience evidence for executives, engineers, operators, auditors, regulators, and mission owners.

The Guardian Resilience Cycle

ArchenFrame™ Guardian is built around three connected functions:

1. Evaluation

Guardian evaluates the system before failure by mapping critical nodes, edges, pathways, dependencies, fallback routes, exposure points, and recovery constraints.

This helps organizations understand where coherence can break, where fragmentation may spread, and which parts of the system are most important to protect, monitor, or redesign.

2. Design

Guardian supports resilience design by turning evaluation results into structured engineering evidence.

This may include design recommendations, upgrade priorities, segmentation strategies, fallback planning, recovery sequencing, controlled-isolation logic, and domain-specific resilience improvements.

The design stage helps organizations strengthen the system before runtime deployment.

3. Runtime Governance

Guardian provides runtime governance during disruption.

It monitors system behavior under stress, drift, outage, intrusion, or partial degradation; scores resilience state; identifies unsafe nodes and edges; supports recovery decisions; and generates decision-grade evidence while the mission is still unfolding.

This is where Guardian moves beyond evaluation and becomes a survivability and assurance layer.

What ArchenFrame™ Guardian Does

ArchenFrame™ Guardian helps organizations:

  • map critical nodes, edges, pathways, dependencies, and recovery routes;

  • evaluate exposure, degradation, fragmentation, and closure failure;

  • support resilience design decisions before deployment;

  • identify upgrade priorities, fallback options, and recovery sequences;

  • monitor system behavior under stress, outage, drift, or intrusion;

  • govern runtime degradation, protection, and recovery decisions;

  • support post-intrusion survivability;

  • strengthen air-gapped, offline, segmented, and controlled-isolation environments;

  • generate evidence reports for leadership, technical teams, auditors, regulators, and mission owners.

The platform is designed for domains where ordinary dashboards are not enough because the mission must continue safely even when part of the system is compromised, fragmented, or degraded.

Core Products

1. ArchenFrame™ Guardian Demo Kit

A portable two-device demonstration system.

One device runs a domain twin, such as a miniature bank, water SCADA system, grid segment, data center, healthcare workflow, mission system, or public-safety pathway.

The second device runs ArchenFrame™ Guardian and shows how the system is mapped, evaluated, scored, degraded, protected, governed, and recovered.

The Demo Kit is the fastest way to see the full Guardian cycle in action:

evaluation, design insight, and runtime governance.

2. ArchenFrame™ Guardian Evaluation and Design Workbench

A pre-deployment resilience workbench for organizations preparing for a Guardian deployment.

The Evaluation and Design Workbench maps the organization’s domain, identifies critical nodes and edges, evaluates exposure and degradation pathways, tests stress scenarios, and produces decision-grade design evidence.

This stage helps answer:

Where is the system fragile?

Which upgrades matter most?

What should be redesigned before runtime deployment?

What evidence supports those decisions?

The workbench may produce resilience scores, design recommendations, scenario results, fallback logic, recovery priorities, and a deployment-readiness package.

When design upgrades are recommended, the organization may choose to implement them and then run a second evaluation before final deployment.

3. ArchenFrame™ Guardian Site Runtime Deployment

A deployable runtime-governance system for one facility, utility, branch, enclave, workflow, infrastructure segment, or operational domain.

Site Runtime Deployment may include edge collectors, local appliances, dashboards, domain-specific node-edge monitoring, degradation scoring, recovery-path logic, controlled-isolation support, recurring evidence reports, and executive resilience summaries.

This is the operational layer of ArchenFrame™ Guardian.

It helps the organization monitor what still works, understand what is degraded, identify unsafe nodes and edges, prioritize recovery, and preserve decision-grade evidence during real stress events.

4. ArchenFrame™ Guardian Enterprise Deployment

A larger deployment for companies, utilities, hospitals, data centers, banks, public-sector partners, infrastructure operators, or multi-site organizations that need broader resilience governance.

Enterprise Deployment may include multiple domain packs, multiple sites, edge collectors, local appliances, executive dashboards, recurring evidence, controlled-isolation support, cross-domain reporting, and resilience-governance workflows.

Managed Resilience support may be added when an organization wants ULST assistance with monitoring, tuning, evidence review, scenario updates, domain-pack refinement, and recurring resilience reporting.

Domains Covered

ArchenFrame™ Guardian can be configured for multiple mission-critical domains. These are covered in more detail on the domain pages of this website.

Key domains include:

Banking and Financial Operations

Core banking, payments, fraud/AML, identity, vendors, branches, ATMs, backups, operational resilience, cyberstability, and post-quantum readiness.

Water, SCADA, and Civil Infrastructure

Pumps, valves, tanks, PLCs, HMIs, telemetry, historians, treatment systems, operator workflows, manual fallback, and biosphere-to-tap resilience.

Grid, Energy, and Industrial Systems

Substations, relays, breakers, distributed energy, industrial controls, hydrogen systems, propulsion, thermal systems, and high-consequence physical operations.

Data Centers, Cloud, and Telecommunications

Power, cooling, UPS, generators, network core, storage, backup, identity, cloud service continuity, fiber/RF pathways, and emergency communications.

Healthcare and Clinical Systems

Medical-device networks, clinical workflows, patient pathways, diagnostics, hospital operations, pharmacy systems, backup systems, and safety-critical medical software.

Mission, Aerospace, and Autonomy

Mission assurance, flight safety, autonomous systems, RF/photonic systems, launch safety, swarm behavior, cyber-physical mission systems, and high-reliability operations.

Post-Quantum and Cryptographic Resilience

Cryptographic inventory, certificate and key dependencies, payment and identity trust edges, vendor cryptographic readiness, crypto-agility, and quantum-era operational continuity.

Air-Gapped and Controlled-Isolation Resilience

Many critical systems cannot rely on ordinary cloud-connected monitoring.

ArchenFrame™ Guardian can support air-gapped, offline, segmented, and controlled-isolation environments where systems must remain safe and decision-ready under stress.

ArchenFrame™ Guardian does not break the air gap.

It helps give isolated systems a survivability map, runtime memory, degradation scoring, recovery-path logic, and decision-grade evidence.

Why It Matters

When a system fails, the most important question is not only whether an alert was triggered.

The deeper question is:

Can the mission still continue safely?

ArchenFrame™ Guardian is built for that question.

It turns complex-system uncertainty into structured resilience evidence by helping organizations evaluate the system, design for resilience, govern behavior at runtime, and act before fragile systems break.

ArchenFrame™ Guardian is not only an evaluation tool.

It is a resilience-engineering platform for integrated cyber-physical subsystems, connecting evaluation, design, and runtime governance into one deployable framework.

A Unifying Layer for Decision-Makers

For managers, CFOs, executives, risk leaders, operators, and mission owners, ArchenFrame™ Guardian acts as a unifying resilience layer across complex subdomains.

Many organizations already have the pieces: cybersecurity tools, financial reports, vendor reviews, engineering assessments, compliance evidence, operational dashboards, recovery plans, and domain-specific teams.

What is often missing is a coherent way to see how those pieces interact under stress.

ArchenFrame™ Guardian helps connect fragmented signals into one mission-aware resilience picture, so leaders can understand what is working, what is degraded, what decisions matter most, and what evidence supports action.

ArchenFrame™ Guardian is designed for leaders and teams responsible for keeping complex systems coherent, resilient, recoverable, and decision-ready under stress.

Typical users and stakeholders may include:

  • Chief Executive Officers responsible for enterprise continuity, strategic risk, mission assurance, and organizational resilience.

  • Chief Operating Officers responsible for operational continuity, recovery priorities, cross-functional coordination, and service delivery under stress.

  • Chief Financial Officers responsible for financial exposure, resilience budgeting, insurance concerns, infrastructure investment, loss prevention, and continuity-related capital decisions.

  • Chief Risk Officers responsible for enterprise risk, operational resilience, systemic exposure, risk aggregation, and board-level risk evidence.

  • Chief Information Officers responsible for technology continuity, platform dependencies, recovery pathways, and digital infrastructure resilience.

  • Chief Information Security Officers responsible for post-intrusion survivability, cyber resilience, segmentation, identity trust, and security evidence.

  • Chief Technology Officers responsible for technical architecture, platform resilience, engineering design, system modernization, and technology strategy.

  • Chief Compliance Officers responsible for regulatory evidence, audit readiness, governance documentation, control mapping, and supervisory review support.

  • Chief Data Officers responsible for data pathways, information integrity, reporting structures, analytics dependencies, and evidence quality.

  • Chief Procurement Officers responsible for vendor exposure, supplier continuity, third-party dependency risk, and recovery alternatives.

  • Chief Sustainability Officers responsible for water, energy, environmental, climate-linked, and supply-chain resilience evidence.

  • Chief Legal Officers and General Counsel responsible for legal exposure, incident documentation, regulatory response, defensible decision records, and governance review.

  • Board members responsible for oversight of enterprise risk, resilience investment, operational continuity, cyber risk, safety, and mission assurance.

  • Executive leadership teams responsible for understanding what still works, what is degraded, what must recover first, and what evidence supports action.

  • General managers responsible for business-unit continuity, operational readiness, staff coordination, customer impact, and service recovery.

  • Operations directors responsible for service continuity, system performance, operational bottlenecks, recovery execution, and cross-team coordination.

  • Engineering directors responsible for system design, technical dependencies, architecture improvements, resilience design priorities, and implementation planning.

  • Plant managers responsible for industrial continuity, safety margins, control pathways, recovery sequencing, and site-level resilience.

  • Utility managers responsible for water, wastewater, grid-adjacent, SCADA, treatment, pump, storage, and distribution resilience.

  • Hospital administrators responsible for clinical operations, patient pathways, medical-device dependencies, backup systems, emergency continuity, and care-delivery resilience.

  • Data-center managers responsible for power, cooling, network, storage, backup, cloud, identity, and service-continuity pathways.

  • Telecom operations managers responsible for network continuity, fiber and RF pathways, emergency communications, service degradation, and recovery routing.

  • Aerospace program managers responsible for readiness evidence, mission assurance, test environments, safety pathways, and high-reliability operations.

  • Mission owners responsible for mission continuity, degraded-mode behavior, command pathways, recovery priorities, and decision-grade assurance.

  • Emergency management directors responsible for response coordination, continuity planning, fallback pathways, public-sector resilience evidence, and recovery prioritization.

  • Public works directors responsible for infrastructure continuity, utility coordination, water access, emergency response, and public-service readiness.

  • Safety officers responsible for safety-critical workflows, degraded operating states, hazard pathways, recovery decisions, and safety evidence.

  • Site reliability engineering leaders responsible for service reliability, dependency mapping, failover behavior, runtime indicators, and recovery pathways.

  • Security operations leaders responsible for cyber incident visibility, degraded system states, unsafe nodes and edges, and post-intrusion evidence.

  • OT and SCADA managers responsible for industrial control resilience, segmented monitoring, local appliances, recovery logic, and air-gapped or controlled-isolation environments.

  • IT infrastructure managers responsible for identity, network, backup, cloud, endpoint, platform, and service-continuity dependencies.

  • Business continuity managers responsible for continuity plans, recovery priorities, tabletop scenarios, operational dependencies, and resilience evidence.

  • Disaster recovery managers responsible for backup readiness, recovery sequencing, degraded-mode operation, restoration evidence, and post-event review.

  • Enterprise risk managers responsible for cross-domain risk visibility, systemic exposure, risk aggregation, and executive resilience reporting.

  • Internal audit leaders responsible for audit evidence, control-pathway review, resilience documentation, and management assurance.

  • Compliance managers responsible for regulatory mapping, evidence packages, reporting workflows, internal controls, and governance documentation.

  • Model-risk managers responsible for model behavior, probability drift, decision-path exposure, validation evidence, and model-governance support.

  • Fraud and AML leaders responsible for transaction-path pressure, fraud detection pathways, escalation workflows, and financial propagation evidence.

  • Treasury leaders responsible for liquidity pathways, settlement exposure, payment continuity, counterparty stress, and financial recovery priorities.

  • Vendor-risk managers responsible for third-party dependencies, supplier exposure, service continuity, substitution pathways, and vendor recovery evidence.

  • Supply-chain leaders responsible for critical materials, supplier concentration, logistics fragility, inventory thresholds, and recovery alternatives.

  • Quality and assurance leaders responsible for readiness evidence, verification workflows, safety cases, recurring resilience indicators, and corrective-action support.

  • Program managers responsible for coordinating technical teams, business stakeholders, evidence packages, and implementation priorities.

  • Product leaders responsible for product continuity, platform dependencies, customer-impact pathways, and resilience-by-design decisions.

  • Research leaders responsible for technical evidence, model assumptions, validation workflows, experimental pathways, and publication-ready findings.

  • Ministry, NGO, and public-good leaders responsible for vulnerable-community protection, water resilience, service continuity, prevention-oriented evidence, and mission-focused resource planning.

  • Consultants and systems integrators responsible for helping clients map dependencies, evaluate fragility, design improvements, and deploy runtime resilience support.

ArchenFrame™ Guardian gives these roles a shared resilience language.

Instead of viewing cyber, operations, finance, engineering, compliance, safety, vendors, infrastructure, and recovery as disconnected reports, Guardian helps leaders see how the pieces interact as one mission system.