Add local Workspace Operations contract surfaces to sourceos-shell#17
Draft
Add local Workspace Operations contract surfaces to sourceos-shell#17
Conversation
Agent-Logs-Url: https://github.com/SourceOS-Linux/sourceos-shell/sessions/0f6cf1f9-4ff1-4575-bb41-2a7664faa98f Co-authored-by: mdheller <21163552+mdheller@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Expose local workspace operations in SourceOS shell UX
Add local Workspace Operations contract surfaces to sourceos-shell
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sourceos-shellneeds to surface and control local Workspace Operations (sync, terminal, browser, agent-machine, model carry, workstation state) while remaining a pure projection/control layer — no Policy Fabric ownership, no Operation Plane runtime logic.Contracts (schemas)
workspace-operation-state.schema.json— read-only projection the shell renders from Operation Plane state. Covers all required lifecycle states (stored→quarantined→admitted→activated→syncing→conflicted→failed), file availability states (local,remote,syncing,conflicted,quarantined), device identity/trust profile,sourceos-syncdsync status, TurtleTerm/BearBrowser/agent-machine entry points, and Operation Tray/Inspector projection metadata.operation-command.schema.json— structured record the shell emits to route actions through the Operation Plane (never executes integrations directly). Command classes:turtleterm-open/close,bearbrowser-open/close,agentmachine-activate/deactivate,sync-request/cancel,diagnostics-export,model-carry-initiate,workstation-state-query. IncludesisDryRunfor plan/preview.diagnostics-export.schema.json— redacted diagnostics export;redactionApplied: trueandcontentCaptureEnabled: falseare schema-enforced invariants.Examples (
examples/workspace-ops/)Eight example fixtures covering the full state space: admitted/syncing, conflicted, and quarantined operation states; turtleterm-open, sync-request, and agentmachine-activate commands; redacted and metadata-only diagnostics exports.
Validation & CI
scripts/validate_workspace_ops.py(mirrorsvalidate_ops_history_receipts.py) validates all examples against their schemas and enforces domain invariants (policyDecisionRefsnon-empty,redactionApplied: true, etc.)..github/workflows/workspace-ops.ymlruns it on every relevant path change.Docs
docs/workspace-operations.mdcaptures boundary rules, surface-to-schema mapping, full state/command-class tables, and integration refs — matching the style ofdocs/ops-history-receipts.md.