How horse-drawn carriage operators are reshaped as AGI capability advances.

Only about 15% of Horse-Drawn Carriage Operators 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: Because there are no seeded child job types, the scalar is derived from the company type's description and parent industry ('Scenic and Sightseeing Transportation, Land'). Key roles like Coachman, Stable Hand, Farrier, and Carriage Mechanic, along with departments dedicated to Equine Health and Carriage Maintenance, represent overwhelmingly hands-on, physical work with animals and vehicles. While ticketing and compliance offer minor administrative surfaces, the core value production is decidedly physical.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Horse-Drawn Carriage Operators runs 10 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.
Horse-Drawn Carriage Operators is organized into 7 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 Horse-Drawn Carriage Operators resolves to 8 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Horse-Drawn Carriage Operators 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 Horse-Drawn Carriage Operators inherits.
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Horse-Drawn Carriage Operators uses 6 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.
Horse-Drawn Carriage Operators typically employs 59 occupations — the labor mix whose desk-knowledge share is the most exposed to becoming digital employees first.
+47 more via typicallyEmploys
Horse-Drawn Carriage Operators 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.
Horse-Drawn Carriage Operators relies on 6 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 Horse-Drawn Carriage Operators reaches for already exposes 10 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.