proxmox/config/dbis-ecosystem-master-plan-tracker.json

{
  "schemaVersion": "1.0.0",
  "updated": "2026-04-24",
  "canonicalRootDoc": "docs/02-architecture/DBIS_ECOSYSTEM_TECHNICAL_MASTER_PLAN.md",
  "workstreams": [
    {
      "id": "W1",
      "title": "Besu / Chain 138 infrastructure and RPC topology",
      "status": "live",
      "horizon": "near_term",
      "ownerClass": "mixed",
      "dependsOn": [],
      "sourceDocs": [
        "docs/06-besu/BESU_NODE_CONFIGURATION_MAP_20260424.md",
        "dbis_chain_138_technical_master_plan.md",
        "docs/03-deployment/PROXMOX_VE_OPERATIONAL_DEPLOYMENT_TEMPLATE.md"
      ],
      "acceptanceGate": "Canonical Besu inventory reconciled across all active cluster hosts, block production healthy, and no unexplained canonical node gaps remain.",
      "evidenceArtifact": "scripts/verify/check-cluster-besu-inventory.sh --json"
    },
    {
      "id": "W2",
      "title": "Liquidity, PMM, bridge, and public routing coverage",
      "status": "partially live",
      "horizon": "near_term",
      "ownerClass": "mixed",
      "dependsOn": [
        "W1"
      ],
      "sourceDocs": [
        "docs/11-references/DEPLOYER_TO_PUBLIC_STABLECOIN_ROUTES.md",
        "docs/11-references/DEPLOYED_TOKENS_BRIDGES_LPS_AND_ROUTING_STATUS.md",
        "reports/status/LIVE_ECOSYSTEM_FINANCIAL_INVENTORY_AND_ROUTING_GAPS_20260424.md"
      ],
      "acceptanceGate": "Machine-readable route coverage is current and can distinguish live, partial, and blocked routing paths for stablecoins and top assets.",
      "evidenceArtifact": "config/public-routing-coverage-matrix.json"
    },
    {
      "id": "W3",
      "title": "Phoenix deploy/control-plane integration",
      "status": "partially live",
      "horizon": "near_term",
      "ownerClass": "mixed",
      "dependsOn": [
        "W1",
        "W2",
        "W4"
      ],
      "sourceDocs": [
        "docs/04-configuration/PHOENIX_SANKOFA_OPERATOR_HANDOFF.md",
        "docs/02-architecture/DBIS_ECOSYSTEM_TECHNICAL_MASTER_PLAN.md"
      ],
      "acceptanceGate": "Phoenix deploy/control APIs expose current canonical manifests and validated deploy targets without drifting from repo truth.",
      "evidenceArtifact": "scripts/validation/validate-config-files.sh"
    },
    {
      "id": "W4",
      "title": "URA manifest, policy profiles, registry, and route confidence",
      "status": "repo-implemented",
      "horizon": "near_term",
      "ownerClass": "repo",
      "dependsOn": [
        "W2",
        "W3"
      ],
      "sourceDocs": [
        "docs/04-configuration/universal-resource-activation/URA_MANIFEST_AUTOMATION_IMPLEMENTATION_TRACKER.md",
        "docs/04-configuration/universal-resource-activation/README.md",
        "config/universal-resource-activation/manifest.json"
      ],
      "acceptanceGate": "URA manifest and policy profiles validate, registry references are coherent, and route-confidence can be produced as a first-class control-plane artifact.",
      "evidenceArtifact": "scripts/validate/validate-universal-resource-activation.mjs"
    },
    {
      "id": "W5",
      "title": "DBIS RTGS / DBIS Rail / OMNL / settlement sidecars",
      "status": "partially live",
      "horizon": "near_term",
      "ownerClass": "mixed",
      "dependsOn": [
        "W4",
        "W6"
      ],
      "sourceDocs": [
        "docs/03-deployment/DBIS_RTGS_MASTER_PLAN_IMPLEMENTATION_TRACKER.md",
        "docs/dbis-rail/DBIS_RAIL_SETTLEMENT_EVENT_SOURCES.md",
        "docs/03-deployment/DBIS_RTGS_FIRST_SLICE_ARCHITECTURE.md"
      ],
      "acceptanceGate": "First-slice settlement boundaries, event sources, custody roles, and sidecar responsibilities are explicit enough for production gating.",
      "evidenceArtifact": "docs/03-deployment/DBIS_RTGS_MASTER_PLAN_IMPLEMENTATION_TRACKER.md"
    },
    {
      "id": "W6",
      "title": "Jurisdiction/compliance and onboarding matrices",
      "status": "repo-implemented",
      "horizon": "near_term",
      "ownerClass": "repo",
      "dependsOn": [
        "W4"
      ],
      "sourceDocs": [
        "docs/04-configuration/compliance-matrices/README.md",
        "docs/04-configuration/jurisdictions/JURISDICTION_CATALOG.md",
        "docs/dbis-rail/DBIS_RAIL_JURISDICTION_TRACEABILITY.md"
      ],
      "acceptanceGate": "Jurisdiction and onboarding matrices are machine-readable enough to gate policy profiles and institutional activation paths.",
      "evidenceArtifact": "config/jurisdictions/catalog.v1.json"
    },
    {
      "id": "W7",
      "title": "Identity / Hyperledger / interoperability stack",
      "status": "planned",
      "horizon": "long_term",
      "ownerClass": "external",
      "dependsOn": [
        "W5",
        "W6"
      ],
      "sourceDocs": [
        "docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md",
        "docs/03-deployment/DBIS_HYPERLEDGER_IDENTITY_STACK_DECISION.md"
      ],
      "acceptanceGate": "Identity and interoperability slices have explicit runtime ownership, promotion gates, and environment-specific deployment decisions.",
      "evidenceArtifact": "docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md"
    },
    {
      "id": "W8",
      "title": "Observability, verification, evidence, and operator readiness",
      "status": "live",
      "horizon": "near_term",
      "ownerClass": "mixed",
      "dependsOn": [
        "W1",
        "W2",
        "W3",
        "W4",
        "W5",
        "W6"
      ],
      "sourceDocs": [
        "docs/00-meta/OPERATOR_HANDOFF_2026_04_24.md",
        "docs/00-meta/OPERATOR_READY_CHECKLIST.md",
        "docs/04-configuration/universal-resource-activation/URA_OPERATIONAL_READINESS_CHECKLIST.md"
      ],
      "acceptanceGate": "Validation, health, and operator readiness outputs are current enough to act as production gates rather than ad hoc references.",
      "evidenceArtifact": "scripts/verify/run-all-validation.sh"
    }
  ],
  "blockedBy": [
    {
      "id": "B1",
      "class": "external",
      "description": "Some institutional integrations, custody counterparties, and settlement-sidecar dependencies cannot be closed from repo-only work."
    },
    {
      "id": "B2",
      "class": "external",
      "description": "Some public-network expansion lanes remain constrained by third-party bridge, exchange, or destination-liquidity realities."
    },
    {
      "id": "B3",
      "class": "operator",
      "description": "Operator promotion of URA, sidecar, and policy-aware runtime slices still trails repo implementation in several areas."
    }
  ]
}