CORP-US Defense · protected operations · civil resilience Public capability page · full detail under authority
CORP-US

Local intelligence for protected operations, resilient infrastructure and disconnected environments.

CORP-US is Wyrd's defense, protected-operations, civil-resilience, strategic-infrastructure, robotics, drone, maritime and government division. It runs on the same governed stack as the rest of the group — identity, mandate, command chain, rules of engagement, theater boundary, escalation ladder, dual key, signed proof — deployed where the network is contested and the consequence is physical.

The authority model

Machines that can operate alone, under authority that never leaves the human.

Every CORP-US system inherits the same ICARUS primitives. This is what makes edge autonomy defensible: the node can decide under signal silence because its limits were signed before it left.

11
CommandChain
The ordered authority path from the institution or commander to execution. No action exists outside a chain.
12
RulesOfEngagement
Domain rules and boundaries for permitted operation, signed and machine-checkable.
13
TheaterBoundary
Geographic, institutional, network or environmental limits on where a system may act at all.
14
EscalationLadder
Routine handling → review → restriction → shutdown, defined before deployment.
15
DualKey
Two-party authorization wherever duties must stay separated.
10
RDOverride
An explicit, recorded research-and-development override — never silent authority.
06
ProofPack
The after-action record: who, what, why, under which mandate, approved by whom, and what was refused.
What this means operationally

A CORP-US node reasons locally, selects an approved model, acts inside a bounded mandate, refuses what is unauthorized, keeps signed records, and synchronizes when a link returns. Human command is not a UI courtesy — it is a cryptographic precondition. Fail-closed is the default: when authority cannot be verified, the system does not act.

Corpus / Legion

Command, cyber and institutional operations.

The operating family inside CORP-US: command theatre, mission context, operator roles, city and field systems, cybersecurity, fleet visibility, human approvals and proof.

CTOS · Command Theatre
City and institutional operating layer.
Architecture defined
What it coordinates

Transport, roads, utilities, emergency response, infrastructure, drones, autonomous mobility, public-service workflows, city digital twins and governed actuation.

Market entry

Planning, observation, simulation, proof and advisory pilots first; narrow authorized actuation after. We do not present CTOS as omniscient city control.

WRAITH
Cybersecurity defense operations.
Architecture defined
Scope

Authorized monitoring, anomaly detection, hardening, incident response, infrastructure preparation, proof, isolated resilience and defensive exercises.

Assurance track

IEC 62443 for operational technology, plus the Conformity Lab's continuous rehearsal against SOC 2, ISO 27001 / 42001, the Cyber Resilience Act and FIPS 140-3.

LANCE
Licensed, authorized offensive-cyber operations — governed separately from WRAITH.
Restricted
Programme status

A separately governed capability track for authorized cyber assessment and high-assurance security operations, subject to law, licensing and client mandate. Separation from WRAITH is deliberate: defensive and offensive authority never share a key.

Release conditions

Lawful customer authority, licensing, export review, procurement rules, independent legal and safety controls. Technical content is exchanged only in that channel — never in web, deck or general partner material.

Field operations

Samael and Azrael — one stack, two doctrines.

Civilian protection and military operations share the software and are governed as separate programs with separate authority. They are never merged, and never share a mandate.

Samael · civilian protection

Judgment before action.

  • Fire, flood, earthquake, rescue
  • Missing-person search, medical evacuation
  • Infrastructure incidents, hazardous-area work
  • Civil defense and resilient field comms
  • Samael Field Mesh for operator support
  • Observe · verify · understand · seek authority · protect · record
Azrael · military operations

Lawful defense support.

  • Situational awareness for the operator and the command
  • Air-gapped coordination under signal silence
  • Logistics and sustainment intelligence
  • Resilient, encrypted communications
  • Operator protection and survivability
  • Human-controlled mission support
  • After-action proof an auditor can verify
Azrael
The military-operations family. Restricted programme, named and placed.
Restricted
What Wyrd contributes

The governed local brain: edge autonomy that keeps functioning without uplink, a mandate that bounds what the node may do in a defined theater, an escalation ladder that ends in shutdown, and a tamper-evident record of every decision and refusal.

