The Hermes-Echo Patent Family
Three filings enclose the governed interaction. Seven coordinated filings govern distinct material mutations within it. Together they express one session-authority invariant across ten technical domains.
The 3-7-10 structure
The family is not a collection of unrelated feature patents. It is a coordinated architecture. Hermes-Echo, Warten, and Ludwig’s Raven define the temporal and participation enclosure. The seven sibling filings address different ways that state, compute, data, devices, trust, and machine action can change inside that enclosure.
Warten
Governs authorized third-party content and activity while a participant is held in the pre-admission state.
Ludwig’s Raven
Negotiates who may participate, through which modality, and under which accessibility or capability conditions.
Hermes-Echo
Preserves the operative session-authority boundary while media or interaction state changes inside the live session.
The ten coordinated filings
| No. | Filing | Technical domain | Authority surface governed |
|---|---|---|---|
| 1 | Hermes-Echo | Compute systems and processes for video messages | Authority continuity when a live media interaction mutates into retrieval, playback, recording, storage, or delivery without originating a second independent session authority. |
| 2 | Warten | Pre-recorded content in a video-call waiting room | What may occur before admission, under whose credential or delegated authority, and within which pre-admission interaction boundary. |
| 3 | Ludwig’s Raven | Dynamic accessibility negotiation in selective multimedia distribution | Participant admission, modality, accessibility, and selective distribution conditions under the same governed interaction. |
| 4 | Muninn | AI pipeline negotiation and inference routing | Admission, substitution, and routing of AI models, agents, tools, and inference pipelines inside the session boundary. |
| 5 | Quetzalcoatl | Merge, fork, cascade, and handoff orchestration | Authority and context continuity when interactions branch, combine, transfer, or form multi-step session graphs. |
| 6 | Zhinü | Multimodal orchestration for IoT, XR, robotics, and telemetry | Heterogeneous devices and modalities joining, leaving, or changing capability without replacing the governing interaction identity. |
| 7 | Lakshmi | Session-level compute marketplace and cost-optimized orchestration | Compute placement, migration, provider selection, and workload allocation as governed session mutations rather than external infrastructure events. |
| 8 | The Griot | Session-native recording and replay provenance | Binding recordings, derived artifacts, model attribution, processing history, and authorized replay views to the interaction that produced them. |
| 9 | Hari Seldon | Session-level data residency routing | Jurisdiction, residency, processing location, and stream-specific routing decisions within the live governed interval. |
| 10 | Deganawida | Zero-trust session attestation and auxiliary-stream governance | Continuous trust, delegation, per-stream authorization, and machine action without relying on a one-time access decision. |
Why it is a picket fence
Each filing addresses a technically distinct control point. The posts are orthogonal, not stacked as a mandatory sequence. A system may encounter the common invariant through a single material mutation: a handoff, a model substitution, a compute move, a new device, a jurisdictional change, an accessibility change, a derivative record, or an autonomous action.
This matters because avoiding one implementation does not necessarily avoid the architecture. A design that moves the same governed interaction through a different technical surface may reach another coordinated filing. The family therefore protects the control structure from several directions while keeping each claimed invention tied to its own technical combination.
Before, during, and after
Before: establish admission, authority, participation, restrictions, modality, and jurisdiction.
During: evaluate each material mutation under the authority governing the live interaction before the proposed change becomes authoritative session state.
After: bind the resulting state, action, recording, or derivative artifact to proof of the governed interaction and the authority under which the transition occurred.
Observation after the event is not governance. Logs may show what happened. The family addresses whether the transition was authorized to become session truth in the first place.
Current public status
Hermes-Echo
U.S. Patent No. 12,659,408, issued June 16, 2026, with twenty claims.
Warten
U.S. Application No. 19/395,642. Claims 1 through 19 allowed. Issue fee paid. Not yet issued.
Ludwig’s Raven and siblings
Coordinated pending filings preserve the remaining authority surfaces across the 3-7-10 architecture.
Continuation depth
Hermes-Hecate continues from Hermes-Echo. Warten-Janus continues from Warten. The prosecution architecture remains active.
Patent scope is determined by the issued claims and the complete facts of a particular implementation. The architectural map explains the coordinated family; it does not substitute for claim-specific legal analysis.
How to read the family
- The Missing Dimension
Why the live interaction is the authority-bearing object.
- What Hermes-Echo Is
The issued anchor and the distinction between transport continuity and authority continuity.
- Authority Surfaces
How the same missing architectural object appears in different technical vocabularies.
- Record
Current prosecution status and public-record references.
- Diligence Index
Structured entry points for technical, legal, commercial, and operational review.
Follow the family through the site
The family page is the canonical portfolio map. The pages below develop the invention, record, implementation logic, failure evidence, and commercial consequences from different directions.
Core architecture
- What Is Hermes-Echo?
- The Missing Dimension
- The Architecture: How SSOAR Works
- Concurrence
- The Engineering: Why SSOAR Works
- Why It Breaks
Patent record and diligence
Authority surfaces
- Authority Surfaces
- Access and Authority
- Capability and Authority
- Signals and Authority
- Attention and Authority
- Memory and Authority
- Provenance
- Ownership Cycles
System constraints and failure evidence
- The Seven Convergent Failure Domains
- The Coordination Limit
- Compliance Boundary
- This Road Does Not Lead to the IoE
- Session and Energy
- Token and Authority
- The Token Toll Reconciliation