A.19.SOURCE-SET-SPACE-SUBSTRATE:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Why it fails	Repair
Treating one archive or front as the search space itself	A source set is not the same kind as one declared `CharacteristicSpace`.	Keep `SourceSetFamily` and `SearchSpaceRef` separate.
Leaving `SpaceRefRelationKind` implicit	The reader then has to guess whether search and outcome share one declared space or use two distinct declared spaces.	Declare `sameDeclaredSpaceAs` or `distinctDeclaredSpaceFrom` next to the two refs.
Letting `DescriptorMapRef` stand in for the whole substrate	A representation layer is not identical to the position-typed space declaration.	State the docking rule explicitly and keep the space refs visible.
Making `SourceSetComposition` or `DerivedViewKind` mandatory in every line	The line fabricates composition or derivation where none exists.	Keep them conditional.
Publishing with bare `portfolio` language	`portfolio` blurs retained-set, selected-set, and posture talk.	Use declared source-set and outcome metadata instead.
Treating all distortion as one bridge story	Not every qualified relation is bridge-mediated.	State the active posture directly.
Letting `G.5` or `G.10` sound like the substrate itself	Publication metadata then silently replaces substrate semantics.	Keep publication as downstream use of the substrate.