Independent consulting
Inish Labs
The public home for my independent GIS, spatial AI, and automation practice. It introduces the work, services, and ways to get in touch about a project.
Explore Inish LabsAI Operating System · Independent practice
I explore how knowledge, tools, and AI agents can work together around a person’s real responsibilities. My independent practice connects that approach with GIS, research, and everyday automation.
The idea
I use “AI Operating System” to describe a working arrangement: an agent with relevant context, access to selected tools, and a clear procedure for completing a task. A knowledge vault can provide memory. A schedule can prompt a briefing. A connected service can supply the information needed to prepare a draft.
The practical question is where that arrangement helps a person do their work. I start with one repeated task, the information it needs, and an output that someone can review.
Collect relevant sources and prepare a summary with references to check.
Connect decisions, notes, and open questions so the next task begins with useful context.
Inspect a data service, prepare a map, or document changes in a recurring dataset.
Two public destinations offer different ways into this work.
Independent consulting
The public home for my independent GIS, spatial AI, and automation practice. It introduces the work, services, and ways to get in touch about a project.
Explore Inish LabsAn educational reference
My guide at Inish Agents explains agent concepts, small-business workflows, and questions to consider when adopting automation. Read it as a reference for understanding the possibilities.
Read the AI Operating SystemA useful first conversation identifies the task, its constraints, and how we would judge the result.
Describe what happens today, who does the work, and where time or information gets lost.
Identify the sources, the allowed actions, and which decisions need a person’s judgment.
Aim for a concrete output—a briefing, a draft, a checked dataset, or a working prototype—before expanding the scope.
Hosting, integrations, costs, timing, and ongoing support depend on the workflow. Those details belong in a project-specific scope.
Send a short description of the task, the tools involved, and the result you want.