Skip to content

feat: Add self-verification with verified:true only on assertion pass - #6

Merged
ThomasHartDev merged 1 commit into
mainfrom
thomas/feat/self-verify
Aug 16, 2026
Merged

feat: Add self-verification with verified:true only on assertion pass#6
ThomasHartDev merged 1 commit into
mainfrom
thomas/feat/self-verify

Conversation

@ThomasHartDev

Copy link
Copy Markdown
Owner

Every RunResult now carries a literal verified flag, and verified:true only appears when the caller-supplied post-condition passes. Verification is its own pure phase in src/verify.ts (selfVerify, allAssertions/anyAssertion, optional reason on failure) so the vm and worker runners just hand the produced value in and never invent trust from a successful execute alone. isVerified narrows on verified:true, and the suite covers pass/fail, reasons, composition, and the failure modes that must stay unverified.

Split post-condition checking into a pure selfVerify phase and tag every
RunResult with a literal verified flag so trusted values only appear when
the caller-supplied assertion holds.
@ThomasHartDev
ThomasHartDev force-pushed the thomas/feat/self-verify branch from 09f04be to 124b636 Compare August 16, 2026 06:27
@ThomasHartDev
ThomasHartDev merged commit 1b6743f into main Aug 16, 2026
@ThomasHartDev
ThomasHartDev deleted the thomas/feat/self-verify branch August 16, 2026 06:27
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