Graphs of Multifamily Housing
Start with the unit
The authored object is the apartment. The building repeats it along a corridor and across levels. Keeping the unit graph distinct from its instances lets one design change propagate without making every apartment lose its individual address.
The air systems become a forest
The mechanical drawing shows repeated local systems alongside shared exhaust relationships. Repetition does not automatically produce one central equipment tree. The model has to declare which equipment belongs to a unit and which network is shared.
Power aggregates by its own rule
Unit panels join a larger electrical organization. The quantity attached to one apartment and the quantity assigned to the building need not use the same aggregation rule. The original demand illustration makes that distinction; it is not a service calculation for this post.
The riser joins the levels
A repeated bathroom is still a room on a particular floor. The plumbing riser is what connects those repeated locations. It can force alignment across levels that a collection of independent unit plans would never require.
Repetition reaches the transfer
The residential module and the structure below it can want different grids. At a transfer, the support graph stops being a simple vertical repeat. Follow the connections through that change of system while the apartment identities remain intact.
A unit is also a contract tier
The ladder keeps room, unit, level, building and site distinct. A lease can attach to a unit while circulation belongs to the building. Moving between scales should preserve those meanings, not just merge nearby shapes.
Let income follow its own objects
The original money view attaches income to apartments and shared obligations to the building. A corridor can serve many units without earning rent as another unit. The illustrative financial labels explain those relationships rather than establish current economics.
The unit has an entry edge
A shared wall between apartments is not a doorway. The corridor supplies the common approach, and the unit entry changes the character of access. Its graph identifies a connection; operation, clearances and accessibility remain geometric questions.
The corridor has to reach more than units
An exit route continues beyond the apartment door. The corridor, stairs and outside belong in that question. A connected list of units alone would miss the network that serves them, and the drawing does not establish a compliant travel path.
Draw a type, locate its instances
A unit drawing describes a repeatable arrangement. Level plans locate particular instances of it. That gives the paper graph a distribution role: the reader must find both the type and where that type occurs in this building.
One party wall carries several promises
The same boundary can separate units, support construction, restrict passage and participate in an acoustic assembly. Editing it changes more than one view. A renovation record needs to expose those separate obligations before calling the wall retained or replaced.
A transfer changes several systems together
At the podium, structure, drainage and enclosure meet a change in building organization. A local plan edit can cross that interface. Keep the existing and proposed relationships available so a stable line in plan does not conceal a changed responsibility.
A repeated type is not every instance
The source instancing diagram separates a recurring shape from the many places it appears. Evidence collected from one instance cannot silently stand for every instance. The record needs both the reusable type and the address that was actually examined.
A contact can be evidence of a conflict
Acoustic adjacency asks a different question from circulation. Rooms that should connect for access may need separation for another purpose. Keep the reason for each edge visible so a useful route does not automatically become a satisfactory shared boundary.
A ratio becomes a layout problem
Parking provision starts as a relationship to the unit count, then becomes stalls, aisles and a site. A preset needs to survive that translation. A plausible apartment total cannot establish that the parking arrangement can be placed.
Test where the repeat breaks
The strongest test is often at the exception: the transfer, corner or change of module. Repeating a typical floor confirms less about those interfaces. Keep the failed connection attached to its location so another run can answer the same question.
Review each meaning of the shared wall
An accepted boundary label should say which property was reviewed and on which version. Support, separation and acoustics require different evidence. Agreement about one meaning does not accept every other promise attached to the same wall.
Keep a changed instance in view
Move a wet room in one apartment and follow the riser relationship again. The type may still be recognizable while that instance has acquired a new coordination problem. The building becomes legible when repetition and exceptions remain visible together.
About the drawings
The building geometry remains the original plan from THE GRAPHS — COMPLETE. Plan-aligned overlays retain their original coordinates. Topics originally drawn as sections or independent diagrams use conceptual graph projections onto this fixed plan; they are not calculated installations. Original numerical annotations have not been rechecked as current design criteria. The eight earlier manuscripts and their evidence remain in the editorial corpus.