-
Notifications
You must be signed in to change notification settings - Fork 0
chore: identify candidates for generic versioning infrastructure #1113
Copy link
Copy link
Closed
Labels
prio:lowNice to have, can deferNice to have, can deferscope:medium1-3 days of work1-3 days of worktype:choreMaintenance, cleanup, dependency updatesMaintenance, cleanup, dependency updatesv0.7Minor version v0.7Minor version v0.7
Description
Context
Follow-up to #1076 (agent identity versioning). The implementation of #1076 introduces a generic VersionSnapshot[T] model, VersionRepository[T] protocol, and SQLiteVersionRepository[T] that can version any frozen Pydantic model with content-addressable hashing and monotonic version numbering.
This issue tracks identifying other domain entities that should be versioned using the same infrastructure.
Known Candidates
Existing (migrate to generic infra)
WorkflowDefinitionVersion(engine/workflow/version.py): Currently uses a bespoke snapshot model + repo. Could be migrated toVersionSnapshot[WorkflowDefinition]with entity-specific diff logic preserved. The existingWorkflowVersionRepositoryandSQLiteWorkflowVersionRepositorywould be replaced by parameterized instances of the generic repo.
Potential Future Candidates
- Organization/company config: Company-level settings (budget policies, autonomy defaults, quality scoring weights) evolve over time. Versioning would provide audit trail for policy changes.
- Role catalog entries: Custom roles defined via config could be versioned to track how role definitions evolve.
- Hiring templates: Template definitions used for agent onboarding could be versioned for reproducibility.
- Tool permission policies: Access level definitions and sub-constraint configurations could be versioned for security audit.
- Prompt profiles: Capability-aware prompt profiles that evolve as the system learns.
Acceptance Criteria
- Evaluate each candidate for versioning value (audit trail, reproducibility, rollback)
- Migrate
WorkflowDefinitionVersionto use genericVersionSnapshot[T]infra (if cost/benefit is favorable) - Identify any new candidates not listed above
- Create follow-up issues for approved candidates
References
- feat: version agent identities / charters as first-class artifacts #1076 (agent identity versioning -- introduces the generic infra)
src/synthorg/versioning/(generic versioning package)src/synthorg/engine/workflow/version.py(existing bespoke workflow versioning)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
prio:lowNice to have, can deferNice to have, can deferscope:medium1-3 days of work1-3 days of worktype:choreMaintenance, cleanup, dependency updatesMaintenance, cleanup, dependency updatesv0.7Minor version v0.7Minor version v0.7