type Placement

bendvy-ecs-core@0.1.0.4 · ordinary_app_schedule_description.bend:10

import Base
import bendvy-ecs-core@0.1.0.4/schedule_provision.bend as SP

10# Names derive only from the retained actual Registry namespace/id. A missing
11# binding stays None; this adapter never invents a label or condition name.
12# Detached zero-based plan placement retaining requirements and condition slot.
13# System names are joined by actual namespace/id; missing bindings remain None.
14# Phase/barrier entries remain in position order, not fabricated system metadata.
15type Placement<S:Data> is Data:
16  System{position:Nat,namespace:U32,id:U32,name:Maybe<&2,String>,condition:U32,requirements:List<&2,SP.Requirement<S>>}
17  Phase{position:Nat,name:String,requirements:List<&2,SP.Requirement<S>>}
18  Barrier{position:Nat,requirements:List<&2,SP.Requirement<S>>}