How tour and travel guides are reshaped as AGI capability advances.

Only about 15% of Tour and Travel Guides is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: The grounding block provides no tools, work activities, or context attributes for this occupation. Relying on the occupation name 'Tour and Travel Guides', the descriptive anchor highlighting employment in sightseeing transportation and recreation, and the deterministic SOC prior of 0.00, the work inherently requires on-site, physical presence to lead and interact with groups. I have assigned the band-center value of 0.15 for the physical band.
grounded in the economy graph · digital scalar 0.15 · physical
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Tour and Travel Guides is typically employed by 69 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+57 more via typicallyEmploys
Tour and Travel Guides is employed across 70 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+58 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Tour and Travel Guides relies on 4 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
The software Tour and Travel Guides reaches for already exposes 3 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
No articles yet for this entity.
No capability events for this entity yet.