Skip to content

feat: enforce restricted trust-domain directory decisions - #110

Merged
RobLe3 merged 2 commits into
mainfrom
feat/restricted-directory-parity
Aug 22, 2026
Merged

feat: enforce restricted trust-domain directory decisions#110
RobLe3 merged 2 commits into
mainfrom
feat/restricted-directory-parity

Conversation

@RobLe3

@RobLe3 RobLe3 commented Aug 22, 2026

Copy link
Copy Markdown
Owner

Summary

Adds the Python SDK's fail-closed restricted-directory operation boundary from the merged Rust reference contract.

  • resolves membership through environment or owner-only file references
  • binds membership and subject headers to protected discovery, dispatch-ticket, and consumer-token operations
  • requires exact, current, operation-specific directory decisions
  • refuses redirects and legacy/public fallback while restricted mode is configured
  • keeps candidate eligibility process-local and does not claim peer-gossip or CIP support
  • leaves public behavior unchanged when the context is absent

Evidence

  • .venv/bin/python -m pytest -q: 1182 passed, 2 skipped
  • .venv/bin/ruff check src tests/test_restricted_directory.py: passed
  • targeted mypy: passed

Closes #103 after review and required CI evidence. Root black-box closure remains owned by RobLe3/iicp.network#921.

@RobLe3
RobLe3 merged commit 88a1e51 into main Aug 22, 2026
1 check passed
@RobLe3
RobLe3 deleted the feat/restricted-directory-parity branch August 22, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement restricted trust-domain parity after reference evidence

1 participant