Brand architecture
Infinitrust makes it usable.
QVTM defines the protocol. Infinitrust provides the commercial platform, services and interfaces through which customers can use it.
Geometry of Trust provides the shared visual foundation for both the protocol and its commercial implementation.
QVTM defines the formal structure of trust through relationships, evidence, verification and continuity.
Infinitrust makes those capabilities usable by customers through APIs, hosted services, applications, workflows and operational tooling.
The two must remain visually related because they belong to the same system, but their roles are not equivalent.
Ecosystem structure¶
flowchart TB
GOT["Geometry of Trust"]
QVTM["QVTM Protocol<br/><small>Specification · Evidence model · Verification rules<br/>Technical diagrams · API semantics</small>"]
INFINITRUST["Infinitrust Platform<br/><small>Commercial API · Hosted services · SaaS application<br/>Onboarding · Operations · Customer workflows</small>"]
CUSTOMERS["Customers and integrations"]
GOT --> QVTM
GOT --> INFINITRUST
QVTM --> INFINITRUST
INFINITRUST --> CUSTOMERS
classDef root fill:#201B32,stroke:#21D4FF,color:#F5F3FA,stroke-width:2px;
classDef protocol fill:#171326,stroke:#8A48FF,color:#F5F3FA,stroke-width:1.5px;
classDef platform fill:#171326,stroke:#C93BCE,color:#F5F3FA,stroke-width:1.5px;
classDef audience fill:#171326,stroke:#FFD34E,color:#F5F3FA,stroke-width:1.5px;
class GOT root;
class QVTM protocol;
class INFINITRUST platform;
class CUSTOMERS audience;QVTM
The protocol defines the formal structure of trust through relationships, evidence, verification and continuity.
Infinitrust
The platform makes the protocol accessible through commercial products, interfaces and operational workflows.
Shared foundation¶
The two products inherit the same structural language.
Common construction
Both use the same master angle, chamfers, spacing logic and directional flow.
Common voice
Geist provides the shared visual voice. IBM Plex Mono expresses code, identifiers and protocol notation.
Common meaning
Magenta always represents identity, cyan verification, yellow attention and red failure or revocation.
Shared versus product-specific¶
| Element | Shared | QVTM | Infinitrust |
|---|---|---|---|
| Core geometry | ✓ | ||
| Typeface families | ✓ | ||
| Base dark palette | ✓ | ||
| Semantic colors | ✓ | ||
| Spacing and layout principles | ✓ | ||
| Accessibility requirements | ✓ | ||
| Protocol notation | ✓ | ✓ | ✓ |
| Low-color documentation mode | ✓ | ||
| Print-safe diagrams | ✓ | ||
| Academic and normative writing | ✓ | ||
| Rich hero objects | ✓ | ||
| Atmospheric lighting | ✓ | ||
| Animated trust visualizations | ✓ | ||
| Commercial storytelling | ✓ |
Product expression¶
- Lead with evidence, notation and diagrams.
- Use restrained color and minimal atmospheric effects.
- Support monochrome printing and formal technical publication.
- Prioritize precision over emotional presentation.
- Lead with product value, workflows and understandable outcomes.
- Use richer magenta, violet and cyan presence.
- Use motion and spatial depth to communicate active trust.
- Remain technically credible and visibly connected to QVTM.
Naming¶
QVTM
Use QVTM when referring to the protocol, specification, protocol behavior, technical implementation or academic material.
Infinitrust
Use Infinitrust when referring to the commercial platform, hosted services, applications, customer experience or company-facing material.
- Infinitrust implements the QVTM protocol.
- QVTM defines the protocol model.
- The Infinitrust platform exposes QVTM capabilities through an API.
- Infinitrust and QVTM are interchangeable names.
- QVTM is the commercial SaaS product.
- Infinitrust is the name of the protocol specification.
The relationship¶
QVTM defines the structure. Infinitrust brings it into motion.
The protocol and platform must remain conceptually distinct while sharing one visual foundation. This distinction allows QVTM to retain technical independence and gives Infinitrust the freedom to communicate commercially without redefining the protocol.