Repository navigation
Releases: Coder-s-OG-s/Trajectory-IR
Release list
v0.2.2
Trajectory IR v0.1.1
Not the current line. Latest production release is v0.2.1 (after v0.2.0). This v0.1.1 tag is a historical Phase 1A patch, published retroactively; GitHub had incorrectly shown it as Latest because it was the most recently published release, not the highest semver.
Note: This release is being published retroactively on 2026-08-14. The > code and changelog entry for v0.1.1 merged tomainon 2026-08-07 (#126), > but the tag and this GitHub Release were never created at the time ΓÇö this > closes that gap. SeeCoder-s-OG-s/Trajectory-IR#175for context. Patch release after v0.1.0: reliability and honesty fixes for the Phase 1A library surface, CI Phase B live driver jobs, adoption demo and E2E docs, and Go Temporal durable backend wording. No new Phase 2 scope. ## Highlights - CI Phase B: live Postgres NodeLog and MinIO S3 CAS integration jobs - Adoption:examples/adoption_host(public client + optional CAS thin package) - Docs: E2E Postgres + CAS + thin.tirwalkthrough - Fail closed storage: missing artifactcontent_hashraises - Atomic.tirexport: no half written package at the destination path - Postgres claim honesty: real DB errors are not misread as lost race - Client IR history: plain (non gated) tools leaveTOOL_CALL/TOOL_RESULT- Clientresume(): real reattach with history check, not a silent alias - Go / Python effect parity:openWorldHintfails closed in Go - Projector safety:CONSTRAINTalways survives policy construction - Spec: Temporal recognized as Go production durable backend (#67) ## Install (from source)bash git clone https://github.com/Coder-s-OG-s/Trajectory-IR.git cd Trajectory-IR git checkout v0.1.1 pip install -e ".[dev]" # optional: pip install -e ".[s3]" or ".[postgres]"When PyPI is published:bash pip install trajectory-ir==0.1.1Go:bash cd go && go test ./...## What landed since v0.1.0 | Area | PRs (approx.) | |------|----------------| | Phase B CI (Postgres + MinIO) | #86 | | Package / branch metadata | #84 | | GoopenWorldHintfail closed | #99 | | Plain tool logging in client | #100 | | CONSTRAINT always in projector policy | #101 | | Durable test fake docs (Go) | #102 | | Missingcontent_hashfail closed | #103 | | NodeLog connection GC close | #104 | | Atomic.tirwrite | #105 | | Postgresclaim_tool_callerror propagation | #106 | | Clientresume()reattach | #107 | | Adoption host demo | #108 | | QUICKSTART E2E Postgres + CAS + thin | #109 | | Release notes prep | #110 | | Go Temporal backend wording in README | #112 | ## Not in 0.1.1 Same non goals as 0.1.0: - Package digital signatures (SIGNATUREreserved) - Live Restate cluster product packaging - Fluid / k8s-fluid profile - Multi tenant SaaS control plane - Automated PyPI Trusted Publishing (manual upload still optional) - Phase 1B Go primary program (tracked under epic #113; not part of this patch) ## Maintainer: after this release commit merges 1. Confirm CI green on the merge commit onmain. 2. Annotated tag:bash git checkout main git pull origin main git tag -a v0.1.1 -m "Trajectory IR v0.1.1 ΓÇö post-0.1.0 reliability and Phase B CI" git push origin v0.1.13. Publish a GitHub Release forv0.1.1using this file as the body. 4. Optional: build +twine uploadfor PyPI (trajectory-ir==0.1.1). See RELEASE.md. ## Full changelog See CHANGELOG.md section[0.1.1].
v0.2.1
Trajectory IR v0.2.1 Phase 1C harden patch
v0.2.0
Trajectory IR v0.2.0
Phase 1B release: Go is the primary SDK and default onboarding path.
Python remains the supported reference and parity port from Phase 1A.
Highlights
- Go primary in the master README and CONTRIBUTING
go/QUICKSTART.mdandgo/examples/adoption_host- Go Postgres NodeLog and S3 CAS (including AWS SDK v2 / MinIO env wiring)
- Go
Resumefails closed without history; plain tools leave IR history - CI: deep gates, cross language
.tirround trip, Go coverage floor 80% - Builds on the 0.1.x reliability and Phase B integration work
Install
git clone https://github.com/Coder-s-OG-s/Trajectory-IR.git
cd Trajectory-IR
git checkout v0.2.0
pip install -e ".[dev]"
# optional: pip install -e ".[s3]" or ".[postgres]"cd go
go test ./...
go run ./examples/adoption_hostWhen PyPI is published:
pip install trajectory-ir==0.2.0Not in 0.2.0
- Package digital signatures
- Fluid / k8s-fluid product packaging
- Multi tenant SaaS control plane
- Automated PyPI Trusted Publishing (manual upload still optional)
- Branch protection on private free GitHub plans (needs public or paid plan)
Full changelog
See CHANGELOG.md section [0.2.0].
v0.1.0
Trajectory IR v0.1.0
First numbered library release of Trajectory IR: a portable, hash-verifiable intermediate representation for agent runs (seals, effect classes, block-and-gate, .tir packages) on top of pluggable durable backends.
Highlights
- Python IR core with DBOS-backed durable steps and SQLite NodeLog
- Optional backends: Postgres NodeLog, Restate-style durable hooks (local memo + injectable
make_run_step), S3 and filesystem CAS - Go IR stack (
go/trajir) with LocalSQLite/Memory memoization, optional Temporal, and filesystem CAS - Portable
.tirthin/fat packages (Python + Go), with verification, resource limits, and thin rehydrate via CAS - Conformance R01–R08 under
pytest conformance/ - Sandbox (R06), graft (R07), projection redaction (R08), projector budget safety (R04) plus optional projector policy file
- Host loop example (
examples/host_loop) using only public client APIs - OSS process: DCO, CI (Ruff/Mypy/pytest coverage floors, Package smoke, Security pip-audit, Go coverage floor + govulncheck), Dependabot, SECURITY.md
Install (from source)
git clone https://github.com/Coder-s-OG-s/Trajectory-IR.git
cd Trajectory-IR
pip install -e ".[dev]"
# optional: pip install -e ".[s3]" or ".[postgres]"From the release tag / PyPI (when published):
pip install trajectory-ir==0.1.0Go:
cd go && go test ./...See QUICKSTART.md and PHASE_1A_STATUS.md.
Not in 0.1.0
- Package digital signatures (
SIGNATUREreserved) - Live Restate cluster product packaging (adapter + local memo only)
- Fluid / k8s-fluid profile
- Full multi-tenant SaaS control plane
- Automated PyPI Trusted Publishing (manual upload optional)
Spec note
Master README still names DBOS as the Phase 1A Python default; Go production Temporal is implemented. Tracking residual wording in issue #67.
CNCF context
Positioned against the storage gap described in the CNCF TAG Infrastructure white paper:
https://www.cncf.io/wp-content/uploads/2026/07/DoK_DataAnalyticsAIMLWorkloads_070826.pdf
Full changelog
See CHANGELOG.md section [0.1.0].