Article summary
Split St Helena, Ascension and Tristan da Cunha records into place-specific queues before reviewing phone provenance and avatar visibility.
St Helena, Ascension and Tristan da Cunha may share one long system label, but their avatar checks should not run as one undifferentiated queue. Provenance, service period and exceptions need place-specific visibility.
How to split the queues
| Queue | Entry evidence | If evidence is weak |
|---|---|---|
| Saint Helena | Order or address | Send to territory_unresolved |
| Ascension | Contract or service place | |
| Tristan da Cunha | Explicit provenance |
Do not fill territory from an avatar
Background, uniform, text or personal characteristics cannot replace order evidence. avatar_state and territory must remain separate in the data model.
Inspect exceptions within each queue
Calculate format exception, not observed, visibility limited and task exception separately so a larger place does not hide defects in another.
Mark shared contact points explicitly
When one organisational phone serves several places, store relationship_scope. Do not duplicate it into three personal customers or assign its avatar to an employee.
Keep long territory names out of TXT
The AppShai upload remains one phone per line. Territory, business ID and permission stay in the crosswalk; batch_row reconnects the Excel output.
Manage observation time by queue
Different service batches can have different expiry rules. A new order in one place must not extend an old avatar observation elsewhere.
Create a fourth queue for uncertainty
territory_unresolved is a formal state that waits for business evidence. A data operator should not select the place that merely seems most likely.
Do not publish cross-territory profiles
Report data quality and workflow states, but do not infer population, language, age or gender differences from avatars.
Division of work with the Full Format page
This page explains place-specific profile queues. A separate Full Format article handles schema and cross-queue merging, keeping the two search intents distinct.