Why it is a separate programme

Because the authority model must be auditable independently of the civilian stack. Azrael carries its own command chain, its own rules of engagement and its own keys.

Release conditions

Lawful customer authority, licensing, export review, procurement rules, independent safety and legal controls, explicit human command and domain-specific approval. Weapons, targeting and offensive-autonomy content is handled in that channel and does not appear in any public or general partner document.

Naming

Azrael is the preferred spelling (recorded variant: Asrael). Never used as a synonym for Samael.

Samael Exo
Protected field-assist and exosuit programme.
Research prototype
Editions
SecureRescueAceso medicalIndustrialSport & training
The stack it combines

Physical load support, Wyrd Lens, a local CAOS field node, encrypted communication, 3D awareness, biometric safety, drone and robot coordination, proof logs and human command.

The promise

Awareness, endurance, survivability, coordination and proof.

Wyrd Lens · field edition
Visual interface and sensor surface for field and industrial work.
Research prototype
Field uses

Visual verification, object memory, guided procedure, industrial work, field awareness and protected-operations visual-feed unification.

Boundary

Consumer and field editions stay visually and legally separated, with local redaction on the sovereign-vision path.

Casualty-reduction intelligence
Awareness intended to lower harm to operators and civilians.
Partner / restricted
Placement

Samael where the customer is civil protection; Azrael where a lawful defense customer and authority exist. Visibility follows the customer and the jurisdiction.

Machines

Air, land, surface, subsea — coordinated as one governed system.

HIVE is domain-neutral. Every vehicle class inherits the same mission contracts, lost-link rules and signed replay. Near-term strategy is partner hardware plus Wyrd software.

HIVE
Multi-agent, multi-robot and fleet coordination.
Integration program
Core software

Mission contracts, task allocation, fleet state, battery and resource awareness, relay planning, dock planning, disconnected operation, lost-link behaviour, adaptive coordination and signed after-action replay.

Protected uses
Field situational awarenessEncrypted relayVisual-feed fusionRoute safetyTeammate & asset awarenessInfrastructure protectionAuthorized surveillanceAfter-action proof
Civil uses
MappingThermal inspectionSearch & rescueFire observationFlood assessmentMedical deliveryPipelines & power linesPortsBorder awarenessDisaster logistics
Evidence

Release gate reports 190 passing tests plus static and security checks. No hardware, SITL, field, regulator or customer validation yet — simulation and SITL come before any vehicle.

Mission simulation — illustrative
THEATER BOUNDARY · TB-04 DOCK relay · lost-link armed mapping thermal search task outside TB-04 ✕ refused no mandate signed after-action replay · every allocation and refusal recorded
Hardware families
The vehicle classes recorded in the design work.
Research prototype
Recorded classes
Short-range mapping multirotorLonger-range relay VTOLCharging podMicro-delivery dronePersistent nodeGround vehicleSurface vesselUnderwater scoutModular Phaeton body
Strategy

Partner hardware, reference designs and certification — not immediate mass manufacture of every vehicle.

Leviathan
Maritime and subsea operations — reusable, autonomous, provable.
Integration program
Product direction

Leviathan Watch for persistent monitoring and mission control · Leviathan Scouts as partner-built underwater vehicles · Leviathan Signal for acoustic, optical, buoy, vessel and delayed-sync communication, with HIVE Deep for disconnected fleet coordination.

Missions
Submarine-cable inspectionOffshore assetsPorts & coastlinesPipelinesSearch & recoveryEnvironmental monitoringInfrastructure security
Still to prove

Manufacturer adapters, realistic simulation, hardware-in-the-loop work, production cryptography and sea trials. Wyrd does not manufacture submarines.

Phaeton
Multimodular robotics.
Research prototype
Reconfigurable bodies
WheelsTracksLegsArmsToolsSensorsCargoAerial modulesSurface modules
Wyrd's contribution

Local brain, mission policy, module identity, tool permissions, coordination, proof and lifecycle. Not a synonym for Leviathan.

