Naming the crossing
The hollow square becomes the place the contract is written.Where a connector leaves a region, §09 already draws a hollow square and calls it the place to ask what the contract is, and §13 already sends unnamed relationships to the review queue. Until now that was a rule with nothing behind it. The square is clickable: one panel, four fields, and a review-queue item a person can discharge.
Unnamed: a hollow square with a question mark, and a row in the review queue.
Risk & Compliance Scheduling
Change approved by CAB
PIVOTAL · E-012 MK
Schedule change window
COMMAND · C-013 MK
RISK & COMPLIANCE → SCHEDULING — §10’S CN-11THE SQUARE IS canvas/CrossingSquare · THE STICKIES ARE canvas/Sticky OFF THE BOARD
Crossing · contract
RISK & COMPLIANCE → SCHEDULINGIN REVIEW QUEUE
| Aggregate | Consumed by | State |
|---|---|---|
| ChangeRequest | Scheduling | AGREED |
| RiskRating | Scheduling | AGREED |
FOUR FIELDS · SIX ui/Chip, ONE ui/OrdinalChip, ONE ui/Field, ONE ui/Matrix
Fidelity: §21 prints CUSTOMER / SUPPLIER on this edge. §13’s map and §24’s CML both print [U,OHS,PL]->[D,ACL], and the model carries ohsPl — two sources against one, so the panel shows OHS / PL. INVENTORY §9 amendment 11 records the decision.
Rules
- Zero new primitives A square, the existing detail panel, ordinal chips and the matrix. The only new behaviour is that the square accepts a click.
- The queue item closes here An unnamed crossing is a review-queue row. Naming it is how the row is discharged — parking it as a question is the other legitimate answer.
- The map reads it back Pattern and right render as the solid and dotted chips on the §13 map. One edit, both views — the map is still a projection.