diff --git a/dbis_chain_138_technical_master_plan.md b/dbis_chain_138_technical_master_plan.md index 7f9f595..b1726e7 100644 --- a/dbis_chain_138_technical_master_plan.md +++ b/dbis_chain_138_technical_master_plan.md @@ -36,13 +36,13 @@ The objective is to move from architecture theory to a production-grade sovereig - Hyperledger FireFly: - primary `6200` is restored as a minimal local FireFly API footprint - - secondary `6201` is present as a stopped container but currently behaves like standby / incomplete deployment + - secondary `6201` is present in inventory but currently behaves like a retired / standby shell with no valid deployment payload - Hyperledger Fabric: - `6000`, `6001`, `6002` are present and running at the CT layer - - current app-level verification does not yet show active Fabric peer / orderer workloads inside those CTs + - current app-level verification does not show active Fabric peer / orderer workloads or meaningful Fabric payloads inside those CTs - Hyperledger Indy: - `6400`, `6401`, `6402` are present and running at the CT layer - - current app-level verification does not yet show active Indy node listeners on the expected ports + - current app-level verification does not show active Indy node listeners or meaningful Indy payloads inside those CTs ## Planned / aspirational @@ -430,9 +430,9 @@ Separate security compliance and benchmark reports remain future deliverables un ## Infrastructure gaps -- FireFly secondary `6201` is currently stopped and should be treated as standby / incomplete until intentionally reactivated. -- Fabric CTs are present, but current app-level verification does not yet prove active Fabric peer or orderer services. -- Indy CTs are present, but current app-level verification does not yet prove active Indy validator listeners. +- FireFly secondary `6201` is currently stopped and should be treated as retired / standby until intentionally rebuilt. +- Fabric CTs are present, but current app-level verification does not prove active Fabric peer or orderer services and does not show meaningful Fabric payloads. +- Indy CTs are present, but current app-level verification does not prove active Indy validator listeners and does not show meaningful Indy payloads. - The current per-node app-level evidence table is maintained in [docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md](docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md). ## Platform gaps diff --git a/docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md b/docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md index 09e1482..73d8dcd 100644 --- a/docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md +++ b/docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md @@ -23,13 +23,13 @@ The checks were based on: | VMID | Service family | CT status | App-level status | Listening ports / probe | Notes | |------|----------------|-----------|------------------|--------------------------|-------| | `6200` | FireFly primary | Running | Healthy minimal local gateway | `5000/tcp` FireFly API, `5432/tcp` Postgres, `5001/tcp` IPFS | `firefly-core` restored on `ghcr.io/hyperledger/firefly:v1.2.0`; `GET /api/v1/status` returned `200`; Postgres `pg_isready` passed; IPFS version probe passed | -| `6201` | FireFly secondary | Stopped | Standby / incomplete | None verified | CT exists but rootfs is effectively empty and no valid FireFly deployment footprint was found; do not treat as active secondary | -| `6000` | Fabric primary | Running | Unproven | No Fabric listener verified | CT runs, but current app-level checks did not show active peer/orderer processes or expected listeners such as `7050` / `7051` | -| `6001` | Fabric secondary | Running | Unproven | No Fabric listener verified | Same current state as `6000` | -| `6002` | Fabric tertiary | Running | Unproven | No Fabric listener verified | Same current state as `6000` | -| `6400` | Indy primary | Running | Unproven | No Indy listener verified | CT runs, but current checks did not show Indy node listeners on expected ports such as `9701`-`9708` | -| `6401` | Indy secondary | Running | Unproven | No Indy listener verified | Same current state as `6400` | -| `6402` | Indy tertiary | Running | Unproven | No Indy listener verified | Same current state as `6400` | +| `6201` | FireFly secondary | Stopped | Formally retired until rebuilt | None verified | CT exists in inventory, but the rootfs is effectively empty and no valid FireFly deployment footprint was found. Treat this as retired / standby metadata only until it is intentionally rebuilt as a real secondary node. | +| `6000` | Fabric primary | Running | CT footprint only | No Fabric listener verified | CT is up, but app-native checks found no active Fabric peer/orderer/couchdb processes, no expected listeners such as `7050` / `7051`, and no meaningful Fabric payload under `/opt`, `/etc`, or `/var`. | +| `6001` | Fabric secondary | Running | CT footprint only | No Fabric listener verified | Same current state as `6000`: container present, no proven Fabric application payload or listeners. | +| `6002` | Fabric tertiary | Running | CT footprint only | No Fabric listener verified | Same current state as `6000`: container present, no proven Fabric application payload or listeners. | +| `6400` | Indy primary | Running | CT footprint only | No Indy listener verified | CT is up, but app-native checks found no active Indy-related processes, no expected listeners such as `9701`-`9708`, and no meaningful Indy payload under `/opt`, `/etc`, or `/var`. | +| `6401` | Indy secondary | Running | CT footprint only | No Indy listener verified | Same current state as `6400`: container present, no proven Indy application payload or listeners. | +| `6402` | Indy tertiary | Running | CT footprint only | No Indy listener verified | Same current state as `6400`: container present, no proven Indy application payload or listeners. | ## Interpretation @@ -37,22 +37,24 @@ The checks were based on: - FireFly primary (`6200`) is restored enough to provide a working local FireFly API backed by Postgres and IPFS. -### Present but not currently proved as active application workloads +### Present only as container footprints right now - Fabric CTs (`6000`-`6002`) - Indy CTs (`6400`-`6402`) -These should be described as container footprints under validation, not as fully verified production application nodes, until app-level services and expected listeners are confirmed. +These should be described as container footprints only, not as active Fabric or Indy application nodes. Current app-native validation found no meaningful service payload, processes, or expected listeners inside those CTs. ### Not currently active -- FireFly secondary (`6201`) should be treated as standby or incomplete deployment state unless it is intentionally rebuilt and verified. +- FireFly secondary (`6201`) should be treated as formally retired / standby metadata unless it is intentionally rebuilt and verified. ## Operational follow-up 1. Keep `6200` under observation and preserve its working config/image path. -2. Do not force `6201` online unless its intended role and deployment assets are re-established. -3. For Fabric and Indy, the next verification step is app-native validation, not more CT-level checks. +2. Do not force `6201` online unless its intended role and deployment assets are re-established from scratch. +3. For Fabric and Indy, the next step is no longer generic validation. It is either: + - deploy real app payloads and verify them, or + - formally reclassify these CTs as reserved placeholders rather than active DLT workloads. 4. Any governance or architecture document should distinguish: - `deployed and app-healthy` - `container present only` diff --git a/docs/03-deployment/DBIS_PHASES_1_TO_3_PRODUCTION_GATE.md b/docs/03-deployment/DBIS_PHASES_1_TO_3_PRODUCTION_GATE.md index 96abd15..749acbb 100644 --- a/docs/03-deployment/DBIS_PHASES_1_TO_3_PRODUCTION_GATE.md +++ b/docs/03-deployment/DBIS_PHASES_1_TO_3_PRODUCTION_GATE.md @@ -21,7 +21,7 @@ ### What is not yet proven production-ready -- FireFly secondary failover footprint (`6201`) +- FireFly secondary failover footprint (`6201`) is not deployed; it is currently retired / standby until rebuilt - Fabric peer / orderer workload health inside `6000-6002` - Indy validator / node listener health inside `6400-6402` - Sovereignized Phase 2 platform baseline: @@ -71,8 +71,8 @@ | Automated liveness wrapper exists | Complete | [scripts/verify/run-dbis-phase3-e2e-simulation.sh](../../scripts/verify/run-dbis-phase3-e2e-simulation.sh) | | Besu liveness passes | Complete | direct script output and [scripts/verify/check-chain138-rpc-health.sh](../../scripts/verify/check-chain138-rpc-health.sh) | | FireFly HTTP liveness passes | Complete | `6200` returns `HTTP 200` on `/api/v1/status` | -| Fabric app-native business flow validation passes | Blocked | CTs are present, but app-level workloads are not yet proven | -| Indy app-native business flow validation passes | Blocked | CTs are present, but app-level listeners are not yet proven | +| Fabric app-native business flow validation passes | Blocked | CTs are present, but current checks found no active Fabric payload, processes, or listeners | +| Indy app-native business flow validation passes | Blocked | CTs are present, but current checks found no active Indy payload, processes, or listeners | | Cross-chain / Cacti business flow validation passes | Blocked | not currently proven as deployed live DBIS path | | Full business E2E has been demonstrated | Blocked | current wrapper is intentionally liveness-only | @@ -84,9 +84,9 @@ The following items still prevent a full “DBIS Chain 138 production complete” declaration: -1. `6201` is not a verified active secondary FireFly node. -2. Fabric `6000-6002` are not yet proven as active peer/orderer workloads. -3. Indy `6400-6402` are not yet proven as active validator workloads. +1. `6201` is not a verified active secondary FireFly node and is currently treated as retired / standby until rebuilt. +2. Fabric `6000-6002` are not yet proven as active peer/orderer workloads; current evidence shows CT footprints only. +3. Indy `6400-6402` are not yet proven as active validator workloads; current evidence shows CT footprints only. 4. Phase 2 sovereignization is still roadmap work, not completed platform state. 5. The current Phase 3 wrapper is liveness validation, not end-to-end business certification. @@ -106,9 +106,9 @@ It is **not** yet accurate to declare: ## Next production-closing actions -1. Decide whether `6201` is to be rebuilt as a real secondary FireFly node or formally retired. -2. Perform app-native Fabric validation inside `6000-6002`. -3. Perform app-native Indy validation inside `6400-6402`. +1. Decide whether `6201` is to be rebuilt as a real secondary FireFly node or left retired as a reserve inventory slot. +2. Either deploy real Fabric workloads inside `6000-6002` and validate them, or reclassify those CTs as placeholders. +3. Either deploy real Indy workloads inside `6400-6402` and validate them, or reclassify those CTs as placeholders. 4. Execute the first real Phase 2 platform milestone: - fleet expansion, or - Ceph pilot, or