Community Theaters
How community theaters are reshaped as AGI capability advances.
The bottom line
Only about 25% of Community Theaters 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: No explicit JobType children are seeded, so the score is derived from the company type description and anchored occupations. The core value-producing work is inherently physical and in-person, evidenced by heavy staffing in roles like Costume Attendants (28% share), Actors (17%), Musicians, Master Carpenters, and Wardrobe Supervisors. While administrative functions like Marketing, Box Office, and Development introduce some digital knowledge work, the overriding focus on live performance, set construction, and front-of-house operations anchors this firmly in the physical band.
grounded in the economy graph · digital scalar 0.25 · physical
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Community Theaters 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.
Community Theaters is organized into 6 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 Community Theaters resolves to 7 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Community Theaters 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 Community Theaters inherits.
Services-as-Software
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Community Theaters uses 7 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.
Community Theaters typically employs 160 occupations — the labor mix whose desk-knowledge share is the most exposed to becoming digital employees first.
+148 more via typicallyEmploys
Community Theaters 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.
Community Theaters 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 Community Theaters reaches for already exposes 1 agent-callable action (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
The problems this exposes
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
Where Community Theaters sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.