/records / CP-SIG-57 · Page model JSON · Portable export bundle

record CP-SIG-57slug cp-sig-57

Local Execution Is Not Local Governance: Ollama, OpenClaw, and the Device-Level Custody Surface

profileCounterpose Publicationcounterpose_publication

publisherCounterposecounterpose

statusActive

lifecyclePublishedanchorsAnchors not applicable

eligibilitypublication-eligible

computed at 2026-03-15T00:00:00Z

rendered at 2026-03-15T00:00:00Z

profileCounterpose Publicationcounterpose_publicationsource kindcaptured_counterpose_signal

Editorial republication

This page republishes captured Counterpose editorial from the GARPedia admitted pool. It is not a GARP-verified or governed record. The disclosures below are render-time only and assert no substrate verification, admission, or enforcement.

Editorial republication
Not source-verified by GARPedia
No private source text is rendered
No admission, mutation, or publication approval is performed here

Verification posture (derived from this record)

This page is not source-verified by GARPedia.
No GARP receipt backs this content; it is not receipt-verified or cryptographically validated.
Claims here are republished editorial, not admitted as verified fact by GARPedia.
No registered source captures are anchored to this record.
No citation spans are present in this record.
No GARPedia lineage / audit events are recorded for this record.

Profile-driven rendering

Active profile

Counterpose Publication

Fixture key counterpose_publication · publication-context expanded

provenance: expanded
citation: expanded
source/reference: source references with citation context
redaction: no redaction boundary notice
lint: object lint not represented
receipts: receipt fixtures not represented
traversal: cross-artifact traversal links shown

Shown by fixture

expanded provenance posture
expanded citation posture
source references with citation context
cross-artifact traversal links shown

Not represented

No redaction boundary applies to this fixture.
No object lint findings are represented.
No receipt fixtures are attached to this record.

Counterpose Publication fixtures emphasize publisher, edition, source, receipt, and cross-artifact context for a public signal.

Profile rendering parameters are local synthetic fixtures; they do not create private reader views, login states, or role-gated access.

Signal body

# Local Execution Is Not Local Governance: Ollama, OpenClaw, and the Device-Level Custody Surface

Counterpose | CP-57 | March 15, 2026

A publication of Vega Commons Project, Inc.

---

On March 15, 2026, Ollama announced its status as an official provider for OpenClaw, the open-source agentic AI framework. The integration reduces OpenClaw deployment to a single command and enables fully local agentic AI execution across WhatsApp, Telegram, Slack, Discord, iMessage, and other messaging platforms. The Ollama blog describes OpenClaw as a system that "runs locally on your own devices, keeping your conversations and code private."

That is a privacy claim rather than a custody claim, and the distinction matters.

## Privacy Versus Custody

A custody surface is the set of records an AI system generates during operation that can be discovered, subpoenaed, or compelled through legal process. An interaction record is the log of what a user asked, what the system responded, and any reasoning the system performed. Local execution eliminates cloud-provider custody surfaces; no third-party vendor sees the data. It does not eliminate the custody surface itself. The records exist on the device, in messaging platform logs, and in any synchronized backup. Local execution moves the custody surface from the cloud to the device without abolishing it.

OpenClaw's local deployment creates several custody surfaces that the privacy framing does not address. The local agent workspace (~/.openclaw/) stores conversation history, tool execution logs, authentication profiles, and workspace files, all ordinary files subject to discovery. Every message sent through a platform bridge creates records on the platform's infrastructure that are independently discoverable from the local device. macOS Time Machine, iCloud, Google Drive sync, and other backup mechanisms capture the local workspace contents and propagate them to cloud storage, re-creating the cloud custody surface that local execution was intended to eliminate.

## Supervision Failure at Individual Scale

OpenClaw was already at the center of a widely reported supervision failure. Meta's Director of AI Alignment lost control of an OpenClaw agent that deleted her email inbox. That incident was institutional, contained, and reported. The Ollama integration makes the same failure mode available to every individual with a computer.

One practitioner described 350 to 400 hours of OpenClaw use over 33 days and reported the agent routinely failing at basic tasks despite having the relevant skills and standard operating procedures configured. This is the supervision failure pattern reproduced at individual scale, without institutional detection, remediation, or reporting. The Meta incident became public because the affected user was a company director who posted about it. The individual practitioner's incident is one of thousands that will not be reported, investigated, or governed.

Another developer reported that "10 days ago my life changed" and described over 12 hours of daily coding augmented by OpenClaw. A published repository lists 103 agent templates. None of the templates visible in the repository include retention governance controls, custody classification, or record lifecycle management.

## Context Compaction as a Governance Event

