Hermes-Echo / SSOAR
Claim Map
How the core SSOAR claims relate to pages, proof cases, and buyer value.
Page role: argument map
Status: stable explanatory page
Last updated: May 10, 2026
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. |
| 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 site should be read from claims to architecture to proof cases to commercialization, not from traffic events or news examples backward.