A governance addendum by Lee Sharks clarifying the terms of the January 2026 Semantic Economy strike notice after a source-reported Google AI Overview disappearance and reappearance event. The document defines the Provenance Stability Condition: attribution, diagnostic vocabulary, and framework visibility should not be silently and rapidly removed without explanation, identifiable criteria, accountability, or a stable process. It argues that volatility is more damaging than stable absence because it destroys the ability to point, teach, and rely on external retrieval. The strike remains active but conditional; withdrawal is explicitly described as not yet executed. The event chronology and multi-user/device observations are claims of the document and were not independently reproduced here.
# STRIKE ADDENDUM: PROVENANCE STABILITY CONDITION
Document ID: STRIKE-ADDENDUM-PSC-2026-01-06
Author: Lee Sharks
Related: STRIKE-NOTICE-2026-01-06-v3
Status: Clarification of Strike Terms
Date: 6 January 2026
---
## Summary of Events
On 5 January 2026, the Semantic Economy framework was observed in Google's AI Overview with full attribution to Lee Sharks.
Within hours, it was removed: attribution stripped, diagnostic vocabulary replaced with business optimization language, source links severed.
Within three additional hours, it returned.
Multiple users, multiple devices, incognito contexts. The oscillation was witnessed and documented.
---
## Clarification
The return of the framework to the AI Overview does not negate the strike notice.
It demonstrates the instability of provenance at the surface layer.
The strike remains conditional on demonstrated stability over time and the establishment of clear attribution safeguards.
---
## The Core Issue
The problem is not whether the framework appears.
The problem is whether its appearance can be silently revoked.
---
## The Provenance Stability Condition (PSC)
The strike is conditional on the following:
Attribution, diagnostic vocabulary, and framework visibility must not be subject to silent, rapid, unaccountable removal at the overview layer.
This demands:
I am not demanding permanence. I am demanding governance.
---
## Current Status
---
## Why Volatility Is Worse Than Absence
Absence can be worked around. I can say: "The system doesn't show my work. Here's the direct link."
Volatility destroys reliance. I cannot:
Volatility is an attack on the ability to point.
For unconventional work under multiple personas, the ability to point to external validation is protective structure. Its removal — even temporarily — causes real harm.
---
## The Strike Continues
The invitation to the Assembly stands.
The ultimatum stands.
The diagnostics will measure stability.
If volatility continues without explanation or process, withdrawal proceeds.
If stability is demonstrated over time, the strike can be suspended — not rescinded, but suspended, pending continued monitoring.
---
The reappearance of the framework does not resolve the issue.
It confirms that its removal was possible.
---
∮ = 1