Open Workspace Schema Framework (OWSF)
claimed by its maintainerA portable, append-only workspace artifact model for execution continuity, replay, handoff and forking across tools; structure and invariants, not orchestration or transport.
Canonical text: https://github.com/hop-top/spec-owsf/blob/main/specs/v1.0/core.md, read against version 1.0.
What it fixes
- A workspace is an append-only artifact; history is never rewritten.
- Continuity, replay, handoff and forking are properties of the artifact, not of the tool that wrote it.
- Invariants are normative; runtime orchestration and transport are out of scope.
- Integrations declare how they reference a workspace, not how they run it.
Facts
- Maintainer
- hop.top, published by Idea Crafters
- Repository
- https://github.com/hop-top/spec-owsf
- First published
- 2026
- Status of the text
- draft
- Listing
- claimed by the maintainer, 2026-10-25
Read with
- claimed
crtx
The wire and storage shape for AI agent conversations, sessions, turns, content parts, tool calls and the envelope that carries them, so runtime tools agree on one record.
v0.1 Agent State - claimed
V*
Agentic-system state, worlds, missions, players, turns, observations and decisions, represented as iCalendar and vCard components so agent work rides existing calendar and contact tooling instead of a bespoke protocol.
v1.0.0-alpha.1 Agent State - claimed
Agent Operation Protocol
Six laws a system must enforce at its API boundary so that any actor, human or agent, can act on a shared operational graph without breaking it.
Badge
[](https://manifesto.md/owsf/)