V* (vstar)
claimed by its maintainerAgentic-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.
Two public copies exist today, an older v0.1 in spec-vstar and this v1.0 line in poly-vstar; the link points at the newer text until the two are reconciled.
Canonical text: https://github.com/hop-top/poly-vstar/tree/main/spec/v1.0, read against version 1.0.0-alpha.1.
What it fixes
- Time, identity and sequence semantics already exist in RFC 5545 and RFC 6350; agent state maps onto them instead of inventing a protocol.
- Each state component has one canonical mapping and a canonicalization rule, so two implementations produce the same bytes.
- Versions are independent directories; breaking changes open a new one.
Facts
- Maintainer
- hop.top, published by Idea Crafters
- Repository
- https://github.com/hop-top/poly-vstar
- First published
- 2026-09
- Status of the text
- draft
- Listing
- claimed by the maintainer, 2026-10-25
Read with
- claimed
Open Workspace Schema Framework
A portable, append-only workspace artifact model for execution continuity, replay, handoff and forking across tools; structure and invariants, not orchestration or transport.
v1.0 Agent State - 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
Badge
[](https://manifesto.md/vstar/)