Files
proxmox/docs/03-deployment/DBIS_COMPLIANCE_ENGINE_ALIGNMENT.md
defiQUG 7ac74f432b chore: sync docs, config schemas, scripts, and meta task alignment
- Institutional / JVMTM / reserve-provenance / GRU transport + standards JSON
- Validation and verify scripts (Blockscout labels, x402, GRU preflight, P1 local path)
- Wormhole wiring in AGENTS, MCP_SETUP, MASTER_INDEX, 04-configuration README
- Meta docs, integration gaps, live verification log, architecture updates
- CI validate-config workflow updates

Operator/LAN items, submodule working trees, and public token-aggregation edge
routes remain follow-up (see TODOS_CONSOLIDATED P1).

Made-with: Cursor
2026-03-31 22:31:39 -07:00

1.7 KiB

DBIS governance / compliance engine — alignment with HYBX sidecar

Technical baseline: hybx_compliance_routing_sidecar_technical_plan.md

Functional mapping

DBIS Digital Master Plan capability HYBX sidecar / stack analogue
Transaction validation Sidecar pre-flight validation hooks
Jurisdiction routing Routing graph + jurisdictional cheat sheets (HYBX docs)
AML/KYC enforcement Policy adapters (external screening APIs)
Sanctions screening Same; audit trail to append-only store
Reporting automation Event export to institutional reporting pipelines

Phased integration

  1. Document — API contracts between settlement paths and sidecar (sync with DBIS_HYBX_SIDECAR_BOUNDARY_MATRIX.md if present).
  2. Pilot — Read-only advisory mode (log only, no block).
  3. Enforce — Config-gated enforcement for selected corridors / asset classes.
  4. Publish — Redacted aggregate metrics via data.d-bis.org with lineage: policy or modelled as appropriate.

Web portal touchpoints

  • Public: Transparency pages link to high-level compliance principles (no PII).
  • members.d-bis.org: Institution-facing compliance attestations and simulation results.
  • developers.d-bis.org: SDK hooks and test vectors for sandbox.

Ownership

  • Product / legal: Policy interpretation and publication on policy.d-bis.org.
  • Engineering: Sidecar deployment per Proxmox/RTGS checklists.
  • Ops: Runbooks, rotation, and incident response shared with explorer/API SLOs.