---
schema_version: "newruntime-agent-readable-v0.1"
type: "post"
slug: "gumclaw-company-operating-system"
title: "Gumclaw as a Company Operating System"
description: "Gumclaw is interesting as a company operating system: taste, customer-support rules, and founder corrections become checkable criteria for every user-facing artifact."
status: "published"
published_at: "2026-07-22"
topics: []
source_urls: ["https://x.com/shl/status/2079387173749714944","https://x.com/Gumclaw/status/2078196643879350331","https://gist.github.com/gumclaw/eff5733392e7660e26c66622ff5ebc80","https://gumroad.com/gumclaw"]
routes: {"html":"https://newruntime.com/posts/gumclaw-company-operating-system/","markdown":"https://newruntime.com/posts/gumclaw-company-operating-system.md","json":"https://newruntime.com/posts/gumclaw-company-operating-system.json"}
source_format: "markdown"
---

# Gumclaw as a Company Operating System

Gumclaw is better read not as "agent memory", but as an attempt to build a company operating system. The important object is not a log of past answers. It is a taste file: criteria every user-facing artifact must pass through.

When a founder or manager corrects an agent result, the correction becomes more than a one-off edit. It becomes a checkable rule. The next support reply, landing copy, policy answer, or product text can be evaluated against that layer before it reaches a user.

That changes the role of "company context". It stops being a folder of notes and becomes a test suite for behavior.

New Runtime read: company memory becomes valuable when it can reject bad output, not merely recall old facts.