2.2 KiB
2.2 KiB
E4.M4 — SecurityTierZoneFlags
Summary
| Field | Value |
|---|---|
| Module ID | E4.M4 |
| Epic | Epic 4 — World Topology |
| Stage target | Prototype |
| Status | Planned (see dependency register) |
Purpose
Layer on top of the zone graph that tags each zone with security tier (e.g. high / low / contested) and exposes server-authoritative policy state and entry-warning payloads. Enables PvP eligibility (E6.M1) and risk UX without circular dependencies: Epic 6 consumes this data; E4.M4 does not depend on Epic 6.
Responsibilities
- Assign and persist
SecurityTierper zone (from data on E4.M1). - Publish
ZonePolicyStatefor server and client display alignment. - Emit or serve
ZoneEntryWarningwhen players transition into higher-risk zones.
Key contracts
| Contract | Role |
|---|---|
SecurityTier |
Discrete tier driving PvP and risk rules. |
ZonePolicyState |
Authoritative flags for what is allowed in-zone. |
ZoneEntryWarning |
Structured warning for consent flows and UI copy. |
Module dependencies
- E4.M1 — ZoneGraphAndTravelRules:
ZoneDef, edges, and travel context for tier attachment.
Dependents (by design)
- E6.M1 — PvPEligibilityAndFlagState: who may engage in PvP where.
- E6.M2 — ConsentAndRiskUxSignals: risk UI from tier and warnings.
Related implementation slices
See Epic 4 Slice 2 — Security tier tagging and UI hooks: server and client agree on tier at transitions; entry-warning contract stable for Epic 6; telemetry security_zone_enter, security_zone_exit aligned with PvP events.
Risks and telemetry
- Client/server mismatch: server is source of truth; client prediction display-only.
- Coordinate with Epic 6 prototype gates for optionality and clarity.
Source anchors
- Master plan:
neon_sprawl_vision.plan.md— Core Epic Map, Epic 4. - Module dependency register