Neighborhood Taverns
How neighborhood taverns are reshaped as AGI capability advances.
The bottom line
Only about 15% of Neighborhood Taverns 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: With no seeded child JobTypes, the score is derived from the company type's description and key roles (Bartenders, Barbacks, Bouncers, and Line Cooks). The core value-producing work of a neighborhood tavern—pouring drinks, serving customers on-site, cooking, and facility maintenance—is heavily physical and on-premises, anchoring the score firmly in the physical band despite minor administrative functions like bookkeeping.
grounded in the economy graph · digital scalar 0.15 · physical
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Neighborhood Taverns runs 13 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.
+1 more via runs
Neighborhood Taverns 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 Neighborhood Taverns resolves to 6 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Neighborhood Taverns 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 Neighborhood Taverns inherits.
Services-as-Software
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Neighborhood Taverns uses 6 products to deliver its outcomes — the toolchain whose work an autonomous stack absorbs as the service becomes software.
Autonomous Agents as digital employees
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Neighborhood Taverns typically employs 110 occupations — the labor mix whose desk-knowledge share is the most exposed to becoming digital employees first.
+98 more via typicallyEmploys
Neighborhood Taverns staffs 8 job types — the roles that, decomposed to tasks, are first in line to run as supervised-then-autonomous digital labor.
Headless SaaS for Agents
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Neighborhood Taverns 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 problems this exposes
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
Where Neighborhood Taverns sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.