Naming guide
Names carry weight in this ecosystem. Using the wrong one in front of a customer creates confusion about what was bought, who runs it, and what a label refers to. This page is normative: when in doubt, follow it.
The locked names
Section titled “The locked names”| Name | What it is | Use it when… | Never use it for… |
|---|---|---|---|
| PRESHai | The company | Referring to who implements, operates, or sells. “PRESHai provisions your tenant.” “Contact the PRESHai team.” | The product itself. Do not say “log in to PRESHai” when you mean the platform. |
| PRESHos Platform | The product (locked name, domain preshos.com) |
Referring to the governed operating layer: tenants, environments, sessions, approvals, audit. “Your session runs on PRESHos Platform.” | The company, or a service engagement. |
| AI Implementation | A service | Referring to the engagement where PRESHai implements the platform for a customer. | The product or a module. |
| Managed AI Ops | A service | Referring to the ongoing operate-and-run engagement. | The product or a module. |
| Agent Ops | A module label | Referring to that specific module’s surface within the platform. | The product as a whole. Never call the platform “Agent Ops”. |
- Company vs. product, always. PRESHai is who; PRESHos Platform is what. “PRESHai operates PRESHos Platform for you” is the canonical sentence.
- Services are engagements. AI Implementation and Managed AI Ops describe work PRESHai does (implementing, running), not software tiers. Do not write “the AI Implementation dashboard” or “Managed AI Ops version 2”.
- Agent Ops is a module label, not the product. It names a part. Calling the whole platform “Agent Ops” collapses the distinction and confuses anyone reading module-scoped docs.
- Product name is locked: PRESHos Platform. Do not shorten to “PRESHos” in customer-facing prose on first reference, and never to “Presh”, “PreshAI”, or “the portal”. On second reference within a page, “the platform” is acceptable; bare “PRESHos” is tolerated only where space is tight and meaning is unambiguous.
- Domain is
preshos.com. Tenant hostnames commonly look likeslug.preshos.com. Do not invent alternate domains in docs.
Examples
Section titled “Examples”Use:
- “PRESHai provisions your PRESHos Platform tenant, then implements your first environments as part of AI Implementation.”
- “Your Agent Ops module shows sessions scoped to your environment.”
- “Managed AI Ops covers ongoing operation of your PRESHos Platform tenant.”
Do not use:
- “Welcome to PRESHai, your Agent Ops platform.” (Conflates company, module, and product.)
- “Our AI Implementation product includes…” (AI Implementation is a service, not a product.)
- “Log in to the portal to…” (Which hostname? Which tenant? Name the thing.)
Why this matters for docs
Section titled “Why this matters for docs”This learning site, the product UI, and customer communication must agree on names. Otherwise Day-0 instructions (“go to your tenant hostname”) and support (“which org_id is the session under?”) break down. If you spot a naming violation in these docs, treat it as a bug and fix it.