[Experiment] CHASM scheduler action and policy contracts - #59
Draft
chaptersix wants to merge 1 commit into
Draft
chaptersix wants to merge 1 commit into
chaptersix wants to merge 1 commit into
Conversation
This was referenced Sep 5, 2026
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
1 participant
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.
The CHASM scheduler now separates action behavior from occurrence generation, overlap planning, start retries, accounting, and retention. This layer moves workflow request construction and completion interpretation into an action implementation, adds resolved policy identities and a validated policy registry, and persists generic execution references alongside legacy workflow projections.
Start results are reconciled by stable occurrence identity and attempt state across buffer movement. A selected start reserves its overlap slot before acknowledgement; compatible completion-before-acknowledgement results merge, accepted starts count once, and failed starts release waiting work. Existing workflow last-success/continued-failure and ALLOW_ALL behavior remain covered by the preserved tests. This layer registers only workflow actions.
Validation: full
go test -tags test_dep ./chasm/lib/scheduler/...passed on this intermediate layer. The complete integration also passes CHASM engine, activity, frontend, functional, and SDK checks andmake lint-code-fast.This is an experimental draft stack; do not merge. The local integration base combines server main
ad7b2298dcce00688cfe3b83ab02819abf9249e8with the published readability stacke6c239bd4a368fcaaae7aefec85e3e4281f38045, preserving both sets of tests. Published branches are unchanged.Cross-repository dependencies:
40766d34ea6c0d2e59c100c1cf20cdf4fb286fe45fd10bc0a6cd7694373353cf6e00a0886a0b8167a6bed7c8ed3c4b90c467f003571c98b44ea8785bd80de5800cde0845596277a1af957c731eb1c0a2onexperiment/extensible-chasm-schedulerValidation uses Go 1.26.7 and an external four-module
go.workcontaining server, API-Go, SDK, and SDK/test. No dependency replacements or workspace files are committed; standalone CI needs these linked revisions wired explicitly until dependency versions are published.Complete server review order: contracts, activity, visibility, coverage.