OpenTeams Intelligence Hub · The execution model

Frames, Cogs & Ops

The execution layer of the OpenTeams Intelligence Hub, explained five ways. A Frame carries your context, a Cog is a governed AI worker, and an Op is the supervised workflow that runs them. Start with the door that fits how you think — concept, build, or example.

Frame — your context Cog — a governed worker Op — a supervised workflow
01

Learn the model

Understand Frames, Cogs & Ops in your own language.

For engineers

Technical Field Guide

A working engineer's mental model for the execution layer — built from analogies, then simple code, then real orchestration, then a full system. Every concept anchored to primitives you already use: config files, stateless workers, DAGs.

Mental modelCode → systemCheat sheet
Open→
For project & program managers

The PM Playbook

The same three ideas in the language of running programs. A Frame is the context you already carry in your decks; a Cog is a teammate who's read all of it; an Op is your recurring ceremony, run with the approval gates you'd never give up.

AnalogiesBefore / afterLineage tracer
Open→
02

Build it today

From your current tools to working workflows, hands-on with Claude Code.

Hands-on · Claude Code

Build Guide

A real, step-by-step build of a working weekly-status Op — using the tools you already live in: GitHub, Slack, Drive, Notion. Each step is the prompt you paste, the file it produces, and the technical why. No Intelligence Hub required; it runs today.

One OpStep-by-stepRuns today
Open→
Hands-on · Claude Code

Build Lab

The companion build — but for the whole PM bench. Set up your context once, then watch the same Frames and Cogs get reused across six working Ops. Ends with an interactive tracer from any Op back to the exact context it sees.

Six OpsReuse storyInteractive tracer
Open→