Mining // SAGE Editor Suite

AUTHORITY BOUNDARY

A lens, not another balance file

Configuration values are composed from current leaf SoT and exhaustively checked against the real converter. Scenario outputs use only the selected configuration and explicit inputs below. Runtime transactions, live balances, Character/crew modifiers, eligibility, and settlement remain Programs authority.

Open machine-readable lineage →

0001 // COVERAGE

What SES can see now

Loading generated source snapshot…

0002 // CONFIGURATION INPUT

Ship configuration envelope

Select an active authored configuration and compare its converter-parity composition with the ship leaf's base Mining stats.

Ship Configuration

SELECTED THROUGHPUT GROUPS

CURRENT PROGRAM FORMULA

fleet mining rate×body richness×1 ÷ selected resources×runtime modifiers

The current Programs path splits effort across up to eight selected resources, then applies runtime modifiers and clips the tick to Food, Ammo, and cargo capacity. Current Fleet::mining_rate has no hardness input.

Selected-config nominal full-cargo time

—

Richness 1, one selected resource, storage cost 1, empty cargo, and no consumable/runtime clipping. Use the scenario workbench for explicit constraints.

0003 // BOUNDED ESTIMATE

Mining scenario workbench

Every editable field is an assumption—not live state. A blank Food or Ammo balance excludes that consumable's runway; Food cargo-volume outflow remains source-derivable.

Ship Config LiteEdit component selections and authored configurations → Ship StatsInspect unified ship-stat display → SAGE Map EditorEdit body resources, richness, and regions → Research NodesEdit Mining progression and requirements → Uber ExportInspect the human/downstream aggregate →

0004 // CONFIG EFFECTS

What configurations can change

One row per component group, with every exercised mining or throughput effect consolidated below it. Empty or neutral attributes are excluded.

Direct yield Direct consumption Indirect throughput

Confirmed design behavior: Heat and Shockwave weapon groups intentionally modify mining yield and/or mining Ammo consumption through the shared component composition path.

Component group	Consolidated effects	Authored configs	Pipeline

0005 // WHERE + WHAT

Resources and authored locations

Catalog tier/planet metadata is joined to body resource richness from Map Editor data. Region gates are shown as authored metadata—not claimed enforcement.

Search Tier

Resource	Tier	Authored planet types	Map coverage	Richness	Allowed region tier sets

0006 // TESTABLE FLOWS

Mining user journeys

A journey can be important without being an editable balance value. This matrix separates derivable inputs from live-runtime actions and real gaps.

0007 // DATA ROUTE

Source → aggregate → converter → runtime

Every row names its authority. “Present in Uber” is not the same thing as “consumed by the converter.”