Tour: v1 → v2 evolution
Goal: pattern-match what kinds of changes appear in v2 across two unrelated projects (OpenHands and Comp-AI), so you know what to expect when you re-architect.
What to look for
| Category | Examples in OpenHands v0→v1 | Examples in Comp-AI v1→v2 |
|---|---|---|
| Renamed primitives | Action ↔ Event semantics tightened | Tenant scoping refactored |
| Pluggability | Condenser made strategy-pluggable | AI integrations slotted behind interface |
| Cleaner seams | Controller ↔ runtime decoupled | RBAC moved to dedicated module |
| Removed features | (note what’s gone) | (note what’s gone) |
Pacing
| Block | Time |
|---|---|
| OpenHands v0 overview | 7 min |
| OpenHands v1 overview | 10 min |
| Comp-AI v1 overview | 5 min |
| Comp-AI v2 overview | 5 min |
| Concept: agent-loop (skim) | 3 min |
Output
A short list of “kinds of changes I expect to make in my v2.” The point is the meta: v2s look surprisingly similar across domains.
Itinerary
-
OpenHands (v0) project
Read v0's overview to anchor what changes.
-
OpenHands (v1) project
v1 — note what's new, what's gone, what's renamed.
-
Comp AI (v1) project
Compliance SaaS v1: data model and RBAC story.
-
Comp AI (v2) project
v2: cleaner model, refined RBAC. Diff to v1.
-
Agent loop concept
v1→v2 changes are usually around the loop's seams.