NOMAD
Persistent aerial-node design study.
Research prototype
Payload intent

Communications relay, sensing, local compute, mapping, emergency support and airspace awareness on a long-endurance platform.

Honest status

A local 3D design study exists. Aerodynamics, certification, energy, payload and field performance are unvalidated.

HIVE Frontier
Lawful border-awareness and rescue system.
Architecture defined
Functions

Corridor monitoring, remote-post connectivity, terrain mapping, missing-person and rescue support, anomaly alerts, inspection prioritization, anti-smuggling intelligence, protected communications, and proof of observation and intervention.

Mandatory controls

Jurisdictional authority, retention limits, access control, civilian protection, anti-discrimination testing, confidence thresholds, human decision, and appeal and audit paths where applicable.

Counter-autonomy

Accountable machine defense.

The problem is not only detecting an uncrewed machine. It is proving whether that machine had authority to be there — and proving what was done about it.

PALLADIUM
Sovereign zero-trust machine-defense and counter-autonomy shield.
Research prototype
The differentiator

A Proof-of-Flight Mandate — or equivalent machine-authority record: identify the machine, verify authority, check time and boundary, deconflict against friendly traffic, then allow, quarantine or escalate, and record proof.

Public boundary

Accountable counter-autonomy and authorized machine verification are described. Countermeasure engineering is not published; it belongs to the restricted channel with the customer's authority.

Wyrd Dome
City-scale accountable counter-UAS governance and proof.
Research prototype
What it governs

Detection, identity, authorization, deconfliction, protected airspace, human decision and evidence — the accountability layer a city or authority needs before anything else happens.

What it is not

Not a claim that Wyrd has deployed an autonomous weapon.

Continuity

When infrastructure fails, the mission does not.

RADOME
Identity-gated continuity bubble for a degraded incident zone.
Pilot candidate
Core objects

MeshNode — local relay and compute. ConnectivityBubble — a bounded incident-zone network. MessageBundle — signed, delayed-sync packets. Plus RADOME Core, Mesh, Response, Citizen, Proof and Integrations for radios, sensors and agency systems.

Missions
WarningEvacuationRescueAid routingResponder coordinationFamily reunificationIncident proof
Doctrine

RADOME moves information, people and aid. It does not move explosives. Copper Dome is the lower-cost COTS configuration for resource-constrained regions.

ORION / OSAS
Rapid logistics and relief-payload programme.
Research prototype
Roadmap

ORION-Micro (compact COTS pod) → ORION-Field (rugged local server, radios, drones, sensors and proof) → ORION-Coastal (buoy and underwater-scout support) → ORION-Strato and ORION-Space as future partnerships.

Honest framing

The first product is the pod, not a spaceship.

Wyrd ARK
Continuity intelligence for isolated facilities.
Pilot candidate
What it does offline

Power and resource forecasting, air and water monitoring, inventory, maintenance, repair guidance, access control, emergency procedures, communication, drills and signed records — for hospitals, mines, offshore platforms, embassies, bases, data centers, shelters and isolated communities.

Hard limit

Life-support control stays with certified deterministic controllers, interlocks and manual override. A language model does not control life support.

Anchorline & Heimdall
Protected-site access, awareness and incident evidence.
Pilot candidate
Capabilities

Zones, detection, context, access, challenge, audit, replay, factory-gate logic and tamper-evident records, with Camera Watchman for locally processed, bounded-retention visual monitoring under human review.

Engagement

How a defense or government customer starts.

Nothing begins with a live weapon system or a live network. It begins with a diagnostic, an authority map, and simulation.

diagnostic authority & jurisdiction map simulation / SITL offline replay read-only field trial bounded mandate exercise controlled pilot measured decision
The institutional briefing

The full CORP-US briefing — programme depth, the Azrael and LANCE tracks, PALLADIUM engineering, integration architecture and the fail-safe contracts — is released against lawful customer authority, licensing, export review and procurement rules, under NDA, to the responsible office. It is not a download.

Edge autonomy that decides under signal silence — and can still be held to account.

Protection-led, bounded by doctrine and law, with a tamper-evident record an auditor can verify.