OmniBOSS simulation studio, input kit v1

1. Choose a starter scenario JSON and load it in the studio.
2. Replace the working assumptions in Configure model, or edit the JSON.
3. Save the scenario before changing it. Export the run to keep both inputs and results.

These files do not describe verified networks. Souillac VCA population is from
Statistics Mauritius Census 2022, amended Volume III G1, PDF page 15: 4,941
resident people. Other study areas use 10,000 assumed people. National ITU
2024 mobile traffic is a benchmark, not measured local traffic. Source URLs,
locators and vintages are retained in each location record. The shared default
inventory is deliberately not scaled when traffic changes. Some country
benchmarks will overload this assumed inventory; this is not a country ranking.

TRAFFIC
traffic-template.csv has hour,a_mbps,b_mbps,c_mbps. Supply all 24 rows in order,
from hour 0 through hour 46, in two-hour steps. Values are mean offered Mbps
per demand group during that interval. They must not be merely carried traffic
when unmet demand exists. Zero is a measured zero; leave unknown cells blank
and resolve them before import. Blank cells are rejected. The example is invented.
Load the CSV in Configure model > Demand & behaviour. This enables direct input.

INVENTORY
The first schema has three representative resource groups, with 300 Mbps RAN
and 600 Mbps backhaul each by default. It is not nine surveyed sites or the
whole of any district. Each group owns a co-located RAN host and transport
route. Coordinates are retained but do not change the schematic or establish
coverage. A multi-site GIS network needs a larger topology/solver before use.
Capacity is stored in 10-Mbps blocks. Power is kW, electricity is USD/kWh,
transport commitment is USD/hour. All prices use one constant-USD basis.

PERMISSIONS
eligibility[origin][host] controls RAN access. reachability[host][route]
controls transport connectivity. True asserts permission and technical reach.
Unexpected access outages can remove a host's uplinks. It is not RF modelling.

EVENTS
Site is indexed 0,1,2. Start and duration are hours in two-hour steps within
48 hours. Planned events enter the scheduler's full-horizon forecast.
Power events use the configured backup endurance. An exhausted or absent
backup removes both RAN and its co-located route. Continuous/overlapping
outages share one allowance; grid return resets it. No fuel or battery dispatch.

VALIDATION
scenario.schema.json checks the shape. The API also checks that shares sum
to 1, active power is not below sleep, events fit the horizon, all numbers are
finite and bounds hold. Unknown metadata does not automatically become a model
input. Keep source notes for new observations. Operator-supplied is not a claim
of independent verification. This kernel is deterministic, not a tested LLM.
