Platform Services
Platform Services are shared infrastructure used by Modules and Applications. They are not customer-installable products and must not depend on an individual module.
Service catalog
| Service | Purpose | Typical consumers |
|---|---|---|
| Authentication | Human identity proofs (WordPress credentials where hosted on WP) | Hub, Intake, future apps |
| Tenant Management | Accounts, memberships, sites | Hub Application |
| Machine Credentials | Site ↔ Hub machine tokens | Intake remote contracts, Hub pulls |
| Licensing | Entitlements to modules/features | Hub, update channel |
| Hub / Module Registry | Connected sites and approved modules | Workspace Application |
| Workspace Contract Validation | Validate Manifest/Workspace payloads | Hub |
| Health | Operator-visible integration health | Operator Console |
| Logging / Notifications | Operational signals and notices | Modules, Applications |
| SearchAsist Core | Authenticated AI Visibility intelligence API | SmartBlocks, Media, Index (when authorized) |
| AI Gateway | Policy-aware AI routing | Modules needing AI |
| Shared Cache / Telemetry | Hub module cache; site signal rollups | Workspace, recommendations |
| Update Services | Secure package provision and updates (WileyLabs repository) | WordPress-packaged modules |
Rules
- Services expose contracts, not module dashboards.
- Services must never depend on a single Module.
- Hosting a service inside the Hub WordPress package does not make it a Module.