06-reference/research

thoughtworks agentworks vs oi governance layer

2026-11-12·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)·! phdata-internal
thoughtworksagent-governanceorganizational-intelligenceagent-registrycompetitive-landscape

Agent/works is a governed agent runtime, OI's governance layer is a scoring taxonomy, so they overlap on vocabulary and not on function

The question

What is Thoughtworks Agent/works (launched 2026-06-16), and does its policy-enforcement and registry layer overlap the Organizational Intelligence governance layer?

Context: surfaced as a follow-up in [[2026-09-27-thoughtworks-agentic-scope-of-authority-nine-blocks]], which found the vault had zero coverage of Agent/works. This is an internal-platform comparison for the founder's phData role. It is not a sellable-differentiator question, since RDCO is dormant. Naming note: "CAF" was retired 2026-08-10; the comparison target is Organizational Intelligence (OI): Organizational Platform to Organizational Map, Intelligence Platform to Intelligence Maturity Assessment (IMA), plus the Organizational Intelligence Process (OIP) and its Pulse cadence.

What we already know (from the vault)

What the web says

Evidence tiers: (primary) = fetched from thoughtworks.com on 2026-11-12, read through a summarizing fetch tool, so exact wording outside quote marks is paraphrase. (search-summary) = appeared only in a search-engine summary and was not confirmed on a fetched page.

Capability overlap table

OI column key: IMA taxonomy means the OI Capability Registry names the capability as something to score at a client. It does not mean OI provides it. "Evidence" is the tier for the Agent/works cell; the OI cell is from the spec working tree in every row.

Agent/works component What it does Nearest OI component Functional overlap Evidence
Governance & Access (policy enforcement at run time) Enforces who and which agent can use which models, tools, resources GOV.AI_GOV.AGENT_GOV, GOV.SECURITY.ACCESS_CONTROL, INFRA.MLOPS.RUNTIME_GUARDRAILS (IMA taxonomy) None. OI scores whether the client has this; it enforces nothing Primary
Pre-execution compliant-path analysis; narrowing time-limited permissions Checks a workflow before it runs; scopes permissions per agent GOV.AI_GOV.AGENT_GOV (IMA taxonomy) None as function; claim is itself unverified Primary, marketing claim only
Approval workflows for sensitive changes Human sign-off gate inside the platform IFACE.HITL.REVIEW_APPROVE, GOV.VALUE_MGMT.STAGE_GATE (IMA taxonomy) None Primary
Agent Registry Inventory of deployed agents, versions, environments INFRA.MLOPS.REGISTRIES (IMA taxonomy). OI's own registries hold capabilities, roles, values and engagement objects None on content. Same word, different thing registered Primary
Model Catalog; MCP Tool Connections Approved models and tools, with per-agent access INTEL.FOUNDATION, INTEL.AGENTIC.TOOL_CATALOG (IMA taxonomy) None Primary
Monitoring & Audit Execution traces, audit records GOV.SECURITY.AUDITABILITY, INFRA.ORCHESTRATION (IMA taxonomy) None Primary
Memory & Context Agent memory persistence and sharing INTEL.AGENTIC.MEMORY (IMA taxonomy) None Primary
Usage & Cost Controls; "verified lower token spend" against a baseline Budgets and limits; savings claim checked against an agreed baseline Business Value Framework, claimed-versus-realized per delivered Upgrade Partial, weak. Both verify a value claim against a baseline; Agent/works covers token cost only, OI covers business value of a workflow change Primary
Evaluation & Optimization Compare agent versions, tune prompts OIP Pulse (re-prioritize backlog as capabilities shift) None. Pulse iterates on use cases and workflows, not on agent versions Primary
Fleet-wide "single source of truth" One view of agents, models, tools, policies Engagement registry (Job, Workflow, Gap, Use Case, Upgrade) Partial, adjacent. Both are a system of record that persists between rounds. Agent/works records what is running; OI records why it was built and what it changed Primary
(nothing found) Organizational Platform / Organizational Map (functions, motions, roles, seats) None. No org-structure or role model on any fetched page Primary, by absence
(nothing found) IMA maturity scoring; OIP Kickstart; use-case intake and prioritization None. No assessment, maturity model or prioritization method on any fetched page Primary, by absence
Cerbos policy engine; AgentSpec agent definitions; lineage Implementation specifics n/a Unknown Search-summary, unverified

Separately, and outside OI: against the July spoke map, Agent/works' agent registry, policy enforcement and evaluation features line up with the Registry, Govern and Evals spokes that other phData teams own. That is where a functional overlap would sit, if there is one. It is marked unknown here because the vault's picture of those spokes is from July and their current scope was not checked.

Convergences and contradictions

Synthesis for RDCO

The direct answer is no. Agent/works' policy-enforcement and registry layers do not cover the same ground as the OI governance layer, because the two are different kinds of object. Agent/works is deployed software that sits in the execution path of agents: it holds an inventory of agents, models and tools, and it allows or blocks actions. OI's Governance Layer is a section of a capability taxonomy that a client is scored against. The overlap is at the level of nouns. Nearly every Agent/works feature has a matching line in the OI Capability Registry, which is what you would expect, since the registry is meant to enumerate what a mature platform contains. Read that way, Agent/works is one possible implementation of roughly eight capability details that an IMA would score, spread across the Governance, Intelligence, Interface and Infrastructure layers. It is an answer to an IMA finding and does not compete with the instrument that produces the finding.

What Agent/works lacks is the half OI is built around. Nothing on the three fetched pages models an organization's functions, roles or workflows, scores maturity, or prioritizes use cases by business value. Its unit of record is the agent; OI's is the job and the workflow. The two real points of contact are narrow. Both keep a persistent system of record, and both verify a savings claim against a baseline, though Agent/works does so for token spend only. Neither is enough to call it a comparison set for OI.

The closer comparison is to the parts of the phData platform the founder does not own. If the July spoke map still holds, Agent/works bundles into one product what phData has as separate Registry, Govern and Evals spokes, and Thoughtworks sells it the same way phData would deliver those: forward-deployed engineers, in the client's environment, no public price. That is worth knowing for a conversation with those spoke owners, with two cautions. First, this brief did not verify the spokes' current state. Second, the evidence that Agent/works is more than a packaged services engagement is thin: no named customer, no independent review, no public documentation, and the only stated production user is Thoughtworks itself, five months after launch.

Confidence. High that there is no functional overlap with OI as specified, since that rests on the OI spec and on what Agent/works' own pages do and do not list. Medium on the feature inventory, which came through a summarizing fetch. Low on implementation details (policy engine, agent definition format) and on anything about adoption.

Why this is in the vault

It closes the Agent/works coverage gap opened by [[2026-09-27-thoughtworks-agentic-scope-of-authority-nine-blocks]] and settles that Agent/works does not belong in OI's comparison set, so OI roadmap and socialization material does not need to position against it. It also flags that the relevant comparison, if any, is against the Registry, Govern and Evals spokes in [[2026-07-06-die-fabric-hub-spoke-map-and-roadmap-implications]].

Open follow-ups

Related

Sources

Vault

OI working tree (phData-internal, outside the vault, read 2026-11-12)

Web (all fetched or searched 2026-11-12)