Scaffold airlock + verified-run primitive#1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sets up the repo from scratch: strict typescript, tsup build, vitest, and a CI workflow, plus the actual primitive this whole thing is built around. runVerified takes some untrusted task, runs it under a deadline with an AbortSignal, and only hands back the value when it beats the clock and passes a post-condition assertion the caller supplies. everything else (timeout, failed assertion, thrown error) comes back as an explicit variant of a discriminated union so you literally can't read the output without proving the run was good first. the in-process tier here can't preempt a synchronous spin loop, that's what the isolated-vm and docker tiers will handle later, but this pins down the contract they'll implement. tests cover the ok path, assertion refusal, timeouts aborting the task, caller cancellation, bad timeout args and a few concurrent runs staying independent.