Global Event Template
A global event is not a temporary reward banner. It is a pressure wave in CT-03 history that asks Operators to contribute from their own sectors and then leaves a public result.
Required Structure
- Source: what planetary condition, project delay, or faction dispute created the event.
- Local participation: what an Operator can do from one sector without pretending to control the planet alone.
- Global indicator link: which public metric moves and what delay applies.
- Faction dispute: why rational groups disagree about the response.
- Outcome record: what Mission Control publishes when the event resolves.
- Residual risk: what pressure remains even after success.
Examples
A storm boundary can ask sectors to reinforce corridors and repair weather relay data. A native trace hold can ask sectors to pause soil activation and fund research. An energy shortage can ask sectors to choose between local comfort and backbone stability.
Content Rule
Every event needs a cost. Avoid writing events as festivals, pure bonuses, or moral tests with one obvious answer.
