SHA-256 digest over the canonical JSON of every other field.
Built environment this schedule was derived from.
What this schedule does not state, sorted by gap subject.
Every schedule carries the subject's fixed scope gap, such as opening-performance, and adds a <subject>-geometry gap when some rows are unmeasured.
Versioned schedule protocol.
Rows ordered by kind, model, width, height (unmeasured first) and basis, with each kind's rows marked <kind>-01, <kind>-02 and so on in that order.
Which family of design records is scheduled.
Number of records of subject the design declares; the row counts sum to exactly this.
Schedule format.
A schedule: one design's spaces, openings or connectors counted instead of drawn.
It is derived from the same validated graph as a drawing, but counts the complete selected subject population while a drawing applies its view's space and element-kind filters. total is the number of subject records in the design, and the row counts sum to it; this identity does not equate a filtered sheet's visible population with the whole-design schedule.
Openings and connectors are grouped into type rows, and each row names a bounded sample of its members with the remainder counted, so a schedule over a tower is the size of its type list. A
spaceschedule lists every space as its own row, because two rooms of one kind and size are still two places to visit.