OSFI Phase 2: forward agent-registry hints via clearance context#2
Closed
mazinal-ani wants to merge 9 commits into
Closed
OSFI Phase 2: forward agent-registry hints via clearance context#2mazinal-ani wants to merge 9 commits into
mazinal-ani wants to merge 9 commits into
Conversation
Scaffolds a local dev environment with docker-compose, env file, and manifest template. Starts vault + judge + postgres, polls health, and prints integration instructions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… in CLI, client, and tests Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Removed all inline ship-safe-ignore comments (one was causing GIT_PYTHON_DEP). Moved test Stripe key to TEST_STRIPE_API_KEY env var with fallback. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…nvironment) Optional VaultConfig fields (LEDGIX_MODEL_PROVIDER/MODEL_ID/ENVIRONMENT) injected into the clearance request context (snake_case) so the Vault can auto-populate the OSFI agent inventory. Additive/backward-compatible; caller-supplied context wins. 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
2 participants
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 (python-sdk)
Phase 2 (optional/additive) —
VaultConfig.model_provider/model_id/environment(envLEDGIX_MODEL_PROVIDER/_MODEL_ID/_ENVIRONMENT) injected into the clearance requestcontext(snake_case) so the Vault can auto-populate the OSFI agent inventory. Caller-supplied context wins.Branched off
main, independent of the in-flight 0.5.0 working-tree changes (not bundled). Needs a version bump + publish to take effect; demo-env tracks the published package.Verified: py_compile + config load.
🤖 Generated with Claude Code
Note
Low Risk
Additive optional config and context enrichment only; no changes to auth, clearance logic, or ledger hashing.
Overview
Adds optional OSFI agent-registry hints on
VaultConfig:model_provider,model_id, andenvironment(viaLEDGIX_MODEL_PROVIDER,LEDGIX_MODEL_ID,LEDGIX_ENVIRONMENT).During clearance request enrichment, any set hints are merged into the request
contextas snake_case keys (model_provider,model_id,environment) so the Vault can auto-populate agent inventory. Caller-suppliedcontextvalues take precedence (setdefault).All fields default to
None; behavior is unchanged when they are unset.Reviewed by Cursor Bugbot for commit 3e91160. Bugbot is set up for automated code reviews on this repo. Configure here.