Repository navigation
refactor(core): standardize participation and public extension APIs - #203
Merged
KartikP merged 5 commits intoNov 3, 2026
Merged
Conversation
This was referenced Nov 2, 2026
Keep the public intervention wording and retain the incoming input-site\nand vector-drive documentation, annotation and forwarding test.
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.
Use one public subject/session API across the UMI.
Subject.participate(session)is the evaluation method;process()remains a concrete convenience.Changes
extractor,answer,policyandintervention.Validation
At
e4b2828, required Linux/macOS, OpenPI and Jenkins checks pass. The coordinated installed-package run passed 954 Core tests per platform, with no skips. Core remains importable without model frameworks. These are interface/fixture checks, not a new trained-model scoring qualification.Coordinated merge
Vision #2632, Language #437, Unified #47. All target
unified-model-interface-v2. This is the agreed pre-release rename; there is nointeractalias. Permanent legacy APIs remain supported. Merge only after the coordinated checks pass, then refresh Unified's peer pins to merged v2 revisions.