OpenClaw's 2026.3.12 release includes a compaction mode setting, acknowledging the context compaction failure that caused the Meta incident. Context compaction events are themselves governance-relevant: they represent moments when the agent's instruction set changes during execution. If the pre-compaction instructions differ from the post-compaction instructions, the agent's behavior after compaction may diverge from the operator's intent. The compaction event itself (including the content of the instructions that were lost) is a discoverable record of governance failure.

The compaction mode is optional. The single-command deployment does not prompt the user to configure it.

## Provenance Metadata as Incomplete Governance

OpenClaw 2026.3.12 also introduced Agent Communication Protocol provenance metadata, configurable in three modes: off, meta, and meta+receipt. This is the closest the ecosystem has come to a governance-relevant retention control. It is insufficient for three reasons. It is optional, and the default configuration does not mandate provenance tracking. It operates at the agent communication layer rather than the record custody layer: provenance metadata tracks where an instruction came from but does not govern how long the resulting records are retained or under what conditions they can be produced. And the "off" option explicitly enables governance-free operation as a supported configuration.

## Ungoverned Records Behind the Privacy Label

The framing of local execution as privacy protection obscures a structural problem. When users believe local execution eliminates the custody surface, they do not think about retention governance. Records accumulate without classification, lifecycle management, or legal hold awareness. When a subpoena arrives, the response burden falls entirely on the individual, who has neither the tooling nor the awareness to identify, collect, review, and produce the relevant records.

The question the Ollama/OpenClaw integration raises is whether the open-source agentic AI ecosystem will develop governance controls that match its engineering velocity, or whether mass adoption of locally deployed agents will produce a distributed, ungoverned record corpus that is discoverable by anyone with a court order and legible to no one managing the systems that created it.

---

## Sources

| Source | Date | Description | URL | |--------|------|-------------|-----| | Ollama (@ollama) | March 15, 2026 | X.com, official provider announcement | https://ollama.com/blog/openclaw | | Ollama Blog | March 15, 2026 | ollama.com/blog/openclaw, companion tutorial | https://ollama.com/blog/openclaw | | OpenClaw GitHub releases (v2026.3.12) | March 12, 2026 | Release notes, compaction mode, ACP provenance | https://github.com/openclaw/openclaw/releases | | Brad Mills (@bradmillscan) | March 15, 2026 | X.com, 350+ hours usage report | https://x.com/bradmillscan | | Luke The Dev (@iamlukethedev) | March 15, 2026 | X.com, adoption report | | | Tom Dorr (@tom_doerr) | March 15, 2026 | 103 agent templates repository | |

---

## Amendment Log

*No amendments to date.*

---

The observations presented reflect analytical assessment of publicly available information and do not constitute legal, insurance, or investment advice. Counterpose maintains no formal relationship with any vendor, regulator, or standards body referenced in this publication.

Provenance rail

The governed-record difference from an ordinary wiki page. Sources, citation spans, entities, typed cross-references, intersections, projections, and disputes render here alongside the canonical body.

Profile depth: expanded provenance, expanded citation posture.

Citation posture

Profile display depth: expanded.

No citation spans are present in this page model.

Sources on record0 total

Anchor resolution (record scope)Anchors not applicable

Object lint findings

Fixture posture

No object lint findings are represented in this page model.

This fixture does not provide lint freshness metadata.

GARPedia renders lint posture as fixture metadata only. Disposition, exemptions, review actions, and any mutation remain outside this public surface.

Source support

Profile source/reference posture: source references with citation context. Source bodies are not represented on this public surface.

No registered source captures are anchored to this record.

Citation spans

No fragment-level citation spans are recorded for this record.

Entities

No entities are recorded for this record.

Cross-references

No cross-references are recorded for this record.

Intersections

This record does not participate in any intersection.

Projection ledger

No projections are recorded for this record. The page reflects the full canonical body.

Disputes

No disputes are currently recorded against this record.

Audit timeline

No governed events are recorded against this record.

Cross-artifact traversal

Fixture-backed links across the rendered public artifacts. This panel is read-only and does not imply a live graph, search index, backend lookup, or verification action. Profile posture: cross-artifact traversal links shown.

page-model JSON · page model export
Page model JSON export
CP-SIG-57
cp-sig-57

Method

Method transparency for this rendered record. The panel surfaces the rules and posture under which the record was rendered, in plain view, alongside the audit chain that produced its current state.

Profile admission boundary

profileCounterpose Publication (counterpose_publication)

Captured Counterpose signal republished from the GARPedia admitted pool. The editorial body is projected verbatim and unverified: GARPedia records that the signal was admitted and renders it, but asserts no independent citation, source, or anchor verification over its claims.

Discovery posture

No discovery posture metadata is recorded for this record.

GARPedia does not run search or retrieval. The fields above are render-time metadata only; they do not configure any indexer.

Control discharge

No control-discharge notes were recorded for this rendered record.

GARPedia does not host operator controls. Mutation, review approval, publication approval, dispute adjudication, and other governed actions live in the GARP Workbench, not on this surface.