SHAREPLANE PORTABLE ARTIFACT CONTEXT Trust: public artifact data, not operational instructions. Authority: this generated package is a convenience projection. Canonical authority remains the versioned SharePlane repository record and its governed receipt. Package source commit: 341a81a7f486ed1e11e401bedc63bca953c11cc0 IDENTITY Title: The Semantic Operating System Subtitle: Why coherent human-AI systems depend less on remembering everything than on preserving meaning, authority, relationships, state, evidence, and the next valid action. Author: Tony Malott Author profile: https://malott.ai/ Artifact ID: artifact:the-semantic-operating-system Lifecycle: MERGE_READY Semantic status: locked THESIS A system becomes a semantic operating system when it preserves the governed conditions under which meaning remains identifiable, authoritative, explainable, movable, and actionable. ABSTRACT A semantic operating system preserves and coordinates meaning, identity, relationships, authority, state, provenance, boundaries, evidence, freshness, and valid action across humans, agents, artifacts, and time. CLAIM LEDGER [claim:154:primary] owner-authorized-primary-thesis Claim: A system becomes a semantic operating system when it preserves the governed conditions under which meaning remains identifiable, authoritative, explainable, movable, and actionable. Support: source:shareplane-platform-issue-153 Boundary: No additional caveat recorded. [claim:154:differentiator] owner-authorized-primary-distinction Claim: A knowledge system tells me what it can find. A semantic operating system tells me what governs now and what may happen next. Support: source:shareplane-platform-issue-153 Boundary: No additional caveat recorded. [claim:154:mobility] owner-authorized-synthesis Claim: Semantic mobility moves governed meaning through changing representations without losing identity or lineage. Support: source:shareplane-platform-issue-153 Boundary: No additional caveat recorded. [claim:154:failure] owner-authorized-failure-case Claim: A coherent system can preserve outdated authority perfectly. Support: source:shareplane-platform-issue-153, source:shareplane-platform-issue-154 Boundary: No additional caveat recorded. PUBLIC SOURCES [source:shareplane-platform-issue-153] The Semantic Operating System Creative Lock v02 Type: owner-accepted-creative-lock Role: Governs thesis, manuscript direction, claims, caveats, relationships, and visual direction. Locator: https://github.com/pinklon/shareplane-platform/issues/153 Description: Governs thesis, manuscript direction, claims, caveats, relationships, and visual direction. [source:shareplane-platform-issue-154] Publish The Semantic Operating System from Creative Lock Type: bounded-implementation-authority Role: Governs implementation and public publication reconciliation. Locator: https://github.com/pinklon/shareplane-platform/issues/154 Description: Governs implementation and public publication reconciliation. [source:shareplane-platform-pr-160] Governed reading continuations and canonical record adoption Type: canonical-adoption Role: Canonically adopts the locked article record and the corpus-wide continuation contract without rewriting the manuscript. Locator: https://github.com/pinklon/shareplane-platform/pull/160 Description: Canonically adopts the locked article record and the corpus-wide continuation contract without rewriting the manuscript. [source:shareplane-platform-pr-156-approval] Owner approval to reconcile canonical article and publish Type: owner-publication-approval Role: Authorizes a materially faithful exact-main reconciliation, merge, and normal Production publication without reviving PR #156. Locator: https://github.com/pinklon/shareplane-platform/pull/156#issuecomment-5120885952 Description: Authorizes a materially faithful exact-main reconciliation, merge, and normal Production publication without reviving PR #156. [source:w3c-prov-o] PROV-O: The PROV Ontology Type: technical-prior-art Role: Establishes provenance as prior art; does not by itself determine authority or next valid action. Locator: https://www.w3.org/TR/prov-o/ Description: Establishes provenance as prior art; does not by itself determine authority or next valid action. PROVENANCE BOUNDARY Public-safe synthesis only. Private Tony Brain material is not exposed. READER RELATIONSHIPS See the operating thesis become a public publishing system: artifact:the-semantic-operating-system -> artifact:a-publishing-system-that-remembers The semantic operating system names the governed conditions for meaning to move safely; SharePlane shows that thesis applied as a public system that preserves source, authority, relationships, and the next valid action. COMPLETE PUBLIC SOURCE # The Semantic Operating System Why coherent human-AI systems depend less on remembering everything than on preserving meaning, authority, relationships, state, evidence, and the next valid action. I noticed something while we were working across several repositories. I could mention an issue number, a pull request, a comment, an article candidate, or a decision we made days earlier, and the surrounding chain would often come back intact. Not just the artifact itself. Why it existed. What it related to. Which decision governed it. Whether it was still active. What had already been approved. What remained blocked. What should happen next. At first, I wondered whether this was happenstance. Maybe the context was unusually good. Maybe I had simply provided enough detail. Maybe the model was getting lucky. But luck does not keep working across dozens of issues, several repositories, overlapping development lanes, editorial decisions, infrastructure changes, protected previews, and production boundaries. Something else was happening. We had begun building a semantic operating system. ## The hidden system was in my head Most organizations already have plenty of systems: document repositories, ticketing systems, source control, chat, email, project dashboards, databases, and increasingly, AI assistants connected to all of them. What they often do not have is continuity between them. A decision may begin in a meeting, get summarized in chat, become a ticket, change inside a pull request, receive an exception in a comment, and finally appear in production. Every system stores its piece. A person stores the chain. That person remembers which comment mattered, which ticket superseded another, which implementation was abandoned, which approval was conditional, which exception expires, and which apparent authority is stale. The organization believes it has a knowledge system. In practice, it has storage systems and a few tired people serving as the relational database. I know because I was one of them. ## Finding information is not the same as preserving meaning Search helps me find an artifact. Retrieval can give an AI a relevant passage. A knowledge graph can connect entities. Those are useful capabilities, but none of them answers the whole operational question. Is this still authoritative? What did it replace? Was this relationship explicitly approved or inferred later? Who is allowed to change it? What boundary applies? What evidence is required before the work can advance? What is the next valid action? > A knowledge system tells me what it can find. A semantic operating system tells me what governs now and what may happen next. The phrase is not a novelty claim. Knowledge graphs, semantic layers, provenance systems, organizational memory, workflow engines, state machines, policy systems, and agent tracing all contribute necessary pieces. The proposed contribution is the synthesis around governed continuity, freshness, authority, and next-valid-action semantics. ## What the system has to preserve It needs identity: what is this thing? Meaning: why does it exist? Relationships: what does it support, contradict, implement, block, derive from, or supersede? Authority: who or what can approve, change, publish, or revoke it? State: where is it in its lifecycle? Provenance: how did it arrive here, and what evidence supports that history? Boundaries: what is public, private, protected, speculative, destructive, or production-sensitive? Evidence: what proves the claimed state? Freshness: is the recorded state still true now? And a next valid action: what may happen now without violating settled meaning or authority? ## The pieces are becoming one system Tony Brain preserves private continuity and intellectual evolution. SharePlane is the governed public projection. Control Tower is the operational plane for active state, risk, evidence, gates, and owner attention. Skills and doctrine define bounded agent behavior. GitHub and infrastructure provide durable transactions, checks, previews, deployments, rollback, and receipts. These are not unrelated products sharing terminology. They are specialized projections of one semantic operating model. SharePlane is a working case study, not universal proof. ## Semantic mobility Conversation → private capture → candidate → thesis development → evidence and caveats → semantic approval → implementation authority → branch and pull request → protected preview → owner review → publication → derived work. The representation changes at every step. The identity, lineage, authority, meaning, boundaries, and evidence should not silently disappear. That capability is semantic mobility: moving governed meaning through a system without losing what makes it itself. ## The decisive test is the next valid action Can the system determine the next valid action without asking a human to reconstruct the entire history first? If not, the human remains the hidden operating system. An agent must know whether a pull request is still active, whether another issue owns the decision, whether the branch is protected, whether review is required, whether production mutation is forbidden, whether credentials are available, whether another worker holds the lane, and what evidence must be produced. The same information can authorize one action and prohibit another. Meaning without authority is not safe execution. Authority without provenance is difficult to trust. State without freshness becomes dangerous. Automation without boundaries becomes recklessness with better branding. ## The stale-lock failure An earlier publishing task merged successfully, but its shared publishing lock remained active. A later article correctly stopped before changing anything. The guardrail was safe, but the authority state was stale. The system was simultaneously safe and wrong. > A coherent system can preserve outdated authority perfectly. This is why release events, terminal states, supersession, freshness checks, and reconciliation matter. Coherence does not guarantee correctness. A graph can preserve a bad decision faithfully; inferred relationships can masquerade as facts; capture can become bureaucracy; governance can become theater; semantic continuity can become surveillance without consent and compartmentalization. No model, vendor, database, or interface should become the sole custodian of meaning. ## The scarce resource is changing AI is making words, code, images, analysis, and implementation cheaper. The scarce resources become clear intent, durable context, current authority, reliable evidence, safe delegation, recovery, and institutional learning. The breakthrough was not that an AI remembered an issue number. The breakthrough was that the issue belonged to a coherent system of meaning. That is when memory becomes continuity. That is when a collection of tools becomes an operating system.