Architecture¶
How MasteryHive products fit together at a level safe for evaluators and partners.
Public vs private¶
| Layer | Audience | Page |
|---|---|---|
| High-level (public) | Anyone with the public docs site | This section |
| Implementation (internal) | MasteryHive engineers | Implementation architecture on the Access-protected Engineering site |
Public Architecture deliberately omits repository paths, topic names, secret names, deploy flags, and vulnerability detail.
Start here¶
- System map — banking app, MasteryHive products, vendors, storage, events, people
- Platform overview — product roles without internals
- Products — readiness and capabilities
Integrators continue under Integration. Engineers use the Access-protected Engineering section (onboarding, implementation architecture, walkthroughs).