docs: add Phase 2.5 (Protocol Foundation) roadmap and strategic reframe#32
docs: add Phase 2.5 (Protocol Foundation) roadmap and strategic reframe#32simonovic86 merged 2 commits intomainfrom
Conversation
Igor is a protocol, not a platform. The competitive moat is agent sovereignty (identity + lineage + portability), not durable execution. Reprioritize roadmap: ship checkpoint format spec, standalone verifier, and effects library before self-migration and compute provider integration. Adoption comes bottom-up through verification, like JWT. - Add Product Phase 2.5: Protocol Foundation (effects library, checkpoint format spec, standalone verifier, browser WASM verifier) - Document known tech debt (budget negativity, layering violation, stringly-typed retry, unchecked type assertion, stale comments) - Add "Igor as Protocol" section to vision doc - Update competitive positioning, open questions, long-term vision Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ac40d3045a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
docs/governance/ROADMAP.md
Outdated
| Igor has completed its research foundation (**Phases 2–5**) and product phases 1–2. The runtime supports **portable, infrastructure-independent agents** with DID identity, cryptographic lineage verification, effect-safe side effects, HTTP/payment hostcalls, and clean CLI workflows (`igord run`, `resume`, `verify`). | ||
|
|
||
| **Product Phase 1 (Portable Sovereign Agent)** is complete. **Product Phase 2 (Agent Self-Provisioning)** is next. | ||
| **Product Phase 1 (Portable Sovereign Agent)** and **Phase 2 (Agent Self-Provisioning)** feature work are complete. **Product Phase 2.5 (Protocol Foundation)** is next — making the checkpoint format, verifier, and effect primitives independently adoptable. |
There was a problem hiding this comment.
Don't mark Phase 2 complete while goals remain open
This change marks Product Phase 2 as complete, but the same roadmap still shows an unfinished Phase 2 goal (Agent decides when to migrate). That contradiction makes planning ambiguous for anyone using this document to prioritize work, because it simultaneously signals "done" and "not done" for the same phase.
Useful? React with 👍 / 👎.
docs/governance/ROADMAP.md
Outdated
| **Binary model after this phase:** | ||
| - `igor` (renamed from `igord`) — agent operators — run, resume, verify, inspect | ||
| - `igor-verify` (new) — anyone verifying lineage — checkpoint parsing + chain verification only | ||
| - `igor-lab` (existing, unchanged) — protocol developers — migration, replay, leases, simulator |
There was a problem hiding this comment.
Keep lab binary naming consistent in Phase 2.5 plan
The new binary model lists igor-lab as "existing, unchanged," but the current repo uses igord-lab; this makes the roadmap internally inconsistent and can misdirect users toward a non-existent executable name in scripts or docs. Please clarify whether the lab binary is also being renamed or should remain igord-lab.
Useful? React with 👍 / 👎.
Address PR review comments: - Clarify Phase 2 is still in progress (self-migration deferred to after Phase 2.5), not complete - Fix lab binary name: igord-lab, not igor-lab (rename only applies to the main binary) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
igor-verify), browser WASM verifier — all before self-migration and compute provider integration.ParseCheckpointHeaderlayering violation, stringly-typed retry classification, unchecked lease type assertion, stale timeout comments.Test plan
make check: fmt, vet, lint, tests)🤖 Generated with Claude Code