How harbor and architecture sightseeing tours are reshaped as AGI capability advances.

Only about 20% of Harbor and Architecture Sightseeing Tours 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 company's primary value-producing work involves physical water operations and in-person hospitality, as evidenced by its core roles (Port Captain, Deckhand, Vessel Maintenance Technician) and top employed occupations (Motorboat Operators, Ship Captains). While ticketing and marketing offer some digital surface, the core output is inherently physical, supporting a strongly physical scalar.
grounded in the economy graph · digital scalar 0.20 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Harbor and Architecture Sightseeing Tours runs 12 core processes — each a candidate for the Code / Generative / Agentic / Human split, with the agentic and code-shaped steps the first to come off human headcount.
Harbor and Architecture Sightseeing Tours is organized into 8 departments. Read as functions of one executable business, each department is a unit of work whose back-office share is increasingly delivered by earned-autonomy digital labor.
The operating model of Harbor and Architecture Sightseeing Tours resolves to 8 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Harbor and Architecture Sightseeing Tours sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Harbor and Architecture Sightseeing Tours inherits.
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Harbor and Architecture Sightseeing Tours uses 7 products to deliver its outcomes — the toolchain whose work an autonomous stack absorbs as the service becomes software.
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Harbor and Architecture Sightseeing Tours typically employs 74 occupations — the labor mix whose desk-knowledge share is the most exposed to becoming digital employees first.
+62 more via typicallyEmploys
Harbor and Architecture Sightseeing Tours staffs 8 job types — the roles that, decomposed to tasks, are first in line to run as supervised-then-autonomous digital labor.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Harbor and Architecture Sightseeing Tours relies on 7 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 Harbor and Architecture Sightseeing Tours 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.