Grey Golus logoGREYGOLUSStart here

07 // Resource guide

Updated June 2026

AI is like a city

Use the city analogy to understand how the major AI pieces relate without memorizing their technical implementation.

Bottom line

You work through a storefront powered by a model, connected to data and services, using instructions and permissions you control.

01 // The map

Walk through the AI city

AI city diagram showing companies as plots, models as buildings, harnesses as storefronts, and data connections underground
The original city visual is a memory aid, not a technical architecture diagram.

02 // Translation

What each part means

AI conceptCity analogyWhat to remember
CompanyPlot ownerDifferent companies build and operate different model families
ModelBuildingThe underlying engine provides the intelligence
HarnessStorefront or workplaceThe interface determines how you interact and what actions are available
ContextOffice records and filing systemOrganized information makes the work more relevant and consistent
PromptWork orderClear instructions define the result, boundaries, inputs, and format
SkillEmployee playbookReusable instructions stop you from re-explaining repeat work
ConnectorRoad or utility connectionA packaged link gives access to an outside service
APIDefined service doorwaySoftware uses a known contract to request data or actions
MCPCommon adapter shapeAI apps can connect to many systems through a shared standard
AutomationStanding orderA workflow runs on a schedule or trigger

03 // Important limits

Where the analogy can mislead you

  • A bigger building does not automatically mean a better result for every job.
  • The same storefront can change the model working behind it.
  • A connector is not the same thing as the data or service it reaches.
  • Having a key does not create permission to share what is inside.
  • Real systems overlap: one product may combine a model, harness, tools, and workflow engine.

04 // Use the map

Diagnose a weak workflow

  1. 01

    Wrong building?

    The model may be too weak, too slow, too expensive, or poorly matched to the task.

  2. 02

    Wrong storefront?

    The harness may not have the files, tools, or working style the task needs.

  3. 03

    Missing records?

    The context may be incomplete, stale, contradictory, or unorganized.

  4. 04

    Missing connection?

    The workflow may need a connector, tool, MCP, API, or manual input.

  5. 05

    Weak work order?

    The prompt or skill may not define done, constraints, or verification clearly enough.

Official sources