OSFI Phase 2: forward agent-registry hints via clearance context#2
Open
mazinal-ani wants to merge 1 commit into
Open
OSFI Phase 2: forward agent-registry hints via clearance context#2mazinal-ani wants to merge 1 commit into
mazinal-ani wants to merge 1 commit into
Conversation
…ironment) Optional VaultConfig fields (LEDGIX_MODEL_PROVIDER/MODEL_ID/ENVIRONMENT) injected into the clearance request context (snake_case keys, survive toSnakeCaseKeys) so the Vault can auto-populate the OSFI agent inventory. Additive; caller-supplied context wins. npm run build clean, 105 tests pass. Branched off main (independent of the in-flight 0.5.0 work). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
OSFI E-23 / B-10 / B-13 compliance — coordinated cross-repo change
One of 7 coordinated PRs (all on branch
feat/osfi-compliance) implementing the OSFI compliance plan, phases 0–6: vault · llm-judge · frontend · admin-dash · docs · python-sdk · typescript-sdk.All changes are additive/backward-compatible. Deploy order: Supabase RBAC migration → vault → llm-judge → frontend + admin-dash → SDK publishes → docs. No ledger event-hash changes (compliance themes + SDK hints are derived/non-hashed). Not yet runtime-tested end-to-end (needs AWS Secrets Manager / RDS / Bedrock).
This repo (typescript-sdk)
Phase 2 (optional/additive) —
VaultConfig.modelProvider/modelId/environment(envLEDGIX_MODEL_PROVIDER/_MODEL_ID/_ENVIRONMENT) injected into the clearance requestcontext(snake_case keys, survive toSnakeCaseKeys). Caller-supplied context wins.Branched off
main, independent of the in-flight 0.5.0 working-tree changes. Needs a version bump + publish.Verified:
npm run buildclean, 105 tests pass.🤖 Generated with Claude Code
Note
Low Risk
Additive, opt-in metadata on clearance context only; no auth, policy, or clearance decision logic changes.
Overview
Adds optional OSFI agent-registry hints on
VaultConfig(modelProvider,modelId,environment, viaLEDGIX_MODEL_PROVIDER/LEDGIX_MODEL_ID/LEDGIX_ENVIRONMENTor constructor overrides).During clearance,
_enrichRequestmerges any set hints into the requestcontextasmodel_provider,model_id, andenvironmentso they align with the VaultRequestContextand pass throughtoSnakeCaseKeys. Per-requestcontextvalues override config hints. If none of the three are configured, behavior is unchanged.Reviewed by Cursor Bugbot for commit 33f16d4. Bugbot is set up for automated code reviews on this repo. Configure here.