Gumclaw is interesting as a company operating system: taste, customer-support rules, and founder corrections become checkable criteria for every user-facing artifact.
In one minute
- Gumclaw is interesting as a company operating system: taste, customer-support rules, and founder corrections become checkable criteria for every user-facing artifact.
- The record is connected to 0 topics: .
- 4 public sources carry the evidence boundary.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|
| 1 | x.comsource | primary receipt | source_urls |
| 2 | x.comsource | supporting receipt | source_urls |
| 3 | gist.github.comrepo | supporting receipt | source_urls |
Showing 3 of 4; the complete set is exposed in the JSON route.
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.