Context
From GF++ Alignment sync meeting (2026-04-09).
Problem
Die and pad-ring components that should contain other instances (pads, circuits) don't fit the current flat schematic model. The die is just another component that cannot encompass others, and connecting many ports to a large component is cumbersome.
Goal
Find a workable approach for representing die/pad-ring components in the schematic. This is an open design question requiring more research.
Ideas Discussed
- Explode into labels/pads: Flatten the die so its ports appear as individual label/pad symbols that can be wired to directly (similar to KLayout approach)
- Array wires/ports: Bus-style connections for large port arrays
- Logical net links: Connect ports by net name without physical wire routing — useful for global nets and large components
- Component locking: Lock large background components in place so smaller components can be placed on top without accidentally moving them
- Resizing: Without component resizing, visual containment is impractical
Meeting Discussion
- Sebastian: Die should contain instances, but Mosaic doesn't support this; also can't resize components
- Joaquin: KLayout approach is to explode the die into labels/pads
- Chris: Option to logically link ports without routing would simplify net definitions
- Pepijn: Exploding into labels is reasonable; array wires/ports could help; locking would help placement
Context
From GF++ Alignment sync meeting (2026-04-09).
Problem
Die and pad-ring components that should contain other instances (pads, circuits) don't fit the current flat schematic model. The die is just another component that cannot encompass others, and connecting many ports to a large component is cumbersome.
Goal
Find a workable approach for representing die/pad-ring components in the schematic. This is an open design question requiring more research.
Ideas Discussed
Meeting Discussion