# Integration support and boundaries A release-specific matrix separates the tested 5D core from integrations that need additional wiring and review or execution capabilities owned by the host. - Canonical: https://5d.langoni.me/evidence/integrations/ - Evidence strength: Verified - Evidence form: Shipped code - Version: 2.0.0 - Author: Loren Angoni; 5D product owner - Created: 2026-09-27 - Updated: 2026-10-06 - Verified: 2026-10-06 ## Scope PyPI release 0.7.0, exact package fivedrisk-0.7.0-py3-none-any.whl, SHA-256 790edf0e09c81e89b232ab77589d6df8551a08ed93d0bef3644f5f1a4043c22c, plus the clearly labelled action-flow walkthrough. ## One release, several materially different contracts The Python verdict socket, function decorator, JSON-lines gateway, Claude Code hooks, LangGraph node, and five framework shims do not expose identical enforcement or approval semantics. The matrix states the stop shape and known bypass boundary for each path. Verified core means the named behavior was exercised from the exact wheel without depending on a live framework SDK. Partial integration means an entry point exists but stronger end-to-end framework evidence is absent. ## Review and semantic evidence do not become permission The public package does not ship a universal reviewer service or a semantic observer. A host may compose Jev or another contextual model, but the observer remains evidence and cannot clear an explicit deterministic block. The has_approval_channel flag is a caller assertion. It is not proof that an authenticated reviewer approved the exact attempt. ## Claim register ### The tested artifact is exact Evidence strength: Verified Evidence form: Shipped code Evidence: pypi-wheel-070 The integration receipt is bound to the public 0.7.0 wheel and its SHA-256 digest rather than to an unpinned working tree. Limit: The receipt proves the exercised wheel behavior, not every possible host integration. ### Core entry points return a disposition before host execution Evidence strength: Verified Evidence form: Shipped code Evidence: pypi-wheel-070 The verdict socket, decorator, and gateway expose pre-action decision paths with fail-closed malformed-input or unknown-band behavior. Limit: The host must place the entry point on every relevant execution path and honor the result. ### Framework shims remain partial integrations Evidence strength: Verified Evidence form: Shipped code Evidence: pypi-wheel-070 Five framework translation shims exist and were tested against in-repository fakes, but do not yet have pinned live-SDK end-to-end proof for every framework. Limit: Adapter availability is not a claim of production support or complete interception coverage. ### The setup skill is repository-hosted Evidence strength: Verified Evidence form: Shipped code Evidence: pypi-wheel-070, setup-skill-source The complete SKILL.md is available from GitHub, while the 0.7.0 wheel omits the complete skill instructions and reference set. Limit: Installing the Python package alone does not install the complete coding-agent skill. ### The complete cascade is an integration contract Evidence strength: Design target Evidence form: Framework mapping Evidence: website-action-flow The action-flow walkthrough describes the desired end-to-end contract while stating clearly that no single package entry point implements every step. Limit: The illustration does not prove a live model observer, reviewer service, executor, or complete deployment. ## Limits - The exact-wheel test receipt does not provide pinned live-SDK end-to-end interception proof for every named framework shim. - The static website has no runtime backend, queue, secret, model call, reviewer, external executor, or integration account. - Coverage, identity validation, approval authority, downstream execution, retries, and recovery must be verified for each deployment path. - The 0.7.0 wheel contains setup helper scripts but does not contain the complete repository-hosted setup skill instructions. ## Sources - [fivedrisk 0.7.0 public release](https://pypi.org/project/fivedrisk/0.7.0/); primary-authority; fivedrisk-0.7.0-py3-none-any.whl ยท SHA-256 790edf0e09c81e89b232ab77589d6df8551a08ed93d0bef3644f5f1a4043c22c; verified 2026-10-06 - [5D action-flow walkthrough](https://5d.langoni.me/action-flow/); website-artifact; normative integration contract 2.0.0; verified 2026-10-06 - [5D setup skill source](https://github.com/theDoc001/fivedrisk/tree/5a5e991eea35e57cf18305fcdc54afa70f879941/fivedrisk-plugin/skills/fivedrisk-setup); immutable-public-source; commit 5a5e991eea35e57cf18305fcdc54afa70f879941; verified 2026-10-06 --- Illustrative website evidence only. No certification, legal conclusion, production integration, or complete coverage is represented.