Documentation vs Company OS
ZAIXOS follows the same pattern as Stripe, Google Cloud, AWS, and Shopify:
| Surface | URL | Audience | Authentication |
|---|---|---|---|
| Corporate site | / | Prospects, partners | None |
| Knowledge Portal | /docs | Engineers, partners, public | None |
| Company OS | /admin | Founders, staff, operators | Required |
| Product admin | *.clinic.zaixos.com/admin | Clinic staff | Required |
Why /docs is public
Engineering documentation is a trust and velocity layer:
- Onboarding engineers without friction
- Sharing architecture with partners and auditors
- Publishing ADRs, standards, and API reference
- Searchable knowledge (⌘K in this portal)
Public docs do not expose secrets, customer data, or operational controls — only approved engineering knowledge.
Why /admin is private
The Company OS is the internal operating system:
- Users, roles, permissions
- Customers, finance, CRM
- Deployments, incidents, infrastructure
- Agent operations, releases, approvals
This requires authentication because it manages live company state, not published knowledge.
How they connect
Knowledge Portal (/docs) | Company OS (/admin) |
|---|---|
| Architecture, ADRs, standards | Architecture Explorer (live graph) |
| Platform & product reference | Products & Platforms CRUD |
| Agent documentation | Agent Operations Center (live metrics) |
| Local operations guide | Operations dashboard (live alerts) |
| Static search (VitePress) | Company Search + AI (indexed federation) |
Staff use both: learn from /docs, operate from /admin.
Deploy commands
bash
# Publish docs to https://zaixos.com/docs
cd zaixos-engineering-platform
npm run docs:deploy
# Bootstrap Company OS data
cd zaixos-company-platform
php artisan company-os:bootstrap