Skip to content

WOR-67: migrate violation evidence to defect semantics - #25

Merged
Ldsystem merged 1 commit into
mainfrom
codex/wor-67-defect-evidence-cutover
Aug 30, 2026
Merged

WOR-67: migrate violation evidence to defect semantics#25
Ldsystem merged 1 commit into
mainfrom
codex/wor-67-defect-evidence-cutover

Conversation

@Ldsystem

Copy link
Copy Markdown
Owner

Summary

  • replace live violation-* evidence/evaluation vocabulary with defect-*
  • add explicit, staged, marker-backed defect-migrate-store
  • keep retired violation-* commands fail-only with migration/replacement guidance
  • preserve evidence record IDs, schema, bytes, and generic On Violation rule prose

Migration safety

  • normal defect commands fail before initialization when legacy, staging, or marker state exists
  • migration validates legacy records, rebuilds the staged index, fingerprints both authorities, and atomically publishes
  • only a valid matching marker permits migration-only crash recovery; unmarked or mismatched two-root states fail closed

Validation

  • 29 focused evidence and migration tests pass
  • 254 affected contract tests passed before the review-bounded test split; the same 29 focused cases pass after the split
  • full CI-equivalent repository suite passed: 650 tests
  • skill package, explicit-root rule validation, retired-vocabulary boundary, and git diff --check pass
  • a copy of the real 77-record legacy store migrated with an identical aggregate record digest; the real store remains untouched until merge

Scope

Breaking change: live command/store/rule vocabulary changes from violation to defect; operators run defect-migrate-store explicitly after upgrading.

Add explicit staged store migration with marker-backed crash recovery, preserve neutral evidence records, and retire work-performing violation commands with guidance.
@Ldsystem
Ldsystem merged commit 3f826f1 into main Aug 30, 2026
2 checks passed
@Ldsystem
Ldsystem deleted the codex/wor-67-defect-evidence-cutover branch August 30, 2026 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant