How rishivadrevu01/microsoft_frabic works
Fabric Capacity Planning Lab is a synthetic-data capacity-planning application. A planner reviews supply and demand across 3-, 6- and 12-month horizons, investigates pool assessments and recommendations, then records an approval; later, the lab can advance time to compare outcomes with the plan. The browser obtains results through the HTTP API, while the server’s assessment engine combines forecasts and independent planning funnels into pool verdicts. The README documents additional request, action-queue, ontology, scenario-lab and outcome capabilities. Some subsystem links rely on README descriptions or SOURCE INDEX references because their source was not excerpted.
Main entry points: server/app.js HTTP Router · store.js Working State · verdict.js Pool Verdict · app/app.js Planning Interface
Components 22
Planner Experience
- Planning Interface
web/app/app.js - World Map
web/app/worldmap.js
HTTP API
- HTTP Router
server/app.js - Capacity Overview
server/lib/overview.js - Supply-Demand Plan
server/lib/planning.js - Request Assessment
server/lib/requester.js
Planning Engine
- Pool Context
server/lib/context.js - Demand Forecast
server/lib/forecast.js - Planning Funnels
server/lib/funnels.js - Pool Verdict
server/lib/verdict.js
Lab State and Decisions
- Validated Dataset
server/lib/data.js - Working State
server/lib/store.js - Request Handling
server/lib/requests.js - Approval Decisions
server/lib/decisions.js - Approval Rules
server/lib/approval.js
Additional Capabilities
- Plan Outcomes
server/lib/outcome.js - Guided Lab
server/lib/lab.js - What-if Scenarios
server/lib/scenarios.js - Capacity Ontology
server/lib/ontology.js - Peak-hour Check
server/lib/peak.js - Hourly Corpus
ml/lib/corpus.js
Other components
- Planner
Connections 24
- Planner → Planning Interface: uses
- Planning Interface → HTTP Router: requests results
- HTTP Router → Capacity Overview: routes overview
server/app.js - HTTP Router → Supply-Demand Plan: routes planning
server/app.js - HTTP Router → Request Assessment: routes requests
server/app.js - HTTP Router → Working State: reads and updates
server/app.js - Working State → Validated Dataset: loads data
server/lib/store.js - Capacity Overview → Pool Verdict: summarizes assessments
server/lib/overview.js - Supply-Demand Plan → Capacity Overview: reuses assessments
server/lib/planning.js - Request Assessment → Request Handling: assesses requests
server/lib/requester.js - Pool Context → Demand Forecast: forecasts demand
server/lib/context.js - Pool Context → Planning Funnels: provides pool context
server/lib/verdict.js - Pool Verdict → Planning Funnels: composes proposals
server/lib/verdict.js - Working State → Pool Verdict: builds assessments
server/lib/store.js - HTTP Router → Approval Decisions: routes decisions
server/app.js - Approval Decisions → Approval Rules: checks approval
server/lib/decisions.js - HTTP Router → Plan Outcomes: routes outcomes
server/app.js - HTTP Router → Guided Lab: routes lab actions
server/app.js - Working State → What-if Scenarios: applies scenarios
server/lib/store.js - HTTP Router → Capacity Ontology: routes ontology
server/app.js - HTTP Router → Peak-hour Check: routes peak check
server/app.js - Peak-hour Check → Pool Verdict: replans pools
server/lib/peak.js - Hourly Corpus → Peak-hour Check: supports profile
- Planning Interface → World Map: renders map