Domain names show whether a service is shared across Affective Technologies or scoped to one tenant and product.
Naming model
| Scope | Pattern | Example |
|---|---|---|
| Shared Affective Technologies service | <service>.affectivetech.com | sso.affectivetech.com |
| IHNYC-scoped product or docs | <product>.ihnyc.affectivetech.com | desk.ihnyc.affectivetech.com |
| Resident Council system | Product-specific Resident Council domain | docs.ihnyc-rc.org |
sso.affectivetech.com is global because future Affective Technologies products may share the identity service. docs.ihnyc.affectivetech.com is tenant-scoped because this site explains the IHNYC implementation.
Current and reserved public names
| Hostname | Purpose |
|---|---|
desk.ihnyc.affectivetech.com | House Desk human pages and staff entry |
calendar.ihnyc-rc.org | Long-lived private Programs-feed compatibility |
pub.ihnyc-rc.org | Pub public, display, and staff surfaces |
docs.ihnyc.affectivetech.com | This documentation site |
sso.affectivetech.com | Reserved address for the planned shared identity service; not live until commissioning |
Cloudflare Tunnel is the chosen publication boundary for the identity service when it is commissioned. It lets the origin make an outbound connection rather than exposing a home-router port. House Desk and Pub remain on their existing deployments and receive identity through Cloudflare Access; neither product connects directly to the identity server.
Private documentation retains origin addresses, tunnel credentials, connector configuration, and recovery procedures.
Future organization-wide docs
docs.affectivetech.com is reserved for standards that genuinely apply across clients or tenants. IHNYC product instructions stay here rather than being duplicated.