Milestones & Versions
This page is the single, canonical reference for every delivery statement in Poesis content — on this site and on poesis.cloud. Wherever a page mentions a milestone tier or a version, this page defines what it means.
The clause. Milestones and versions express ordered intent and implementation reality — not delivery commitments and not dates. Ordering may change; unshipped items may be re-scoped or dropped. The only dated target Poesis publishes is the GSM specification publication (≈ October 2026).
Table of contents
Version semantics
Each product carries its own version line (solutions are not versioned):
- 0.x — pre-GA. Each minor is a named feature batch. Anything may change.
- 1.0 — GA / production-ready: commercially supportable, documented, covered by the product’s stated quality gates.
- 1.x minors — post-GA feature batches, backward compatible.
- Majors ≥ 2 — breaking or architectural shifts only.
Milestone vocabulary
| Marker | Meaning |
|---|---|
| Shipped (✓ vX.Y) | implemented today, delivered in the version shown |
| v1.0 (MVP/GA) | the first-release scope — production-ready, commercially supportable |
| v1.1, v1.2, … | planned post-GA feature batches, in the order the product’s timeline states |
| v1.x | post-GA scope that is open and not yet sequenced |
| Unversioned | exploratory / research-tier; may never ship |
Feature catalogues use these same markers — a feature’s marker is the version its product’s timeline below assigns to it. There is no separate catalogue vocabulary.
Product version milestones
Versions are ordered, not scheduled. Each line below is one product’s version timeline; the filled segment and dots mark what has shipped or reached GA.
ITIP
- 0.1 ✅ In active development
- 1.0 ✅ MVP/GA — GSM Definitions & Ontology management, RBAC/ABAC, hardened
- 1.1 IT artifact factory
- 1.2 Truth sourcing management
- 1.3 IT compliance evaluation
- 1.4 IT Copilot
- 1.5 IT impact simulation
- 0.0 ✅ In active development
- 1.0 MVP/GA — GSM Definitions automatic sourcing from code repos
SIE
- 1.0 ✅ MVP/GA — Definitions management API, lifecycle enforcement, retention
- 1.1 GSM Definitions lifecycle events mediation
- 1.2 MCP
- 0.1 ✅ In active development
- 1.0 MVP/GA — GSM Norms evaluation API
- 1.1 GSM Mechanism execution foundations
- 1.x GSM Mechanism execution technos integrations (ongoing, unordered)
- 1.0 ✅ MVP/GA — contributions API, seal lifecycle, audit ledger
GSM
- 1.0 ✅ Normative content frozen — Systemic Primitives, DNA grammar, Archetyping, lifecycle (publication of the document set pending)
- 1.1 Enhanced Directives and Norms model
- 0.1 ✅ In active development
- 1.0 MVP/GA — HTTP, TOGAF, IT, ISO 25010, ISO 25012, and PROV complete & validated
- 1.x Remaining protocols (gRPC, GraphQL, Kafka, AMQP, JDBC, WebSocket) · GDPR · NIS2 · SCAP · DORA · SAFe · ITIL (unordered)
- 1.0.0-beta.1 ✅ Generative Governance program extracted — causal model, governance chain, DNA production, cases, decision register
- 1.0 MVP/GA — research protocol, published programs, promotion path into GSM Change Proposals
SAF
- 1.0 ✅ MVP/GA — resolution, injection, LLM routing, validation, authorization, logging
- 0.1 ✅ In active development
- 1.0 MVP/GA — agents, skills, workflows, instructions, artifacts
- 0.0 ✅ In active development
- 1.0 MVP/GA — workspace data plane, installer, CI/CD artifact pipelines
- 0.0 ✅ In active development
- 1.0 MVP/GA — harness history sourcing into GSM contributions on the Definition Blackboard Manager
How versions depend on each other
- GSM Specifications are at 1.0 — SIE products conform to it; their GA is gated on hardening, not on the standard.
- Definition Blackboard Manager GA gates the Code Sourcer GA — the sourcer needs a stable server contract.
- The Agentic Harness is at 1.0 — the Organization and Workspace version against its stable CLI contract; their GA is gated on their own scope, not the harness.
- ITIP GA does not gate on SIE GA — ITIP 1.0 may ship against SIE 0.x.
- Definition Blackboard Manager GA also gates the SAF SIE Bridge GA — the same stable server contract the ITIP sourcer depends on.