speckle-impl-federation
Installation
SKILL.md
speckle-impl-federation
Quick Reference
Federation Architecture
| Concept | Description | Key Constraint |
|---|---|---|
| Federated View | Multiple models from different tools loaded into one Speckle project | Each model retains its source hierarchy |
| applicationId | Stable cross-version identifier from the source application | NEVER use content-based id for tracking — it changes on every data update |
| displayValue | Interoperable geometry primitives (Mesh, Line, Point) | ALWAYS the universal fallback — Brep only for Rhino-capable receivers |
| Proxy | Relationship container linking objects to shared resources | Proxies reference objects by applicationId, NEVER by id |
| Asymmetric Fidelity | Publishing preserves MORE data than loading can reconstruct | ALWAYS plan for information loss on the receiving side |
| Collections | Hierarchical containers preserving source application structure | Each connector writes its own hierarchy pattern |
Fidelity Loss Matrix
This matrix defines EXACTLY what happens when data moves between tool pairs. Every cell describes the receiving outcome.