Restricted & partner register Visibility model · authorized channels Names and placement only · detail is gated
Visibility

The restricted programs exist. Their detail lives in authorized channels.

This page is the complete ledger: what is partner-only, what is private, what is restricted, and which categories of material never leave a lawful, licensed channel. Nothing is hidden from the map — the map simply states where each thing is discussed.

How to read this page

Every entry below is real and recorded in company canon. What appears here is the name, the placement and the boundary. Operational content — methods, procedures, parameters, targeting, payloads, intrusion technique — is not published in any Wyrd material, public or partner. It is handled under lawful customer authority, licensing, export review, procurement rules, independent safety and legal controls, and explicit human command.

Public

Main website, public deck, recruiting, general press.

Partner

Qualified design partners, regulated institutions, technical diligence.

Private

Investors, board, internal operating documents, controlled demonstrations.

Restricted

Authorized governmental, legal, security or defense channels only.

CORP-US

Protected-operations programs and their boundaries.

CORP-US spans civil protection through to restricted defense support. The split between them is doctrinal, not cosmetic: Samael and Azrael are separate programs and are never merged.

Azrael
The restricted military-operations family.
Restricted
What may be described at all

Lawful defense support, situational awareness, air-gapped coordination, logistics, resilient communications, operator protection, human-controlled mission support and after-action proof.

What is never described

Operational, targeting, weapons and offensive-autonomy material stays outside every public and general partner document. It exists only in restricted channels with a lawful customer, licensing and export review.

Naming rule

Azrael is the preferred spelling (recorded variant: Asrael). It must not be merged with Samael, which is civilian protection.

Visibility

Restricted

LANCE
Separately governed, licensed, authorized offensive-cyber operations concept.
Restricted
Placement

Inside Corpus / Legion, governed separately from WRAITH's defensive work. It belongs in restricted materials only.

The only sentence we publish

"Authorized cyber assessment and high-assurance security operations, subject to law, licensing and client mandate."

What is never published

Operational intrusion methods, payload design, persistence methods, sabotage procedures and unauthorized surveillance capability. Not on the website, not in decks, not in partner packs.

Visibility

Restricted

PALLADIUM
Sovereign zero-trust machine-defense and counter-autonomy shield.
Research · partner detail
The differentiator

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

Public boundary

Accountable counter-autonomy and authorized machine verification may be described. Operational countermeasure detail may not. Public detail stays high level by rule.

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

Detection, identity, authorization, deconfliction, protected airspace, human decision and evidence.

What it is not

It is not a claim that Wyrd has deployed an autonomous weapon.

HIVE Frontier
Proposed lawful border-awareness and rescue system.
Architecture defined
Possible functions

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

Mandatory controls

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

Visibility

Partner

Samael Exo
Protected field-assist and exosuit direction.
Research prototype
Editions

Secure · Rescue · Aceso medical · Industrial · Sport and training.

The stack it may combine

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

The public promise

Awareness, endurance, survivability, coordination and proof.

Casualty-reduction intelligence
High-level protected-operations awareness.
Partner / restricted
Placement

Samael for civilian protection; Azrael where a lawful defense customer and authority exist. Visibility is partner or restricted depending on the customer and the jurisdiction.

Corpus / Legion · CTOS · WRAITH
The command, city and cyber operating family inside CORP-US.
Architecture defined
What they combine

Command theatre, mission context, operator roles, city and field systems, cybersecurity, fleet visibility, human approvals and proof. They are internal product families, not peer divisions.

WRAITH's scope

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

Security & sovereignty modules

Partner-level and research-level security work.

Recorded across the shared stack. Several require a legal and technical review before they are offered to anyone.

Module
Placement
Current interpretation
Federation Mesh
Shared security
Governed cooperation among separate Wyrd nodes or institutions.
Private communications tunnel
Shared security
Protected communication path bound to policy and identity.
Metadata hardening
Shared security
Minimize and protect revealing communication metadata.
Hidden-traffic messaging
Research · gated
Traffic-analysis resistance concept. Requires legal and technical review before any offer.
4D access policy
ICARUS
Access bound to identity, role, place, time, context or other explicit dimensions.
Anti-capture watermark / polarizer
Hardware research
Make unauthorized capture detectable or less useful.
Confidential joint math / MPC
Cryptography
Multi-party computation for analysis without exposing each party's raw input.
Top-tier record sealing
Nestar PSV
High-assurance sealing for crown-jewel records.
Secure channel / paired link
Shared security
Explicitly paired, authenticated communication between trusted endpoints.
Sovereign vision / redaction
Lens · AEGIS
Local visual processing, privacy filtering and bounded evidence extraction.
Drift detector
Assurance
Detect model, data, policy or behaviour drift.
Uncertainty clarifier
Assurance
Force explicit uncertainty, evidence gaps and escalation.
Formal verification & retraction
Assurance
Machine-checkable invariants plus a controlled correction path.
Anubis signed audit spine
Proof · cryptography
Signed evidence, hash chain, attestation and tamper evidence. Potentially separable as a standalone audit product.
Nestar PSV
Nestar cryptography
Information-theoretic k-of-n protection for the highest-tier secrets.
Wyrd IP Guard
RASOS · Labs
Transparent protection of Wyrd proprietary components. Locks Wyrd's modules, never the client's machine.
The exclusion register

The categories that never appear as product instruction or current capability.

These categories are recorded in internal transcripts and concept documents. They are named here so the boundary is explicit and auditable — and so no one has to guess where the line sits.

Parked, rejected or superseded

Recorded and deliberately not revived: a from-scratch OS kernel; a phone manufactured from scratch as version one; the Foundation as a venture funnel; a wide startup factory; maritime Anchorline; Synthetic Studios and Cognitive Engagement as main directorates; the old IRIS geopolitics module name; Firewatch as an umbrella brand; an unbounded agent currency before authorization; a weaponized RADOME; and any operational-harm or intrusion instruction in public material.

Labels

The full status vocabulary.

Label
Class
Meaning
Working software
Built
Running code exists with direct test or runtime evidence.
Integrated alpha
Built
Major components work together, but release, hardware, security or deployment work remains.
Pilot candidate
Gated
Coherent enough for a controlled design-partner pilot, subject to explicit gates.
Integration program
Gated
Reusable Wyrd components exist; domain integration and validation remain.
Research prototype
Testing
Code or simulation exists to test a hypothesis, not to promise a product.
Architecture defined
Testing
Structure, contracts and roadmap exist; implementation is partial.
Future option
Optionality
A recorded expansion path, not a present commercial promise.
Restricted
Gated
Named and placed publicly; the operational detail is released only in authorized government, legal, security or defense channels.
Historical name
Superseded
A retired label kept only to prevent confusion.

The map is complete. Access to each layer is not.

Partner and restricted material is released against authority, licensing and jurisdiction — never against curiosity.