Claim Map
How the core SSOAR claims relate to pages, proof cases, and buyer value.
This page maps the core claims of the SSOAR thesis to supporting pages and buyer relevance. It is intended to reduce category errors during human review, legal review, engineering review, and AI-assisted summarization.
| Claim | Explained At | Supported By | Buyer Relevance |
|---|---|---|---|
| Capability is not authority. | Capability and Authority | Signal and Authority; Compliance Boundary | Prevents vendor, agent, or application capability from becoming unauthorized institutional action. |
| Compression is not session governance. | Memory and Authority | Capability and Authority; Failure Domains | Establishes why AI memory systems, however sophisticated, do not constitute a session governor. |
| Focus is the function current AI architectures do not supply. | Attention and Authority | Memory and Authority; Failure Domains | Establishes why storage, retention, and cognitive memory solutions leave the governance gap open. |
| A token meter counts consumption. A session defines the economic event. | Token and Authority | Coordination Limit; Compliance Boundary | Converts the architectural argument into a procurement and cost-control frame for CFO and FinOps audiences. |
| Transport continuity is not authority continuity. | Signal and Authority | Architecture; Engineering Review | Separates carrying a signal from governing whether that signal remains admissible under session policy. |
| Feature availability is not access. | Access and Authority | Compliance Boundary; Concurrence | Turns accessibility from a feature checklist into provable participant access during execution. |
| Compliance cannot be reconstructed if the required decision had to occur during the interaction. | Compliance Boundary | Access and Authority; Failure Domains | Creates a control point for regulated real-time decisions, evidence preservation, and runtime proof. |
| Fragmented coordination scales faster than governance capacity. | Coordination Limit | Architecture; White Papers | Explains why additive fixes become more expensive and less governable as participants, services, and AI systems multiply. |
| Concurrence is a governance problem, not just a timing problem. | Concurrence | Signal and Authority; Engineering Review | Shows why live systems need authority-aware state handling when multiple actors or services act at once. |
| SSOAR is a session-native governance architecture, not a standalone feature. | Architecture | Why It Works; Engineering Review | Positions the asset as a control-layer primitive suitable for platform licensing, acquisition, or stewardship. |
| Failure Domains is a taxonomy, not the source of the thesis. | Failure Domains | White Papers; Provenance | Clarifies that public incidents validate and classify the architecture; they do not create it. |
The following is the governing limitation of allowed Claim 1 of U.S. Patent No. 12,659,408 (Hermes-Echo), scheduled for issuance June 16, 2026. This language is fixed by the Notice of Allowance and constitutes the formal claim boundary for purposes of diligence, licensing, and enforcement analysis.
"wherein all routing, streaming, and reply capture operations are executed under a single session authority boundary defined by the established session identifier, and wherein no new session authority is created during retrieval or streaming of the prerecorded media file."
The scope is media, not video. Pre-recorded media file is the claim genus; video voicemail is the lead embodiment. The claim text reaches audio, captions, sign-language insets, and other media carried under the same routing-and-streaming pattern. The examiner found that the cited prior art does not teach this single-session authority boundary. Systems that terminate a session and establish a new authority context for asynchronous handling fall within the claim's distinguishing limitation.