Plan Architecture¶
Scope¶
Plan mode supports schedule and charging simulations with a migration path from legacy multi-service orchestration to digital twin centered orchestration.
Dual Architecture¶
flowchart TB
Flag[Feature flag: plan-digital-twin-migration]
Flag -->|OFF| Legacy[Legacy path]
Flag -->|ON| Twin[Digital twin path]
Legacy --> UI1[bf-bnl-ui]
UI1 --> Settings[bf-bnl-settings]
Settings --> Compute[bf-bnl-schedule-analysis-compute]
Compute --> Route[bf-route-modelling]
UI1 --> Creator1[bf-schedule-creator]
Settings --> DDB1[(aws dynamodb)]
Settings --> S31[(aws s3)]
Compute --> S31
Creator1 --> S31
Twin --> UI2[bf-bnl-ui]
UI2 --> DT[bf-digital-twin]
DT --> Creator2[bf-schedule-creator]
DT --> S32[(aws s3)]
DT --> DDB2[(aws dynamodb)]
Creator2 --> S32
DT -. integration .-> Core[bf-manage-core]Why this matters in bf-dev¶
- Same local harness must support both migration states
- Service startup must include legacy and target services for compatibility
- Documentation must keep endpoint routing behavior explicit for debugging