A harness is everything around a model that turns it into a useful product — grounding, tools, memory, safeguards, and the loop that lets it iterate until a job is done. On The Cloud, the harness is a workspace.

From business processes to harnesses

Companies today are built on business processes — the documented ways work gets done. As agents take on that work, the process becomes a harness: the same workflow, now grounded, tool-equipped, and autonomous. The harness is where a company's real operating knowledge will live.

The harness is your Cloud

You don't assemble a harness from a dozen arcane parts — a model here, a memory store there, a tool layer, a runtime, a permission system. On The Cloud that whole stack is one shared workspace: the grounding is your Memory, the tools are open and authenticated, the runtime is governed, and the agent is your Ora.

One generator, many packs

The scalable way to build harnesses is not one per use case. It is a single generator that composes a workspace from reusable primitives — pages, memory, tools, offers, forms — configured by a light pack per domain. The workspace is the harness; the pack is the specialization.

Three layers to tune

You can raise a harness's ceiling at three layers: the model, the harness itself (tools and workspace), and the context you ground it on. The model is rented and improving. The harness and context are yours to own and compound.

Ora · Opus 4.8 · Cowork