Aspire venues are Australian, default to AU / AUD / +61 / en-AU
Context
Aspire has a long Thai-business history (much of Kom's network is in Bangkok / Chiang Mai). New agents and tooling consistently default to Thai locale settings (Asia/Bangkok timezone, THB currency, +66 phone, th-TH language) when seeded with Aspire context. This is wrong for the operational entities.
Detail
The 3 hospitality venues (all WA, Australia)
| Venue | City | State | Timezone |
|---|---|---|---|
| Chanya Thai | Albany | WA | Australia/Perth |
| Venice Albany | Albany | WA | Australia/Perth |
| Six Degrees | Albany | WA | Australia/Perth |
Other AU-based operations
- Goldroom Design (the marketing agency) — operates AU.
- Alby Place / Alby Travel — Albany, WA market focus.
- Aspire Digital Group / Aspire Hospitality Group — registered AU (ABNs).
Defaults
| Setting | Value | NOT |
|---|---|---|
| Timezone | Australia/Perth (venues) or Australia/Sydney (corp) | NOT Asia/Bangkok |
| Currency | AUD | NOT THB |
| Phone country code | +61 | NOT +66 |
| Locale | en-AU | NOT th-TH |
| Country code (ISO) | AU | NOT TH |
Exceptions where Thai context IS correct
- Brand Ecosystem outreach project (180 Thai businesses in PostgreSQL) — that data is genuinely Thai.
- Some MCP servers (
xero-chanyathai,xero-sixdegree, etc.) are Aspire AU entities, NOT Thai entities — the names just reference the hospitality brand. - PowerEPOS / Tanda / STAAH integrations — all AU instances.
When in doubt
Default to AU/AUD/+61. If a project genuinely needs Thai locale, that's an explicit override per-page.
Related
🔗 Relationships
graph LR
aspire_venue_geography["aspire-venue-geography"]:::self
aspire_venue_geography --> aspire_brand_architecture["aspire-brand-architecture"]
classDef self fill:#715EE3,color:#fff,stroke:#291F50;