How coastal aquaculture operation are reshaped as AGI capability advances.

Only about 15% of Coastal Aquaculture Operation 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, this score relies on the company type name and its parent industry, NAICS 112 'Animal Production and Aquaculture'. The description defines the core work as breeding and raising aquatic animals in coastal or offshore environments. This is fundamentally hands-on, physical agricultural labor, keeping the scalar firmly in the physical band.
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, Coastal Aquaculture Operation 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.
Coastal Aquaculture Operation 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 Coastal Aquaculture Operation resolves to 7 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Coastal Aquaculture Operation 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 Coastal Aquaculture Operation inherits.
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Coastal Aquaculture Operation 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.
Coastal Aquaculture Operation staffs 7 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.
Coastal Aquaculture Operation 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 Coastal Aquaculture Operation reaches for already exposes 8 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.